locally chaos storage

Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

locally chaos storage

This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos storage --help prints.

For more information see Chaos Engineering and Storage Emulator.

locally chaos storage

Simulate Storage (data plane) failure modes.

Simulate Storage (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 storage <fault> --percentage N
  locally chaos storage <fault> reset
  locally chaos storage show
  locally chaos storage reset

Usage

locally chaos storage [flags]
  locally chaos storage [command]

Flags

-h, --help[=true|false]   help for storage

Subcommands

locally chaos storage 403

Answer requests with 403, as when a role assignment has not replicated yet.

Answer requests with 403, as when a role assignment has not replicated yet. On
the control plane the error code is AuthorizationFailed; on a database the
engine's own equivalent error is sent instead.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, file, dfs.

Examples:
locally chaos storage 403 --percentage 25
  locally chaos storage 403 --percentage 100 --location london
  locally chaos storage 403 reset --location london
  locally chaos storage 403 --percentage 100 --name acct1

Usage

locally chaos storage 403 [flags]
  locally chaos storage 403 [command]

Flags

-h, --help[=true|false]     help for 403
      --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 storage 403 reset

Remove one 403 rule, or put the whole fault back to zero.

Reset the 403 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 storage 403 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 storage 429

Answer requests with 429 Too Many Requests and a retry hint.

Answer requests with 429 Too Many Requests and a retry hint. On a database the
engine's own throttling error is sent instead.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, file, dfs.

--retry-after sets the Retry-After header the fault answers with, such as 5s.
Without one the service's usual hint is sent.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos storage 429 --percentage 25
  locally chaos storage 429 --percentage 25 --retry-after 5s
  locally chaos storage 429 --percentage 100 --location london
  locally chaos storage 429 reset --location london
  locally chaos storage 429 --percentage 100 --name acct1

Usage

locally chaos storage 429 [flags]
  locally chaos storage 429 [command]

Flags

-h, --help[=true|false]     help for 429
      --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)
      --retry-after string    Retry-After this fault answers with, e.g. 5s or 500ms (the service's usual hint when omitted)
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos storage 429 reset

Remove one 429 rule, or put the whole fault back to zero.

Reset the 429 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 storage 429 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 storage 500

Answer requests with 500 Internal Server Error.

Answer requests with 500 Internal Server Error. On a database the engine's own
equivalent error is sent instead.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, file, dfs.

Examples:
locally chaos storage 500 --percentage 25
  locally chaos storage 500 --percentage 100 --location london
  locally chaos storage 500 reset --location london
  locally chaos storage 500 --percentage 100 --name acct1

Usage

locally chaos storage 500 [flags]
  locally chaos storage 500 [command]

Flags

-h, --help[=true|false]     help for 500
      --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 storage 500 reset

Remove one 500 rule, or put the whole fault back to zero.

Reset the 500 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 storage 500 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 storage delivery-delay

Hold messages, events or triggers for the rolled duration before delivering them.

Hold messages, events or triggers for the rolled duration before delivering
them.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob.

--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.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos storage delivery-delay --percentage 25 --seconds 30-120
  locally chaos storage delivery-delay --percentage 100 --seconds 30-120 --location london
  locally chaos storage delivery-delay reset --location london
  locally chaos storage delivery-delay --percentage 100 --seconds 30-120 --name acct1

Usage

locally chaos storage delivery-delay [flags]
  locally chaos storage delivery-delay [command]

Flags

-h, --help[=true|false]     help for delivery-delay
      --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 storage delivery-delay reset

Remove one delivery-delay rule, or put the whole fault back to zero.

Reset the delivery-delay 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 storage delivery-delay 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 storage delivery-drop

Deliver nothing for some messages, events or triggers.

Deliver nothing for some messages, events or triggers. Event Grid push treats it
as an endpoint failure and retries until the event is dead-lettered.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob.

Examples:
locally chaos storage delivery-drop --percentage 25
  locally chaos storage delivery-drop --percentage 100 --location london
  locally chaos storage delivery-drop reset --location london
  locally chaos storage delivery-drop --percentage 100 --name acct1

Usage

locally chaos storage delivery-drop [flags]
  locally chaos storage delivery-drop [command]

Flags

-h, --help[=true|false]     help for delivery-drop
      --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 storage delivery-drop reset

Remove one delivery-drop rule, or put the whole fault back to zero.

Reset the delivery-drop 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 storage delivery-drop 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 storage 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.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, file, dfs.

Examples:
locally chaos storage drop-connection --percentage 25
  locally chaos storage drop-connection --percentage 100 --location london
  locally chaos storage drop-connection reset --location london
  locally chaos storage drop-connection --percentage 100 --name acct1

Usage

locally chaos storage drop-connection [flags]
  locally chaos storage drop-connection [command]

Flags

-h, --help[=true|false]     help for drop-connection
      --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 storage 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 storage 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 storage duplicate-delivery

Deliver some messages, events or triggers twice.

Deliver some messages, events or triggers twice.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob.

Examples:
locally chaos storage duplicate-delivery --percentage 25
  locally chaos storage duplicate-delivery --percentage 100 --location london
  locally chaos storage duplicate-delivery reset --location london
  locally chaos storage duplicate-delivery --percentage 100 --name acct1

Usage

locally chaos storage duplicate-delivery [flags]
  locally chaos storage duplicate-delivery [command]

Flags

-h, --help[=true|false]     help for duplicate-delivery
      --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 storage duplicate-delivery reset

Remove one duplicate-delivery rule, or put the whole fault back to zero.

Reset the duplicate-delivery 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 storage duplicate-delivery 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 storage failover

Fail the primary over on a schedule.

Fail the primary over on a schedule. On a hit the primary is unavailable for the
rolled duration and any secondary serves reads only, then the primary returns.

Without scope flags this sets the fault's rate on Storage (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 storage failover --percentage 25 --seconds 30-120 --interval 10m
  locally chaos storage failover --percentage 100 --seconds 30-120 --interval 10m --location london
  locally chaos storage failover reset --location london
  locally chaos storage failover --percentage 100 --seconds 30-120 --interval 10m --name acct1

Usage

locally chaos storage failover [flags]
  locally chaos storage failover [command]

Flags

-h, --help[=true|false]     help for failover
      --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 storage failover reset

Remove one failover rule, or put the whole fault back to zero.

Reset the failover 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 storage failover 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 storage 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 Storage (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 storage incident --percentage 25 --seconds 30-120 --interval 10m
  locally chaos storage incident --percentage 100 --seconds 30-120 --interval 10m --location london
  locally chaos storage incident reset --location london
  locally chaos storage incident --percentage 100 --seconds 30-120 --interval 10m --name acct1

Usage

locally chaos storage incident [flags]
  locally chaos storage 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 storage 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 storage 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 storage 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.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, file, dfs.

--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.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos storage latency --percentage 25 --seconds 30
  locally chaos storage latency --percentage 100 --seconds 30 --location london
  locally chaos storage latency reset --location london
  locally chaos storage latency --percentage 100 --seconds 30 --name acct1

Usage

locally chaos storage latency [flags]
  locally chaos storage latency [command]

Flags

-h, --help[=true|false]     help for latency
      --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 storage 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 storage 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 storage lock-lost

Report that a lock or lease the client holds is gone.

Report that a lock or lease the client holds is gone. It applies to requests
that use one, such as completing a Service Bus message or writing to a leased
blob.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, file, dfs.

Examples:
locally chaos storage lock-lost --percentage 25
  locally chaos storage lock-lost --percentage 100 --location london
  locally chaos storage lock-lost reset --location london
  locally chaos storage lock-lost --percentage 100 --name acct1

Usage

locally chaos storage lock-lost [flags]
  locally chaos storage lock-lost [command]

Flags

-h, --help[=true|false]     help for lock-lost
      --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 storage lock-lost reset

Remove one lock-lost rule, or put the whole fault back to zero.

Reset the lock-lost 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 storage lock-lost 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 storage 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 Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, file, dfs.

--retry-after sets the Retry-After header the fault answers with, such as 5s.
Without one the service's usual hint is sent.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos storage outage --percentage 25
  locally chaos storage outage --percentage 25 --retry-after 5s
  locally chaos storage outage --percentage 100 --location london
  locally chaos storage outage reset --location london
  locally chaos storage outage --percentage 100 --name acct1

Usage

locally chaos storage outage [flags]
  locally chaos storage 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)
      --retry-after string    Retry-After this fault answers with, e.g. 5s or 500ms (the service's usual hint when omitted)
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos storage 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 storage 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 storage partial-response

Send the status, headers and part of the body, then cut the connection.

Send the status, headers and part of the body, then cut the connection. The
client sees a response that ends early.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, file.

Examples:
locally chaos storage partial-response --percentage 25
  locally chaos storage partial-response --percentage 100 --location london
  locally chaos storage partial-response reset --location london
  locally chaos storage partial-response --percentage 100 --name acct1

Usage

locally chaos storage partial-response [flags]
  locally chaos storage partial-response [command]

Flags

-h, --help[=true|false]     help for partial-response
      --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 storage partial-response reset

Remove one partial-response rule, or put the whole fault back to zero.

Reset the partial-response 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 storage partial-response 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 storage request-timeout

Fail requests with the service's own server-side timeout, such as Cosmos DB's 408 or Storage's OperationTimedOut.

Fail requests with the service's own server-side timeout, such as Cosmos DB's
408 or Storage's OperationTimedOut.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, file, dfs.

Examples:
locally chaos storage request-timeout --percentage 25
  locally chaos storage request-timeout --percentage 100 --location london
  locally chaos storage request-timeout reset --location london
  locally chaos storage request-timeout --percentage 100 --name acct1

Usage

locally chaos storage request-timeout [flags]
  locally chaos storage request-timeout [command]

Flags

-h, --help[=true|false]     help for request-timeout
      --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 storage request-timeout reset

Remove one request-timeout rule, or put the whole fault back to zero.

Reset the request-timeout 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 storage request-timeout 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 storage reset

Zero every Storage (data plane) fault and drop every rule.

Zero every Storage (data plane) fault and drop every rule.

Examples:
locally chaos storage reset

Usage

locally chaos storage reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos storage show

Print the current Storage (data plane) chaos configuration.

Print the current Storage (data plane) chaos configuration.

Examples:
locally chaos storage show

Usage

locally chaos storage show [flags]

Flags

-h, --help[=true|false]     help for show
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos storage slow-body

Slow the response body down.

Slow the response body down. The status and headers arrive as usual, then the
body is written with a pause before every write.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, file.

--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.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos storage slow-body --percentage 25 --millis 100-800
  locally chaos storage slow-body --percentage 100 --millis 100-800 --location london
  locally chaos storage slow-body reset --location london
  locally chaos storage slow-body --percentage 100 --millis 100-800 --name acct1

Usage

locally chaos storage slow-body [flags]
  locally chaos storage slow-body [command]

Flags

-h, --help[=true|false]     help for slow-body
      --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 storage slow-body reset

Remove one slow-body rule, or put the whole fault back to zero.

Reset the slow-body 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 storage slow-body 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 storage stale-read

Serve stale reads after a write.

Serve stale reads after a write. Each write opens a window on what it wrote, and
reads inside the window see it as it was before the write.

Without scope flags this sets the fault's rate on Storage (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.

Add an endpoint to narrow a rule to one of the resource's services: --name
acct1:blob. This fault can be scoped to blob, queue, table, dfs.

--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.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos storage stale-read --percentage 25 --seconds 30
  locally chaos storage stale-read --percentage 100 --seconds 30 --location london
  locally chaos storage stale-read reset --location london
  locally chaos storage stale-read --percentage 100 --seconds 30 --name acct1

Usage

locally chaos storage stale-read [flags]
  locally chaos storage stale-read [command]

Flags

-h, --help[=true|false]     help for stale-read
      --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 storage stale-read reset

Remove one stale-read rule, or put the whole fault back to zero.

Reset the stale-read 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 storage stale-read 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)
Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

A local cloud for you and your AI agents.

Your Azure infrastructure, running on your machine. Deploy in seconds, break things freely, and ship to Azure when you're ready.