Container monitoring and alerting test
Run a series of resource experiments on containers to verify that your monitoring and alerting tools detect spikes in CPU, disk I/O, memory, and packet latency.
CPU
Disk
Memory
Latency
Containers
20 minutes
How this Scenario works
This Scenario runs four sequential resource experiments inside your containers, each generating a short spike in a different resource: CPU, disk I/O, memory, and network latency. This validates that your observability stack has visibility into container-level resource consumption.
Why run this Scenario?
This Scenario helps test your observabilty tool by causing short spikes in four different resources. This lets you:
- Verify that your monitoring tools have visibility into container-level resource metrics, not just the host.
- Detect gaps in alert coverage specific to containerized workloads.
- Validate that container resource limits interact correctly with your alerting thresholds.
- Build confidence that resource pressure inside containers will be detected and surfaced before it impacts your application.
What to expect when you run it
As each experiment runs, your monitoring tools show corresponding spikes in CPU, disk I/O, memory usage, and packet latency with minimal delay.
More Scenarios to try
Avoid downtime. Use Gremlin to turn failure into resilience.
Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.
.svg)