Gremlin Scenario: Linux monitoring and alerting test

How it works

How this Scenario works

This Scenario runs four sequential resource experiments on your Linux hosts, each generating a short spike in a different resource: CPU, disk I/O, memory, and network latency. This exercises the full breadth of your observability stack against real resource pressure at the OS level.

Use cases

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 observability tool is receiving metrics for critical resources.
Check for significant delays in receiving and analyzing metrics.
Test any alerts you have configured for resource consumption or exhaution.

Result

What to expect when you run it

As each experiment runs, our monitoring tool shows corresponding spikes in each resource (CPU, disk I/O, memory usage, and packet latency).

Keep going

More Scenarios to try

Kubernetes packet loss

Ensure your Kubernetes systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate liveness/readiness probe and load balancer behavior.

Container packet loss

Ensure your containerized systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.

Windows packet loss

Ensure your Windows systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.

Linux monitoring and alerting test