Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 14 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-20 02:02:10.
› →|
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

pubsub.dashboards-test26-dashsub: 6 failed runs in the last 6 h — message type retired, no longer ingested

warning Background job failing test26 resolved impact 25 opened 63d ago · last observed 2d ago · observed 39× · #1698 · 2b88c0f5f279f0bc3ba8

What happened template

The background job pubsub.dashboards-test26-dashsub on test26 failed 6 runs recently (206 failure lines; lines within one run count once), detected via its structured error/exception field (below ERROR severity). A job that logs its failures below ERROR severity — a WARNING carrying an error field — is invisible to the novel-shape detector and to the page's own failed count; this detector reads the error field itself, which is why the finding now appears. The sample failure is in the facts.

A named background job whose runs keep failing (error-severity bursts) in the last hour — volume, not novelty; the novel-shape detector only fires the first time.

The facts

jobpubsub.dashboards-test26-dashsub
servicedashrsvc
failed_runs6
error_lines206
samplemessage type retired, no longer ingested
error_signaturemessage type retired, no longer ingested
failing_atqueue/pubsub.go:63
traceprojects/tilda-trial-dev/traces/778d33c9f2017298ad41523edab771a2
detected_viastructured error/exception field (below ERROR severity)
notea run is a burst of lines that truly look like failures — an error/exception field, an error-worded message, or a failure status; lines within one burst count as one run. Lines a job dumps at ERROR that are neither (the steps that SUCCEEDED, banner rules) are ignored, so a service that logs its whole context on failure is not miscounted. `failing_at` is the call site those failures came from — for a coarse job (one set_job wrapping a pipeline) more specific than the job name.
discriminator
window2026-11-16 01:26:53 UTC → 2026-11-16 07:26:53 UTC

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

History

  • 2026-11-16 02:09:59 UTCreopened x-ray · severity=warning was=warning title=pubsub.dashboards-test26-dashsub: 5 failed runs in the last 6 h — message type retired, no longer ingested level=medium was_level=medium finding={'id': 1698, 'fingerprint': '2b88c0f5f279f0bc3ba8', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'test26', 'subject': 'pubsub.dashboards-test26-dashsub', 'title': 'pubsub.dashboards-test26-dashsub: 5 failed runs in the last 6 h — message type retired, no longer ingested', 'facts': {'job': 'pubsub.dashboards-test26-dashsub', 'service': 'dashrsvc', 'failed_runs': 5, 'error_lines': 7, 'sample': 'message type retired, no longer ingested', 'error_signature': 'message type retired, no longer ingested', 'failing_at': 'queue/pubsub.go:63', 'trace': 'projects/tilda-trial-dev/traces/c4facbeefc81cae5413fdeae29794899', 'detected_via': 'structured error/exception field (below ERROR severity)', 'window': [1794773399, 1794794999], 'note': 'a run is a burst of lines that truly look like failures — an error/exception field, an error-worded message, or a failure status; lines within one burst count as one run. Lines a job dumps at ERROR that are neither (the steps that SUCCEEDED, banner rules) are ignored, so a service that logs its whole context on failure is not miscounted. `failing_at` is the call site those failures came from — for a coarse job (one set_job wrapping a pipeline) more specific than the job name.', 'discriminator': ''}, 'evidence': [{'label': "This job's page", 'href': '/jobs/pubsub.dashboards-test26-dashsub?cluster=test26&from=1794773399&to=1794794999'}, {'label': 'Background jobs', 'href': '/jobs?cluster=test26&from=1794773399&to=1794794999'}, {'label': 'Its error logs', 'href': '/logs?cluster=test26&from=1794773399&to=1794794999&severity=ERROR&q=pubsub.dashboards-test26-dashsub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-dev/traces/c4facbeefc81cae5413fdeae29794899?cluster=test26'}], 'provenance': {'source': 'live', 'collected_at': None, 'age_seconds': None, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': 'error-severity job lines from BigQuery, last hour, burst-grouped per job'}, 'impact': 20.0, 'status': 'open', 'first_seen': 1789550648, 'last_seen': 1794794999, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 34, 'narrative': "The background job pubsub.dashboards-test26-dashsub on test26 failed 5 runs recently (63 failure lines; lines within one run count once), detected via its structured error/exception field (below ERROR severity). A job that logs its failures below ERROR severity — a WARNING carrying an error field — is invisible to the novel-shape detector and to the page's own failed count; this detector reads the error field itself, which is why the finding now appears. The sample failure is in the facts.", 'narrative_kind': 'template', 'discriminator': '', 'level': 'medium', 'told_level': None, 'episode_at': 1794794999, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 5244406, 'stale_s': 55}
  • 2026-11-16 08:28:23 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 1698, 'fingerprint': '2b88c0f5f279f0bc3ba8', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'test26', 'subject': 'pubsub.dashboards-test26-dashsub', 'title': 'pubsub.dashboards-test26-dashsub: 6 failed runs in the last 6 h — message type retired, no longer ingested', 'facts': {'job': 'pubsub.dashboards-test26-dashsub', 'service': 'dashrsvc', 'failed_runs': 6, 'error_lines': 206, 'sample': 'message type retired, no longer ingested', 'error_signature': 'message type retired, no longer ingested', 'failing_at': 'queue/pubsub.go:63', 'trace': 'projects/tilda-trial-dev/traces/778d33c9f2017298ad41523edab771a2', 'detected_via': 'structured error/exception field (below ERROR severity)', 'window': [1794792413, 1794814013], 'note': 'a run is a burst of lines that truly look like failures — an error/exception field, an error-worded message, or a failure status; lines within one burst count as one run. Lines a job dumps at ERROR that are neither (the steps that SUCCEEDED, banner rules) are ignored, so a service that logs its whole context on failure is not miscounted. `failing_at` is the call site those failures came from — for a coarse job (one set_job wrapping a pipeline) more specific than the job name.', 'discriminator': ''}, 'evidence': [{'label': "This job's page", 'href': '/jobs/pubsub.dashboards-test26-dashsub?cluster=test26&from=1794792413&to=1794814013'}, {'label': 'Background jobs', 'href': '/jobs?cluster=test26&from=1794792413&to=1794814013'}, {'label': 'Its error logs', 'href': '/logs?cluster=test26&from=1794792413&to=1794814013&severity=ERROR&q=pubsub.dashboards-test26-dashsub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-dev/traces/778d33c9f2017298ad41523edab771a2?cluster=test26'}], 'provenance': {'source': 'live', 'collected_at': None, 'age_seconds': None, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': 'error-severity job lines from BigQuery, last hour, burst-grouped per job'}, 'impact': 25.0, 'status': 'resolved', 'first_seen': 1789550648, 'last_seen': 1794814013, 'resolved_at': 1794817703, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 39, 'narrative': "The background job pubsub.dashboards-test26-dashsub on test26 failed 6 runs recently (206 failure lines; lines within one run count once), detected via its structured error/exception field (below ERROR severity). A job that logs its failures below ERROR severity — a WARNING carrying an error field — is invisible to the novel-shape detector and to the page's own failed count; this detector reads the error field itself, which is why the finding now appears. The sample failure is in the facts.", 'narrative_kind': 'template', 'discriminator': '', 'level': 'medium', 'told_level': None, 'episode_at': 1794794999, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 5267110, 'stale_s': 3745}

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

sourcelive
collected_atNone
age_secondsNone
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteerror-severity job lines from BigQuery, last hour, burst-grouped per job
detectorjob_failing