Closed codeboten closed 2 weeks ago
Thanks @songy23, will wait to get feedback on the rest of the PR before fixing to ensure contributors are ok with this approach. One of the annoying things is that most of the internal telemetry is defined in helper packages, which don't currently have metadata.yaml configuration since they're not components. This is a solvable problem, but I do want to raise this as something that will have to change.
Ideally I would like to see internal telemetry generated by *helper
packages listed in the documentation for components that use them. For example, i would like to see exporter_sent_log_records
listed as a metric that is emitted by every exporter in their documentation. I think it would make it easier for end users to understand the telemetry their pipelines emit, than to have to search for the helper's documentation. Alternatively a link from one to the other works too :)
Attention: Patch coverage is 50.00000%
with 38 lines
in your changes are missing coverage. Please review.
Project coverage is 91.67%. Comparing base (
109173d
) to head (6e2018b
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Description
This updates mdatagen to generate internal telemetry for components based on metadata.yaml configuration.
Testing
Added tests to mdatagen and updated the batch processor to use this as well for synchronous counters and histogram