4 ms·
Probably, but some critical errors like stack overflow or out of memory could prevent the stack from unwinding gracefully or otherwise prevent the accumulated l
by BonesJustice 8y ago
Probably, but some critical errors like stack overflow or out of memory could prevent the stack from unwinding gracefully or otherwise prevent the accumulated log from being written. And then you’d have nothing.
- dragonwriter 8y agoConceptually, if you separate out the application generating the log from the one constructing the structure, so that the former is still streaming individual messages with added context information and the latter (probably a log viewing application, so it is completely out of the critical path of recording information) uses context information to provide a structured view, then that's not a problem.
- dkersten 8y agoAlternatively, as others have mentioned, log as usual but include an instance id and then use an external service/process to aggregate log entries with the same id together.
- dragonwriter 8y agoThat's actually an example, not an alternative (the instance id is the “context information”, the external service/process is the separate component using the context information to construct the structured view.)
- dkersten 8y agoAh, good point.