Ops Briefing Surface

Production Reliability Dashboard

Generated 2026-04-03 12:55 for 2026-03-14 07:00 to 2026-03-21 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 services11Mapped from Slack and Pingdom evidence
AWS alarms in ALARM1Still alarming at window end
Latest observed signal2026-03-21 00:00Most 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 and catalog database alarms still look active.

Pingdom customer impact

External signal
No criticalActive: 1Total seen: 1

1 active item(s) in this window.

Slack impacted services

Application signal
2 criticalActive: 9Total seen: 9

2 critical, 7 non-critical active item(s).

AWS alarms

Infrastructure signal
1 criticalActive: 1Total seen: 2

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

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 uni-api-svc-4000, accommodations-api-svc-4100 as the primary application investigation set

    Treat critical services uni-api-svc-4000, accommodations-api-svc-4100 as the primary application investigation set. Use TraefikServiceHighErrorRate as the leading category, reproduce the failing paths on uni-api-svc-4000, accommodations-api-svc-4100, compare against the latest deploy or config change, and do not close it until both error rate and latency flatten. The thread points toward a data-integrity or write-path failure, so recent schema or persistence changes should be checked first.

    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-03-21 00:00adservio-ro-api-v2-status
Adservio RoNo recent customer-visible issue00m2026-03-21 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
uni-api-svc-4000Critical122026-03-20 21:47Seen todayTraefikServiceHighErrorRate (12)Observability storageGeneral investigation
SQL Integrity Constraint Violation: (conn=3570102) Cannot add or update a child row: a foreign key constraint fails (`ums_uni_catalog`.`dis… | Andrei Alexandru
accommodations-api-svc-4100Critical52026-03-18 13:24Recent (72h)TraefikServiceHighErrorRate (5)General investigation
Ionut Ciolan | de ce apar stack trace-urile alea? nu par folositoare
ai-api-svc-3900Warning42026-03-20 16:35Seen todayTraefikServiceHighLatency (4)NoneNo thread note
subscriptions-apiWarning32026-03-20 11:11Seen todayKubeHpaMaxedOut (3)NoneNo thread note
admission-end-session
Grouped 6 variantsVariant mentions 62Active variants 6
Warning272026-03-19 07:46Recent (72h)KubeJobFailed (27)NoneNo thread note
docgen2-apiWarning62026-03-19 13:11Recent (72h)KubeHpaMaxedOut (6)NoneNo thread note
grafanaWarning42026-03-19 12:27Recent (72h)NodeSystemSaturation (3)NodeCPUHighUsage (1)NoneNo thread note
update-recurentaWarning132026-03-16 10:52Seen this weekKubeJobFailed (13)NoneNo thread note
web-80Warning12026-03-17 04:13Seen this weekTraefikServiceHighLatency (1)NoneNo thread note
Evidence

Slack Alert Families

AlertSeverityCountLast SeenStatusThreadsTop Impacted ServicesDiscussion SignalLatest Thread Note
TraefikServiceHighErrorRateCritical172026-03-20 21:47Seen today3uni-api-svc-4000 (12)accommodations-api-svc-4100 (5)General investigationObservability storage
SQL Integrity Constraint Violation: (conn=3570102) Cannot add or update a child row: a foreign key constraint fails (`ums_uni_catalog`.`dis… | Andrei Alexandru
KubeHpaMaxedOutWarning92026-03-20 11:11Seen today0docgen2-api (6)subscriptions-api (3)None
TraefikServiceHighLatencyWarning52026-03-20 16:35Seen today0ai-api-svc-3900 (4)web-80 (1)None
KubeJobFailedWarning272026-03-19 07:46Recent (72h)0admission-end-session (27)update-recurenta (13)None
NodeSystemSaturationWarning32026-03-19 12:27Recent (72h)0grafana (3)None
NodeCPUHighUsageWarning12026-03-18 14:53Recent (72h)0grafana (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-mysql-master-memory-low633231622026-03-15 12:382026-03-18 07:09ALARMStill alarming
adservio-rds-mysql-master-write-latency-high21112026-03-16 23:082026-03-16 23:13OKLatest 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
2026-03-20 21:47TraefikServiceHighErrorRateCriticaluni-api-svc-4000General investigation
SQL Integrity Constraint Violation: (conn=3570102) Cannot add or update a child row: a foreign key constraint fails (`ums_uni_catalog`.`dis… | Andrei Alexandru
2026-03-18 12:48TraefikServiceHighErrorRateCriticalaccommodations-api-svc-4100General investigation
Ionut Ciolan | de ce apar stack trace-urile alea? nu par folositoare
2026-03-17 10:45TraefikServiceHighErrorRateCriticaluni-api-svc-4000Observability storage
errors.group-already-exists