o11y requests too large for nods in the prod-eu-west-2 region.
Aug 5, 11:41 UTCAug 5, 11:44 UTC
Duration
3m
Impact
Minor
Root cause
Not disclosed
Grafana Labs, 90 days
74 incidents
Affected
AWS Germany - prod-eu-west-2: Rule EvaluationAWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration APIAWS Germany - prod-eu-west-2: AlertmanagerAlerting and SLO - AWS Germany - prod-eu-west-2: Rule EvaluationAlerting and SLO - AWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration APIAlerting and SLO - AWS Germany - prod-eu-west-2: Alertmanager
Final update
This incident has been resolved.
Timeline
- Resolved · Aug 5, 11:44 UTC
This incident has been resolved.
- Investigating · Aug 5, 11:41 UTC
We are currently investigating an issue with critical o11y requests being too large for nods in the prod-eu-west-2 region. This is leading to issues in scaling up services, and may may lead increased errors in requests.
More from Grafana Labs
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2221:27 UTC | Kubernetes Observability Billing & Usage Incorrect | minor | 16h 39m |
| Sep 2214:57 UTC | IRM Access Issues for a Small Group of Users | major | 20h 10m |
| Sep 2119:16 UTC | Mimir write request errors | none | 0m |
| Sep 1712:34 UTC | Elevated Latency Managing Cloud Provider Integrations in GCP US Central | minor | 0m |
| Sep 1510:00 UTC | Increased Execution Time for Browser Checks in Synthetic Monitoring | minor | 1h 17m |
| Sep 1507:49 UTC | Intermittent Metric Write Errors in GCP US Central (prod-us-central-0) | minor | 0m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.