camel cmd chaos-experiment
Run one chaos experiment in the exploration of a running integration: add its rules, send its traffic, wait for the verdict, and end it
Options
| Option | Description | Default | Type |
|---|---|---|---|
| The body of the messages: text, file:<path>, or file:<folder> for a message per file | String | |
| End the open experiment (with --note) instead of running a new one | boolean | |
| The endpoint, or the id of the route, to send the messages of the experiment to; a route that serves HTTP gets HTTP requests, or give the path to call, such as 'PUT /orders/42' | String | |
| A header of the messages as key=value; can be given more than once | List | |
| What the experiment tests, in a few words, such as 'orders survive a payment outage' | String | |
| The pause between two messages, such as 200ms, or a range such as 100..500 to draw each pause at random (at most 60s) | String | |
| What to note with the experiment when it ends | String | |
| How many messages to send in all (at most 10000) | int | |
| A rule in its one-line text form, as an entry of camel.chaos.rules; can be given more than once, and one of them needs an expectation (expect=) | List | |
| How long to wait for the integration to answer, in millis or as a duration such as 30s | 10000 | long |
| The longest wait for the verdict after the messages were sent, and at least the within= of the expectations (at most 10m) | 2m | String |
| Display the help and sub-commands | boolean |