It is required to implement configurable components to process and export internal telemetry data.
The new component will collect metrics from the MetricsRegistryHandle as a snapshot, send it to internal processors in sequence and then export the processed data to the different exporters configured.
This component will run every "flush_interval".
The internal processors and internal exporters are configured from a set of implemented components.
An example of the configuration of the internal telemetry is:
settings:
telemetry_config:
metrics:
flush_interval: 10s
processors:
- type: processor1
- type: processor2
exporters:
- type: logging
- type: prometheus
config:
host: "localhost"
port: 8080
nodes:
...
The example presents the configuration of flush_interval for metrics, two processors in sequence and two different exporters with their own configuration.
It is required to implement configurable components to process and export internal telemetry data.
The new component will collect metrics from the MetricsRegistryHandle as a snapshot, send it to internal processors in sequence and then export the processed data to the different exporters configured.
This component will run every "flush_interval".
The internal processors and internal exporters are configured from a set of implemented components.
An example of the configuration of the internal telemetry is:
The example presents the configuration of flush_interval for metrics, two processors in sequence and two different exporters with their own configuration.