Vectra M365 - Incident Detection source plugin
The Vectra M365 - Incident Detection source plugin
(name: 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
This plugin for Chronosphere Telemetry Pipeline supports these telemetry types:
| Logs | Metrics | Traces |
|---|---|---|
Configuration parameters
Use the parameters in this section to configure your plugin. The Telemetry Pipeline web interface uses the values in the Name column to describe the parameters. Items in the Key column are the YAML keys to use in pipeline configuration files.
General
| Name | Key | Description | Default |
|---|---|---|---|
| Vectra Portal URL | oauth2_token_url | Required. Your Vectra portal URL. | none |
| OAuth2 Client ID | oauth2_client_id | Required. Your OAuth2 client ID for accessing the Vectra portal. | none |
| OAuth2 Client Secret | oauth2_client_secret | Required. The OAuth2 secret key for accessing the Vectra portal. | none |
Advanced
| Name | Key | Description | Default |
|---|---|---|---|
| Memory Buffer Limit | mem_buf_limit | For pipelines with the Deployment or DaemonSet workload type only. 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 (opens in a new tab). If unspecified, no limit is enforced. | none |