Xray
1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 1 hour▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 07:21:58.
› →|
updated 20h ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.
← findings

execsvc: p99 latency (ms) 7.08 s — 12.9× the fleet's usual 550 ms (also p95 latency (ms) 4.01 s)

info Service outlier master open impact 16 Owner: Madhava Mukkamala (backup: Shashank Agrawal) opened 83d ago · last observed 1d ago · observed 957× · #167 · 0b1600faa19f67f5b619

What happened template

execsvc differs from the other 5 services on 2 measures over six hours: p99 latency (ms) 7.08 s against the peers' 550 ms (56.1 MADs above); p95 latency (ms) 4.01 s against the peers' 468 ms (7.8 MADs above). Peer comparison is structural more often than it is news — a service that does more work per request will sit here for as long as it does — which is why this is informational unless it is about failures.

A service unlike the rest of the fleet on one measure (robust z against its peers).

The facts

measures{'measure': 'p99 latency (ms)', 'value': 7075.000000000007, 'value_fmt': '7.08 s', 'median': 549.9999999999972, 'median_fmt': '550 ms', 'mad': 116.23583999999626, 'z': 56.13586996919556, 'direction': 'above', 'peers': 5}, {'measure': 'p95 latency (ms)', 'value': 4009.999999999999, 'value_fmt': '4.01 s', 'median': 468.1818181818182, 'median_fmt': '468 ms', 'mad': 451.80363030303045, 'z': 7.839286681788366, 'direction': 'above', 'peers': 5}
measurep99 latency (ms)
value7,075
value_fmt7.08 s
median550.00
median_fmt550 ms
z56.14
directionabove
peers5
rule{"min_score": 3.5, "min_relative_pct": 35, "warn_on": []}
discriminator
window2026-11-16 21:12:58 UTC → 2026-11-17 03:12:58 UTC

What is failing in execsvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from execsvc. In this finding's window (2026-11-16 21:12:58 UTC → 2026-11-17 03:12:58 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

787× Request completed — 500 · failed to fetch activity status: could not match participant question to activity graph: quest… since 2026-10-16 12:11:42 UTC
787× Failed to fetch activity status — could not match participant question to activity graph: questionId="b3228925-d16e-41cf… since 2026-11-04 11:18:42 UTC
787× could not match participant questionnaire/question/table/doc-upload to activity graph since 2026-11-17 04:05:17 UTC
30× No cached node found for activation chain ref node since 2026-11-12 13:43:21 UTC
29× no result from branch evaluation since 2026-11-13 15:11:12 UTC

All execsvc errors, grouped → · service page · its logs

History

Check it yourself

Every link carries the finding's own time window, so it shows tomorrow what it shows now.

Actions

Sign in (IAP) to acknowledge, snooze or resolve.

Where the numbers come from

sourcerollup
collected_at1794884962
age_seconds216
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers