Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Workload Check

Check

Check

Checks the state of a given workload in New Relic.
Install now

Workload Check

Checks the state of a given workload in New Relic.
Check

Check

Install now

Workload Check

Check

Check

Checks the state of a given workload in New Relic.
Install now

Workload Check

Checks the state of a given workload 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 the status of a workload in New Relic are popping up. Or the opposite.

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

Experiments can be aborted and marked as failed when the workload 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 the state of the workload ?30s
Expected StatesWhich states are expected?"OPERATIONAL", "CRITICAL", "UNKNOWN", "DISRUPTED", "DEGRADED"
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
Install now

Useful Templates

See all
New Relic should detect a disrupted workflow when a workload is unavailable

Verify that New Relic alerts you to disruptions in your workflow, such as a critical deployment without pods ready to serve traffic.

Motivation

Kubernetes features a liveness probe to determine whether your pod is healthy and can accept traffic. If Kubernetes cannot probe a pod, it restarts it in the hope that it will eventually be ready. In case it is a critical deployment, New Relic workflow should alert on this disruption

Structure

First, check that the New Relic Workflow is marked as operational As soon as all pods of a workload aren't reachable, caused by the block traffic attack, New Relic should detect this by marking the workflow as disrupted and ensuring your on-call team is taking action.

Solution Sketch

  • Kubernetes liveness, readiness, and startup probes
  • New Relic Workflow
New Relic
Harden Observability
Kubernetes

Containers

Kubernetes cluster

New Relic Accounts

New Relic Workloads

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
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon