> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prometheus scrape source plugin

> Configure the Prometheus scrape source plugin in Palo Alto Networks Telemetry Pipeline to ingest metrics for processing and routing.

export const entity_0 = "Prometheus scrape source plugin"

export const plugin_0 = "Prometheus scrape source plugin"

<Info>
  This information is for Palo Alto Networks Telemetry Pipeline, which is a standalone
  product separate from Palo Alto Networks Cortex XCOR.
</Info>

You can use the Prometheus scrape [source plugin](/ingest/pipeline/plugins/source-plugins)
(name: `prometheus_scrape`) to ingest data from your Prometheus instances and
into a telemetry pipeline.

This is a
[pull-based](/ingest/pipeline/plugins/source-plugins#push-based-and-pull-based-source-plugins)
source plugin.

## Supported telemetry types

The {plugin_0} for Palo Alto Networks Telemetry Pipeline supports these telemetry types:

| Logs | Metrics | Traces |
| :-: | :-: | :-: |
| <Icon icon="ban" color="red" /> | <Icon icon="circle-check" color="green" /> | <Icon icon="ban" color="red" /> |

## Configuration parameters

Use the parameters in this section to configure the {entity_0}. The
Palo Alto Networks Telemetry Pipeline web interface uses the items in the **Name** column to
describe these parameters. [Pipeline configuration files](/ingest/pipeline/v2/configure/config-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` | 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](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit#unit-sizes). If unspecified, no limit is enforced. <p />For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet [workload](/ingest/pipeline/v2/configure/kubernetes/workloads) type. To learn more, see the v2 [backpressure](/ingest/pipeline/v2/configure/backpressure) guide. <p />For v3 pipelines, this parameter is independent from the [OpenTelemetry `memory_limiter` and `batch` processors](/ingest/pipeline/v3#route-data-from-fluent-bit-to-opentelemetry). | *none* |


## Related topics

- [Prometheus Remote Write source plugin](/ingest/pipeline/plugins/source-plugins/prometheus-remote.md)
- [Ingest telemetry data with source plugins](/ingest/pipeline/plugins/source-plugins.md)
- [Scrape Prometheus native histograms](/ingest/metrics-traces/collector/configure/native-histograms.md)
- [Prometheus Remote Write destination plugin](/ingest/pipeline/plugins/destination-plugins/prometheus-remote-write.md)
- [Scrape configuration using Kubernetes](/ingest/metrics-traces/collector/discover/scrape-configuration.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.