Microsoft Sentinel
LyftData sends JSON events to Azure Log Analytics, which is the ingestion path used by Microsoft Sentinel. The azure-monitor output is the supported integration. LyftData does not provide an input that reads from Microsoft Sentinel; use a documented input such as HTTP polling when the source system exposes an API.
Prerequisites
Section titled “Prerequisites”- An Azure Log Analytics workspace and its workspace ID.
- The workspace’s base64-encoded shared key. Store it as a governed secret and reference it with
${secret|azure/log_analytics_shared_key}. - A licensed LyftData edition. The Azure Monitor Data Collector is available in Licensed editions.
Send events to Azure Monitor
Section titled “Send events to Azure Monitor”Add azure-monitor as the job output. This example uses placeholder values. It batches events and sends them as a JSON array to the default workspace ingestion endpoint, which expects an array.
name: sentinel-eventsdescription: "Send JSON events to Azure Monitor for Microsoft Sentinel"input: http-server: address: 127.0.0.1:8080 only-body: true json: trueoutput: azure-monitor: workspace-id: "00000000-0000-0000-0000-000000000000" shared-key: "${secret|azure/log_analytics_shared_key}" log-type: LyftDataEvents batch: mode: fixed fixed-size: 100 wrap-as-json: true retry: count: 5 pause: 1sThe workspace-id is the Azure Log Analytics customer ID. shared-key is the base64-encoded workspace key. If you omit ingestion-uri, LyftData builds https://{workspace}.ods.opinsights.azure.com/api/logs?api-version=2016-04-01; set ingestion-uri when your workspace requires a full custom endpoint, or set api-version when you need a different API version.
log-type becomes the Azure Monitor Log-Type value and defaults to LyftDataLogs when omitted. Set body-field to send only a field that contains JSON. Set time-generated-field to an ISO 8601 timestamp field, or set resource-id to add the Azure resource ID header.
Use batch to group events into one request. mode is fixed or document. In fixed mode, set fixed-size to a value greater than 0; without it the Job fails with fixed size value cannot be 0 when batching mode is set to fixed. max-bytes is an additional limit and does not replace fixed-size. timeout defaults to 100ms in fixed mode; document mode uses 24h instead. Set wrap-as-json: true so the request body is a JSON array.
Failure behavior
Section titled “Failure behavior”The retry policy applies to Azure Monitor requests. count sets the number of retry attempts; when it is omitted, retries continue indefinitely. pause sets the delay before retrying. A request that continues to fail therefore remains subject to the configured retry policy instead of being silently discarded. When test-url is set, it overrides the workspace and API-version endpoint.
The example uses http-server only as a local source. Put an authenticated gateway in front of an internet-facing listener and keep the shared key in a secret reference.