이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Overview
There are two ways to define correlation between application traces and logs:
Follow the documentation on how to inject a Trace ID in the application logs. Log integrations automatically handle all remaining setup steps by default.
Use the trace remapper processor to define a log attribute as its associated trace ID.
Use cases
The Trace Remapper is typically used to select the Trace ID within a log message that needs first to be parsed with a Grok Parser.
API
Use the Datadog Log Pipeline API endpoint with the following trace remapper JSON payload:
{
"type": "trace-id-remapper",
"name": "Define dd.trace_id as the official trace id associated with this log",
"is_enabled": true,
"sources": ["dd.trace_id"]
}
| Parameter | Type | Required | Description |
|---|
type | String | Yes | Type of the processor. |
name | String | No | Name of the processor. |
is_enabled | Boolean | No | If the processor is enabled or not. Default: false. |
sources | Array of strings | No | Array of source attributes. Default: dd.trace_id. |
Note: Trace IDs and span IDs are not displayed in your logs or log attributes in the UI.
Further reading
