We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
We are seeing this alert after deploying multiple Redis clusters in different namespaces. AFAICT Redis itself does not consider this setup a problem.
Does the alert not take this scenario into account, or are we mistaken in thinking we do not have a real problem?
Shouldn't the query be
count(redis_instance_info{role="master"}) by (namespace) > 1 or something similar that takes this scenario into account?
https://github.com/samber/awesome-prometheus-alerts/blame/826be5877ffc129ca3511cd25af87d67ea67fb48/_data/rules.yml#L795
The text was updated successfully, but these errors were encountered:
Hi @exolab and thanks for the report.
Do you have a better label than "namespace" for the cluster differentiation?
Do you know if redis_exporter exposes any cluster name?
Sorry, something went wrong.
Maybe by(service) would work. But I am by no means an expert on this.
by(service)
Hello @samber , I have same issue, my situation is setup a redis cluster with 3 master and 3 salve. Each master only handle part of slot:
This rule and RedisDisconnectedSlaves will calculated a wrong result.
RedisDisconnectedSlaves
How about using this formula to determine the cluster status? redis_cluster_state{%(redisExporterSelector)s} == 0
No branches or pull requests
Hi,
We are seeing this alert after deploying multiple Redis clusters in different namespaces. AFAICT Redis itself does not consider this setup a problem.
Does the alert not take this scenario into account, or are we mistaken in thinking we do not have a real problem?
Shouldn't the query be
count(redis_instance_info{role="master"}) by (namespace) > 1 or something similar that takes this scenario into account?
https://github.com/samber/awesome-prometheus-alerts/blame/826be5877ffc129ca3511cd25af87d67ea67fb48/_data/rules.yml#L795
The text was updated successfully, but these errors were encountered: