이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.
Logs in Traces

The correlation between Datadog APM and Datadog Log Management is improved by the injection of trace IDs, span IDs, env, service, and version as attributes in your logs. With these fields you can find the exact logs associated with a specific service and version, or all logs correlated to an observed trace.

It is recommended to configure your application’s tracer with DD_ENV, DD_SERVICE, and DD_VERSION. This will provide the best experience for adding env, service, and version. See the unified service tagging documentation for more details.

Before correlating traces with logs, ensure your logs are either sent as JSON, or parsed by the proper language level log processor. Your language level logs must be turned into Datadog attributes in order for traces and logs correlation to work.

Note: Traces and logs are sampled independently. Even after correlation is configured, a log may contain a trace ID that refers to a trace that was not ingested or not retained due to trace sampling. This does not indicate a configuration error. For more information, see Log has a trace ID but the associated trace is missing.

To learn more about automatically or manually connecting your logs to your traces, select your language below:

Java
Python
go
Ruby
Node.js
.Net
PHP
OpenTelemetry