New Relic Detects an Incident for CPU Spikes in an ECS Task
New Relic Detects an Incident for CPU Spikes in an ECS Task
New Relic Detects an Incident for CPU Spikes in an ECS Task
New Relic Detects an Incident for CPU Spikes in an ECS Task
Validate your observability to detect a CPU spike in your AWS ECS cluster
Motivation
When you have New Relic configured to detect CPU spikes in your AWS ECS cluster, you can easily validate your observability strategy with this experiment template.
Structure
First, we validate whether New Relic has no ongoing incident. After that, we inject the CPU spike for an ECS service and expected that New Relic detect this as an incident within the given time frame of 3 minutes.
How to use this template?
Import via Hub Connection
Steadybit’s Reliability Hub is already connected to your platform. If you are an admin, you can just easily import templates with just one click.
Import template
Are you on-prem?
This is how you import Templates