For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/serverless/logic_apps/troubleshooting.md. A documentation index is available at /llms.txt.

Troubleshooting Serverless Monitoring for Azure Logic Apps

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
  2. Navigate to Diagnostic settings in the left menu
  3. Verify that a diagnostic setting named datadog_log_forwarding_<ID> exists
Azure Logic App diagnostic settings showing datadog_log_forwarding configuration

This setting is automatically created by the Datadog Azure Automated Log Forwarding 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
  2. Search for @properties.resource.workflowId:*
  3. 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
  2. Select Live Search in the upper right corner
  3. 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

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
  2. Check diagnostic settings logs category: The diagnostic setting should be capturing WorkflowRuntime logs

Traces are missing intermittently

If traces appear inconsistently:

  1. Add a retention filter: Create a retention filter with the query operation_name:azure.logicapps to ensure traces are retained
  2. Set retention rate: For debugging, set the retention rate to 100%
  3. Check sampling: Verify that traces aren’t being dropped due to sampling configurations

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
  2. Wait for propagation: Tag changes may take 30 minutes to propagate to new executions
  3. Trigger new executions: Invoke the workflow again after setting tags

Need more help?

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