Signal Sciences 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 Signal Sciences source plugin (name: http_loader) lets you query the Signal Sciences API to ingest data into a telemetry pipeline. This is a pull-based source plugin.

This plugin doesn’t support the use of a descriptive metadata name in the Pipeline Builder interface.

This plugin doesn’t support duplicates of itself within the same pipeline. Additionally, this plugin can’t be used in combination with these source plugins within the same telemetry pipeline:

Supported telemetry types

The Signal Sciences 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 Signal Sciences 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.

General

The configured fields replace sections of the url field in the YAML file in the following way:

https://dashboard.signalsciences.net{{with
  .Response.Body.next.uri}}.{{else}}/api/v0/corps/CORP/sites/SITENAME/requests?q=SEARCH_QUERY{{end}}

Name	Key	Description	Default
Corp	none	Required. Added to `url` field.	none
Site Name	none	Required. Added to `url` field.	none
Search Query	none	The query to pass to the Signal Sciences API, as part of the `url` field.	none
API Access Token	none	Your Signal Sciences API access token.	none

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

​General

​Advanced

Supported telemetry types

Configuration parameters

General

Advanced