During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
locally chaos horizondb
This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos horizondb --help prints.
For more information see Chaos Engineering and HorizonDB.
locally chaos horizondb
Simulate HorizonDB (data plane) failure modes.
Simulate HorizonDB (data plane) failure modes. A fault command sets the fault's rate. With a scope flag (--location / --name) it adds or edits a rule instead. Examples: locally chaos horizondb <fault> --percentage N locally chaos horizondb <fault> reset locally chaos horizondb show locally chaos horizondb reset
Usage
locally chaos horizondb [flags] locally chaos horizondb [command]
Flags
-h, --help[=true|false] help for horizondb
Subcommands
- locally chaos horizondb disconnect - Close live connections cleanly, in the protocol's own terms, so the client has to reconnect.
- locally chaos horizondb drop-connection - Close the connection without answering.
- locally chaos horizondb incident - Take each resource down for a while, then bring it back.
- locally chaos horizondb latency - Hold requests for a random delay before they are handled.
- locally chaos horizondb outage - Fail requests for as long as the rule is armed, like a region or service that is down.
- locally chaos horizondb reset - Zero every HorizonDB (data plane) fault and drop every rule.
- locally chaos horizondb show - Print the current HorizonDB (data plane) chaos configuration.
locally chaos horizondb disconnect
Close live connections cleanly, in the protocol's own terms, so the client has to reconnect.
Close live connections cleanly, in the protocol's own terms, so the client has to reconnect. Every interval each open connection is rolled for. Compare drop-connection, which cuts them with nothing said. Without scope flags this sets the fault's rate on HorizonDB (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos horizondb disconnect --percentage 25 --interval 10m locally chaos horizondb disconnect --percentage 100 --interval 10m --location london locally chaos horizondb disconnect reset --location london locally chaos horizondb disconnect --percentage 100 --interval 10m --name acct1
Usage
locally chaos horizondb disconnect [flags] locally chaos horizondb disconnect [command]
Flags
-h, --help[=true|false] help for disconnect
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos horizondb disconnect reset - Remove one disconnect rule, or put the whole fault back to zero.
locally chaos horizondb disconnect reset
Remove one disconnect rule, or put the whole fault back to zero.
Reset the disconnect fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos horizondb disconnect reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos horizondb drop-connection
Close the connection without answering.
Close the connection without answering. The client sees the connection reset, with no status code or error body. With --interval it also cuts live connections: every interval each is rolled for, and on a hit it is reset with nothing said - no close frame or goodbye. For a clean close, use disconnect. Without scope flags this sets the fault's rate on HorizonDB (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --interval adds periodic action on live connections, such as every 30s, to the fault's per-request behaviour, which carries on as before. For periodic cuts with no per-request drops, arm disconnect instead. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos horizondb drop-connection --percentage 25 locally chaos horizondb drop-connection --percentage 25 --interval 30s locally chaos horizondb drop-connection --percentage 100 --location london locally chaos horizondb drop-connection reset --location london locally chaos horizondb drop-connection --percentage 100 --name acct1
Usage
locally chaos horizondb drop-connection [flags] locally chaos horizondb drop-connection [command]
Flags
-h, --help[=true|false] help for drop-connection
--interval string Also act on live connections this often, e.g. 30s or 10m (adds to the per-request fault; use disconnect for periodic cuts only)
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos horizondb drop-connection reset - Remove one drop-connection rule, or put the whole fault back to zero.
locally chaos horizondb drop-connection reset
Remove one drop-connection rule, or put the whole fault back to zero.
Reset the drop-connection fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos horizondb drop-connection reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos horizondb incident
Take each resource down for a while, then bring it back.
Take each resource down for a while, then bring it back. Every interval each resource (or, on the directory and identity surfaces, the tenant) rolls against the percentage; on a hit every request to it fails for the rolled duration, answered as an outage would be, then it recovers on its own. Compare outage, which fails requests for as long as it is armed. Without scope flags this sets the fault's rate on HorizonDB (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. One value N picks 0 to N each time; MIN-MAX, such as 30-120, picks within that range. A duration is required whenever the fault fires. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos horizondb incident --percentage 25 --seconds 30-120 --interval 10m locally chaos horizondb incident --percentage 100 --seconds 30-120 --interval 10m --location london locally chaos horizondb incident reset --location london locally chaos horizondb incident --percentage 100 --seconds 30-120 --interval 10m --name acct1
Usage
locally chaos horizondb incident [flags] locally chaos horizondb incident [command]
Flags
-h, --help[=true|false] help for incident
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--location string Scope this rule to one location, e.g. london
--millis string Duration in milliseconds, e.g. 250; N for 0 to N, or MIN-MAX for a range
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; N for 0 to N, or MIN-MAX for a range
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos horizondb incident reset - Remove one incident rule, or put the whole fault back to zero.
locally chaos horizondb incident reset
Remove one incident rule, or put the whole fault back to zero.
Reset the incident fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos horizondb incident reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos horizondb latency
Hold requests for a random delay before they are handled.
Hold requests for a random delay before they are handled. The response is unchanged, just late. With --interval it also stalls live connections: every interval each is rolled for, and on a hit nothing crosses it in either direction until the rolled delay has passed. Nothing is dropped; it all arrives late. Without scope flags this sets the fault's rate on HorizonDB (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. The value is a maximum: each firing picks 0 to N. A duration is required whenever the fault fires. --interval adds periodic action on live connections, such as every 30s, to the fault's per-request behaviour, which carries on as before. For periodic cuts with no per-request drops, arm disconnect instead. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos horizondb latency --percentage 25 --seconds 30 locally chaos horizondb latency --percentage 25 --seconds 30 --interval 30s locally chaos horizondb latency --percentage 100 --seconds 30 --location london locally chaos horizondb latency reset --location london locally chaos horizondb latency --percentage 100 --seconds 30 --name acct1
Usage
locally chaos horizondb latency [flags] locally chaos horizondb latency [command]
Flags
-h, --help[=true|false] help for latency
--interval string Also act on live connections this often, e.g. 30s or 10m (adds to the per-request fault; use disconnect for periodic cuts only)
--location string Scope this rule to one location, e.g. london
--millis string Duration in milliseconds, e.g. 250; the maximum: each firing picks 0 to N
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; the maximum: each firing picks 0 to N
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos horizondb latency reset - Remove one latency rule, or put the whole fault back to zero.
locally chaos horizondb latency reset
Remove one latency rule, or put the whole fault back to zero.
Reset the latency fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos horizondb latency reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos horizondb outage
Fail requests for as long as the rule is armed, like a region or service that is down.
Fail requests for as long as the rule is armed, like a region or service that is down. Each request rolls against the percentage, so at 100 every request fails until the fault is turned off. Each service answers in its own terms, usually 503 Service Unavailable, and a protocol with live connections also closes the ones open when the outage starts. For downtime that ends by itself, see incident. Without scope flags this sets the fault's rate on HorizonDB (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. Examples: locally chaos horizondb outage --percentage 25 locally chaos horizondb outage --percentage 100 --location london locally chaos horizondb outage reset --location london locally chaos horizondb outage --percentage 100 --name acct1
Usage
locally chaos horizondb outage [flags] locally chaos horizondb outage [command]
Flags
-h, --help[=true|false] help for outage
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos horizondb outage reset - Remove one outage rule, or put the whole fault back to zero.
locally chaos horizondb outage reset
Remove one outage rule, or put the whole fault back to zero.
Reset the outage fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos horizondb outage reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos horizondb reset
Zero every HorizonDB (data plane) fault and drop every rule.
Zero every HorizonDB (data plane) fault and drop every rule. Examples: locally chaos horizondb reset
Usage
locally chaos horizondb reset [flags]
Flags
-h, --help[=true|false] help for reset
--subscription string Subscription UUID (defaults to the configured default)
locally chaos horizondb show
Print the current HorizonDB (data plane) chaos configuration.
Print the current HorizonDB (data plane) chaos configuration. Examples: locally chaos horizondb show
Usage
locally chaos horizondb show [flags]
Flags
-h, --help[=true|false] help for show
--subscription string Subscription UUID (defaults to the configured default)
During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in