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

Semantic convention type mismatch for http.status_code #2855

Closed
danelson opened this issue Oct 4, 2022 · 0 comments · Fixed by #2943
Closed

Semantic convention type mismatch for http.status_code #2855

danelson opened this issue Oct 4, 2022 · 0 comments · Fixed by #2943
Assignees
Labels
[label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR spec:miscellaneous For issues that don't match any other spec label

Comments

@danelson
Copy link

danelson commented Oct 4, 2022

What are you trying to achieve?

I am trying to understand if it is intentional that the type as described by the semantic conventions for http.status_code is different for Metrics and Traces.

  • Metrics defines it as a string (although ambiguous because the example value 200 does not use quotes ("))
  • Traces defines it as int

What did you expect to see?

I expect these to be the same type for each of Logs/Metrics/Traces and that all SDKs follow the same convention. For example, in the dotnet SDK, Metrics use string and Traces use int.

Additional context.

  • My assumption is that this could be an artifact of when Metrics only support attributes of type string.
  • Metrics are handled differently by different SDKs (might be related to the ambiguity mentioned above)
  • I am currently working around this by using the attributes proccessor with the convert function.
@danelson danelson added the spec:miscellaneous For issues that don't match any other spec label label Oct 4, 2022
@reyang reyang added the [label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR spec:miscellaneous For issues that don't match any other spec label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants