Xray
1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 6 hours▾
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 18:53:43.
› →|
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: Neo4j queries per request 161.0 — 27.8× the fleet's usual 5.8 (also p95 latency (ms) 9.24 s; p99 latency (ms) 18.30 s)

info Service outlier test27 open impact 13 Owner: Suresh Boddapati (backup: Madhava Mukkamala) opened 83d ago · last observed 1d ago · observed 2744× · #212 · 8740f42376edd1907770

What happened template

studiosvc differs from the other 7 services on 3 measures over six hours: Neo4j queries per request 161.0 against the peers' 5.8 (19.9 MADs above); p95 latency (ms) 9.24 s against the peers' 451 ms (13.7 MADs above); p99 latency (ms) 18.30 s against the peers' 1.01 s (12.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': 'Neo4j queries per request', 'value': 161.0203642384106, 'value_fmt': '161.0', 'median': 5.782875960482985, 'median_fmt': '5.8', 'mad': 7.7841807335444475, 'z': 19.942688073641605, 'direction': 'above', 'peers': 7}, {'measure': 'p95 latency (ms)', 'value': 9239.130434782608, 'value_fmt': '9.24 s', 'median': 450.80061983471074, 'median_fmt': '451 ms', 'mad': 639.4194260226451, 'z': 13.744233373724024, 'direction': 'above', 'peers': 7}, {'measure': 'p99 latency (ms)', 'value': 18298.24561403512, 'value_fmt': '18.30 s', 'median': 1012.499999999995, 'median_fmt': '1.01 s', 'mad': 1434.3072810218903, 'z': 12.051633455921438, 'direction': 'above', 'peers': 7}
measureNeo4j queries per request
value161.02
value_fmt161.0
median5.78
median_fmt5.8
z19.94
directionabove
peers7
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 4; every line links to the grouped errors behind it.

POST /api/studio/forms/:id/activationRuleChains 4 bad of 433 calls · 100% of the service's 5xx

The error shapes behind them

17× http error response returned to client since 2026-10-06 01:20:44 UTC
6× Request completed — 500 · could not create activation rule chain:activation rule \ since 2026-10-02 11:58:33 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_at1794911730
age_seconds312
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers