Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Max · 30 days▾
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 11:50:31.
› →|
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: Neo4j queries per request 107.5 — 18.6× the fleet's usual 5.8 (also p95 latency (ms) 2.77 s)

info Service outlier test27 open impact 10 Owner: Prasad Limaye (backup: Harish Kumar) opened 25d ago · last observed 1d ago · observed 895× · #5497 · 6be5ba4386377870175f

What happened template

docsvc differs from the other 7 services on 2 measures over six hours: Neo4j queries per request 107.5 against the peers' 5.8 (13.1 MADs above); p95 latency (ms) 2.77 s against the peers' 451 ms (3.6 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': 107.46153846153847, 'value_fmt': '107.5', 'median': 5.782875960482985, 'median_fmt': '5.8', 'mad': 7.7841807335444475, 'z': 13.062217589950167, 'direction': 'above', 'peers': 7}, {'measure': 'p95 latency (ms)', 'value': 2768.7499999999973, 'value_fmt': '2.77 s', 'median': 450.80061983471074, 'median_fmt': '451 ms', 'mad': 639.4194260226451, 'z': 3.6250843903563172, 'direction': 'above', 'peers': 7}
measureNeo4j queries per request
value107.46
value_fmt107.5
median5.78
median_fmt5.8
z13.06
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 docsvc — the bad events, decomposed

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

PATCH /api/documents/v2 1 bad of 11 calls · 100% of the service's 5xx

The error shapes behind them

2× failed to process db result — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=1… since 2026-11-03 12:36:16 UTC
1× failed to write relationship cypher — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transac… since 2026-11-03 12:36:16 UTC
1× Failed to create EventPlan for Study — failed to link event plan to study: Neo4jError: Neo.TransientError.Transaction.De… since 2026-11-15 16:39:56 UTC
1× could not update document metadata for doc id fde96cb4-ea75-492a-85f3-e5b447ff3612: conflict: document fde96cb4-ea75-492… since 2026-11-17 06:53:42 UTC
1× Request completed — 500 · could not update document metadata for doc id fde96cb4-ea75-492a-85f3-e5b447ff3612: conflict: … since 2026-11-17 06:53:42 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_at1794911730
age_seconds312
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers