Priority Queue Explorer

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

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" }

Stage configuration01-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