Set .Context.Operation.Id, not only parent-child relationships

[SergeyKanzhelev]

I'd suggest to set .Context.Operation.Id across entire distributed trace so missing telemetry will not break a chain of execution and end-to-end view will be rendered successfully.

[SLdragon]

Hi, @SergeyKanzhelev
Do you mean we need to set Operation Id to the correlationId in the logs?

[SergeyKanzhelev]

Yes. This will enable transaction view in Application Insights UI

[SLdragon]

OK, i know, thanks

[SLdragon]

Fixed: #8

[SergeyKanzhelev]

@SLdragon I don't see it fixed in that PR. Please set Operation.Id explicitly. You may be lucky by relying on this issue: https://github.com/Microsoft/ApplicationInsights-Home/issues/237

[SLdragon]

Hi, @SergeyKanzhelev , maybe i misunderstood your suggestion, do you mean I also need to add this:
dependencyTelemetry.Context.Operation.Id = correlationId;
We have already set dependencyTelemetry.Id = correlationId , why we also need to set this?

[SergeyKanzhelev]

dependencyTelemetry.Context.Operation.Id = correlationId refer to the ID of the overall transaction. dependencyTelemetry.Id = correlationId refer to the ID of this specific call. All events of the distributed trace should have the same value in .Context.Operation.Id so they can be correlated.

[SLdragon]

Thanks @SergeyKanzhelev, I created another pull request to fix this issue, you can have a look. #9