Azure Logic Apps is a fully managed service, and the Datadog Agent cannot be directly installed on Logic Apps. However, Datadog can monitor Logic Apps through Azure diagnostic logs.

Prerequisites

• The Azure Automated Log Forwarding service must be installed

Setup

1. Install Datadog Azure Automated Log Forwarding

Follow the instructions in the Azure Automated Log Forwarding guide to install the service and setup tags for filtering the intended resource logs. Once installed, all new Logic Apps will automatically have log forwarding configured to send diagnostic logs to Datadog.

Note: The Azure Automated Log Forwarding service creates a diagnostic setting named datadog_log_forwarding_<ID> on each Logic App. This setting captures workflow execution logs and forwards them to Datadog.

2. Configure tags (optional but recommended)

Add service and env tags to your Logic Apps to organize and filter your workflows in Datadog.

1. In the Azure Portal, open your Logic App
2. Navigate to the Tags section
3. Add the following tags:
   • env: The environment name (for example, dev, staging, or prod)
   • service: The service name for your Logic App

The env tag is required to see traces in Datadog and defaults to dev if not set. The service tag defaults to the Logic App’s workflow name if not set.

3. Invoke the workflow

After configuring log forwarding, invoke your Logic App workflow a couple of times to generate execution data.

4. Verify traces in Datadog

Use Live Search in Datadog APM to verify that traces are being received:

1. Navigate to APM > Traces in Datadog
2. Use the query operation_name:azure.logicapps to filter for Logic Apps traces
3. Live Search returns all spans without sampling, so you should see your executions after they complete

Additional configuration

Add a retention filter for APM spans (recommended)

To control which traces are retained beyond the default live search period, add a retention filter:

1. In Datadog, search for Retention Filters (use Cmd+K and type “retention filters”)
2. Click Add Retention Filter
3. Set the filter query to operation_name:azure.logicapps
4. Add any additional filters for your service, such as service:<SERVICE_NAME> and env:<ENV_NAME>
5. Configure the retention rate based on your needs

Adding service and env tags to your retention filter helps save costs by retaining traces only for important environments and services.

See Trace Retention for more information.

Add a log index (recommended)

To enable searching and analyzing historic Logic Apps logs, create a dedicated log index:

1. In Datadog, search for Indexes (use Cmd+K and type “index”)
2. Navigate to Logs > Configuration > Indexes
3. Click New Index
4. Set the filter to @properties.resource.workflowId:*
5. Configure the index name and retention settings

See Log Indexes for more information.

Note: Indexing logs may incur additional costs. Consider your retention requirements and budget when configuring indexes.

See your Logic App traces in Datadog

After invoking your Logic App:

1. In Datadog, go to APM > Traces.
2. Select Live Search in the upper right corner.
3. Search for operation_name:azure.logicapps to find your traces.

If you cannot see your traces, see Troubleshooting.

Further Reading

Additional helpful documentation, links, and articles:

Azure IntegrationDOCUMENTATION Azure Automated Log ForwardingDOCUMENTATION