During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
locally chaos monitor
This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos monitor --help prints.
For more information see Chaos Engineering.
locally chaos monitor
Simulate Monitor (data plane) failure modes.
Simulate Monitor (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. These faults reach queries and metrics. Sending telemetry and logs has its own: 'locally chaos monitoringestion'. Examples: locally chaos monitor <fault> --percentage N locally chaos monitor <fault> reset locally chaos monitor show locally chaos monitor reset
Usage
locally chaos monitor [flags] locally chaos monitor [command]
Flags
-h, --help[=true|false] help for monitor
Subcommands
- locally chaos monitor 403 - Answer requests with 403, as when a role assignment has not replicated yet.
- locally chaos monitor 429 - Answer requests with 429 Too Many Requests and a retry hint.
- locally chaos monitor 500 - Answer requests with 500 Internal Server Error.
- locally chaos monitor delivery-delay - Hold messages, events or triggers for the rolled duration before delivering them.
- locally chaos monitor delivery-drop - Deliver nothing for some messages, events or triggers.
- locally chaos monitor drop-connection - Close the connection without answering.
- locally chaos monitor duplicate-delivery - Deliver some messages, events or triggers twice.
- locally chaos monitor incident - Take each resource down for a while, then bring it back.
- locally chaos monitor latency - Hold requests for a random delay before they are handled.
- locally chaos monitor outage - Fail requests for as long as the rule is armed, like a region or service that is down.
- locally chaos monitor request-timeout - Fail requests with the service's own server-side timeout, such as Cosmos DB's 408 or Storage's OperationTimedOut.
- locally chaos monitor reset - Zero every Monitor (data plane) fault and drop every rule.
- locally chaos monitor show - Print the current Monitor (data plane) chaos configuration.
- locally chaos monitor stale-read - Serve stale reads after a write.
locally chaos monitor 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 Monitor (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 monitor 403 --percentage 25 locally chaos monitor 403 --percentage 100 --location london locally chaos monitor 403 reset --location london locally chaos monitor 403 --percentage 100 --name acct1
Usage
locally chaos monitor 403 [flags] locally chaos monitor 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 monitor 403 reset - Remove one 403 rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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. --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 monitor 429 --percentage 25 locally chaos monitor 429 --percentage 25 --retry-after 5s locally chaos monitor 429 --percentage 100 --location london locally chaos monitor 429 reset --location london locally chaos monitor 429 --percentage 100 --name acct1
Usage
locally chaos monitor 429 [flags] locally chaos monitor 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 monitor 429 reset - Remove one 429 rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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 monitor 500 --percentage 25 locally chaos monitor 500 --percentage 100 --location london locally chaos monitor 500 reset --location london locally chaos monitor 500 --percentage 100 --name acct1
Usage
locally chaos monitor 500 [flags] locally chaos monitor 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 monitor 500 reset - Remove one 500 rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos monitor delivery-delay --percentage 25 --seconds 30-120 locally chaos monitor delivery-delay --percentage 100 --seconds 30-120 --location london locally chaos monitor delivery-delay reset --location london locally chaos monitor delivery-delay --percentage 100 --seconds 30-120 --name acct1
Usage
locally chaos monitor delivery-delay [flags] locally chaos monitor 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 monitor delivery-delay reset - Remove one delivery-delay rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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 monitor delivery-drop --percentage 25 locally chaos monitor delivery-drop --percentage 100 --location london locally chaos monitor delivery-drop reset --location london locally chaos monitor delivery-drop --percentage 100 --name acct1
Usage
locally chaos monitor delivery-drop [flags] locally chaos monitor 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 monitor delivery-drop reset - Remove one delivery-drop rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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 monitor drop-connection --percentage 25 locally chaos monitor drop-connection --percentage 100 --location london locally chaos monitor drop-connection reset --location london locally chaos monitor drop-connection --percentage 100 --name acct1
Usage
locally chaos monitor drop-connection [flags] locally chaos monitor 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 monitor drop-connection reset - Remove one drop-connection rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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 monitor duplicate-delivery --percentage 25 locally chaos monitor duplicate-delivery --percentage 100 --location london locally chaos monitor duplicate-delivery reset --location london locally chaos monitor duplicate-delivery --percentage 100 --name acct1
Usage
locally chaos monitor duplicate-delivery [flags] locally chaos monitor 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 monitor duplicate-delivery reset - Remove one duplicate-delivery rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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 monitor incident --percentage 25 --seconds 30-120 --interval 10m locally chaos monitor incident --percentage 100 --seconds 30-120 --interval 10m --location london locally chaos monitor incident reset --location london locally chaos monitor incident --percentage 100 --seconds 30-120 --interval 10m --name acct1
Usage
locally chaos monitor incident [flags] locally chaos monitor 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 monitor incident reset - Remove one incident rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos monitor latency --percentage 25 --seconds 30 locally chaos monitor latency --percentage 100 --seconds 30 --location london locally chaos monitor latency reset --location london locally chaos monitor latency --percentage 100 --seconds 30 --name acct1
Usage
locally chaos monitor latency [flags] locally chaos monitor 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 monitor latency reset - Remove one latency rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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. --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 monitor outage --percentage 25 locally chaos monitor outage --percentage 25 --retry-after 5s locally chaos monitor outage --percentage 100 --location london locally chaos monitor outage reset --location london locally chaos monitor outage --percentage 100 --name acct1
Usage
locally chaos monitor outage [flags] locally chaos monitor 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 monitor outage reset - Remove one outage rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor 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 Monitor (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 monitor request-timeout --percentage 25 locally chaos monitor request-timeout --percentage 100 --location london locally chaos monitor request-timeout reset --location london locally chaos monitor request-timeout --percentage 100 --name acct1
Usage
locally chaos monitor request-timeout [flags] locally chaos monitor 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 monitor request-timeout reset - Remove one request-timeout rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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 monitor reset
Zero every Monitor (data plane) fault and drop every rule.
Zero every Monitor (data plane) fault and drop every rule. Examples: locally chaos monitor reset
Usage
locally chaos monitor reset [flags]
Flags
-h, --help[=true|false] help for reset
--subscription string Subscription UUID (defaults to the configured default)
locally chaos monitor show
Print the current Monitor (data plane) chaos configuration.
Print the current Monitor (data plane) chaos configuration. Examples: locally chaos monitor show
Usage
locally chaos monitor show [flags]
Flags
-h, --help[=true|false] help for show
--subscription string Subscription UUID (defaults to the configured default)
locally chaos monitor 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 Monitor (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. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos monitor stale-read --percentage 25 --seconds 30 locally chaos monitor stale-read --percentage 100 --seconds 30 --location london locally chaos monitor stale-read reset --location london locally chaos monitor stale-read --percentage 100 --seconds 30 --name acct1
Usage
locally chaos monitor stale-read [flags] locally chaos monitor 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 monitor stale-read reset - Remove one stale-read rule, or put the whole fault back to zero.
locally chaos monitor 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 monitor 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)
During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in