Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 3 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 21:44:14.
› →|
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 on master has served nothing for 1.7 h; at this hour it normally serves about 144 calls/hour

warning Service gone silent master resolved impact 39 Owner: Prasad Limaye (backup: Harish Kumar) opened 76d ago · last observed 2d ago · observed 108× · #650 · 91510f161fff0411bcac

What happened template

docsvc on master has served no API calls for 100 minutes (last call 2026-11-16 17:00 UTC); at this hour of the week its baseline — 4 weeks of history — expects about 144 calls an hour, 72 in the window checked. It carried 10.1% of the cluster's calls over the last week. A deploy landed just before the silence began — see the facts. Silence is not measured downtime: the pods may be up and unused, or crashed, or cut off upstream — Reliability and Pods say which. It resolves on its own once the service serves again.

A service that normally serves requests at this hour has served none for the sustain window — down, or cut off.

The facts

servicedocsvc
silent_minutes100
silent_since1,794,848,700
last_call_at1,794,848,400
expected_calls_in_window72.00
expected_per_hour144.00
baseline_weeks4
buckets_checked6
share_of_api_calls_7d0.10
discriminator
window2026-11-16 18:15:00 UTC → 2026-11-16 18:45:00 UTC

Adjacent deploys — adjacency, not proof

automateddocsvc · 57 min before

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 18:15:00 UTC → 2026-11-16 18:45:00 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

All docsvc errors, grouped → · service page · its logs

The story — No docsvc deploy or hand change is recorded in the hour before this opened. Everything below is docsvc only.

History

  • 2026-11-16 18:32:09 UTCreopened x-ray · severity=warning was=warning title=docsvc on master has served nothing for 1.3 h; at this hour it normally serves about 129 calls/hour level=medium was_level=medium finding={'id': 650, 'fingerprint': '91510f161fff0411bcac', 'kind': 'service.silent', 'severity': 'warning', 'cluster': 'master', 'subject': 'docsvc', 'title': 'docsvc on master has served nothing for 1.3 h; at this hour it normally serves about 129 calls/hour', 'facts': {'service': 'docsvc', 'silent_minutes': 80, 'silent_since': 1794848700, 'last_call_at': 1794848400, 'expected_calls_in_window': 64.5, 'expected_per_hour': 129.0, 'baseline_weeks': 4, 'buckets_checked': 6, 'share_of_api_calls_7d': 0.1017, 'recent_deploys': [{'who': 'automated', 'resource': 'docsvc', 'image': None, 'revision': '34ce8df3df2b2274f56808cd961b860ac4434500', 'ts': 1794845262, 'minutes_before': 57}], 'window': [1794851700, 1794853500], 'discriminator': ''}, 'evidence': [{'label': 'docsvc overview', 'href': '/service/docsvc?cluster=master&range=24h'}, {'label': 'Reliability', 'href': '/reliability?cluster=master&range=24h'}, {'label': 'docsvc logs', 'href': '/logs?cluster=master&service=docsvc&range=24h'}], 'provenance': {'source': 'rollup', 'collected_at': 1794853851, 'age_seconds': 105, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 34.0, 'status': 'open', 'first_seen': 1788412810, 'last_seen': 1794853929, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 105, 'narrative': "docsvc on master has served no API calls for 75 minutes (last call 2026-11-09 17:00 UTC); at this hour of the week its baseline — 4 weeks of history — expects about 212 calls an hour, 106 in the window checked. It carried 7.5% of the cluster's calls over the last week. Silence is not measured downtime: the pods may be up and unused, or crashed, or cut off upstream — Reliability and Pods say which. It resolves on its own once the service serves again.", 'narrative_kind': 'template', 'discriminator': '', 'level': 'medium', 'told_level': None, 'episode_at': 1794853929, 'chat_thread': None, 'kind_label': 'Service gone silent', 'group': 'Reliability', 'age_s': 6441145, 'stale_s': 26}
  • 2026-11-16 19:14:41 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 650, 'fingerprint': '91510f161fff0411bcac', 'kind': 'service.silent', 'severity': 'warning', 'cluster': 'master', 'subject': 'docsvc', 'title': 'docsvc on master has served nothing for 1.7 h; at this hour it normally serves about 144 calls/hour', 'facts': {'service': 'docsvc', 'silent_minutes': 100, 'silent_since': 1794848700, 'last_call_at': 1794848400, 'expected_calls_in_window': 72.0, 'expected_per_hour': 144.0, 'baseline_weeks': 4, 'buckets_checked': 6, 'share_of_api_calls_7d': 0.1006, 'recent_deploys': [{'who': 'automated', 'resource': 'docsvc', 'image': None, 'revision': '34ce8df3df2b2274f56808cd961b860ac4434500', 'ts': 1794845262, 'minutes_before': 57}], 'window': [1794852900, 1794854700], 'discriminator': ''}, 'evidence': [{'label': 'docsvc overview', 'href': '/service/docsvc?cluster=master&range=24h'}, {'label': 'Reliability', 'href': '/reliability?cluster=master&range=24h'}, {'label': 'docsvc logs', 'href': '/logs?cluster=master&service=docsvc&range=24h'}], 'provenance': {'source': 'rollup', 'collected_at': 1794855211, 'age_seconds': 115, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 39.0, 'status': 'resolved', 'first_seen': 1788412810, 'last_seen': 1794855299, 'resolved_at': 1794856481, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 108, 'narrative': "docsvc on master has served no API calls for 100 minutes (last call 2026-11-16 17:00 UTC); at this hour of the week its baseline — 4 weeks of history — expects about 144 calls an hour, 72 in the window checked. It carried 10.1% of the cluster's calls over the last week. A deploy landed just before the silence began — see the facts. Silence is not measured downtime: the pods may be up and unused, or crashed, or cut off upstream — Reliability and Pods say which. It resolves on its own once the service serves again.", 'narrative_kind': 'template', 'discriminator': '', 'level': 'medium', 'told_level': None, 'episode_at': 1794853929, 'chat_thread': None, 'kind_label': 'Service gone silent', 'group': 'Reliability', 'age_s': 6443699, 'stale_s': 1210}

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_at1794855211
age_seconds115
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectorservice_silent