-
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
Add obsreport network metrics api, OTLP-gRPC receiver/exporter support #6712
Conversation
@bogdandrutu I left this PR in draft state because it has no tests, but I'd be willing to write tests if you approve of the approach. Please take a look. |
Codecov ReportBase: 89.90% // Head: 89.15% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #6712 +/- ##
==========================================
- Coverage 89.90% 89.15% -0.75%
==========================================
Files 248 249 +1
Lines 14342 14500 +158
==========================================
+ Hits 12894 12928 +34
- Misses 1187 1308 +121
- Partials 261 264 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
Description:
Adds a new
obsreport
API for counting network bytes sent and received by exporters and receivers. This functionality is opt-in on a component-by-component basis. These metrics are disabled in a Basic-level metrics configuration. Under Normal level, only the primary direction of travel is counted (sent for exporters, received for receivers). Under Detailed level, both directions of travel are counted.Link to tracking Issue: #6638
Testing:
TODO: This is a WIP.
Documentation:
TODO: WIP