-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Add support for filtering traces for certain commands #3519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Jason Parraga <sovietaced@gmail.com>
Signed-off-by: Jason Parraga <sovietaced@gmail.com>
Hello @Sovietaced and thank you for your contribution. Maybe @vmihailenco can take a look at this. If he doesn't I will around the end of the month. |
@Sovietaced I can see we have #3481 opened as well, I personally prefer the filtering approach in this PR, but let's discuss with @vmihailenco. @htemelski-redis feel free to decide which one you prefer when you are back from vacation. |
I also do like this approach. My only concern is the introduction of the A better approach, in my opinion, would be to rename it to |
Ultimately it is up to you all so I'm fine with updating the pull request with whatever decision you make. My preference is to provide safe defaults that don't cause security incidents since many folks will not spend time customizing these things. |
Signed-off-by: Jason Parraga <sovietaced@gmail.com>
I do agree with @Sovietaced that we would like to hide the hello and acl commands by default. This may be considered a bugfix, not a breaking change. cc @htemelski-redis |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving this, will merge it instead of the alternative.
* Add support for filtering commands when tracing Signed-off-by: Jason Parraga <sovietaced@gmail.com> * Filter sensitive data by default Signed-off-by: Jason Parraga <sovietaced@gmail.com> * Address comments Signed-off-by: Jason Parraga <sovietaced@gmail.com> --------- Signed-off-by: Jason Parraga <sovietaced@gmail.com> Co-authored-by: Nedyalko Dyakov <1547186+ndyakov@users.noreply.github.com>
Closes #3516
redisotel
can generate traces for Redis commands that include sensitive data (ie. hello command). There currently exists an option to disable thedb.statement
attribute in traces but this is a global setting.This pull request adds support for a configurable command filter that will omit traces for commands that filter returns true for. It also adds a basic command filter to filter out sensitive data by default which I feel like should be the correct behavior to prevent security incidents.