--- import Lightbox from '../Lightbox.astro'; interface Callout { title: string; body: string; } const callouts: Callout[] = [ { title: 'Cross-service correlation.', body: 'Every exchange carries its correlation ID forward. One click jumps to what the downstream route did with the same message.', }, { title: 'Runtime detail, not guesswork.', body: 'Circuit breaker tripped. Fallback path ran. Request tried backend:80. The pieces a 3 AM page actually needs — already captured.', }, { title: 'The whole story of a failure.', body: 'Exception class, message, stack trace, headers, payload — all pinned to the exchange. No log-grepping tour.', }, ]; ---

// When something breaks

The 3 AM page. With and without Cameleer.

Same Camel app. Same failed exchange. Different night.

Without Cameleer · 03:12 AM
$ kubectl logs camel-router-7d4f8c
ERROR org.apache.camel.CamelExecutionException
  at org.apache.camel.processor.SendProcessor.process
  at org.apache.camel.processor.Pipeline.process
  ...

$ grep "order-842" *.log
router-3.log: WARN  exchange order-842 stuck in saga-fulfillment
router-3.log: ERROR processor backend:80 → connect timeout

$ ssh prod-integration-3
prod-integration-3 $ kubectl logs ...

> slack #integration-team
  "anyone know why order-842 is stuck??"
  [3 of 4 reactions, no answer]

~47 min later: someone wakes up an SRE.
With Cameleer · 30 sec
Open exchange order-842 → see the failure pinned → click Replay after fix.