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 14:14:20.
› →|
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

docsvc: 5xx rate (%) 0.55% — 7.5× the fleet's usual 0.07%

info Service outlier automation open impact 13 Owner: Prasad Limaye (backup: Harish Kumar) opened 26d ago · last observed 1d ago · observed 1832× · #5403 · d5904715f5ca6e036faf

What happened template

docsvc's 5xx rate (%) is 0.55% against the 15 other services' median of 0.07% (4.4 robust MADs above, six-hour window). This compares the service with its peers, not with its own history — the seasonal detector does that.

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

The facts

measures{'measure': '5xx rate (%)', 'value': 0.5496392992098935, 'value_fmt': '0.55%', 'median': 0.07346459006758742, 'median_fmt': '0.07%', 'mad': 0.1089186012342051, 'z': 4.371840105790551, 'direction': 'above', 'peers': 15}
measure5xx rate (%)
value0.55
value_fmt0.55%
median0.07
median_fmt0.07%
z4.37
directionabove
peers15
rule{"min_score": 3.5, "min_relative_pct": 35, "warn_on": []}
discriminator
window2026-11-17 00:00:02 UTC → 2026-11-17 06:00:02 UTC

What is failing in docsvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from docsvc. In this finding's window (2026-11-17 00:00:02 UTC → 2026-11-17 06:00:02 UTC) there were 48; every line links to the grouped errors behind it.

POST /api/documents/folders/manager 15 bad of 40 calls · 31% of the service's 5xx
PATCH /api/documents/v2/:id/internal 14 bad of 485 calls · 29% of the service's 5xx
POST /api/documents/tasks 4 bad of 51 calls · 8% of the service's 5xx
POST /api/events/placeholders 3 bad of 78 calls · 6% of the service's 5xx
PUT /api/documents/:id/promote 3 bad of 52 calls · 6% of the service's 5xx
POST /api/events/:id/placeholders/:id/matches 2 bad of 33 calls · 4% of the service's 5xx
…7 more endpoints with fewer 5xx — all in the grouped view

The error shapes behind them

385× failed to run cypher in transaction — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transac… since 2026-10-29 19:47:42 UTC
38× Request completed — 500 · folder manager already has folders since 2026-09-25 08:36:31 UTC
29× failed to run cypher in transaction — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transac… since 2026-10-31 21:25:03 UTC
29× failed to process db result — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=1… since 2026-10-31 07:21:15 UTC
27× failed to process db result — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=2… since 2026-10-31 21:27:46 UTC

All docsvc 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_at1794894820
age_seconds382
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers