Skip to content
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

Closed
stonkie opened this issue Dec 7, 2023 · 11 comments
Closed

Update to latest semantic conventions #29687

stonkie opened this issue Dec 7, 2023 · 11 comments
Labels

Comments

@stonkie
Copy link

stonkie commented Dec 7, 2023

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

image

Actual Result

image

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

@stonkie stonkie added bug Something isn't working needs triage New item requiring triage labels Dec 7, 2023
@stonkie
Copy link
Author

stonkie commented Dec 7, 2023

I managed to work around it using this processor for both requests and dependencies :

      attributes:
        actions:
          - key: http.status_code
            action: insert
            from_attribute: http.response.status_code
          - key: http.url
            action: insert
            from_attribute: url.full
          - key: http.target
            action: insert
            from_attribute: url.path
          - key: http.host
            action: insert
            from_attribute: server.address
          - key: http.scheme
            action: insert
            from_attribute: url.scheme
          - key: http.method
            action: insert
            from_attribute: http.request.method

Copy link
Contributor

github-actions bot commented Dec 7, 2023

Pinging code owners for exporter/azuremonitor: @pcwiese. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1
Copy link
Member

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 v1.6.1 of semantic conventions, so it should be updated to latest. It may be good also to document in the README the semantic convention version it's on, so users aren't caught off guard like this in the future.

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.

@crobert-1 crobert-1 added enhancement New feature or request and removed needs triage New item requiring triage bug Something isn't working labels Dec 7, 2023
Copy link
Contributor

github-actions bot commented Feb 6, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@aygalinc
Copy link

I open an MR on repository collector to generate appropriate specification file : open-telemetry/opentelemetry-collector#9593

Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Apr 29, 2024
@crobert-1 crobert-1 removed the Stale label Apr 29, 2024
@kamilzzz
Copy link

Is there any update on this?

Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jul 17, 2024
@codeboten codeboten added help wanted Extra attention is needed and removed Stale labels Aug 7, 2024
@codeboten
Copy link
Contributor

The correct semantic convention attributes are available in the v1.25.0 of the semconv package so making this change should be unblocked

Copy link
Contributor

github-actions bot commented Oct 7, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Oct 7, 2024
Copy link
Contributor

github-actions bot commented Dec 6, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants