These were only used by the memory limiter processor and were never
automatically calculated by the processorhelper. It's better to move
them to processor specific metrics that can be managed within the
component itself.
---------
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
This allows component authors to specify the stability level of
telemetry emitted by components. This provides visibility to end users
as to what they can expect from the telemetry.
---------
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
This updating the existing metric points that were recently added to use
signal as an attribute instead of separating the metric name. It follows
the suggestions in [otep
259](https://github.com/open-telemetry/oteps/pull/259) for the metric
and attribute names.
Putting this in draft to get some feedback from @djaglowski before
moving forward with this change
---------
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
This updates units for processhelper's internal telemetry.
Related #10556
Fixes
https://github.com/open-telemetry/opentelemetry-collector/issues/10651
For this PR i updated `metadata.yaml` and ran `make gogenerate`, then
`make -C processor test`
---------
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
This ensures the consistency for folks emitting metrics w/ OTLP until
the OTEP to specify pipeline telemetry is completed.
Waiting on
https://github.com/open-telemetry/opentelemetry-collector/pull/9775
before moving this forward
Fixes#9315
---------
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
#### Link to tracking issue
Resolves#10353
#### Testing
Added equivalent testing to other processor metrics (accepted, refused,
dropped).
#### Documentation
Metric documentation is autogenerated.
#### Open Question
My initial implementation includes a breaking change to
`componenttest.TestTelemetry` which is public facing API. If we want to
avoid an immediate breaking change in this test package, I would propose
the following, which I can submit in a prerequisite PR:
1. Deprecate all `TestTelemetry.Check*` methods.
2. Replace with more granular `TestTelemetry.CheckOneSpecificMetric`
methods.
This allows end users to see what telemetry each component should be
emitting.
---------
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Andres Borja
Bogdan Drutu
Alex Boten
Daniel Jaglowski