Skip to content

Only treat StatusCode == ERROR as error or fault and determine error/… #1740

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

Merged
merged 1 commit into from
Dec 2, 2020

Conversation

anuraaga
Copy link
Contributor

@anuraaga anuraaga commented Dec 2, 2020

…fault based on HTTP status code.

Description: I think when replacing the status code, the logic for mapping errors drifted a bit, probably due to the unit tests themselves being incorrect. This makes sure to only treat ERROR as error, and uses HTTP information when present to determine fault vs error like x-ray expects.

Link to tracking Issue: Fixes #1739

Testing: Unit tests

@anuraaga anuraaga requested a review from kbrockhoff as a code owner December 2, 2020 07:48
@anuraaga anuraaga requested a review from a team December 2, 2020 07:48
@codecov
Copy link

codecov bot commented Dec 2, 2020

Codecov Report

Merging #1740 (aa2e0b9) into master (d1485f2) will increase coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1740      +/-   ##
==========================================
+ Coverage   89.87%   89.89%   +0.01%     
==========================================
  Files         376      376              
  Lines       18149    18154       +5     
==========================================
+ Hits        16311    16319       +8     
+ Misses       1379     1377       -2     
+ Partials      459      458       -1     
Flag Coverage Δ
integration 70.93% <ø> (ø)
unit 88.58% <100.00%> (+0.01%) ⬆️

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

Impacted Files Coverage Δ
exporter/awsxrayexporter/translator/cause.go 96.85% <100.00%> (+0.08%) ⬆️
processor/groupbytraceprocessor/event.go 96.77% <0.00%> (+0.80%) ⬆️
receiver/k8sclusterreceiver/watcher.go 97.64% <0.00%> (+2.35%) ⬆️

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 d1485f2...aa2e0b9. Read the comment docs.

@bogdandrutu bogdandrutu merged commit 2897617 into open-telemetry:master Dec 2, 2020
@anuraaga anuraaga deleted the fix-fault-error branch December 2, 2020 14:02
dyladan referenced this pull request in dynatrace-oss-contrib/opentelemetry-collector-contrib Jan 29, 2021
ljmsc referenced this pull request in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
…orters/metric/prometheus (#1740)

* Bump github.com/prometheus/client_golang in /exporters/metric/prometheus

Bumps [github.com/prometheus/client_golang](https://github.com/prometheus/client_golang) from 1.9.0 to 1.10.0.
- [Release notes](https://github.com/prometheus/client_golang/releases)
- [Changelog](https://github.com/prometheus/client_golang/blob/master/CHANGELOG.md)
- [Commits](prometheus/client_golang@v1.9.0...v1.10.0)

Signed-off-by: dependabot[bot] <[email protected]>

* Auto-fix go.sum changes in dependent modules

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Tyler Yahn <[email protected]>
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.

X-Ray Exporter is treating HTTP 200 as a fault
3 participants