-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Metrics send_failed_requests is inaccurate/abnormal #7456
Labels
bug
Something isn't working
Comments
mizhexiaoxiao
changed the title
Metric of send_failed_requests is inaccurate/abnormal
Metrics send_failed_requests is inaccurate/abnormal
Mar 31, 2023
Thanks for investigating @klboke! Would you like to submit a fix? |
maybe i can try fix it! @TylerHelmuth /assign |
codeboten
pushed a commit
that referenced
this issue
Apr 24, 2023
fix otelcol_exporter_send_failed_requests count error Link to tracking Issue: fixed #7456
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I found that regardless of whether in a local or other environment, when attempting to send data, Otel exporter always reports a number greater than 0 for send failed requests. This is puzzling. The number of send failed requests always matches the group of spans sent. For example, based on the information below, 3 group of spans were sent and 3 metric of send failed requests were generated. Would anyone be able to assist in identifying the root cause of this issue? Thank you
Steps to reproduce
./otelcol-contrib --config config.yaml
What did you expect to see?
otelcol_exporter_send_failed_requests should be 0
What did you see instead?
I saw that the exporter sent a total of 11 divided into 3 groups, and there were 3 send failed reqeusts
What version did you use?
Version: v0.73.0, version > 0.63.0 has this problem
What config did you use?
Config: (e.g. the yaml config file)
Environment
OS: MacOS M1
Compiler(if manually compiled): go1.18 darwin/arm64
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: