Container monitoring and alerting test

What this Scenario does

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.

‍

Expected outcome

As each experiment runs, your monitoring tools show corresponding spikes in CPU, disk I/O, memory usage, and packet latency with minimal delay.