Skip to content

Blog: Chaos in Camel 4.24, part 1 and part 2 - #1852

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

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

Conversation

@davsclaus

@davsclaus davsclaus commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Two blog posts on camel-chaos, new in Camel 4.24. They go out together, both dated 2026-11-22. Part 1 links to part 2 at its start and its end, and part 2 links back to part 1. With the same date, the blog lists part 1 first (by title).

Part 1: break your routes on purpose, before production does

content/blog/2026/11/camel-chaos/: built around the new chaos example (apache/camel-jbang-examples#134).

  • 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;
  • a list of what more chaos can do.

The feature image is drawn as an SVG (panicking camels, dice, a 503 sign) and rendered to 1200x675.

Part 2: let there be chaos, an AI that breaks your routes on purpose

content/blog/2026/11/let-there-be-chaos/: an AI explores chaos on a running integration by itself for a time budget (camel cmd chaos-explore, CAMEL-26760) and reports what held and what broke. It is built from a real recorded run: a local model (qwen3.6 35B via Ollama) explored the shop of the chaos example, with an added Kafka refunds route without error handling, for 10 minutes on 4.24.0-SNAPSHOT.

  • let-there-be-chaos.gif: a 16 second hook cut from the recording.
  • chaos-exploration.svg: the ten minutes as one figure, drawn from the saved exploration JSON.
  • A journal table of all ten experiments, the AI's diagnosis quoted, and an "Honest about the model" section.
  • featured.jpg: the part 1 image with a "Part 2" badge.

Status

Claude Code on behalf of Claus Ibsen

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

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

1 similar comment
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

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

@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 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 12 commits November 20, 2026 10:18
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>
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>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
…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>
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>
An AI explores chaos on a running integration by itself for a time budget
(camel cmd chaos-explore), with the run of a local model on the shop of the
chaos example: a figure of the ten minutes, the journal, and what it found.

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>
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, part 1 - break your routes on purpose Blog: Chaos in Camel 4.24, part 1 and part 2 Nov 20, 2026
@davsclaus
davsclaus marked this pull request as ready for review November 20, 2026 09:19
@github-actions

Copy link
Copy Markdown
Contributor

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

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