Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,590 questions
Azure Application Insight-Mulesoft Operation ID Missing
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 22%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJN%3C/text%3E%3C/svg%3E)
Jerick Naboya
0
Reputation points
We are currently using Azure Application Insights to capture logs from MuleSoft, and we've noticed that the operation_Id is missing in the results table. We've tried passing various headers (using Postman to MuleSoft) referenced from Microsoft article sources, such as traceparent, parent-id, id, trace-id, etc., but the operation_Id is still missing. The operation_Id is properly passed from our Java app, but once it reaches MuleSoft, it is always null.
We currently have these configured in our app:
ApplicationInsights.xml
log4j2.xml :
pom.xml :
Setup Reference : https://help.salesforce.com/s/articleView?id=001116858&language=en_US&type=1
Anything we're missing here so we can explicitly or passively set the operationId in order for it to show in Application Insight?
Thank you.
Azure Monitor
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 20%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPR%3C/text%3E%3C/svg%3E)
Pranay Reddy Madireddy 4,415 Reputation points Microsoft External Staff Moderator2025-05-08T13:03:51.5866667+00:00 Please confirm that headers such as traceparent and request-id are being correctly forwarded from your Java application to MuleSoft. These headers are essential for correlating telemetry and must be captured and propagated accurately.
Review you ApplicationInsights.xml configuration file to ensure that telemetry collection is correctly set up. Pay particular attention to context settings that impact how telemetry data is structured and linked.
Enable self-diagnostics in Application Insights at the DEBUG level. This can help identify if there are any issues during telemetry collection or processing. Logs generated can provide valuable insight into what might be going wrong.
MuleSoft may have specific behaviors or configurations affecting how incoming headers are processed. Please verify that MuleSoft is not stripping or modifying critical headers such as traceparent and request-id.
https://learn.microsoft.com/en-us/azure/azure-monitor/app/distributed-trace-data#telemetry-correlation-in-java
Kindly let us know if the above helps or you need further assistance on this issue.
Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Sign in to comment
Sign in to answer