Skip to content

Unexpected behavior with Open Telemetry and Azure Monitor (Resource Attributes and Traces) #53416

@adam-delen

Description

@adam-delen

Seeing some unexpected or unusual behavior between open telemetry and application insights.

Firstly resource attributes are not being applied correctly to spans/activity traces as expected, from my understanding resource attributes should act similar to "custom properties" a key value pair that is being attached to each span, however in application insights these resource attributes are being emitted as individual "trace" logs.

Image Image

Second issue or strange behavior we are seeing is that telemetry messaging is being split into individual traces potentially by new line, for example in this screenshot below appears to be an exception message that has been split into multiple different trace messages, note that exceptions are also being logged correctly

Image

We are using the AzureMonitor() exporter for our implementation here

services.AddOpenTelemetry().UseAzureMonitor

SDK Version - azurefunctions:4.1042.0.0_dotnet8.0.21:otel1.9.0:ext1.3.0-beta.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    ClientThis issue is related to a non-management packageMonitor - ApplicationInsightsApplication InsightsService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions