Stop write warning in redisb if no keys configuration
See original GitHub issueHi!
redisdb integration supports keys
configuration setting to collect length of Redis keys.
But if I am not interested in this functionality – my check becomes WARNING
state because of this https://github.com/DataDog/integrations-core/blob/master/redisdb/datadog_checks/redisdb/redisdb.py#L248.
My redisdb check shouldn’t become WARNING if don’t use keys
.
See https://github.com/DataDog/integrations-core/commit/bb4e550980d803228b5468455260ad9bf0cbfb28, previously there was guard if
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
how to suppress all warning · Issue #1705 - GitHub
Hi! What's the error message? no error, but the warning can't be suppressed. All reactions.
Read more >Suppress code analysis warnings - .NET - Microsoft Learn
You can disable a rule that's causing a warning by setting its severity to none in an EditorConfig or AnalyzerConfig configuration file.
Read more >How to disable Python warnings? - Stack Overflow
Look at the Temporarily Suppressing Warnings section of the Python docs: If you are using code that you know will raise a warning,...
Read more >How To Manage Redis Databases and Keys - DigitalOcean
To delete one or more keys of any data type, use the del command followed by one or more keys that you want...
Read more >Disable all warnings. | Apple Developer Forums
hi, I want to know how to remove/disable all errors on Xcode while am writing a code, as am practicing for an exam...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the same issue on
v6.14.0
I confim that bumping tov6.15.1
fixed it. Thanks!Thanks everyone!