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 12:11:25.
› →|
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

studiosvc: p99 latency (ms) ≥ 2.0 min — 75.2× the fleet's usual 1.60 s (also p95 latency (ms) 42.23 s; Neo4j queries per request 27.7)

info Service outlier automation open impact 13 Owner: Suresh Boddapati (backup: Madhava Mukkamala) opened 25d ago · last observed 1d ago · observed 2821× · #5401 · 3d1f1f1d8a5a9bb0d0f4

What happened template

studiosvc differs from the other 13 services on 3 measures over six hours: p99 latency (ms) ≥ 2.0 min against the peers' 1.60 s (76.5 MADs above); p95 latency (ms) 42.23 s against the peers' 671 ms (71.4 MADs above); Neo4j queries per request 27.7 against the peers' 4.1 (5.1 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': 120000.0, 'value_fmt': '≥ 2.0 min', 'median': 1595.0000000000045, 'median_fmt': '1.60 s', 'mad': 1547.8343999999965, 'z': 76.49720150941229, 'direction': 'above', 'peers': 13}, {'measure': 'p95 latency (ms)', 'value': 42231.249999999935, 'value_fmt': '42.23 s', 'median': 671.4285714285697, 'median_fmt': '671 ms', 'mad': 581.9961428571401, 'z': 71.4091011403367, 'direction': 'above', 'peers': 13}, {'measure': 'Neo4j queries per request', 'value': 27.70014942719575, 'value_fmt': '27.7', 'median': 4.134328358208955, 'median_fmt': '4.1', 'mad': 4.57593901164773, 'z': 5.149942123136183, 'direction': 'above', 'peers': 13}
measurep99 latency (ms)
value120,000
value_fmt≥ 2.0 min
median1,595
median_fmt1.60 s
z76.50
directionabove
peers13
rule{"min_score": 3.5, "min_relative_pct": 35, "warn_on": []}
discriminator
window2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC

What is failing in studiosvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from studiosvc. In this finding's window (2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

1403× http error response returned to client since 2026-10-07 10:27:55 UTC
112× failed to fetch question detail — question not found since 2026-10-06 16:21:43 UTC
5× Request completed — 500 · could not create activation rule chain:activation rule \ since 2026-09-25 09:22:48 UTC
2× failed to create question — question with same title and VariableName already exists since 2026-08-27 12:28:38 UTC
1× failed to create node — Neo4jError: Neo.ClientError.Schema.ConstraintValidationFailed (Node(272803) already exists with … since 2026-11-17 06:39:58 UTC

All studiosvc 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_at1794911375
age_seconds667
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers