This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
http_loader, alias: vectra-m365-incident-detection) lets you retrieve
data from Vectra and ingest it 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 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.General
| Name | Key | Description | Default |
|---|---|---|---|
| Vectra Portal URL | vectra_portal_url | Required. Your Vectra portal URL. | none |
| OAuth2 Client ID | oauth2_client_id | Required. Your OAuth 2.0 client ID for accessing the Vectra portal. | none |
| OAuth2 Client Secret | oauth2_client_secret | Required. The OAuth 2.0 secret key for accessing the Vectra portal. | 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 |