Pingdom customer impact
External signalNo criticalActive: 1Total seen: 1
1 active item(s) in this window.
Ops Briefing Surface
Production Reliability Dashboard
Generated 2026-07-28 18:25 for 2026-07-18 07:00 to 2026-07-26 10: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: 3
Impacted services10Mapped from Slack and Pingdom evidence
AWS alarms in ALARM0Still alarming at window end
Latest observed signal2026-07-26 09:16Most recent cross-source activity
Data source availability
Some enrichments were unavailable in this run; drilldowns below stay focused on captured evidence.
What needs attention
Bottom line: Pingdom observed recent customer-facing glitches (email unconfirmed) and application-level critical paths are present.
Slack impacted services
Application signal4 criticalActive: 9Total seen: 9
4 critical, 5 non-critical active item(s).
AWS alarms
Infrastructure signalNo criticalActive: 0Total seen: 0
No AWS alarm emails were captured in this window.
No active issue listed in this category.
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 |
|---|---|---|---|---|---|---|
| Adservio Ro | Recovered recently | 3 | 3m | 2026-07-23 16:55 | unclassified | Pingdom-only evidence so far |
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 |
|---|---|---|---|---|---|---|---|
| grafana | Critical | 61 | 2026-07-26 08:03 | Seen today | Watchdog (16)KubeletServerCertificateExpiration (13)KubeAPIErrorBudgetBurn (11)RESOLVED - KubeAPIErrorBudgetBurn (4)RESOLVED - KubeContainerMemoryHigh (3) | None | No thread note |
| admission-api Grouped 6 variantsVariant mentions 31Active variants 6 | Critical | 21 | 2026-07-24 17:27 | Recent (72h) | TraefikServiceHighErrorRate (2)KubePodContainerRestartingFrequently (6)RESOLVED - KubePodContainerRestartingFrequently (3)RESOLVED - TraefikServiceHighErrorRate (2)RESOLVED - TraefikServiceHighLatency (2) | Scaling config | admission-api pods kept crashing (out-of-memory) because Node only uses about half the container's memory limit for its heap the 512Mi limi… |
| uni-api | Critical | 1 | 2026-07-21 18:41 | Seen this week | TraefikServiceHighErrorRate (1) | None | No thread note |
| web-80 | Critical | 1 | 2026-07-18 12:06 | No recent signal | TraefikServiceHighErrorRate (1) | None | No thread note |
| metrics-server | Warning | 22 | 2026-07-26 09:16 | Seen today | KubeAggregatedAPIDown (22) | None | No thread note |
| loki | Warning | 6 | 2026-07-23 19:51 | Recent (72h) | RESOLVED - KubeContainerMemoryHigh (3)KubeContainerMemoryHigh (3) | None | No thread note |
| core-kube-state-metrics | Warning | 2 | 2026-07-23 07:31 | Seen this week | RESOLVED - KubePodContainerRestartingFrequently (1)KubePodContainerRestartingFrequently (1) | None | No thread note |
| tigera-operator | Warning | 2 | 2026-07-23 05:41 | Seen this week | RESOLVED - KubePodContainerRestartingFrequently (1)KubePodContainerRestartingFrequently (1) | None | No thread note |
| core-scheduled-events-worker | Warning | 2 | 2026-07-20 02:04 | Seen this week | KubePodContainerRestartingFrequently (2) | None | No thread note |
Slack Alert Families
| Alert | Severity | Count | Last Seen | Status | Threads | Top Impacted Services | Discussion Signal | Latest Thread Note |
|---|---|---|---|---|---|---|---|---|
| TraefikServiceHighErrorRate | Critical | 4 | 2026-07-24 16:54 | Recent (72h) | 1 | admission-api (2)web-80 (1)uni-api (1) | Scaling config | admission-api pods kept crashing (out-of-memory) because Node only uses about half the container's memory limit for its heap the 512Mi limi… |
| TraefikServiceHighLatencyCritical | Critical | 1 | 2026-07-24 16:48 | Recent (72h) | 0 | admission-api (1) | None | |
| CriticalPagerDutyTest | Critical | 1 | 2026-07-21 16:20 | Seen this week | 0 | grafana (1) | None | |
| KubeAggregatedAPIDown | Warning | 22 | 2026-07-26 09:16 | Seen today | 0 | metrics-server (22) | None | |
| Watchdog | Warning | 16 | 2026-07-26 00:21 | Seen today | 0 | grafana (16) | None | |
| KubeletServerCertificateExpiration | Warning | 13 | 2026-07-25 18:31 | Seen today | 0 | grafana (13) | None | |
| KubeAPIErrorBudgetBurn | Warning | 11 | 2026-07-26 08:03 | Seen today | 0 | grafana (11) | None | |
| RESOLVED - KubeAPIErrorBudgetBurn | Warning | 4 | 2026-07-26 03:52 | Seen today | 0 | grafana (4) | None | |
| RESOLVED - KubeletServerCertificateExpiration | Warning | 1 | 2026-07-25 20:56 | Seen today | 0 | grafana (1) | None | |
| RESOLVED - KubeClientErrors | Warning | 1 | 2026-07-25 12:07 | Seen today | 0 | grafana (1) | None | |
| KubeClientErrors | Warning | 1 | 2026-07-25 12:02 | Seen today | 0 | grafana (1) | None | |
| KubePodContainerRestartingFrequently | Warning | 10 | 2026-07-24 16:47 | Recent (72h) | 0 | admission-api (6)core-scheduled-events-worker (2)tigera-operator (1)core-kube-state-metrics (1) | None | |
| RESOLVED - KubePodContainerRestartingFrequently | Warning | 5 | 2026-07-24 17:27 | Recent (72h) | 0 | admission-api (3)tigera-operator (1)core-kube-state-metrics (1) | None | |
| RESOLVED - KubeContainerMemoryHigh | Warning | 3 | 2026-07-23 19:51 | Recent (72h) | 0 | grafana (3)loki (3) | None | |
| KubeContainerMemoryHigh | Warning | 3 | 2026-07-23 19:46 | Recent (72h) | 0 | grafana (3)loki (3) | None | |
| RESOLVED - KubeHpaMaxedOut | Warning | 3 | 2026-07-23 16:47 | Recent (72h) | 0 | grafana (3) | None | |
| KubeHpaMaxedOut | Warning | 3 | 2026-07-23 16:37 | Recent (72h) | 0 | grafana (3) | None | |
| RESOLVED - TraefikServiceHighErrorRate | Warning | 2 | 2026-07-24 16:59 | Recent (72h) | 0 | admission-api (2) | None | |
| RESOLVED - TraefikServiceHighLatencyCritical | Warning | 1 | 2026-07-24 16:53 | Recent (72h) | 0 | admission-api (1) | None | |
| RESOLVED - TraefikServiceHighLatency | Warning | 2 | 2026-07-20 09:34 | Seen this week | 0 | admission-api (2) | None | |
| TraefikServiceHighLatency | Warning | 2 | 2026-07-20 09:29 | Seen this week | 0 | admission-api (2) | None | |
| RESOLVED - CriticalPagerDutyTest | Warning | 1 | 2026-07-21 16:25 | Seen this week | 0 | grafana (1) | None | |
| RESOLVED - KubePodCrashLooping | Warning | 1 | 2026-07-20 14:43 | Seen this week | 0 | admission-api (1) | None | |
| KubePodCrashLooping | Warning | 1 | 2026-07-20 14:38 | Seen this week | 0 | admission-api (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 |
|---|
“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-07-20 14:19 | TraefikServiceHighErrorRate | Critical | admission-api | Scaling config | admission-api pods kept crashing (out-of-memory) because Node only uses about half the container's memory limit for its heap the 512Mi limi… |