Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Incident Check

Check

Check

Checks if there are any open incidents in New Relic.
Install now

Incident Check

Checks if there are any open incidents in New Relic.
Check

Check

Install now

Incident Check

Check

Check

Checks if there are any open incidents in New Relic.
Install now

Incident Check

Checks if there are any open incidents in New Relic.
Check

Check

Install now
Go back to list
YouTube content is not loaded by default for privacy reasons.

Introduction

When executing chaos experiments, you may want to check if incidents in New Relic are popping up. Or the opposite.

The incident check step can be dragged&dropped into the experiment editor. The action needs one or more New Relic accounts to be selected as targets. Once done, you can use it to collect information about the state of the New Relic incidents and, optionally, to verify that they are within the expected condition.

Experiments can be aborted and marked as failed when the incident check's actual state diverges from the expected state. This helps to implement pre-/post-conditions and invariants. For example, to only start an experiment when the system is healthy.

Use Cases

  • Pre-/postcondition or invariant for any experiment.
  • Verify that incidents are triggered during experiments.

Parameters

ParameterDescriptionDefault
DurationHow long should steadybit check for incidents ?30s
Incident Priority FilterWhich incident priorities should be reported"LOW", "MEDIUM", "HIGH", "CRITICAL"
Entity Tag FilterFilter Incidents based on tags of their related entities
ConditionIf you pick a condition, the experiment will fail if the condition is not met.No check, only show incidents
Condition Check ModeHow often should the status be expected. "At least once" or "All the time""All the time"
Statistics
-Stars
Tags
New Relic
Check
Observability
Monitoring
Homepage
hub.steadybit.com/extension/com.steadybit.extension_newrelic
License
MIT
MaintainerSteadybit

Useful Recipes

See all
New Relic detects a Kubernetes pod in crash loop

When one of your containers has problems starting, it may result in a crash loop and, eventually, Kubernetes backing off to restart this container. Verify that New Relic notices a crash loop and will alert you to take action.

Tags:
Kubernetes
New Relic
Restart
Crash loop
Harden Observability
Targets:

New Relic Accounts

Kubernetes pods

More New Relic Account Actions

See all
Create Muting Rule

Creates a muting rule in New Relic.

Other

New Relic Accounts


Start Using Steadybit Today

Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Steadybit logoResilience Hub
Try Steadybit
HubActionsTargetsAdviceExtensionsRecipes
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon