Skip to main content

Troubleshooting

Quick Diagnosis​

# Check container status
docker ps | grep content-routing

# Check recent logs
docker logs content-routing --tail 50 2>&1 | grep -i error

# Test connectivity
curl -X POST http://localhost:8080/events \
  -H "Content-Type: application/json" \
  -d '{"severity": "INFO", "message": "test"}'

Common Issues​

Events going to wrong destination​

Cause: Severity field missing or misspelled

# Check what's being received
docker logs content-routing --tail 20 2>&1 | grep severity

Fix: Ensure events have valid severity field: CRITICAL, ERROR, WARN, INFO, DEBUG

Events stuck / not processing​

Cause: Downstream destination unavailable

# Check destination health
curl -s http://localhost:9200/_cluster/health  # Elasticsearch
curl -s $SLACK_WEBHOOK_URL                     # Slack

Fix: Verify destination URLs in environment variables, check network connectivity

High latency​

Cause: Large batch sizes or slow destinations

Fix: Reduce batch size in pipeline config:

batching:
  count: 50
  period: 5s

Memory growing​

Cause: Messages backing up due to destination issues

# Check container memory
docker stats content-routing --no-stream

Fix: Check destination connectivity, increase resources, or add circuit breaker

Still stuck?​

  1. Add debug logging to your pipeline config: logger: {level: DEBUG}
  2. Check the Complete Pipeline for reference config
  3. Review Circuit Breakers for handling destination failures