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-19 13:21:17.
› →|
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

studiosvc shape 8D3802C7: p95 1.73 s now vs 746 ms earlier (2.3×, 232 runs)

warning Query shape degrading master resolved impact 26 Owner: Suresh Boddapati (backup: Madhava Mukkamala) opened 2d ago · last observed 2d ago · observed 3× · #17387 · 06b6a3600892dddd512a

What happened template

A studiosvc query shape on master has p95 1.7 s in the second half of the window against 746 ms in the first (2.3×, 232 executions). The shape reads: “MATCH (proto:FormV2 {tildaid: $protoId})-[pr:PROTOCOL_TO_GRAPH_NODE_REF]->(ref:GraphNodeRef) MATCH (ref)-[:GRAPH_NODE_RE…”. Slower can mean more data, a lost index, or lock contention — the shape page has the CPU/wait split. Shapes whose p95 stays under a second are never reported: below that nobody notices, whatever the ratio.

A Cypher shape whose p95 is worsening across the window and is at least 1 s now; spikes under a second are ignored.

First look — investigated before anyone looked

Cause not clear from logs and recent changes; Neo4j read shape 8D3802C7 in studiosvc (FormV2 -> GraphNodeRef -> target lookup by tildaid) slowed from p95 450 ms to 2.05 s (4.6x, 289 runs) in the window ending 2026-11-16 10:19 UTC.
Checked: 0 studiosvc error lines in the window and no other findings within 30 min.
The 4 deploys in the prior 24 h were autosync config-only (latest b82321d7eadd at 08:05 UTC, 133 min before), with no image or commit change and nothing linking them to this query.
Other studiosvc shapes (6FFE6352, 3D9AC821) have also been degrading since 2026-11-13, which points to the database or data growth rather than one change.
Next step: open the shape page, compare the plan and per-run timings early vs late in the window, and check whether specific $protoId values or large $targetIds lists drive the slow runs.

low confidence

claude-opus-5-5 · 2d ago · $0.03 — every link above is evidence it read; nothing else was claimed.

The facts

servicestudiosvc
plan_hash8D3802C7
queries232
floor_ms1,000
p95_early745.83
p95_late1,725
ratio2.31
avg_ms130.71
sampleMATCH (proto:FormV2 {tildaid: $protoId})-[pr:PROTOCOL_TO_GRAPH_NODE_REF]->(ref:GraphNodeRef) MATCH (ref)-[:GRAPH_NODE_REF_TO_GRAPH_NODE|GRAPH_NODE_REF_TO_QUESTION {protocolid: $protoId}]->(target) WHERE (target:QuestionV2 OR target:ResponseSet OR target:FormV2) AND target.tildaid IN $targetIds RETURN target.tildaid AS tid, ref.tildaid AS refId, pr.path AS path
rwread
discriminator8D3802C7
window2026-11-16 05:24:39 UTC → 2026-11-16 11:24:39 UTC

What is failing in studiosvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from studiosvc. In this finding's window (2026-11-16 05:24:39 UTC → 2026-11-16 11:24:39 UTC) there were 7; every line links to the grouped errors behind it.

GET /api/studio/activities/:id 4 bad of 742 calls · 57% of the service's 5xx
POST /api/studio/graph/:id/nodeAction 2 bad of 50 calls · 29% of the service's 5xx
GET /api/studio/protocols/:id/visits/:id 1 bad of 599 calls · 14% of the service's 5xx

The error shapes behind them

249× http error response returned to client since 2026-10-06 15:35:21 UTC
95× Could not read from db — Pool could not find any servers to connect to since 2026-11-13 05:41:56 UTC
45× Request completed — 500 · failed to fetch Visit detail. error: Pool could not find any servers to connect to since 2026-11-13 05:41:57 UTC
20× Request completed — 500 · failed to fetch Activity detail. error: Pool could not find any servers to connect to since 2026-11-13 17:09:11 UTC
10× failed to fetch form summary — form 5a4d37c2-3a02-4293-bffb-9028257cc51d not found since 2026-11-04 14:46:50 UTC

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

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

  • 2026-11-16 10:00:00 UTClatency studiosvc p95 peaked at ≥ 2.0 min
  • 2026-11-16 10:19:38 UTCthis finding studiosvc shape 8D3802C7: p95 1.73 s now vs 746 ms earlier (2.3×, 232 runs)

History

  • 2026-11-16 10:19:38 UTCopened x-ray · severity=critical title=studiosvc shape 8D3802C7: p95 2.05 s now vs 450 ms earlier (4.6×, 289 runs) finding={'id': 17387, 'fingerprint': '06b6a3600892dddd512a', 'kind': 'shape.degrading', 'severity': 'critical', 'cluster': 'master', 'subject': 'studiosvc', 'title': 'studiosvc shape 8D3802C7: p95 2.05 s now vs 450 ms earlier (4.6×, 289 runs)', 'facts': {'service': 'studiosvc', 'plan_hash': '8D3802C7', 'queries': 289, 'floor_ms': 1000, 'p95_early': 450.0, 'p95_late': 2049.9999999999973, 'ratio': 4.555555555555549, 'avg_ms': 104.43944636678201, 'sample': 'MATCH (proto:FormV2 {tildaid: $protoId})-[pr:PROTOCOL_TO_GRAPH_NODE_REF]->(ref:GraphNodeRef) MATCH (ref)-[:GRAPH_NODE_REF_TO_GRAPH_NODE|GRAPH_NODE_REF_TO_QUESTION {protocolid: $protoId}]->(target) WHERE (target:QuestionV2 OR target:ResponseSet OR target:FormV2) AND target.tildaid IN $targetIds RETURN target.tildaid AS tid, ref.tildaid AS refId, pr.path AS path', 'rw': 'read', 'window': [1794802778, 1794824378], 'recent_deploys': [], 'discriminator': '8D3802C7'}, 'evidence': [{'label': 'Query shape', 'href': '/neo/shape/8D3802C7?cluster=master&from=1794802778&to=1794824378'}, {'label': 'Degrading shapes', 'href': '/neo/queries?cluster=master&from=1794802778&to=1794824378&order=degrading'}], 'provenance': {'source': 'rollup', 'collected_at': 1794823281, 'age_seconds': 1102, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 42.0, 'status': 'open', 'first_seen': 1794824378, 'last_seen': 1794824378, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 1, 'narrative': None, 'narrative_kind': None, 'discriminator': '8D3802C7', 'level': 'medium', 'told_level': None, 'episode_at': 1794824378, 'chat_thread': None, 'kind_label': 'Query shape degrading', 'group': 'Neo4j', 'age_s': 5, 'stale_s': 5}
  • 2026-11-16 14:10:27 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 17387, 'fingerprint': '06b6a3600892dddd512a', 'kind': 'shape.degrading', 'severity': 'warning', 'cluster': 'master', 'subject': 'studiosvc', 'title': 'studiosvc shape 8D3802C7: p95 1.73 s now vs 746 ms earlier (2.3×, 232 runs)', 'facts': {'service': 'studiosvc', 'plan_hash': '8D3802C7', 'queries': 232, 'floor_ms': 1000, 'p95_early': 745.8333333333323, 'p95_late': 1725.0000000000014, 'ratio': 2.312849162011178, 'avg_ms': 130.70689655172413, 'sample': 'MATCH (proto:FormV2 {tildaid: $protoId})-[pr:PROTOCOL_TO_GRAPH_NODE_REF]->(ref:GraphNodeRef) MATCH (ref)-[:GRAPH_NODE_REF_TO_GRAPH_NODE|GRAPH_NODE_REF_TO_QUESTION {protocolid: $protoId}]->(target) WHERE (target:QuestionV2 OR target:ResponseSet OR target:FormV2) AND target.tildaid IN $targetIds RETURN target.tildaid AS tid, ref.tildaid AS refId, pr.path AS path', 'rw': 'read', 'window': [1794806679, 1794828279], 'recent_deploys': [], 'discriminator': '8D3802C7'}, 'evidence': [{'label': 'Query shape', 'href': '/neo/shape/8D3802C7?cluster=master&from=1794806679&to=1794828279'}, {'label': 'Degrading shapes', 'href': '/neo/queries?cluster=master&from=1794806679&to=1794828279&order=degrading'}], 'provenance': {'source': 'rollup', 'collected_at': 1794827926, 'age_seconds': 359, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 26.2, 'status': 'resolved', 'first_seen': 1794824378, 'last_seen': 1794828279, 'resolved_at': 1794838227, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 3, 'narrative': 'A studiosvc query shape on master has p95 1.7 s in the second half of the window against 746 ms in the first (2.3×, 232 executions). The shape reads: “MATCH (proto:FormV2 {tildaid: $protoId})-[pr:PROTOCOL_TO_GRAPH_NODE_REF]->(ref:GraphNodeRef) MATCH (ref)-[:GRAPH_NODE_RE…”. Slower can mean more data, a lost index, or lock contention — the shape page has the CPU/wait split. Shapes whose p95 stays under a second are never reported: below that nobody notices, whatever the ratio.', 'narrative_kind': 'template', 'discriminator': '8D3802C7', 'level': 'low', 'told_level': None, 'episode_at': 1794824378, 'chat_thread': None, 'kind_label': 'Query shape degrading', 'group': 'Neo4j', 'age_s': 13854, 'stale_s': 9953}

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_at1794827926
age_seconds359
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectorshapes