Telemetry: Operation_id used across multiple operations and instances

The same `operation_id` is used for multiple function invocations and on multiple instances in my logs. I am not sure whether this is a bug or a feature, but I would expect the operation id to be unique, i.e. it would be used for at a most one function invocation. Could someone explain what the `operation_id` and `operation_parentId` are and how they relate to each other.

Functions v2 with C#, Durable Functions and Service Bus Triggers.

Example from my logs: Operation Id "n7LLU+NoOp8=" ran on multiple instances, e.g. 5a8fad246c55816174b4eba84beb44c2bba324ebc473273ee4ce50505bdb95ef and 12ea8c4cfaa1172d9e4f5a970a2d02cfddd8b6d2eccf39cd2cda6162f2b013fb. See also screenshot from the logs below. Let me know if you want to have the whole table and I can email it to you.


Start with the reported logs and the definitions of operation_id and operation_parentId in the Azure Functions telemetry for Functions v2, Durable Functions, and Service Bus triggers. Determine whether one operation_id can span invocations or instances, then document the relationship and clarify whether the example reflects expected behavior or a telemetry defect.

Written by the indexing model from the issue text.