> ## 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.

# Dummy logs, metrics, and traces source plugin

> Generate sample telemetry data for Palo Alto Networks Telemetry Pipeline.

export const entity_0 = "Dummy logs, metrics, and traces source plugin"

export const plugin_0 = "Dummy logs, metrics, and traces 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>

The Dummy logs, metrics, and traces [source plugin](/ingest/pipeline/plugins/source-plugins)
(name: `event_type`) lets you create placeholder telemetry data for Palo Alto Networks
Telemetry Pipeline.

Although this is a self-contained plugin that doesn't communicate with external
sources, it's still classified as 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="circle-check" color="green" /> | <Icon icon="circle-check" color="green" /> | <Icon icon="circle-check" color="green" /> |

## 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 |
| - | - | - | - |
| **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` | 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

- [Test plugin settings](/ingest/pipeline/plugins/test-settings.md)
- [Dummy HTTP source plugin](/ingest/pipeline/plugins/source-plugins/dummy-http.md)
- [Ingest telemetry data with source plugins](/ingest/pipeline/plugins/source-plugins.md)
- [Mock Data source plugin](/ingest/pipeline/plugins/source-plugins/mock-data.md)
- [Vercel Logs source plugin](/ingest/pipeline/plugins/source-plugins/vercel.md)


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