Durable function logging and application insight

Question

Durable function logging and application insight

ZZ 120

When invoking an azure durable function, the response gives an 'id', which is the same 'instanceId' in the 'queryStatusUrl'.

I want to know if there is a way to filter all logs produced by this instance when looking at the logs for this azure function using application insights. I mean, obviously all logs for this function app can be found in application insights but how do you know which belongs to which 'invocation'? Can you link them by using this 'id/instanceId'?

If not directly, can this be achieved through configuring my app's logging, or even 'acquiring' this id and then use it in my own logging code?

Thanks

Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-06-19T11:47:11.94+00:00
Hello ZZ,

Thanks for reaching out.

Each function invocation is assigned a unique InvocationId, which is stored in the customDimensions field of telemetry tables like traces, requests, and exceptions.

You can run a Kusto Query like this in Log Analytics:

kusto

traces | project timestamp, customDimensions["InvocationId"], message | where customDimensions["InvocationId"] == "your-instance-id-here"

This will return all logs associated with that specific invocation.
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-06-23T03:32:11.9933333+00:00

Hello ZZ,

Following up to see if you have chance to check my previous response and please let us know with an update to assist you further on this.
ZZ 120 Reputation points

2025-06-23T09:48:26.51+00:00
Thanks. I did try what you told me but it did not fully solve my problem. When you make a call to the durable function, you get an instance Id, but that is not the invocationId because it simply schedules the job, which has not triggered invocation yet. So it did not work. Also my durable function uses a lot of libraries and their log messages are not there. In fact, I think those logs are not treated as been created by the durable function itself.

This is the final query that worked for me:

let targetInstanceId = "instance-id-of-the-durable-function-call"; let hostId = requests | where customDimensions.DurableFunctionsInstanceId == targetInstanceId | project HostInstanceId = tostring(customDimensions.HostInstanceId) | take 1; traces | where tostring(customDimensions.HostInstanceId) in (hostId) | project timestamp, message, customDimensions
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-06-24T03:44:31.3266667+00:00

Hello ZZ,

Could you please check the private message and provide the required details for troubleshooting the issue further.

Here is the reference link on how to access & data retention policy of private messages in Microsoft Q&A.

Accepted answer

0 additional answers

Your answer

Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-06-19T11:47:11.94+00:00

Hello ZZ,

Thanks for reaching out.

Each function invocation is assigned a unique InvocationId, which is stored in the customDimensions field of telemetry tables like traces, requests, and exceptions.

You can run a Kusto Query like this in Log Analytics:

kusto

traces | project timestamp, customDimensions["InvocationId"], message | where customDimensions["InvocationId"] == "your-instance-id-here"

This will return all logs associated with that specific invocation.
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-06-23T03:32:11.9933333+00:00

Hello ZZ,

Following up to see if you have chance to check my previous response and please let us know with an update to assist you further on this.
ZZ 120 Reputation points

2025-06-23T09:48:26.51+00:00

Thanks. I did try what you told me but it did not fully solve my problem. When you make a call to the durable function, you get an instance Id, but that is not the invocationId because it simply schedules the job, which has not triggered invocation yet. So it did not work. Also my durable function uses a lot of libraries and their log messages are not there. In fact, I think those logs are not treated as been created by the durable function itself.

This is the final query that worked for me:

let targetInstanceId = "instance-id-of-the-durable-function-call"; let hostId = requests | where customDimensions.DurableFunctionsInstanceId == targetInstanceId | project HostInstanceId = tostring(customDimensions.HostInstanceId) | take 1; traces | where tostring(customDimensions.HostInstanceId) in (hostId) | project timestamp, message, customDimensions
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-06-24T03:44:31.3266667+00:00

Hello ZZ,

Could you please check the private message and provide the required details for troubleshooting the issue further.

Here is the reference link on how to access & data retention policy of private messages in Microsoft Q&A.

Answer 1

Hello ZZ,

Glad to hear that your issue has been resolved.

After using below query:

let targetInstanceId = "instance-id-of-the-durable-function-call";

let hostId =

requests

| where customDimensions.DurableFunctionsInstanceId == targetInstanceId

| project HostInstanceId = tostring(customDimensions.HostInstanceId)

| take 1;

traces

| where tostring(customDimensions.HostInstanceId) in (hostId)

| project timestamp, message, customDimensions

Note: you must firstly find out what ID the actual started instance gets, then use that to find the logs.

If this answer was helpful, please click "Accept the answer" and mark Yes, as this can help other community members.

User's image

If you have any other questions or are still experiencing issues, feel free to ask in the "comments" section, and I'd be happy to help.

Share via

Durable function logging and application insight

0 additional answers

Your answer