Set an ADMIN_TOKEN secret on the app and redeploy. On Miabi, add it under the app's environment as a secret.
| Host | Version | Clients | Requests | Seen |
|---|
Set DEBUG_ENDPOINTS=true on the app to enable failure injection. The traffic probe below works either way.
Exit the process with status 1. Miabi's restart policy brings it back.
Shows: restarts · alerts · eventsMake /healthz return 503 on the replica that receives this.
Saturate every core for a while.
Shows: metrics · resource alertsAllocate MiB for N seconds. Exceed the memory limit to trigger an OOM restart.
Shows: memory limits · OOM killWrite a burst of log lines.
Shows: live logs · searchFire requests from this browser and tally who answered. With replicas you'll see the load spread; during a canary you'll see the traffic split by version.
Watch what Miabi does during a rolling update: this tool bounces one replica at a time with the chaos endpoint while polling the replica table. Each restarted replica comes back with its request counter reset and, during a canary, a new version. Needs debug endpoints; run it with Redis attached so every replica is listed.