Ops Briefing Surface

Production Reliability Dashboard

Generated 2026-04-04 14:27 for 2026-03-28 07:00 to 2026-04-04 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: 2
Impacted services19Mapped from Slack and Pingdom evidence
AWS alarms in ALARM0Still alarming at window end
Latest observed signal2026-04-04 04:36Most recent cross-source activity
Executive summary

What needs attention

Bottom line: Pingdom observed recent customer-facing glitches (email unconfirmed) and application-level critical paths are present.

Pingdom customer impact

External signal
No criticalActive: 1Total seen: 1

1 active item(s) in this window.

Slack impacted services

Application signal
1 criticalActive: 17Total seen: 17

1 critical, 16 non-critical active item(s).

AWS alarms

Infrastructure signal
No criticalActive: 2Total seen: 2

2 active item(s) in this window.

What to do next

  1. NextUse Pingdom check https://www

    Use Pingdom check https://www.adservio.ro/api/v2/status as churn/degradation evidence, and escalate to customer-facing incident priority only after inbox confirmation or strong cross-source correlation.

    Executive recommendation
  2. ThenTreat critical services docgen2-api-svc-3600 as the primary application investigation set

    Treat critical services docgen2-api-svc-3600 as the primary application investigation set. Use TraefikServiceHighErrorRate as the leading category, reproduce the failing paths on docgen2-api-svc-3600, compare against the latest deploy or config change, and do not close it until both error rate and latency flatten.

    Executive recommendation
Global Evidence Explorer

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

Customer View

Pingdom Checks

Pingdom CheckStatusEventsDowntimeLast SeenLikely ServicesCorrelated Evidence
https://www.adservio.ro/api/v2/statusRecovered recently22m2026-04-04 00:00adservio-ro-api-v2-status
Adservio RoNo recent customer-visible issue00m2026-04-04 00:00adservio-ro

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.

Application View

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 / ResourceHighest SeverityCountLast SeenStatusTop Alert TypesDiscussion SignalLatest Thread Note
docgen2-api-svc-3600Critical12026-04-03 09:24Seen todayTraefikServiceHighErrorRate (1)NoneNo thread note
grafanaWarning142026-04-04 04:19Seen todayKubeAggregatedAPIDown (10)KubeCPUOvercommit (1)KubeHpaMaxedOut (3)NoneNo thread note
update-recurenta
Grouped 2 variantsVariant mentions 11Active variants 2
Warning112026-04-04 04:36Seen todayKubeJobFailed (10)KubeJobNotCompleted (1)NoneNo thread note
ai-api-svc-3900Warning62026-04-03 19:02Seen todayTraefikServiceHighLatency (6)NoneNo thread note
docgen2-apiWarning42026-04-03 13:55Seen todayKubeHpaMaxedOut (4)NoneNo thread note
accommodations-sync-usersWarning312026-04-02 09:39Recent (72h)KubeJobFailed (31)NoneNo thread note
accommodations-eventsWarning252026-04-02 09:04Recent (72h)KubeDeploymentReplicasMismatch (25)NoneNo thread note
minicrm-syncWarning82026-04-02 09:39Recent (72h)KubeJobFailed (8)NoneNo thread note
accommodations-events-cf9b9b448-d94d7Warning52026-04-02 07:58Recent (72h)KubePodCrashLooping (5)NoneNo thread note
accommodations-events-9c7b649d-scl7jWarning22026-04-02 14:29Recent (72h)KubePodCrashLooping (2)NoneNo thread note
accommodations-events-7c8fdfb7d5-k8vfxWarning22026-04-01 14:00Recent (72h)KubePodCrashLooping (2)NoneNo thread note
metrics-serverWarning12026-04-02 15:44Recent (72h)KubeDeploymentReplicasMismatch (1)NoneNo thread note
accommodations-events-67574dccbd-ggv9bWarning12026-04-02 10:00Recent (72h)KubePodCrashLooping (1)NoneNo thread note
accommodations-events-6d787575df-nscmtWarning12026-04-02 09:02Recent (72h)KubePodCrashLooping (1)NoneNo thread note
core-grafana-58bcc69dd8-q4sb5Warning12026-04-01 10:54Recent (72h)KubePodNotReady (1)NoneNo thread note
accommodations-events-7c8fdfb7d5-dl54wWarning12026-04-01 09:28Recent (72h)KubePodCrashLooping (1)NoneNo thread note
download-albumWarning132026-03-30 11:17Seen this weekKubeJobFailed (13)NoneNo thread note
Evidence

Slack Alert Families

AlertSeverityCountLast SeenStatusThreadsTop Impacted ServicesDiscussion SignalLatest Thread Note
TraefikServiceHighErrorRateCritical12026-04-03 09:24Seen today0docgen2-api-svc-3600 (1)None
KubeJobFailedWarning542026-04-04 04:36Seen today0accommodations-sync-users (31)download-album (13)update-recurenta (10)minicrm-sync (8)None
KubeAggregatedAPIDownWarning102026-04-04 04:19Seen today0grafana (10)None
KubeHpaMaxedOutWarning72026-04-03 13:55Seen today0docgen2-api (4)grafana (3)None
TraefikServiceHighLatencyWarning62026-04-03 19:02Seen today0ai-api-svc-3900 (6)None
KubeCPUOvercommitWarning12026-04-03 10:18Seen today0grafana (1)None
KubeDeploymentReplicasMismatchWarning262026-04-02 15:44Recent (72h)0accommodations-events (25)metrics-server (1)None
KubePodCrashLoopingWarning122026-04-02 14:29Recent (72h)0accommodations-events-cf9b9b448-d94d7 (5)accommodations-events-7c8fdfb7d5-k8vfx (2)accommodations-events-9c7b649d-scl7j (2)accommodations-events-7c8fdfb7d5-dl54w (1)accommodations-events-6d787575df-nscmt (1)None
KubeJobNotCompletedWarning12026-04-02 15:05Recent (72h)0update-recurenta (1)None
KubePodNotReadyWarning12026-04-01 10:54Recent (72h)0core-grafana-58bcc69dd8-q4sb5 (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 AlarmEmailsALARMOKState FlipsFirst SeenLast SeenLatest StateStatus
adservio-rds-postgres-billing-cpu-high42232026-04-01 10:112026-04-02 10:22OKLatest OK
adservio-root-account-usage21112026-04-03 13:332026-04-03 13:50OKLatest 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 DateAlertSeverityServicesSignalKey Notes