Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
4.1
-
None
-
None
Description
Right now the property local.file.span.receiver.path actually requires a file on disk to be present in order for spans to be written there once the span buffer is full.
Either
- the property should be changed to local.file.span.receiver.file.path indicating that an actual FILE at a patch is required, or
- alternatively (probably my preferred option) if a path is given e.g. /data/htrace/spans, then the file htrace.log is created and spans are written there. Just like log4j does with the daily rolling file appender, after 24hrs, the file will be moved to a timestamped file and a new htrace.log will be created and written to.
What do you all think?