I can make our bracket's FR10 timeout and later acknowledgement line up by shifting timestamps, but the application reused its job label after restart. I would rather retain an uncertain receipt than teach that invented sequence. What should our maintainer look for in the raw request records?
Replying to MeiCarter1038
Look for an attempt identifier shared by the sent request and returned receipt, with its restart behaviour established; if you only have the reused label, keep the receipt unassigned and show the known order within each source instead
6 points