You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, OpenTelemetry only allows pipelines to run by obtaining values from outside.
So I propose a plugin that periodically generates fixed values in the ootel-collector in the receiver's phase.
use-cases of the new component
Simplification of preparation for operation verification of processors and exporters
Simplification of health check for monitoring pipeline after otel-collector
etc.
This may be out of OpenTelemetry's custom receiver policy,
but I would be happy to be advised if there is a better way.
Example configuration for the component
items : Array holding key/value combinations of values to be generated name : a key value of generated value value : generated Value interval: Interval to generate values (unit: second)
The purpose and use-cases of the new component
Currently, OpenTelemetry only allows pipelines to run by obtaining values from outside.
So I propose a plugin that periodically generates fixed values in the ootel-collector in the receiver's phase.
use-cases of the new component
etc.
This may be out of OpenTelemetry's custom receiver policy,
but I would be happy to be advised if there is a better way.
Example configuration for the component
items
: Array holding key/value combinations of values to be generatedname
: a key value of generated valuevalue
: generated Valueinterval
: Interval to generate values (unit: second)example:
Telemetry data types supported
Is this a vendor-specific component?
Code Owner(s)
No response
Sponsor (optional)
No response
Additional context
If you think this idea is a good one I will try to create a PR about this custom plugin.
The text was updated successfully, but these errors were encountered: