Xray
1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 1 hour▾
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 03:34:23.
› →|
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

workplansvc runs 28 foreground Neo4j queries per request (2,423 queries / 88 calls, last hour)

info N+1 fan-out automation resolved impact 12 Owner: Suresh Boddapati (backup: Madhava Mukkamala) opened 27d ago · last observed 4d ago · observed 21× · #5247 · cda05eda36b6a72dc186

What happened template

workplansvc on automation averaged 27.5 foreground Neo4j queries per API request over the last hour (2,423 queries for 88 calls). Dozens of queries per request is the N+1 signature: a round-trip per row instead of one query. The Journey page shows which screens pay for it, request by request.

One request that runs a large number of Neo4j queries.

The facts

serviceworkplansvc
qpr27.50
calls88.00
fg_queries2,423
bg_queries684.00
discriminator
window2026-11-15 02:26:54 UTC → 2026-11-15 03:26:54 UTC

What is failing in workplansvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from workplansvc. In this finding's window (2026-11-15 02:26:54 UTC → 2026-11-15 03:26:54 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

132× Failed to create workplan config — site 3aab23db-d69f-4946-b743-2613d2dccfef not found since 2026-10-20 01:14:02 UTC
8× work plan template name cannot be empty since 2026-09-15 01:46:21 UTC
8× Request completed — 500 · work plan template name cannot be empty since 2026-09-25 09:27:33 UTC
8× Request completed — 500 · could not create work plan type:work plan type name cannot be empty since 2026-09-25 09:21:59 UTC
8× could not create work plan type:work plan type name cannot be empty since 2026-09-15 01:41:21 UTC

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

History

  • 2026-11-15 03:26:54 UTCreopened x-ray · severity=info was=info title=workplansvc runs 28 foreground Neo4j queries per request (2,423 queries / 88 calls, last hour) level=low was_level=low finding={'id': 5247, 'fingerprint': 'cda05eda36b6a72dc186', 'kind': 'n1.fanout', 'severity': 'info', 'cluster': 'automation', 'subject': 'workplansvc', 'title': 'workplansvc runs 28 foreground Neo4j queries per request (2,423 queries / 88 calls, last hour)', 'facts': {'service': 'workplansvc', 'qpr': 27.5, 'calls': 88.0, 'fg_queries': 2423.0, 'bg_queries': 684.0, 'window': [1794709614, 1794713214], 'discriminator': ''}, 'evidence': [{'label': 'Neo4j by service', 'href': '/overview?cluster=automation&from=1794709614&to=1794713214'}, {'label': 'Journey (per-request Cypher)', 'href': '/journey?cluster=automation&from=1794709614&to=1794713214'}], 'provenance': {'source': 'rollup', 'collected_at': 1794713079, 'age_seconds': 142, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 6.6, 'status': 'open', 'first_seen': 1792675615, 'last_seen': 1794713214, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 21, 'narrative': 'workplansvc on automation averaged 28.2 foreground Neo4j queries per API request over the last hour (5,927 queries for 210 calls). Dozens of queries per request is the N+1 signature: a round-trip per row instead of one query. The Journey page shows which screens pay for it, request by request.', 'narrative_kind': 'template', 'discriminator': '', 'level': 'low', 'told_level': None, 'episode_at': 1794713214, 'chat_thread': None, 'kind_label': 'N+1 fan-out', 'group': 'Journey', 'age_s': 2037606, 'stale_s': 7}
  • 2026-11-15 20:17:28 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 5247, 'fingerprint': 'cda05eda36b6a72dc186', 'kind': 'n1.fanout', 'severity': 'info', 'cluster': 'automation', 'subject': 'workplansvc', 'title': 'workplansvc runs 28 foreground Neo4j queries per request (2,423 queries / 88 calls, last hour)', 'facts': {'service': 'workplansvc', 'qpr': 27.5, 'calls': 88.0, 'fg_queries': 2423.0, 'bg_queries': 684.0, 'window': [1794709614, 1794713214], 'discriminator': ''}, 'evidence': [{'label': 'Neo4j by service', 'href': '/overview?cluster=automation&from=1794709614&to=1794713214'}, {'label': 'Journey (per-request Cypher)', 'href': '/journey?cluster=automation&from=1794709614&to=1794713214'}], 'provenance': {'source': 'rollup', 'collected_at': 1794713079, 'age_seconds': 142, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 11.6, 'status': 'resolved', 'first_seen': 1792675615, 'last_seen': 1794713214, 'resolved_at': 1794773848, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 21, 'narrative': 'workplansvc on automation averaged 27.5 foreground Neo4j queries per API request over the last hour (2,423 queries for 88 calls). Dozens of queries per request is the N+1 signature: a round-trip per row instead of one query. The Journey page shows which screens pay for it, request by request.', 'narrative_kind': 'template', 'discriminator': '', 'level': 'low', 'told_level': None, 'episode_at': 1794713214, 'chat_thread': None, 'kind_label': 'N+1 fan-out', 'group': 'Journey', 'age_s': 2098240, 'stale_s': 60641}

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_at1794713079
age_seconds142
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectorfanout