Hello,
Is there anyone out there that is using the Redis 2.0 extension that has figured out a way to get around the constraint of having to supply the password from the redis.conf file into the extension during the setup? We're running into a scenario where in the event that the whole Cloud environment is upgraded, the password in the redis.conf changes which means we lose metrics until we update the Redis 2.0 extension with the new password. This “default password” only authentication approach for Redis 2.0 is not usable by Dynatrace because it is dynamically generated for each Redis server being created and deployed meaning there is no way to predict nor control its value.
It would be best if Dynatrace was able to pull/extract this dynamic password from the redis.conf file but that doesn't seem to be the case. Another thought or question here is if Dynatrace supports the new “ACL” security for Redis 6.0 and later. This ACL process allows us to create a global username and password that Dynatrace can use to log into any Redis server.
For reference this is the extension: https://www.dynatrace.com/hub/detail/redis-20/
Hope that makes sense. Look forward to hearing what others think.
Thanks,
Steven
