-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
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
Initial Mixin #25
Initial Mixin #25
Conversation
mixin/alerts.libsonnet
Outdated
alert: 'LogishIngesterUnhealthy', | ||
'for': '15m', | ||
expr: ||| | ||
min(logish_ring_ingesters{state="Unhealthy", job=~"[a-z]+/distributor"}) by (namespace, job) > 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see this in Prometheus: https://admin-ops-tools1.grafana.net/prometheus/graph?g0.range_input=1h&g0.expr=logish_ring_ingesters&g0.tab=1
mixin/alerts.libsonnet
Outdated
expr: ||| | ||
100 * sum(rate(cortex_gw_request_duration_seconds_count{status_code=~"5.."}[1m])) by (namespace, job, route) | ||
/ | ||
sum(rate(logish_gw_request_duration_seconds_count[1m])) by (namespace, job, route) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logish_gw_request_duration_seconds_count?
mixin/alerts.libsonnet
Outdated
{ | ||
alert: 'LogishRequestLatency', | ||
expr: ||| | ||
namespace_job_route:logish_request_duration_seconds:99quantile{route!="metrics"} > 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
namespace_job_route:logish_request_duration_seconds?
Can we also have a promtail mixin please? An alerts on errors writing entries, latency and the usual dashboard. |
Done |
Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>
Update from upstream repository
One big issue is that we are using the same cortex-gw hence the recording-rules and alerts for the frontend are the same.