Prometheus has slow rule evaluations

Start time: 19 January 2021, 12:37AM (UTC)
Severity: critical
full_query: (prometheus_rule_group_last_duration_seconds / prometheus_rule_group_interval_seconds) * 100 > 70
Monitoring tool: Prometheus
Description: gitlab-monitoring-promethe-prometheus at 10.222.5.183:9090 prometheus-gitlab-monitoring-promethe-prometheus-1 rule group /etc/prometheus/rules/prometheus-gitlab-monitoring-promethe-prometheus-rulefiles-1/monitoring-sidekiq.yaml;sidekiq.rules is taking more than 70% of the evaluation over the last 30 minutes.
GitLab alert: https://gitlab.com/gitlab-com/gl-infra/production/-/alert_management/55/details

---

Summary

More information will be added as we investigate the issue.

Timeline

All times UTC.

`YYYY-MM-DD` - `00:00` - ...

Corrective Actions

---

Click to expand or collapse the Incident Review section.

Incident Review

---

Summary

1. Service(s) affected:
2. Team attribution:
3. Time to detection:
4. Minutes downtime or degradation:

Metrics

Customer Impact

1. Who was impacted by this incident? (i.e. external customers, internal customers)
   1. ...
2. What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
   1. ...
3. How many customers were affected?
   1. ...
4. If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
   1. ...

What were the root causes?

"5 Whys"

Incident Response Analysis

1. How was the incident detected?
   1. ...
2. How could detection time be improved?
   1. ...
3. How was the root cause diagnosed?
   1. ...
4. How could time to diagnosis be improved?
   1. ...
5. How did we reach the point where we knew how to mitigate the impact?
   1. ...
6. How could time to mitigation be improved?
   1. ...
7. What went well?
   1. ...

Post Incident Analysis

1. Did we have other events in the past with the same root cause?
   1. ...
2. Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
   1. ...
3. Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
   1. ...

Lessons Learned

Guidelines

• Blameless RCA Guideline

Resources

1. If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)

Incident Review Stakeholders

added IncidentActive incident labels

changed the severity to Critical - S1

Hi @alert-bot,

This incident issue does not have any service attribution. Please add one or more of the appropriate service label that are prefixed with Service:.

Please also add a group:: scoped label to help trace to a correct engineering group.

Thanks for your help!

---

You are welcome to help improve this comment.

added auto updated label

automatically closed this incident because the alert resolved

mentioned in issue on-call-handovers#1326 (closed)

added ServiceMonitoring-Other label

This incident was automatically labeled with IncidentResolved because it was closed.

Please review the Incident Workflow section on the Incident Management handbook page for more information.

added IncidentResolved label and removed IncidentActive label

mentioned in issue reliability-reports#108 (closed)

added severity4 label

changed the severity to Low - S4