Skip to content

Log response error with zap #1050

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
Sep 21, 2020
Merged

Conversation

anuraaga
Copy link
Contributor

@anuraaga anuraaga commented Sep 18, 2020

Description:

Currently, even when an error is returned from an exporter, it doesn't seem to be automatically logged. I sort of expected it to but added manual logging instead.

@anuraaga anuraaga requested a review from a team September 18, 2020 12:35
@codecov
Copy link

codecov bot commented Sep 18, 2020

Codecov Report

Merging #1050 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1050      +/-   ##
==========================================
+ Coverage   88.81%   88.83%   +0.01%     
==========================================
  Files         250      250              
  Lines       11924    11925       +1     
==========================================
+ Hits        10590    10593       +3     
+ Misses        990      989       -1     
+ Partials      344      343       -1     
Flag Coverage Δ
#integration 75.42% <ø> (ø)
#unit 87.84% <100.00%> (+0.01%) ⬆️

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

Impacted Files Coverage Δ
exporter/awsxrayexporter/awsxray.go 66.66% <100.00%> (+0.66%) ⬆️
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 bff19a2...856eb6f. Read the comment docs.

@bogdandrutu bogdandrutu merged commit 60a3581 into open-telemetry:master Sep 21, 2020
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
* Move proto to OTLP exporter

* Update OTLP exporter import of proto

* Use gogo protobuf

To stop using the deprecated github.com/golang/protobuf and match what
the collector is doing, switch to generating OTLP with the
github.com/gogo/protobuf/proto instead of
github.com/golang/protobuf/proto.

* Clean dependencies

Remove all protobuf dependencies from otel package and all of its
dependencies.

* Update CHANGELOG

* Clean OTLP exporter go mod

Remove submodule beforehand to avoid unneeded direct dependencies.

* Use default ref for GitHub workflow

* Update path that triggers proto gen action

* Correct license-check exclusion for OTLP

* Update commented location of the OTLP and code
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.

2 participants