-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update to latest semantic conventions #29687
Comments
I managed to work around it using this processor for both requests and dependencies :
|
Pinging code owners for exporter/azuremonitor: @pcwiese. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Thanks for filing @stonkie, and including references and a temporary workaround! I looked into this and agree that references to semantic conventions need to be updated. Currently the exporter is at For context, the central method that would need updated is here, but whoever ends up making this change needs to confirm other conversions are up to date as well. The Attribute Mapping section of the exporter's README will also need updated as a part of this change. |
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. |
I open an MR on repository collector to generate appropriate specification file : open-telemetry/opentelemetry-collector#9593 |
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. |
Is there any update on this? |
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. |
The correct semantic convention attributes are available in the v1.25.0 of the semconv package so making this change should be unblocked |
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. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
No response
What happened?
Description
Semantic conventions have settled on a slightly different set of properties for HTTP clients than those implemented : https://github.com/open-telemetry/semantic-conventions/blob/v1.23.0/docs/http/http-spans.md#http-client
The main one is using http.url instead of url.full. http.response.status_code should also be used instead of http.status_code
When used with the latest OpenTelemetry.Instrumentation.Http 1.6.0-rc.1 (see this change : open-telemetry/opentelemetry-dotnet#5068), the AppInsight integration is quite bare.
The logic here would need to be updated to take url.full into account : https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/azuremonitorexporter/trace_to_envelope.go
Steps to Reproduce
Instrumented dotnet application with OpenTelemetry.Instrumentation.Http 1.6.0-rc.1 and a collector using the azuremonitorexporter.
Expected Result
Actual Result
Collector version
'otel/opentelemetry-collector-contrib:0.90.1'
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: