- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
Automatic instrumentation allows you to create spans automatically for your application. It allows you to capture observability data from a wide range of standard operations and popular frameworks with minimal manual intervention. You can automatically instrument your application when you install the Datadog Agent with Single Step Instrumentation or when you manually add Datadog tracing libraries to your code.
Some situations when you might use automatic instrumentation include:
Follow the relevant documentation for your automatic instrumentation approach to learn more:
If you install or update a Datadog Agent with the Enable APM Instrumentation (beta) option selected, the Agent is installed and configured to enable APM. This allows you to automatically instrument your application, without any additional installation or configuration steps.
To get started, read the Single Step Instrumentation documentation.
To automatically instrument your application with Datadog libraries:
Install and configure the Datadog Agent to receive traces from your instrumented application. By default, the Datadog Agent is configured to receive traces in your datadog.yaml
file under apm_config
with enabled: true
and listens for trace data at http://localhost:8126
.
For containerized environments, follow the links below to enable trace collection within the Datadog Agent.
apm_non_local_traffic: true
in the apm_config
section of your main datadog.yaml
configuration file.The trace client attempts to send traces to the Unix domain socket /var/run/datadog/apm.socket
by default. If the socket does not exist, traces are sent to http://localhost:8126
.
If a different socket, host, or port is required, use the DD_TRACE_AGENT_URL
environment variable. For example:
DD_TRACE_AGENT_URL=http://custom-hostname:1234
DD_TRACE_AGENT_URL=unix:///var/run/datadog/apm.socket
Similarly, the trace client attempts to send stats to the /var/run/datadog/dsd.socket
Unix domain socket. If the socket does not exist, then stats are sent to http://localhost:8125
.
DD_SITE
in the Datadog Agent to
to ensure the Agent sends data to the right Datadog location.To set up Datadog APM in AWS Lambda, see the Tracing Serverless Functions documentation.
Tracing is available for several other environments, such as Heroku, Cloud Foundry, AWS Elastic Beanstalk, and Azure App Service.
For other environments, see the Integrations documentation for that environment and contact support if you are encountering any setup issues.
Set up your application to send traces using one of the following official Datadog tracing libraries:
To instrument an application written in a language that does not have official library support, see the list of community tracing libraries.
Additional helpful documentation, links, and articles: