---
title: Troubleshooting Serverless Monitoring for Azure Logic Apps
description: >-
  Diagnose missing traces and logs for Azure Logic Apps monitoring by verifying
  diagnostic settings, log forwarding, and APM span generation in Datadog.
breadcrumbs: >-
  Docs > Serverless > Serverless Monitoring for Azure Logic Apps >
  Troubleshooting Serverless Monitoring for Azure Logic Apps
---

# Troubleshooting Serverless Monitoring for Azure Logic Apps

## I cannot see any traces{% #i-cannot-see-any-traces %}

Follow these steps to diagnose why traces are not appearing in Datadog:

### 1. Verify that Diagnostic Settings are configured

Check that the Logic App has the required diagnostic setting:

1. In the Azure Portal, open your Logic App
1. Navigate to **Diagnostic settings** in the left menu
1. Verify that a diagnostic setting named `datadog_log_forwarding_<ID>` exists

{% image
   source="https://docs.dd-static.net/images/serverless/logic_apps/diagnostic_settings.a108506c2e6d50493c83c5a18bb87bb9.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/serverless/logic_apps/diagnostic_settings.a108506c2e6d50493c83c5a18bb87bb9.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Azure Logic App diagnostic settings showing datadog_log_forwarding configuration" /%}

This setting is automatically created by the [Datadog Azure Automated Log Forwarding](https://docs.datadoghq.com/logs/guide/azure-automated-log-forwarding.md) service. If it's missing, verify that you have installed the Azure Automated Log Forwarding service correctly.

### 2. Verify that Logic Apps logs are in Datadog

Check that logs are being forwarded to Datadog:

1. In Datadog, go to [**Logs > Live Tail**](https://app.datadoghq.com/logs/livetail)
1. Search for `@properties.resource.workflowId:*`
1. Trigger your Logic App workflow a few times if needed

If you don't see any logs:

- Verify that the Azure Automated Log Forwarding service is properly configured

### 3. Verify that APM spans exist

Check that traces are being generated from the logs:

1. In Datadog, go to [**APM > Traces**](https://app.datadoghq.com/apm/traces?query=operation_name%3Aazure.logicapps)
1. Select **Live Search** in the upper right corner
1. Search for `operation_name:azure.logicapps`

If you see logs but no traces, wait a few minutes for logs to be processed and traces to be generated

## Additional troubleshooting tips{% #additional-troubleshooting-tips %}

### Logs are not appearing in Datadog{% #logs-are-not-appearing-in-datadog %}

If logs are not appearing in Datadog:

1. **Verify the Azure Automated Log Forwarding setup**: Ensure that the Event Hubs namespace and Datadog destination are properly configured
1. **Check diagnostic settings logs category**: The diagnostic setting should be capturing `WorkflowRuntime` logs

### Traces are missing intermittently{% #traces-are-missing-intermittently %}

If traces appear inconsistently:

1. **Add a retention filter**: Create a [retention filter](https://docs.datadoghq.com/tracing/trace_pipeline/trace_retention.md#retention-filters) with the query `operation_name:azure.logicapps` to ensure traces are retained
1. **Set retention rate**: For debugging, set the retention rate to 100%
1. **Check sampling**: Verify that traces aren't being dropped due to sampling configurations

### Tags are not appearing on traces{% #tags-are-not-appearing-on-traces %}

If `env` and `service` tags are not appearing on your traces:

1. **Verify tags in Azure**: Check that the tags are correctly set on the Logic App in the Azure Portal
1. **Wait for propagation**: Tag changes may take 30 minutes to propagate to new executions
1. **Trigger new executions**: Invoke the workflow again after setting tags

## Need more help?{% #need-more-help %}

For further questions or issues not covered here, contact [Datadog support][5].