Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

New Relic Detects an Incident for CPU Spikes in an ECS Task

Targets:
ECS Tasks
New Relic Accounts
Use Template

New Relic Detects an Incident for CPU Spikes in an ECS Task

Use Template

New Relic Detects an Incident for CPU Spikes in an ECS Task

Targets:
ECS Tasks
New Relic Accounts
Use Template

New Relic Detects an Incident for CPU Spikes in an ECS Task

Use Template
Go back to list

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

Import as Experiment

Simply download the template and upload it as an experiment to use it once. Perfect if you are no administrator in the platform and just want to use the template once.

.json (4KB)

Used Actions

See all
Incident Check
Checks if there are any open incidents in New Relic.
CheckCheck
New Relic Accounts
>_ boost your chaos journey Connect Your Hub to Steadybit

Maximise Steadybit potential! Connect your own Hub to the platform and smoothly import your own templates: using them it’s never been this easy!

Tags
New Relic
AWS ECS
CPU
License
MIT
MaintainerSteadybit
Use Template
Steadybit logoResilience Hub
Try Steadybit
© 2025 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon