Skip to content

Conversation

@cijothomas
Copy link
Member

@cijothomas cijothomas commented Apr 28, 2022

Description: Fixes AzureMonitor Log Exporter correlation fields

  1. TraceId was already correctly mapped to operationId, but it was also added as custom property, which is not required. This removes adding TraceId as custom property.
  2. SpanId was incorrectly stored as custom property. This PR fixes it by correctly storing SpanId as OperationParentId.

Ref: https://github.com/microsoft/ApplicationInsights-dotnet/blob/main/BASE/src/Microsoft.ApplicationInsights/Extensibility/OperationCorrelationTelemetryInitializer.cs#L68

@cijothomas cijothomas requested review from a team and dashpole April 28, 2022 20:05
@cijothomas cijothomas changed the title Fix AzureMonitor LogExporter correlation [WIP] Fix AzureMonitor LogExporter correlation Apr 28, 2022
@cijothomas cijothomas changed the title [WIP] Fix AzureMonitor LogExporter correlation Fix AzureMonitor LogExporter correlation Apr 28, 2022
@cijothomas cijothomas changed the title Fix AzureMonitor LogExporter correlation [exporter/azuremonitorexporter] Fix LogExporter correlation bug Apr 29, 2022
@cijothomas
Copy link
Member Author

@bogdandrutu Could you help merge this?

@codeboten codeboten merged commit 20793ad into open-telemetry:main May 2, 2022
@cijothomas cijothomas deleted the cijothomas/azmon_log_correlationfix branch May 2, 2022 16:44
djaglowski pushed a commit to djaglowski/opentelemetry-collector-contrib that referenced this pull request May 10, 2022
…-telemetry#9579)

* Fix AzureMonitor LogExporter correlation

* Fix unwanted

* Fix test and add changelog

* Fix unused

* logrecord name

* logrecord name

* changelog

* chnagelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants