-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[exporter/azuremonitor] Exporter doesn't export span links #35855
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Comment to keep open |
Component(s)
exporter/azuremonitor
What happened?
Description
The AzureMonitor exporter doesn't seem to export span links. I've had a look through the code and I can't see any mapping of span links taking place.
Steps to Reproduce
In a C# app with otel configured and pointing to a collector with the azure monitor exporter
Expected Result
Link between activities to appear in application insights timeline view
Actual Result
No link in timeline view
Collector version
a2a52e43c1a80aa94120ad78c2db68780eb90e6d11c8db5b3ce2f6a0cc6b5029
Environment information
Environment
OS: (macos 14.7)
Collector image otel/opentelemetry-collector-contrib sha256:a2a52e43c1a80aa94120ad78c2db68780eb90e6d11c8db5b3ce2f6a0cc6b5029
Dotnet sdk: 8.0.401
OpenTelemetry.* Nuget packages: 1.9.0
OpenTelemetry Collector configuration
Log output
Additional context
I've attached logs from the collector showing that span are being produced links
Workaround
Setting a tag on the localActivity with the key of
_MS.links
and and array of operation links with the following schema links the activities in the application insights timeline viewProcessor
The text was updated successfully, but these errors were encountered: