docsvc: Neo4j queries per request 5.1 — 2.1× the fleet's usual 2.4
info
Service outlier
master
open
impact 14
Owner: Prasad Limaye (backup: Harish Kumar)
opened 84d ago · last observed 1d ago · observed 2941× · #106 · 5900ab16e04c1e828a65
What happened template
docsvc's Neo4j queries per request is 5.1 against the 6 other services' median of 2.4 (3.7 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': 'Neo4j queries per request', 'value': 5.097345132743363, 'value_fmt': '5.1', 'median': 2.3943031451462207, 'median_fmt': '2.4', 'mad': 0.7361666620938787, 'z': 3.6717799470963275, 'direction': 'above', 'peers': 6} |
| measure | Neo4j queries per request |
| value | 5.10 |
| value_fmt | 5.1 |
| median | 2.39 |
| median_fmt | 2.4 |
| z | 3.67 |
| direction | above |
| peers | 6 |
| rule | {"min_score": 3.5, "min_relative_pct": 35, "warn_on": []} |
| discriminator | |
| window | 2026-11-16 22:16:30 UTC → 2026-11-17 04:16:30 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-16 22:16:30 UTC → 2026-11-17 04:16:30 UTC) there were 0; every line links to the grouped errors behind it.
The error shapes behind them
| 23× | Request completed — 500 · could not update document metadata for doc id 0211da3b-b92d-4f58-a742-62624434f054: could not … since 2026-09-30 16:47:17 UTC |
| 7× | Request completed — 500 · could not update document metadata for doc id 5e8b6a30-080e-4d35-9878-e57e75108c3d: could not … since 2026-10-08 19:24:13 UTC |
| 7× | could not update document metadata for doc id b59d0e97-516c-41b7-a96b-2fc113fc1bbe: could not update the document: Eithe… since 2026-11-13 04:59:59 UTC |
| 3× | could not update document metadata for doc id 3b6cc256-1e7a-4e3d-af36-34264f3800fc: could not update document for catego… since 2026-11-13 04:59:57 UTC |
| 1× | message was never published because transaction was never committed since 2026-11-17 08:36:31 UTC |
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
| source | rollup |
| collected_at | 1794888882 |
| age_seconds | 109 |
| stale | False |
| shown | None |
| total | None |
| truncated | False |
| coverage_from | None |
| retain_days | None |
| note | None |
| detector | outliers |