Description
The timestamp entry TS10 is defined in internal/metrics/schema.go with the label "CR.terminated", where the schema comment states that CR.* denotes the create phase. However, TS10 is captured inside reexecUnikontainer() in cmd/urunc/create.go, which runs in the reexec process — the RX phase. Any tooling that parses the metrics log by the timestampName field misattributes this timestamp to the wrong lifecycle phase.
Steps to reproduce
Visible in source at internal/metrics/schema.go (TS10 definition) and cmd/urunc/create.go (capture site).
Expected behavior: The TS10 label uses the RX.* prefix, consistent with the schema comment and the actual lifecycle phase in which it is captured.
Current behavior: TS10 is labeled "CR.terminated" but is captured in the reexec process (RX phase), causing incorrect phase attribution in metrics output.
Proposed solution: Change the TS10 label in internal/metrics/schema.go from "CR.terminated" to an appropriate RX.* label that describes the point in the reexec lifecycle where it is captured (e.g. "RX.container_hooks_done").
Description
The timestamp entry
TS10is defined ininternal/metrics/schema.gowith the label"CR.terminated", where the schema comment states thatCR.*denotes the create phase. However,TS10is captured insidereexecUnikontainer()incmd/urunc/create.go, which runs in the reexec process — theRXphase. Any tooling that parses the metrics log by thetimestampNamefield misattributes this timestamp to the wrong lifecycle phase.Steps to reproduce
Visible in source at
internal/metrics/schema.go(TS10 definition) andcmd/urunc/create.go(capture site).Expected behavior: The TS10 label uses the
RX.*prefix, consistent with the schema comment and the actual lifecycle phase in which it is captured.Current behavior: TS10 is labeled
"CR.terminated"but is captured in the reexec process (RXphase), causing incorrect phase attribution in metrics output.Proposed solution: Change the TS10 label in
internal/metrics/schema.gofrom"CR.terminated"to an appropriateRX.*label that describes the point in the reexec lifecycle where it is captured (e.g."RX.container_hooks_done").