event_type) lets you create placeholder telemetry data for Telemetry
Pipeline.
Although this is a self-contained plugin that doesn’t communicate with external
sources, it’s still classified as a pull-based
source plugin.
Supported telemetry types
The for Chronosphere Telemetry Pipeline supports these telemetry types:| Logs | Metrics | Traces |
|---|---|---|
Configuration parameters
Use the parameters in this section to configure the . The Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.Required
| Name | Key | Description | Default |
|---|---|---|---|
| Telemetry Type | type | Required. The type of telemetry data to generate. Accepted values: logs, metrics, traces. | logs |
Advanced
| Name | Key | Description | Default |
|---|---|---|---|
| Memory Buffer Limit | mem_buf_limit | For pipelines with the Deployment or DaemonSet workload type only. Sets a limit for how much buffered data the plugin can write to memory, which affects backpressure. This value must follow Fluent Bit’s rules for unit sizes. If unspecified, no limit is enforced. | none |