Start-up is not traced #374

Closed
opened 2026-10-25 08:56:28 -07:00 by rays · 1 comment
Owner

Found reviewing what production's traces and metrics leave out, 2026-10-25. Opening the database, creating what is missing and the catalogue's repairs (retire_stranded, regroup_unmanaged) run before the daemon serves and have no trace, so how long a deploy took to come back, and what held it, are unknown. Wanted: a start-up trace with a span each.

Found reviewing what production's traces and metrics leave out, 2026-10-25. Opening the database, creating what is missing and the catalogue's repairs (retire_stranded, regroup_unmanaged) run before the daemon serves and have no trace, so how long a deploy took to come back, and what held it, are unknown. Wanted: a start-up trace with a span each.
rays added the enhancement label 2026-10-25 08:56:28 -07:00
Author
Owner

Fixed in dd91602: a start trace from open_database and assemble_config through the repairs to daemon started; production's first was 347 ms. Deployed 2026-10-25.

Fixed in dd91602: a start trace from open_database and assemble_config through the repairs to daemon started; production's first was 347 ms. Deployed 2026-10-25.
rays closed this issue 2026-10-25 09:35:55 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#374