Skip to content

[Azure Monitor Exporter] Correct HTTP status code -> success mapping according to specs #588

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

Conversation

pcwiese
Copy link
Contributor

@pcwiese pcwiese commented Jul 31, 2020

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

e.g. 101 - SwitchingProtocols should map to success

Testing:
[x] E2E tests with traces from the dotnet OTEL sdk

@pcwiese pcwiese requested a review from a team July 31, 2020 20:08
@codecov
Copy link

codecov bot commented Jul 31, 2020

Codecov Report

Merging #588 into master will increase coverage by 15.17%.
The diff coverage is 100.00%.

Impacted file tree graph

@@             Coverage Diff             @@
##           master     #588       +/-   ##
===========================================
+ Coverage   71.09%   86.26%   +15.17%     
===========================================
  Files          14      195      +181     
  Lines         602    10632    +10030     
===========================================
+ Hits          428     9172     +8744     
- Misses        150     1128      +978     
- Partials       24      332      +308     
Flag Coverage Δ
#integration 71.09% <ø> (ø)
#unit 86.10% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
exporter/azuremonitorexporter/trace_to_envelope.go 96.16% <100.00%> (ø)
receiver/kubeletstatsreceiver/kubelet/utils.go 100.00% <0.00%> (ø)
...xporter/alibabacloudlogserviceexporter/uploader.go 100.00% <0.00%> (ø)
exporter/honeycombexporter/factory.go 88.88% <0.00%> (ø)
receiver/collectdreceiver/collectd.go 92.45% <0.00%> (ø)
...r/resourcedetectionprocessor/internal/testutils.go 100.00% <0.00%> (ø)
receiver/kubeletstatsreceiver/kubelet/fs.go 100.00% <0.00%> (ø)
receiver/receivercreator/runner.go 51.72% <0.00%> (ø)
processor/resourcedetectionprocessor/factory.go 90.90% <0.00%> (ø)
...ver/k8sclusterreceiver/collection/metadatastore.go 0.00% <0.00%> (ø)
... and 177 more

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 368adbd...38b3d08. Read the comment docs.

@pcwiese pcwiese changed the title Correct HTTP status code -> success mapping according to specs [Azure Monitor Exporter] Correct HTTP status code -> success mapping according to specs Jul 31, 2020
@bogdandrutu bogdandrutu merged commit 157e5a6 into open-telemetry:master Aug 4, 2020
@pcwiese pcwiese deleted the pwiese/fix-http-status-code-mapping branch January 12, 2021 19:18
ljmsc referenced this pull request in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
codeboten pushed a commit that referenced this pull request Nov 23, 2022
Without using binary here, users will need the tools to compile psycopg2 on
their systems.
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