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 14:21:51.
› →|
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.

Neo4j schema production

Every Go service creates the constraints and indexes for the labels it owns when it boots, by reading the live schema (main #16243). A constraint the data violates does not fail the boot: a standby _idx index stands in and the object reads DEGRADED until the rows are fixed — often by a data migration that needs a person. This page shows what each service found on its latest boot, what is blocking each degraded object, and how the clusters compare. UNEXPECTED objects (in the database, not in the model) are informational — usually an older key waiting on its two-release retirement — and never make a service unhealthy.

Last refreshed never · read every 6 h — only the minutes around each service start
Services healthy
12 / 12
every owned object is in place
Objects not in place
0
0 degraded · 0 drift · 0 failed
Migrations waiting on a person
0
0 failed · 0 blocked · 0 pending
Objects in place
623
1 created on the latest boots · 2 undeclared (informational)

Newest boot 2 days ago. Convergence runs only at boot, so a report is what the service found when it last started — data fixed since then shows on its next boot.

Services 12

One row per owning service, unhealthy first. The bar is every object the service owns, by what convergence found.

presentcreatedretireddegradeddriftfailedunexpected
servicestateobjectsnot in place data migrationsreportedearlier boots
docsvc healthy
71 objects
—
3 / 3 applied · counted
3 applied on earlier boots (counted, not listed)
2 days ago
boot · pod 4blr2
enrollsvc healthy
25 objects
— none declared 2 days ago
boot · pod 9z8pw
execsvc healthy
178 objects
—
8 / 8 applied · counted
6 applied on earlier boots (counted, not listed)
2 days ago
boot · pod fvtfj
finsvc healthy
27 objects
— none declared 2 days ago
boot · pod bcm7n
notifsvc healthy
23 objects
— none declared 2 days ago
boot · pod lbgkm
onboardingsvc healthy
77 objects
—
3 / 3 applied · counted
3 applied on earlier boots (counted, not listed)
2 days ago
boot · pod 5qfwx
patientsvc healthy
47 objects
— none declared 2 days ago
boot · pod c6snd
regsvc healthy
22 objects
— none declared 2 days ago
boot · pod vc5hn
schedsvc healthy
15 objects
— none declared 2 days ago
boot · pod 6fkkb
studiosvc healthy
91 objects
2 undeclared
8 / 8 applied · counted
7 applied on earlier boots (counted, not listed)
2 days ago
boot · pod dzcp8
tusker healthy
18 objects
—
1 / 1 applied · counted
1 applied on earlier boots (counted, not listed)
2 days ago
boot · pod wf9cf
workplansvc healthy
31 objects
—
2 / 2 applied · counted
2 applied on earlier boots (counted, not listed)
2 days ago
boot · pod j5hks

Data migrations

Each service's numbered data fixes, in order. A PENDING step is a manual action not yet done, FAILED gave up after its attempts, BLOCKED waits on an earlier one. The constraint a step enables stays degraded until it applies.

execsvc 8 of 8 applied · 6 applied on earlier boots (counted, not listed)
0007_questionnaire_variablename_backfill APPLIED · 1 attempt
enables Questionnaire_name_nodeId_treeId_variablename_deltimestamp
applied on this boot
→
0008_autoquery_eval_marker_seed APPLIED · 1 attempt
applied on this boot
studiosvc 8 of 8 applied · 7 applied on earlier boots (counted, not listed)
0008_autoquery_lineageid_backfill APPLIED · 1 attempt
applied on this boot

Created and retired on the latest boots 1

What convergence changed. A created constraint that replaced a standby index is a degraded object that healed — its data was fixed and the boot made the real constraint. Retired objects were declared obsolete by their owner and dropped.

objectchangeservicelabelpropertieswhen
Questionnaire_name_nodeId_treeId_variablename_deltimestamp
replaced standby index "Questionnaire_name_nodeId_treeId_variablename_deltimestamp_idx"
healed execsvcQuestionnaire namenodeIdtreeIdvariablenamedeltimestamp 2 days ago

Every cluster 7

Objects not in place per service and cluster (green = healthy). A problem on one dev cluster is stale data; the same one on production is the model. Click a cell for that cluster.

servicemasterautomationnexusproductiondeltatest27test26
advpsvc · ✓ · · · ✓ ✓
authz · · · · · · 3
budgetsvc · · · · · ✓ ·
docsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
enrollsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
execsvc 1 ✓ ✓ ✓ ✓ 1 1
finsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
notifsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
onboardingsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
patientsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
regsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
schedsvc ✓ ✓ ✓ ✓ ✓ ✓ ✓
studiosvc ✓ ✓ ✓ ✓ ✓ 2 ✓
tusker ✓ ✓ ✓ ✓ ✓ ✓ ✓
workplansvc ✓ ✓ ✓ ✓ ✓ 3 ✓

Undeclared objects 2

In the database, absent from the data model. Never dropped automatically: each is a pending retirement (declare it in schema_retired.go with its ReplacedBy) or something created outside the model. Not unhealthy.

studiosvc — 2
objectlabelproperties
ESign_archivedtimestamp_state_title_version_deltimestampESign archivedtimestampdeltimestampstatetitleversion
Trigger_state_version_deltimestamp_scope_operation_orgidTrigger stateversiondeltimestampscopeoperationorgid