Skip to content

Blog: Chaos in Camel 4.24, part 1 - break your routes on purpose - #1852

Draft
davsclaus wants to merge 9 commits into
mainfrom
blog/camel-chaos
Draft

davsclaus wants to merge 9 commits into
mainfrom
blog/camel-chaos

Conversation

@davsclaus

@davsclaus davsclaus commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Part 1 of two blog posts on camel-chaos, new in Camel 4.24 (part 2 is #1853), built around the new chaos example (apache/camel-jbang-examples#134).

feature image

The post covers:

  • camel run * --chaos, camel cmd chaos-suggest, and adding the first rule;
  • the same in the Camel TUI: F2 > Run an Example... with Chaos testing ticked (chore: camel-jbang - the run options form can turn on chaos testing (--chaos) camel#29567), then a on the chaos screen to add a rule from the known faults, filled in with the endpoints of the integration;
  • the chaos screen and the timeline of the Camel TUI (three live screenshots of the example);
  • losing orders when the dead letter channel fails too: the verdict is FAIL;
  • a .chaos scenario with a seed, used as a build gate through the exit code;
  • a bug that chaos found while an AI agent wrote the example (CAMEL-26734);
  • an author's note: testing is not only JUnit anymore; the CLI, TUI and AI make trying things quick, and Citrus, chaos and camel-test-dst test the integration for real;
  • a list of what more chaos can do.

All the output shown comes from runs of the example on 4.24.0-SNAPSHOT. The feature image is drawn as an SVG (panicking camels, dice, a 503 sign) and rendered to 1200x675.

Before publishing:

Claude Code on behalf of Claus Ibsen

davsclaus and others added 2 commits November 8, 2026 12:30
A post on camel-chaos with the chaos example of camel-jbang-examples: suggest
rules, add them while the shop runs, watch them in the Camel TUI, lose orders
when the dead letter channel fails too, and gate a build with a scenario. It
ends with a list of what more chaos can do. Feature image: panicking camels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

🚀 Preview is available at https://pr-1852--camel.netlify.app

davsclaus and others added 2 commits November 8, 2026 19:38
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

🚀 Preview is available at https://pr-1852--camel.netlify.app

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Preview is available at https://pr-1852--camel.netlify.app

davsclaus and others added 2 commits November 10, 2026 16:29
…d add a rule from the known faults

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
… chaos), and links to it

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@davsclaus davsclaus changed the title Blog: Chaos in Camel 4.24, break your routes on purpose Blog: Chaos in Camel 4.24, part 1 - break your routes on purpose Nov 10, 2026
davsclaus and others added 2 commits November 10, 2026 21:45
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant