During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
locally chaos iothub
This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos iothub --help prints.
For more information see Chaos Engineering and IoT Hub Emulator.
locally chaos iothub
Simulate IoT Hub (data plane) failure modes.
Simulate IoT Hub (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 iothub <fault> --percentage N locally chaos iothub <fault> reset locally chaos iothub show locally chaos iothub reset
Usage
locally chaos iothub [flags] locally chaos iothub [command]
Flags
-h, --help[=true|false] help for iothub
Subcommands
- locally chaos iothub 403 - Answer requests with 403, as when a role assignment has not replicated yet.
- locally chaos iothub 429 - Answer requests with 429 Too Many Requests and a retry hint.
- locally chaos iothub 500 - Answer requests with 500 Internal Server Error.
- locally chaos iothub connack-refuse - Refuse MQTT connections.
- locally chaos iothub delivery-delay - Hold messages, events or triggers for the rolled duration before delivering them.
- locally chaos iothub delivery-drop - Deliver nothing for some messages, events or triggers.
- locally chaos iothub disconnect - Close live connections cleanly, in the protocol's own terms, so the client has to reconnect.
- locally chaos iothub drop-connection - Close the connection without answering.
- locally chaos iothub entity-disabled - Refuse requests because the entity is disabled.
- locally chaos iothub latency - Hold requests for a random delay before they are handled.
- locally chaos iothub outage - Fail requests for as long as the rule is armed, like a region or service that is down.
- locally chaos iothub quota-exceeded - Refuse requests because a quota is full.
- locally chaos iothub reset - Zero every IoT Hub (data plane) fault and drop every rule.
- locally chaos iothub show - Print the current IoT Hub (data plane) chaos configuration.
locally chaos iothub 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 IoT Hub (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 iothub 403 --percentage 25 locally chaos iothub 403 --percentage 100 --location london locally chaos iothub 403 reset --location london locally chaos iothub 403 --percentage 100 --name acct1
Usage
locally chaos iothub 403 [flags] locally chaos iothub 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 iothub 403 reset - Remove one 403 rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub 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 IoT Hub (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 iothub 429 --percentage 25 locally chaos iothub 429 --percentage 25 --retry-after 5s locally chaos iothub 429 --percentage 100 --location london locally chaos iothub 429 reset --location london locally chaos iothub 429 --percentage 100 --name acct1
Usage
locally chaos iothub 429 [flags] locally chaos iothub 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 iothub 429 reset - Remove one 429 rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub 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 IoT Hub (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 iothub 500 --percentage 25 locally chaos iothub 500 --percentage 100 --location london locally chaos iothub 500 reset --location london locally chaos iothub 500 --percentage 100 --name acct1
Usage
locally chaos iothub 500 [flags] locally chaos iothub 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 iothub 500 reset - Remove one 500 rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub connack-refuse
Refuse MQTT connections.
Refuse MQTT connections. The CONNACK says the server is unavailable or the client is not authorised, and the connection closes. Without scope flags this sets the fault's rate on IoT Hub (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 iothub connack-refuse --percentage 25 locally chaos iothub connack-refuse --percentage 100 --location london locally chaos iothub connack-refuse reset --location london locally chaos iothub connack-refuse --percentage 100 --name acct1
Usage
locally chaos iothub connack-refuse [flags] locally chaos iothub connack-refuse [command]
Flags
-h, --help[=true|false] help for connack-refuse
--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 iothub connack-refuse reset - Remove one connack-refuse rule, or put the whole fault back to zero.
locally chaos iothub connack-refuse reset
Remove one connack-refuse rule, or put the whole fault back to zero.
Reset the connack-refuse 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 iothub connack-refuse 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 iothub 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 IoT Hub (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 iothub delivery-delay --percentage 25 --seconds 30-120 locally chaos iothub delivery-delay --percentage 100 --seconds 30-120 --location london locally chaos iothub delivery-delay reset --location london locally chaos iothub delivery-delay --percentage 100 --seconds 30-120 --name acct1
Usage
locally chaos iothub delivery-delay [flags] locally chaos iothub 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 iothub delivery-delay reset - Remove one delivery-delay rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub 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 IoT Hub (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 iothub delivery-drop --percentage 25 locally chaos iothub delivery-drop --percentage 100 --location london locally chaos iothub delivery-drop reset --location london locally chaos iothub delivery-drop --percentage 100 --name acct1
Usage
locally chaos iothub delivery-drop [flags] locally chaos iothub 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 iothub delivery-drop reset - Remove one delivery-drop rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub 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 IoT Hub (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 iothub disconnect --percentage 25 --interval 10m locally chaos iothub disconnect --percentage 100 --interval 10m --location london locally chaos iothub disconnect reset --location london locally chaos iothub disconnect --percentage 100 --interval 10m --name acct1
Usage
locally chaos iothub disconnect [flags] locally chaos iothub 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 iothub disconnect reset - Remove one disconnect rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub 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 IoT Hub (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 iothub drop-connection --percentage 25 locally chaos iothub drop-connection --percentage 25 --interval 30s locally chaos iothub drop-connection --percentage 100 --location london locally chaos iothub drop-connection reset --location london locally chaos iothub drop-connection --percentage 100 --name acct1
Usage
locally chaos iothub drop-connection [flags] locally chaos iothub 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 iothub drop-connection reset - Remove one drop-connection rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub entity-disabled
Refuse requests because the entity is disabled.
Refuse requests because the entity is disabled. The error is MessagingEntityDisabled for a queue, topic or event hub, and DeviceDisabled for an IoT device. Without scope flags this sets the fault's rate on IoT Hub (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 iothub entity-disabled --percentage 25 locally chaos iothub entity-disabled --percentage 100 --location london locally chaos iothub entity-disabled reset --location london locally chaos iothub entity-disabled --percentage 100 --name acct1
Usage
locally chaos iothub entity-disabled [flags] locally chaos iothub entity-disabled [command]
Flags
-h, --help[=true|false] help for entity-disabled
--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 iothub entity-disabled reset - Remove one entity-disabled rule, or put the whole fault back to zero.
locally chaos iothub entity-disabled reset
Remove one entity-disabled rule, or put the whole fault back to zero.
Reset the entity-disabled 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 iothub entity-disabled 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 iothub 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 IoT Hub (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 iothub latency --percentage 25 --seconds 30 locally chaos iothub latency --percentage 25 --seconds 30 --interval 30s locally chaos iothub latency --percentage 100 --seconds 30 --location london locally chaos iothub latency reset --location london locally chaos iothub latency --percentage 100 --seconds 30 --name acct1
Usage
locally chaos iothub latency [flags] locally chaos iothub 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 iothub latency reset - Remove one latency rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub 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 IoT Hub (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 iothub outage --percentage 25 locally chaos iothub outage --percentage 25 --retry-after 5s locally chaos iothub outage --percentage 100 --location london locally chaos iothub outage reset --location london locally chaos iothub outage --percentage 100 --name acct1
Usage
locally chaos iothub outage [flags] locally chaos iothub 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 iothub outage reset - Remove one outage rule, or put the whole fault back to zero.
locally chaos iothub 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 iothub 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 iothub quota-exceeded
Refuse requests because a quota is full.
Refuse requests because a quota is full. On the control plane a resource creation (PUT) gets 409 Conflict with QuotaExceeded; on a data plane the service's own quota error is sent, such as a full Service Bus queue. Without scope flags this sets the fault's rate on IoT Hub (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 iothub quota-exceeded --percentage 25 locally chaos iothub quota-exceeded --percentage 100 --location london locally chaos iothub quota-exceeded reset --location london locally chaos iothub quota-exceeded --percentage 100 --name acct1
Usage
locally chaos iothub quota-exceeded [flags] locally chaos iothub quota-exceeded [command]
Flags
-h, --help[=true|false] help for quota-exceeded
--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 iothub quota-exceeded reset - Remove one quota-exceeded rule, or put the whole fault back to zero.
locally chaos iothub quota-exceeded reset
Remove one quota-exceeded rule, or put the whole fault back to zero.
Reset the quota-exceeded 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 iothub quota-exceeded 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 iothub reset
Zero every IoT Hub (data plane) fault and drop every rule.
Zero every IoT Hub (data plane) fault and drop every rule. Examples: locally chaos iothub reset
Usage
locally chaos iothub reset [flags]
Flags
-h, --help[=true|false] help for reset
--subscription string Subscription UUID (defaults to the configured default)
locally chaos iothub show
Print the current IoT Hub (data plane) chaos configuration.
Print the current IoT Hub (data plane) chaos configuration. Examples: locally chaos iothub show
Usage
locally chaos iothub 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