SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

Hi team!
Is it expected, when exporting kubernetes metrics using <https://signoz.io/docs/tutorial/kubernetes-infra-metrics/|signoz/k8s-infra> to a self-hosted signoz deployment, that the
span_id and trace_id will be empty? Log events do not seem to contain trace_id and therefore the "Go to related logs" does not work.

yes, it is expected. Automatic log collection enabled by k8s-infra uses filelog receiver, and it would not be possible to have correlation between  the logs and traces.

You will have to collect logs from the OTEL SDK itself for this.

cc <@U03BTNACHNX>

In case you have trace_id, span_id in your logs in some pattern you can extract them using pipeline <https://signoz.io/docs/logs-pipelines/introduction/>

Ahh, now I understand. Thank you <@U02SS3ZAMKQ> and <@U03BTNACHNX>

`You will have to collect logs from the OTEL SDK itself for this.`

<@U02SS3ZAMKQ> Is there documentation that explains? Our applications do implement OTEL SDK for traces, exceptions and metrics.