Skip to content

Routing

Routes connect a pipeline to one or more emitters. A route can add a second condition after pipeline matching, allowing the same normalized event to be delivered differently by status, action or severity.

Azure Front Door status split

Azure Front Door diagnostic settings select whole log categories and destinations; they don't filter individual access-log records by HTTP status. To send successful responses to Blob while sending failures to a SIEM, stream the access-log category to Event Hubs and perform the record-level split in Logstrm. Sending the same category directly to both Event Hubs and Storage archives the full category in both places.

For Azure Monitor resource logs, configure ingestors[].eventhub.resource_logs: true. The normalizer expands an optional records envelope and lifts nested properties fields before pipeline matching. AFD distinguishes client-facing ResponseStatusCode from origin BackendStatusCode; use the former to route and retain both for investigation. Confirm field casing and event shape from an actual exported record before deployment. See Microsoft's AFD log configuration, AFD monitoring reference, and Azure Monitor diagnostic settings.

routes:
  - name: frontdoor-security-events
    pipeline: azure_frontdoor
    condition: 'response_status_code < 200 OR response_status_code >= 400 OR category == "FrontDoorWebApplicationFirewallLog"'
    emitters: [sentinel-dcr]

  - name: frontdoor-access-archive
    pipeline: azure_frontdoor
    condition: 'response_status_code >= 200 AND response_status_code < 400'
    emitters: [azure-blob-archive]

This sample archives successful responses and redirects to Blob Storage, sends client-facing failures to Sentinel, and sends every WAF record to Sentinel regardless of its HTTP status. A WAF event with a 2xx/3xx response can intentionally match both routes. If you need Splunk too, add its emitter to the security route. ResponseStatusCode is the status AFD returned to the client; keep BackendStatusCode for diagnosing the origin response. Validate the exact exported field casing and envelope using a real Event Hubs record before deploying the rules.

Semantics

  • pipeline selects the normalized event shape.
  • condition is evaluated against the transformed event.
  • emitters names must exist in the top-level emitters list.
  • Multiple matching routes can intentionally fan out one event to multiple destinations.
  • A catch-all route uses true and should be placed deliberately because it can archive events already sent to a security destination.

Use distinct route names for operations and metrics. Keep routing conditions simple enough to audit during an incident; move complicated normalization into the pipeline transform stage.