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 21:33:03.
› →|
updated 1d 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) 1.95 s — 3.7× the fleet's usual 530 ms (also p95 latency (ms) 1.48 s)

info Service outlier test26 open impact 11 Owner: Madhava Mukkamala (backup: Shashank Agrawal) opened 84d ago · last observed 1d ago · observed 617× · #125 · 0e9fab4edb1ae7e8df95

What happened template

execsvc differs from the other 5 services on 2 measures over six hours: p99 latency (ms) 1.95 s against the peers' 530 ms (6.4 MADs above); p95 latency (ms) 1.48 s against the peers' 257 ms (5.0 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': 1951.7241379310353, 'value_fmt': '1.95 s', 'median': 530.4166666666674, 'median_fmt': '530 ms', 'mad': 222.11819000000193, 'z': 6.398879224003921, 'direction': 'above', 'peers': 5}, {'measure': 'p95 latency (ms)', 'value': 1482.7586206896551, 'value_fmt': '1.48 s', 'median': 257.00000000000017, 'median_fmt': '257 ms', 'mad': 246.04074044117678, 'z': 4.981933554954116, 'direction': 'above', 'peers': 5}
measurep99 latency (ms)
value1,952
value_fmt1.95 s
median530.42
median_fmt530 ms
z6.40
directionabove
peers5
rule{"min_score": 3.5, "min_relative_pct": 35, "warn_on": []}
discriminator
window2026-11-17 03:22:05 UTC → 2026-11-17 09:22:05 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-17 03:22:05 UTC → 2026-11-17 09:22:05 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

21× error anchor visit index has not been set. Does this study have an anchor visit? continuing without setting day/date ran… since 2026-11-06 00:02:19 UTC
12× error anchor visit index has not been set. Does this study have an anchor visit? continuing without setting day/date ran… since 2026-11-12 15:37:28 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_at1794907321
age_seconds5
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers