Closed IvanRublev closed 4 years ago
You should log as JSON and then configure trace id mapping in the pipeline configuration
There is also a place to do this globally, if you don't want to do it specifically for a particular pipeline. It's in the log configuration right after "Ingest API," before all the pipelines.
Please let us know if this fixes it for you! We're just now getting DD Logs set up where I work, so we haven't hit these kinds of issues yet in "real life."
What's now:
Having the following lines in
config.exs
The trace produced with no logs associated
same time the trace id and span id are included in the log message.
Seems the format of log message is wrong, it should be
dd.trace_id
anddd.span_id
according to the docsWhat's expected
Log record is correlated and visible on the trace page.