This message was deleted.

@nitya-signoz may have more insights on this

Hi Dudu, if your logs already emit trace_id and span_id then you can use trace_parser operator to parse it https://signoz.io/docs/userguide/logs/#operators-for-parsing-and-manipulating-logs . Example : https://github.com/SigNoz/logs-benchmark/blob/596fe018b377b4635aeb555ccc8ec824122fd934/signoz/signoz-client/otel-collector-config.yaml#L22

Thanks @nitya-signoz. I’m still failing to understand who should be the initiator who should create these span_id and trace_parser fields where and at what point in flow.

Okay so your application should create the spans and the logger has to take care that it is adding trace_id and span_id to the logs that are getting generated. If you can describe what stack you are using for your applications we might be able to help you.

nestjs

So I am assuming that you have already instrumented your application with opentelemtry and already getting traces and spans, but you need that in logs as well.

Correct.

I think you should be able to do that by adding your headers and body as events in the span. @Vishal Sharma correct me if I am wrong here.

You can add them as attributes/tags @Devops Netapp

Thanks, this is very helpful.

Hi @Devops Netapp you can create a logger like this https://github.com/pragmaticivan/nestjs-otel-prom-grafana-tempo/tree/main/src/logger to add traceId and spanId to your logs