To use APM, start by sending your traces to Datadog, and then configure your environment. You can send traces to Datadog in multiple different ways depending on your system setup: including using the Datadog Agent locally, on containers, and several other ways. For the full overview of all of the steps to set up APM, see the APM overview.
APM is enabled by default in Agent 6. If you are sending traces from a nonlocal environment (like a container), set
apm_non_local_traffic: true in your main
datadog.yaml configuration file.
To get an overview of all the possible settings for APM, take a look at the Agent’s
datadog.example.yaml configuration file. For all of the metrics sent to Datadog by the Agent, see APM metrics sent by the Datadog Agent. For more information about the Datadog Agent, see the Agent documentation or refer to the
datadog.yaml configuration template.
See the specific setup instructions to ensure that the Agent is configured to receive traces in a containerized environment:
For step-by-step instructions scoped to your deployment configuration (hosts, Docker, Kubernetes, or Amazon ECS), follow the Quickstart instructions within the Datadog app.
To set up Datadog APM in AWS Lambda, see the Tracing Serverless Functions documentation.
The Datadog extension for Azure App Services provides tracing capabilities for Azure Web Apps. For more information setting up tracing in Azure, see the Azure App Services Extension documentation.
Datadog APM requires sending trace data to a running Agent. A workaround for enabling trace collection for a serverless setup is to configure a separate VM that accepts trace traffic externally.
There are alternatives to the Agent and containers that you can use to collect traces.
Tracing is enabled by default when monitoring with Heroku. For more information about configuring tracing for Heroku, see the Heroku cloud documentation.
Tracing is enabled by default when monitoring with Cloud Foundry. For more information about configuring tracing for Cloud Foundry, see the Cloud Foundry documentation.
Tracing is enabled by default when monitoring with AWS Elastic Beanstalk. For more information about configuring tracing for AWS Elastic Beanstalk, see the AWS Elastic Beanstalk documentation.
See our guide on setting the
env tag and an additional primary tag for scoping APM data.
Additional helpful documentation, links, and articles: