Pingdom customer impact
External signalNo criticalActive: 0Total seen: 0
No Pingdom checks were available in this window.
No active issue listed in this category.
Ops Briefing Surface
Production Reliability Dashboard
Generated 2026-06-02 14:04 for 2026-05-23 07:00 to 2026-05-30 07:00 from Pingdom checks, Slack #_alerts_prod, and AWS SNS alerts.
All sources
Pingdom customer checks
Slack alert families
AWS alarm emails
Email-confirmed customer incidents0Pingdom down/slow events confirmed by inbox alertsObserved in Pingdom: 0
Impacted services5Mapped from Slack and Pingdom evidence
AWS alarms in ALARM0Still alarming at window end
Latest observed signal2026-05-29 18:06Most recent cross-source activity
What needs attention
Bottom line: application-level critical paths are present.
Slack impacted services
Application signal1 criticalActive: 5Total seen: 5
1 critical, 4 non-critical active item(s).
AWS alarms
Infrastructure signalNo criticalActive: 1Total seen: 2
1 active item(s) in this window.
Global Evidence Explorer
Global Evidence Explorer
Report-wide charts and tables stay here, separate from the active investigation scope.
Global Evidence Explorer
Report-wide charts and tables stay here, separate from the active investigation scope.
Application + Infrastructure Alerts by Day
Pingdom latency + downtime by source
Pingdom Checks
| Pingdom Check | Status | Events | Downtime | Last Seen | Likely Services | Correlated Evidence |
|---|
Pingdom rows show externally visible signal first. The correlated evidence column helps tie the failing check back to services, Slack alert families, or AWS alarms when those links exist.
Slack Impacted Service / Resource View
This view attributes alerts to the workload or resource named in the alert text. Grafana, Loki, and Tempo are treated as observability components and are excluded when a more specific impacted target is also present.
| Impacted Service / Resource | Highest Severity | Count | Last Seen | Status | Top Alert Types | Discussion Signal | Latest Thread Note |
|---|---|---|---|---|---|---|---|
| core-grafana-80 | Critical | 2 | 2026-05-29 18:04 | Seen today | TraefikServiceHighErrorRate (2) | None | No thread note |
| grafana | Warning | 11 | 2026-05-29 12:26 | Seen today | NodeSystemSaturation (4)KubeMemoryOvercommit (4)KubeHpaMaxedOut (3) | Release / migration issue | Worker node 10.66.133.111 (c7a.2xlarge, 8 vCPU) is CPU-saturated at 91% real usage 6 of 21 web pods landed on it (no topology spread on the… | Also durable fix is adding topologySpreadConstraints | to the web Deployment which i will look into |
| ai-api | Warning | 6 | 2026-05-29 18:06 | Seen today | TraefikServiceHighLatency (6) | None | No thread note |
| docgen2-api | Warning | 9 | 2026-05-26 13:06 | Seen this week | KubeHpaMaxedOut (9) | None | No thread note |
| biling-efactura-worker-ff45f6d-rxxlg | Warning | 1 | 2026-05-26 13:51 | Seen this week | KubePodNotReady (1) | None | No thread note |
Slack Alert Families
| Alert | Severity | Count | Last Seen | Status | Threads | Top Impacted Services | Discussion Signal | Latest Thread Note |
|---|---|---|---|---|---|---|---|---|
| TraefikServiceHighErrorRate | Critical | 2 | 2026-05-29 18:04 | Seen today | 0 | core-grafana-80 (2) | None | |
| TraefikServiceHighLatency | Warning | 6 | 2026-05-29 18:06 | Seen today | 0 | ai-api (6) | None | |
| NodeSystemSaturation | Warning | 4 | 2026-05-29 12:26 | Seen today | 1 | grafana (4) | Release / migration issue | Worker node 10.66.133.111 (c7a.2xlarge, 8 vCPU) is CPU-saturated at 91% real usage 6 of 21 web pods landed on it (no topology spread on the… | Also durable fix is adding topologySpreadConstraints | to the web Deployment which i will look into |
| KubeHpaMaxedOut | Warning | 12 | 2026-05-28 14:40 | Recent (72h) | 0 | docgen2-api (9)grafana (3) | None | |
| KubeMemoryOvercommit | Warning | 4 | 2026-05-28 19:09 | Recent (72h) | 0 | grafana (4) | None | |
| KubePodNotReady | Warning | 1 | 2026-05-26 13:51 | Seen this week | 0 | biling-efactura-worker-ff45f6d-rxxlg (1) | None |
Status is heuristic. Slack rarely posts explicit resolutions, so “Seen today” or “Recent” means the alert family still appeared in production recently, not that it is definitely unresolved.
AWS Email Alarm Families
| AWS Alarm | Emails | ALARM | OK | State Flips | First Seen | Last Seen | Latest State | Status |
|---|---|---|---|---|---|---|---|---|
| adservio-rds-mysql-master-memory-low | 13 | 6 | 7 | 12 | 2026-05-25 07:55 | 2026-05-29 12:00 | OK | Flapping, latest OK |
| adservio-rds-postgres-billing-cpu-high | 4 | 2 | 2 | 3 | 2026-05-28 10:11 | 2026-05-29 10:23 | OK | Latest OK |
“Flapping, latest OK” means the most recent email was an OK, but the alarm toggled repeatedly and is still a reliability concern.
Global Discussion-Derived Signal
| Thread Date | Alert | Severity | Services | Signal | Key Notes |
|---|---|---|---|---|---|
| 2026-05-28 08:16 | NodeSystemSaturation | Warning | grafana | Release / migration issue | Worker node 10.66.133.111 (c7a.2xlarge, 8 vCPU) is CPU-saturated at 91% real usage 6 of 21 web pods landed on it (no topology spread on the… | Also durable fix is adding topologySpreadConstraints | to the web Deployment which i will look into |