You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem
Attempts to fetch the extra config metrics for a Redis instance fail on cloud managed Redis instances - on at least AWS Elasticache and GCP Memorystore.
(This doesn't stop anything else, as the exporter continues onto the next ste of metrics).
What version of redis_exporter are you running?
1.59.0
Running the exporter
N/A (using the Docker image).
Expected behavior
Redis Exporter has a way to disable fetching the config metrics.
e.g. maybe a new environment variable to disable fetching these, so that we don't issue a command that will never succeed (and avoid these error messages when debug level logging is enabled).
Screenshots
N/A
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I like the idea of adding a flag to skip calling the CONFIG command, I think that makes sense. Alas, I don't have the bandwidth right now to add the feature myself.
Feel free to open a PR, happy to review it.
Describe the problem
Attempts to fetch the extra config metrics for a Redis instance fail on cloud managed Redis instances - on at least AWS Elasticache and GCP Memorystore.
CONFIG
is not an allowed command on most cloud managed Redis:(This doesn't stop anything else, as the exporter continues onto the next ste of metrics).
What version of redis_exporter are you running?
1.59.0
Running the exporter
N/A (using the Docker image).
Expected behavior
Redis Exporter has a way to disable fetching the config metrics.
e.g. maybe a new environment variable to disable fetching these, so that we don't issue a command that will never succeed (and avoid these error messages when debug level logging is enabled).
Screenshots
N/A
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: