Mock Data source plugin - Cortex XCOR Documentation

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

The Mock Data source plugin (name: dummy) lets you input user-generated data into a 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.

To use the Mock Data source plugin, you must create your own dataset and feed that data to the plugin. If you’d prefer to have Palo Alto Networks Telemetry Pipeline generate simulated log data on your behalf, use the Datagen plugin instead.

This plugin doesn’t support duplicates of itself within the same pipeline.

Supported telemetry types

The Mock Data source plugin for Palo Alto Networks Telemetry Pipeline supports these telemetry types:

Logs	Metrics	Traces

Configuration parameters

Use the parameters in this section to configure the Mock Data source plugin. The Palo Alto Networks 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
Mock Data	`dummy`	Required. Your mock data, in JSON format.	none

Advanced

Name	Key	Description	Default
Rate	`rate`	The amount of events per second to mock.	`1`
Samples	`samples`	How many times to generate events.	`0`
Base Timestamp in seconds	`start_time_sec`	A dummy base timestamp, in seconds.	`-1`
Base Timestamp in nano seconds	`start_time_nsec`	A dummy base timestamp, in nanoseconds	`-1`
Enable Fixed Timestamp	`fixed_timestamp`	If `true`, use a fixed timestamp, which lets the message pre-generate once. Accepted values: `true`, `false`	`false`
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. If unspecified, no limit is enforced. For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet workload type. To learn more, see the v2 backpressure guide. For v3 pipelines, this parameter is independent from the OpenTelemetry `memory_limiter` and `batch` processors.	none

​Supported telemetry types

​Configuration parameters

​Required

​Advanced

Supported telemetry types

Configuration parameters

Required

Advanced