Tracing
Instrument your main application with the dd-trace-js
library. See Tracing Node.js applications for instructions.
Metrics
Custom metrics are also collected through the tracer. See the code examples.
Logs
The Datadog sidecar uses file tailing to collect logs. Datadog recommends writing application logs to /home/LogFiles/
because this directory is persisted across restarts.
You can also create a subdirectory, such as /home/LogFiles/myapp
, if you want more control over what is sent to Datadog. However, if you do not tail all log files in /home/LogFiles
, then Azure App Service application logs related to startups and errors are not collected.
To set up logging in your application, see Node.js Log Collection. To set up trace log correlation, see Correlating Node.js Logs and Traces.
Tracing
Instrument your main application with the dd-trace-py
library. See Tracing Python applications for instructions.
Metrics
Custom metrics are also collected through the tracer. See the code examples.
Logs
The Datadog sidecar uses file tailing to collect logs. Datadog recommends writing application logs to /home/LogFiles/
because this directory is persisted across restarts.
You can also create a subdirectory, such as /home/LogFiles/myapp
, if you want more control over what is sent to Datadog. However, if you do not tail all log files in /home/LogFiles
, then Azure App Service application logs related to startups and errors are not collected.
To set up logging in your application, see Node.js Log Collection. To set up trace log correlation, see Correlating Node.js Logs and Traces.
Tracing
Instrument your main application with the dd-trace-java
library. See Tracing Java applications for instructions.
Metrics
Custom metrics are also collected through the tracer. See the code examples.
Logs
The Datadog sidecar uses file tailing to collect logs. Datadog recommends writing application logs to /home/LogFiles/
because this directory is persisted across restarts.
You can also create a subdirectory, such as /home/LogFiles/myapp
, if you want more control over what is sent to Datadog. However, if you do not tail all log files in /home/LogFiles
, then Azure App Service application logs related to startups and errors are not collected.
To set up logging in your application, see Node.js Log Collection. To set up trace log correlation, see Correlating Node.js Logs and Traces.
Tracing
Instrument your main application with the dd-trace-go
library. See Tracing Go applications for instructions.
Metrics
Custom metrics are also collected through the tracer. See the code examples.
Logs
The Datadog sidecar uses file tailing to collect logs. Datadog recommends writing application logs to /home/LogFiles/
because this directory is persisted across restarts.
You can also create a subdirectory, such as /home/LogFiles/myapp
, if you want more control over what is sent to Datadog. However, if you do not tail all log files in /home/LogFiles
, then Azure App Service application logs related to startups and errors are not collected.
To set up logging in your application, see Node.js Log Collection. To set up trace log correlation, see Correlating Node.js Logs and Traces.
Tracing
Instrument your main application with the dd-trace-php
library. See Tracing PHP applications for instructions.
Metrics
Custom metrics are also collected through the tracer. See the code examples.
Logs
The Datadog sidecar uses file tailing to collect logs. Datadog recommends writing application logs to /home/LogFiles/
because this directory is persisted across restarts.
You can also create a subdirectory, such as /home/LogFiles/myapp
, if you want more control over what is sent to Datadog. However, if you do not tail all log files in /home/LogFiles
, then Azure App Service application logs related to startups and errors are not collected.
To set up logging in your application, see Node.js Log Collection. To set up trace log correlation, see Correlating Node.js Logs and Traces.