Health Rule Check

Check

New

Collects information about the health-rule state and optionally verifies that the rule has an expected state.

Targets:

AppDynamics health rules

Install now

Health Rule Check

Collects information about the health-rule state and optionally verifies that the rule has an expected state.

Check

Targets:

AppDynamics health rules

Install now

Health Rule Check

Check

New

Collects information about the health-rule state and optionally verifies that the rule has an expected state.

Targets:

AppDynamics health rules

Install now

Health Rule Check

Collects information about the health-rule state and optionally verifies that the rule has an expected state.

Check

Targets:

AppDynamics health rules

Install now

Go back to list

Steadybit's "Health Rule Check" allows you to verify the behaviour of your AppDynamics alert rules.

Introduction

The health rule check step can be dragged&dropped into the experiment editor. Once done, you can use it to collect information about the state of the AppDynamics health rules and, optionally, to verify that they are within the expected state.

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

At last, to help you understand the health rule states and how they evolved, the run view also contains a state visualization. Through this visualization, you can see what states the Health rules had throughout the experiment execution.

Use Cases

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

Parameters

Parameter	Description	Default
Duration	How long should the state of the alert rule be checked	30s
Expected State	The expected state of the health rule. Violating or not.
State Check Mode	How often should the state be expected. "At least once" or "All the time"	"All the time"

Useful Templates

See all

AppDynamics alerts when a Kubernetes pod is in crash loop

Verify that an AppDynamics health violation alerts you when pods are not ready to accept traffic for a certain time.

Motivation

Kubernetes features a readiness probe to determine whether your pod is ready to accept traffic. If it isn't becoming ready, Kubernetes tries to solve it by restarting the underlying container and hoping to achieve its readiness eventually. If this isn't working, Kubernetes will eventually back off to restart the container, and the Kubernetes resource remains non-functional.

Structure

First, check that the AppDynamics health violation responsible for tracking non-ready containers is in a non-violating state. As soon as one of the containers is crash looping, caused by the crash loop attack, the AppDynamics health violation should notify and escalate it to your on-call team.