AppDynamics
ExtensionAppDynamics
A Steadybit check implementation for data exposed through AppDynamics.ExtensionAppDynamics
ExtensionAppDynamics
A Steadybit check implementation for data exposed through AppDynamics.Extension
Go back to listYouTube content is not loaded by default for privacy reasons.
Introduction to the AppDynamics Extension
The Steadybit AppDynamics Extension bridges the world of Steadybit and AppDynamics. The extension adds checks to your Chaos Engineering experiments to validate AppDynamics Health rules state and reports events of your experiments to AppDynamics as custom events to ease correlation.
Integration and Functionality
Integration of AppDynamics into Steadybit works via the AppDynamics API. Thus, all you need is a AppDynamics's Access token.
Integration of AppDynamics in Steadybit
With the Health Rule Check you can integrate your AppDynamics health rules into your experiments. Verify that AppDynamics health rules notice a fault injected by Steadybit to check that your observability strategy is working as expected.
Integration of Steadybit in AppDynamics
The extension reports experiment executions to AppDynamics if an Application Event ID (A manually created Steadybit App is sufficient) is given, which helps you to correlate experiments with your dashboards.
Installation and Setup
To integrate the AppDynamics extension with your environment, follow our setup guide.
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.
Solution Sketch
- Kubernetes liveness, readiness, and startup probes
