Priority Queue 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 4 stages in order

1. Original Input
   Start with one processing path before adding authored priority labels and branches.
2. Severity-Based Routing
   Messages are classified by log severity (CRITICAL, ERROR, WARNING, INFO) and routed to dedicated queues with appropriate batching policies. Critical messages bypass batching entirely.
3. Customer Tier Enhancement
   Add an authored customer-tier field to the example priority score.
4. Multi-Criteria Scoring
   Sophisticated scoring algorithm combines severity, customer tier, event type, urgency, and business context into a numerical priority score for precise routing decisions.

Interactive pipeline

PRIORITY QUEUES

Priority scoring and routing configuration

Stage1. Original Input2. Severity-Based Routing3. Customer Tier Enhancement4. Multi-Criteria Scoring

Stage 1 of 4

Original Input

Start with one processing path before adding authored priority labels and branches.

0HighlightsAuthored emphasis only—not a computed diff.

Highlights only

Copy & download

Input

 { "timestamp": "2024-01-15T14:30:00Z", "severity": "CRITICAL", "event_type": "payment.failed", "customer_tier": "enterprise", "urgency": "high", "service": "payment-service", "message": "Payment processing failed", "amount": 50000 }

Output

 { "timestamp": "2024-01-15T14:30:00Z", "severity": "CRITICAL", "event_type": "payment.failed", "customer_tier": "enterprise", "urgency": "high", "service": "payment-service", "message": "Payment processing failed", "amount": 50000, "processed_at": "2024-01-15T14:30:01Z" }

Partial snippet01-original-input.yaml

# No priority routing - all messages treated equally
output:
  kafka:
    addresses: ["kafka-broker-1:9092","kafka-broker-2:9092"]
    topic: all-events
    batching:
      count: 100      # Same batching for all
      period: 30s     # Same delay for all
    max_retries: 3    # Same reliability for all