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

Remove 499 from mapping of OTel status code and HTTP #1226

Closed
wants to merge 1 commit into from

Conversation

anuraaga
Copy link
Contributor

@anuraaga anuraaga commented Jun 29, 2020

Description: <Describe what has changed.

Currently, status codes and HTTP are not mapped in a way that matches the spec. There is no mention of 499 or cancelled

https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/semantic_conventions/http.md#status

Link to tracking Issue:

Testing: < Describe what testing was performed and which tests were added.>

Documentation: < Describe the documentation added.>

@codecov
Copy link

codecov bot commented Jun 29, 2020

Codecov Report

Merging #1226 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1226      +/-   ##
==========================================
- Coverage   88.08%   88.06%   -0.03%     
==========================================
  Files         203      203              
  Lines       14658    14658              
==========================================
- Hits        12912    12909       -3     
- Misses       1309     1310       +1     
- Partials      437      439       +2     
Impacted Files Coverage Δ
translator/trace/grpc_http_mapper.go 100.00% <ø> (+7.14%) ⬆️
translator/internaldata/resource_to_oc.go 83.72% <0.00%> (-4.66%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 12b3d9c...387958f. Read the comment docs.

@james-bebbington
Copy link
Member

I might not be across other conversations on this, but should we not update the spec instead? It seems this is documented as the "official" HTTP mapping as per: https://github.com/googleapis/googleapis/blob/master/google/rpc/code.proto#L41

I actually don't know why we don't just reference that doc in the spec.

@anuraaga
Copy link
Contributor Author

Probably because this is OpenTelemetry, not Google :)

Went ahead and filed open-telemetry/opentelemetry-specification#676 to see which one we want to fix.

@anuraaga
Copy link
Contributor Author

anuraaga commented Jul 1, 2020

Closing since we'll update the spec instead

@anuraaga anuraaga closed this Jul 1, 2020
MovieStoreGuy pushed a commit to atlassian-forks/opentelemetry-collector that referenced this pull request Nov 11, 2021
…1226)

* Update label.ArrayValue to store copies of 1D arrays

* Update OTLP transform of array attributes

* Add changes to CHANGELOG

* Add PR number to changes

* Update value function documentation

* Remove redundant checks

* Add Array test for invalid array types

* Add test to ensure return from AsArray is a type

* Clean up iteration
hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this pull request Apr 27, 2023
…y#1226)

Bumps [boto3](https://github.com/boto/boto3) from 1.20.51 to 1.20.52.
- [Release notes](https://github.com/boto/boto3/releases)
- [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst)
- [Commits](boto/boto3@1.20.51...1.20.52)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
swiatekm pushed a commit to swiatekm/opentelemetry-collector that referenced this pull request Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants