Microsoft Azure App Services is a group of serverless resources that enable you to build and host web apps, mobile back ends, event-driven functions, and RESTful APIs without managing infrastructure. It can host workloads of all sizes and offers auto-scaling and high availability options.
Datadog provides monitoring capabilities for all Azure App Services resource types:
The Datadog extension for Azure App Services provides additional monitoring capabilities for Azure Web Apps. This support includes:
Trace_IDinjection into application logs.
The Datadog .NET APM extension supports the following .NET runtimes in both x64 and x86 architectures when running on Windows instances (AAS does not yet support extensions on Linux). For more details about automatically instrumented libraries, see the Tracer documentation.
DD_API_KEYand a value of your Datadog API Key.
DD_SITEwith datadoghq.eu as the value. By default, the extension submits data to the US Datadog site (the datadoghq.com domain). So if you use the US Datadog site, there is no additional application setting required.
Logs for Azure Web Apps can be submitted to Datadog with Eventhub using the process described in the Azure Integration documentation. Note: The Eventhub must be located in the same region as your web application.
Once the Eventhub and forwarder function are configured, create a diagnostic setting for your web application. Select the logs you want to send to Datadog:
Once you establish the logging pipeline for your application, Trace ID injection allows you to connect logs and traces in Datadog. To enable this with the extension, add an application setting
Note: Trace ID injection occurs in the application, so application logs include the trace ID. Other categories of diagnostic logs available from Azure, like HTTP logs and audit logs, do not include the trace ID.
If your app begins throwing 5XX errors immediately after installation, first try to reinstall with the application in a full stop. To do this:
A clean install to a stopped app typically solves the problem. However, if you’re still getting 5XX errors, it may be related to something like an enabled debug setting, which can slow down the startup time of your application, and can result in a 500 error. You can also try:
If you’re missing traces or not receiving them at all, make sure you have not manually adjusted any port settings. The Tracer Agent, in the extension, communicates with your application to identify the correct port to use for external traffic. Manual port settings can interfere with this process resulting in missed traces.
Still need help? Contact Datadog support.