Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 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:39: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

virtual-assistant: Neo4j queries per request 47.5 — 22.2× the fleet's usual 2.1 (also p95 latency (ms) 5.58 s)

info Service outlier test27 open impact 10 Owner: Sambasiva Bandarupalli (backup: Ahmed Aburaed) opened 84d ago · last observed 1d ago · observed 3064× · #114 · 046ddc9ae0be3b83e3bd

What happened template

virtual-assistant differs from the other 9 services on 2 measures over six hours: Neo4j queries per request 47.5 against the peers' 2.1 (18.5 MADs above); p95 latency (ms) 5.58 s against the peers' 518 ms (7.0 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': 47.471698113207545, 'value_fmt': '47.5', 'median': 2.1373737373737374, 'median_fmt': '2.1', 'mad': 2.4509052102815674, 'z': 18.496971725245004, 'direction': 'above', 'peers': 9}, {'measure': 'p95 latency (ms)', 'value': 5583.333333333324, 'value_fmt': '5.58 s', 'median': 518.1034482758573, 'median_fmt': '518 ms', 'mad': 724.9094983583705, 'z': 6.987396215014678, 'direction': 'above', 'peers': 9}
measureNeo4j queries per request
value47.47
value_fmt47.5
median2.14
median_fmt2.1
z18.50
directionabove
peers9
rule{"min_score": 3.5, "min_relative_pct": 35, "warn_on": []}
discriminator
window2026-11-16 11:27:13 UTC → 2026-11-16 17:27:13 UTC

What is failing in virtual-assistant — the bad events, decomposed

“Bad events” are HTTP 5xx answers from virtual-assistant. In this finding's window (2026-11-16 11:27:13 UTC → 2026-11-16 17:27:13 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

3× [DocumentSubscriber] Missing required fields in docsvc message since 2026-11-02 06:25:54 UTC
1× ❌ Tool 'update_work_order_properties' failed: This due date follows the training. Change it on the trainee in Training. since 2026-11-17 01:20:43 UTC

All virtual-assistant 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_at1794850029
age_seconds5
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers