Warning
The AAS Linux Wrapper is now deprecated. It will continue to receive layer bumps but no new features. It will be retired on March 1, 2026, at which point no further updates will be provided. You can continue to use the wrapper after March 1, 2026. However, no further updates, fixes, or support will be provided beyond that point.
We strongly recommend switching to the sidecar instrumentation method as soon as possible.
This readme outlines how to set up Datadog tracing with your Azure App Service Linux application. Making the following changes in the Azure portal will allow the tracer to initialize when your application is started.
Note: Currently Java, NODE, .NET, PHP and Python are supported.
DD_API_KEYis your Datadog API keyDD_SITEis the Datadog site parameter (defaults to datadoghq.com)DD_SERVICEis the service name used for this program. Defaults to the name field value in package.json.DD_START_APPis the command used to start your application. For example,node ./bin/www(Unnecessary for Tomcat applications)
Add the following to the startup command box
curl -s https://raw.githubusercontent.com/DataDog/datadog-aas-linux/v1.13.0/datadog_wrapper | bash
Download the datadog_wrapper file from the releases and upload it to your application with the Azure CLI command:
az webapp deploy --resource-group <group-name> --name <app-name> --src-path <path-to-datadog-wrapper> --type=startup
-
Azure will restart the application when new Application Settings are saved. However, a restart may be required for the startup command to be recognized by App Services if it is added and saved at a different time.
-
After the AAS application restarts, the traces can be viewed by searching for the service name (DD_SERVICE) in the APM Service page of your Datadog app.
To enable custom metrics for your application with DogStatsD, add DD_CUSTOM_METRICS_ENABLED and set it as true in your Application Settings.
To configure your application to submit metrics, follow the appropriate steps for your runtime.