When running the redis_sentinel integration to monitor a group of Redis Sentinel servers, the check fails with the following error:
2024-05-24 22:57:33 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:131 in LogMessage) | redis_sentinel:e8118be2e61e206d | (redis_sentinel.py:42) | Error collecting metrics for master myprimary: AUTH <password> called without any password configured for the default user. Are you sure your configuration is correct?
Configure the redis_sentinel check similar to above and restart agent
Observe error upon check execution
Describe the results you received:
Received an AUTH error during check execution
Describe the results you expected:
For the check execution to complete successfully
Additional information you deem important (e.g. issue happens only occasionally):
I was able to fix this in the redis_sentinel.py by passing a username of "default" when initializing the redis connection with redis.StrictRedis, e.g. -
So I believe this is related to the implementation of ACLs after Redis version 5. According to this doc, you can configure Redis to function the same as it did prior to the change, but I haven't been successful in getting any configuration changes on Redis side to work.
Happy to accept this is an issue I need to resolve in my Redis configuration, but in case others run into this, I figured it would be helpful to have a record either way.
Output of the info page
When running the redis_sentinel integration to monitor a group of Redis Sentinel servers, the check fails with the following error:
This is my conf.yaml:
Additional environment details (Operating System, Cloud provider, etc):
redis:latest
&redis:6.2.6
datadog/agent:7
Steps to reproduce the issue:
datadog-agent integration install -t datadog-redis_sentinel==1.1.0
(or 1.1.1) in agent containerDescribe the results you received: Received an AUTH error during check execution
Describe the results you expected: For the check execution to complete successfully
Additional information you deem important (e.g. issue happens only occasionally): I was able to fix this in the
redis_sentinel.py
by passing a username of "default" when initializing the redis connection withredis.StrictRedis
, e.g. -So I believe this is related to the implementation of ACLs after Redis version 5. According to this doc, you can configure Redis to function the same as it did prior to the change, but I haven't been successful in getting any configuration changes on Redis side to work.
Happy to accept this is an issue I need to resolve in my Redis configuration, but in case others run into this, I figured it would be helpful to have a record either way.
Thanks!