Repository navigation
Conversation
Contributor
|
🚀 Preview is available at https://pr-1852--camel.netlify.app |
1 similar comment
Contributor
|
🚀 Preview is available at https://pr-1852--camel.netlify.app |
Contributor
|
🚀 Preview is available at https://pr-1852--camel.netlify.app |
40 tasks done
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
force-pushed
the
blog/camel-chaos
branch
from
November 20, 2026 09:18
343c907 to
e740d64
Compare
davsclaus
marked this pull request as ready for review
November 20, 2026 09:19
Contributor
|
🚀 Preview is available at https://pr-1852--camel.netlify.app |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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;aon the chaos screen to add a rule from the known faults, filled in with the endpoints of the integration;.chaosscenario with a seed, used as a build gate through the exit code;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.featured.jpg: the part 1 image with a "Part 2" badge.Status
Claude Code on behalf of Claus Ibsen
🤖 Generated with Claude Code