locally chaos containerapps

Preview

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

locally chaos containerapps

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

For more information see Chaos Engineering.

locally chaos containerapps

Simulate Container Apps (data plane) failure modes.

Simulate Container Apps (data plane) failure modes.

A fault command sets the fault's rate. With a scope flag (--location / --name /
--traffic / --path) it adds or edits a rule instead.

Examples:
locally chaos containerapps <fault> --percentage N
  locally chaos containerapps <fault> reset
  locally chaos containerapps show
  locally chaos containerapps reset

Usage

locally chaos containerapps [flags]
  locally chaos containerapps [command]

Flags

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

Subcommands

locally chaos containerapps 403

Answer requests with Envoy's 403 RBAC: access denied reply.

Answer requests with Envoy's 403 RBAC: access denied reply. The app never sees
them.

Without scope flags this sets the fault's rate on Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

Examples:
locally chaos containerapps 403 --percentage 25
  locally chaos containerapps 403 --percentage 100 --location london
  locally chaos containerapps 403 reset --location london
  locally chaos containerapps 403 --percentage 100 --name my-app
  locally chaos containerapps 403 --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps 403 --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps 403 [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --percentage int        How often this fault fires, 0-100 (required)
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps 429

Answer requests with Envoy's 429 local_rate_limited reply and a Retry-After header, as the app's ingress does.

Answer requests with Envoy's 429 local_rate_limited reply and a Retry-After
header, as the app's ingress does. The app never sees them.

Without scope flags this sets the fault's rate on Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

--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 containerapps 429 --percentage 25
  locally chaos containerapps 429 --percentage 25 --retry-after 5s
  locally chaos containerapps 429 --percentage 100 --location london
  locally chaos containerapps 429 reset --location london
  locally chaos containerapps 429 --percentage 100 --name my-app
  locally chaos containerapps 429 --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps 429 --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps 429 [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --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)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps 500

Answer requests with Envoy's 500 reply, as the app's ingress does.

Answer requests with Envoy's 500 reply, as the app's ingress does. The app never
sees them.

Without scope flags this sets the fault's rate on Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

Examples:
locally chaos containerapps 500 --percentage 25
  locally chaos containerapps 500 --percentage 100 --location london
  locally chaos containerapps 500 reset --location london
  locally chaos containerapps 500 --percentage 100 --name my-app
  locally chaos containerapps 500 --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps 500 --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps 500 [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --percentage int        How often this fault fires, 0-100 (required)
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps 502

Answer requests with 502 Bad Gateway from the service's front end, as when it cannot reach the app behind it.

Answer requests with 502 Bad Gateway from the service's front end, as when it
cannot reach the app behind it. The app never sees the request.

Without scope flags this sets the fault's rate on Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

Examples:
locally chaos containerapps 502 --percentage 25
  locally chaos containerapps 502 --percentage 100 --location london
  locally chaos containerapps 502 reset --location london
  locally chaos containerapps 502 --percentage 100 --name my-app
  locally chaos containerapps 502 --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps 502 --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps 502 [flags]
  locally chaos containerapps 502 [command]

Flags

-h, --help[=true|false]     help for 502
      --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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --percentage int        How often this fault fires, 0-100 (required)
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 502 reset

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

Reset the 502 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 containerapps 502 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps 504

Answer requests with 504 Gateway Timeout from the service's front end, as when the app behind it takes too long.

Answer requests with 504 Gateway Timeout from the service's front end, as when
the app behind it takes too long. The app never sees the request.

Without scope flags this sets the fault's rate on Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

Examples:
locally chaos containerapps 504 --percentage 25
  locally chaos containerapps 504 --percentage 100 --location london
  locally chaos containerapps 504 reset --location london
  locally chaos containerapps 504 --percentage 100 --name my-app
  locally chaos containerapps 504 --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps 504 --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps 504 [flags]
  locally chaos containerapps 504 [command]

Flags

-h, --help[=true|false]     help for 504
      --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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --percentage int        How often this fault fires, 0-100 (required)
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 504 reset

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

Reset the 504 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 containerapps 504 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps cold-start

Make the app start from cold.

Make the app start from cold. Whenever it starts or restarts, requests get the
platform's warm-up 503 until the rolled window closes.

Without scope flags this sets the fault's rate on Container Apps (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 containerapps cold-start --percentage 25 --seconds 30-120
  locally chaos containerapps cold-start --percentage 100 --seconds 30-120 --location london
  locally chaos containerapps cold-start reset --location london
  locally chaos containerapps cold-start --percentage 100 --seconds 30-120 --name acct1

Usage

locally chaos containerapps cold-start [flags]
  locally chaos containerapps cold-start [command]

Flags

-h, --help[=true|false]     help for cold-start
      --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 containerapps cold-start reset

Remove one cold-start rule, or put the whole fault back to zero.

Reset the cold-start 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 containerapps cold-start 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 containerapps disconnect

Close live WebSockets cleanly.

Close live WebSockets cleanly. Every interval each open WebSocket is rolled for;
on a hit the client gets a 1001 Going Away close frame, then the TCP connection
is closed. Compare drop-connection, which resets the connection with no close
frame.

Without scope flags this sets the fault's rate on Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

--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 containerapps disconnect --percentage 25 --interval 10m
  locally chaos containerapps disconnect --percentage 100 --interval 10m --location london
  locally chaos containerapps disconnect reset --location london
  locally chaos containerapps disconnect --percentage 100 --interval 10m --name my-app
  locally chaos containerapps disconnect --percentage 100 --interval 10m --name my-app --traffic websocket
  locally chaos containerapps disconnect --percentage 100 --interval 10m --name my-app --path /api/

Usage

locally chaos containerapps disconnect [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --percentage int        How often this fault fires, 0-100 (required)
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps 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; over HTTP/2, where one request cannot cut a
shared connection, it gets the front end's 503 instead. With --interval it also
cuts live WebSockets: 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 Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

--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 containerapps drop-connection --percentage 25
  locally chaos containerapps drop-connection --percentage 25 --interval 30s
  locally chaos containerapps drop-connection --percentage 100 --location london
  locally chaos containerapps drop-connection reset --location london
  locally chaos containerapps drop-connection --percentage 100 --name my-app
  locally chaos containerapps drop-connection --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps drop-connection --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps drop-connection [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --percentage int        How often this fault fires, 0-100 (required)
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps exit

Kill the app on a schedule, as a crash would.

Kill the app on a schedule, as a crash would. Every interval each app is rolled
for; on a hit its containers (a Function App's worker process) are killed, and
the platform starts it again.

Without scope flags this sets the fault's rate on Container Apps (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 containerapps exit --percentage 25 --interval 10m
  locally chaos containerapps exit --percentage 100 --interval 10m --location london
  locally chaos containerapps exit reset --location london
  locally chaos containerapps exit --percentage 100 --interval 10m --name acct1

Usage

locally chaos containerapps exit [flags]
  locally chaos containerapps exit [command]

Flags

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

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

Reset the exit 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 containerapps exit 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 containerapps freeze

Pause the app on a schedule.

Pause the app on a schedule. Every interval each app is rolled for; on a hit its
containers (a Function App's worker process) are paused for the rolled duration,
then resume where they were. Nothing is closed: requests and WebSockets to it
just go quiet until it resumes.

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

Usage

locally chaos containerapps freeze [flags]
  locally chaos containerapps freeze [command]

Flags

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

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

Reset the freeze 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 containerapps freeze 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 containerapps latency

Hold requests for a random delay before the app sees them.

Hold requests for a random delay before the app sees them. The response is
unchanged, just late; a WebSocket handshake is held the same way. With
--interval it also stalls live WebSockets: 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 Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

--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 containerapps latency --percentage 25 --seconds 30
  locally chaos containerapps latency --percentage 25 --seconds 30 --interval 30s
  locally chaos containerapps latency --percentage 100 --seconds 30 --location london
  locally chaos containerapps latency reset --location london
  locally chaos containerapps latency --percentage 100 --seconds 30 --name my-app
  locally chaos containerapps latency --percentage 100 --seconds 30 --name my-app --traffic websocket
  locally chaos containerapps latency --percentage 100 --seconds 30 --name my-app --path /api/

Usage

locally chaos containerapps latency [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --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)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps outage

Fail requests outright with Envoy's 503 "upstream connect error", as the app's ingress does when no replica answers.

Fail requests outright with Envoy's 503 "upstream connect error", as the app's
ingress does when no replica answers. The app never sees them. A WebSocket
handshake is refused the same way, and when the outage starts every WebSocket
already open to the app is closed once, with a 1001 Going Away close frame.

Without scope flags this sets the fault's rate on Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

--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 containerapps outage --percentage 25
  locally chaos containerapps outage --percentage 25 --retry-after 5s
  locally chaos containerapps outage --percentage 100 --location london
  locally chaos containerapps outage reset --location london
  locally chaos containerapps outage --percentage 100 --name my-app
  locally chaos containerapps outage --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps outage --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps outage [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --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)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps 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 Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

Examples:
locally chaos containerapps partial-response --percentage 25
  locally chaos containerapps partial-response --percentage 100 --location london
  locally chaos containerapps partial-response reset --location london
  locally chaos containerapps partial-response --percentage 100 --name my-app
  locally chaos containerapps partial-response --percentage 100 --name my-app --traffic websocket
  locally chaos containerapps partial-response --percentage 100 --name my-app --path /api/

Usage

locally chaos containerapps partial-response [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --percentage int        How often this fault fires, 0-100 (required)
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

locally chaos containerapps reset

Zero every Container Apps (data plane) fault and drop every rule.

Zero every Container Apps (data plane) fault and drop every rule.

Examples:
locally chaos containerapps reset

Usage

locally chaos containerapps reset [flags]

Flags

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

locally chaos containerapps restart

Restart the app on a schedule.

Restart the app on a schedule. Every interval each app is rolled for; on a hit
it restarts the way its Restart action does, dropping its connections.

Without scope flags this sets the fault's rate on Container Apps (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 containerapps restart --percentage 25 --interval 10m
  locally chaos containerapps restart --percentage 100 --interval 10m --location london
  locally chaos containerapps restart reset --location london
  locally chaos containerapps restart --percentage 100 --interval 10m --name acct1

Usage

locally chaos containerapps restart [flags]
  locally chaos containerapps restart [command]

Flags

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

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

Reset the restart 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 containerapps restart 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 containerapps show

Print the current Container Apps (data plane) chaos configuration.

Print the current Container Apps (data plane) chaos configuration.

Examples:
locally chaos containerapps show

Usage

locally chaos containerapps show [flags]

Flags

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

locally chaos containerapps 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 Container Apps (data plane).
With --location / --name / --traffic / --path 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.

--traffic narrows a rule to http (page loads, API and gRPC calls) or websocket
(WebSocket handshakes and the connections they open). --path narrows it to
requests whose path starts with the value, such as /api/; it is a plain,
case-sensitive prefix, so /api also matches /apis. They combine with --name and
--location on one rule, and a rule naming an app outranks one naming only
traffic or a path - so to spare one app's path, put both on the same rule.

--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 containerapps slow-body --percentage 25 --millis 100-800
  locally chaos containerapps slow-body --percentage 100 --millis 100-800 --location london
  locally chaos containerapps slow-body reset --location london
  locally chaos containerapps slow-body --percentage 100 --millis 100-800 --name my-app
  locally chaos containerapps slow-body --percentage 100 --millis 100-800 --name my-app --traffic websocket
  locally chaos containerapps slow-body --percentage 100 --millis 100-800 --name my-app --path /api/

Usage

locally chaos containerapps slow-body [flags]
  locally chaos containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --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)
      --traffic string        Scope this rule to one kind of traffic: http or websocket

Subcommands

locally chaos containerapps 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 containerapps 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
      --path string           Scope this rule to requests whose path starts with this, e.g. /api/
      --subscription string   Subscription UUID (defaults to the configured default)
      --traffic string        Scope this rule to one kind of traffic: http or websocket
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.