-
Notifications
You must be signed in to change notification settings - Fork 528
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
Otel exporter for internal telemetry #11470
Conversation
0de00c1
to
1a424e4
Compare
This pull request does not have a backport label. Could you fix it @dmathieu? 🙏
NOTE: |
ce00b94
to
5febde7
Compare
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.
I didn't look too closely at the modelpb usage, just the overall structure. Looks good, just a few comments.
2228d0d
to
b0a8bc9
Compare
7d9d543
to
f7c94a0
Compare
I have added the new exporter to the global meter provider. |
* setup otel metric exporter * handle float counter * handle int64 counter and gauges * add histograms * handle labels * use our custom boundaries * extract and test config * filter metrics * run check-full * document the specific boundaries * initialize new structs, instead of cloning * mention apm-data * remove agent * add local exporter
Motivation/summary
This sets up an OpenTelemetry exporter to collect internal metrics, export them as internal APM events and send them to the processor.
It is the boilerplate for #10623, yet no metrics are emitted yet. So this code isn't used at the moment.
Checklist
apmpackage
have been made)For functional changes, consider:
How to test these changes
This PR is unit-tested.
Related issues