-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[statsdreceiver] fixup metamonitoring #32309
Conversation
the statsd receiver does not currently emit metrics or traces about its own internal operations, making it difficult to understand if it's working properly. this introduces an integration w/ the receiverhelper.ObsReport helper, which is the standard way to emit this information. this also changes how the transport debug logs are emitted; they are now logged via a new transport.Logger interface; the primary reason for this is to avoid confusion w/ the naming--the 'reporter' is now the ObsReport instance, and what the transport.Reporter really was doing was simply emitting debug logs.
7dda2a3
to
6626803
Compare
fixes #32335 (i had to file the issue to pass the changelog check) |
this is an alternate implementation to #31839 - the approach in this PR uses the standard ObsReporter helper and hooks it onto the flush function. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
duplicated by #33415 |
Description:
the statsd receiver does not currently emit metrics or traces about its own internal operations, making it difficult to understand if it's working properly. this introduces an integration w/ the receiverhelper.ObsReport helper, which is the standard way to emit this information.
this also changes how the transport debug logs are emitted; they are now logged via a new transport.Logger interface; the primary reason for this is to avoid confusion w/ the naming--the 'reporter' is now the ObsReport instance, and what the transport.Reporter really was doing was simply emitting debug logs.
Link to tracking Issue: #32335
Testing:
no new tests are added, but existing tests are updated to pass.
Documentation:
n/a