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
{{ message }}
This repository has been archived by the owner on Dec 5, 2023. It is now read-only.
We have a client that experienced a shard loss without any standard redis provided Prometheus alerts firing.
I tested the alert below that requires shards ids (master shards) - it works but requires hard coded values
Maybe that can be improved to be made generic
- alert: Shard went down
expr: absent(redis_up{job="redis-enterprise", status="active", redis="42"}) == 1 or absent(redis_up{job="redis-enterprise", status="active", redis="39" }) == 1
for: 20s
labels:
severity: critical
annotations:
description: "Shard is down - Cluster: {{ $labels.cluster }} Shard: {{$labels.redis}} Node: {{$labels.node}} Database:{{$labels.bdb}}"
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a client that experienced a shard loss without any standard redis provided Prometheus alerts firing.
I tested the alert below that requires shards ids (master shards) - it works but requires hard coded values
Maybe that can be improved to be made generic
The text was updated successfully, but these errors were encountered: