Skip to main content

Content Routing Explorer

Use the stage controls to compare the synthetic input, authored output, and configuration at each step.

How to use this explorer

Move between stages with the arrows or the numbered stage list. Each stage shows the input it receives on the left and the output it produces on the right, with the lines that changed marked. The configuration that makes the change sits below the comparison, and the final stage shows the complete pipeline.

The 5 stages in order

  1. Original Input
    Start with one example destination before adding field-based branches.
  2. Severity-Based Routing
    Map authored severity values to named PagerDuty, Slack, and Elasticsearch branches.
  3. Geographic Routing
    Add a region field to the branch order. Destination labels do not establish physical location or transfer treatment.
  4. Event Type Routing
    Map authored event types to separate named branches. Delivery semantics are not exercised.
  5. Priority Queue Routing
    Add priority labels and authored batching settings to the branch order.

Interactive pipeline

CONTENT-BASED ROUTING

Field-based branch configuration

Stage 1 of 5

Original Input

Start with one example destination before adding field-based branches.

0HighlightsAuthored emphasis only—not a computed diff.
Copy & download

Input

{"event_id": "alert-001","severity": "CRITICAL","message": "Payment processor down","region": "eu-west"}{"event_id": "user-002","severity": "INFO","event_type": "user.login","region": "us-east"}{"event_id": "payment-003","severity": "WARN","event_type": "payment.failed","user_tier": "premium","region": "eu-west"}

Output

→ kafka:topic: general-events→ kafka:topic: general-events→ kafka:topic: general-events
Complete pipeline01-original-input.yaml
input:
  http_server:
    address: 0.0.0.0:8080
    path: /events

output:
  kafka:
    addresses: [localhost:9092]
    topic: general-events