prometheus_scrape) to ingest data from your Prometheus instances and
into a telemetry pipeline.
This is 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 |
|---|---|---|---|
| Host | host | Required. The host of the Prometheus metric endpoint you want to scrape. | none |
| Port | port | Required. The port of the Prometheus metric endpoint you want to scrape. | none |
| Metrics URI Endpoint | metrics_path | Required. The metrics URI endpoint, which must start with a forward slash. Parameters can also be added to the path by using `?`. | /metrics |
| Scrape Interval | scrape_interval | Required. The interval to scrape metrics. | 10s |
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 |