This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
http_loader, alias: microsoft-intune-audit-events) lets you ingest
data from Microsoft Intune logs into a telemetry pipeline.
This is a pull-based source plugin.
Supported telemetry types
The for Chronosphere Telemetry Pipeline supports these telemetry types:
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 |
|---|
| Tenant ID | tenantID | Required. Your Microsoft tenant ID. | none |
| OAuth2 Client ID | oauth2_client_id | Required. Your Microsoft OAuth 2.0 client ID. | none |
| OAuth2 Client Secret | oauth2_client_secret | Required. Your Microsoft OAuth 2.0 client secret. | 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 |
