Dynatrace
Extension
Dynatrace
Bi-directional integration of Steadybit and Dynatrace via the Dynatrace API.Extension
Dynatrace
Extension
Dynatrace
Bi-directional integration of Steadybit and Dynatrace via the Dynatrace API.Extension
YouTube content is not loaded by default for privacy reasons.
Introduction to the Dynatrace Extension
The Steadybit Dynatrace Extension bridges the world of Steadybit and Dynatrace. The extension adds checks to your Chaos Engineering experiments to validate detection of Dynatrace problems and reports events of your experiments to Dynatrace to ease correlation.
Integration and Functionality
Integration of Dynatrace into Steadybit works via the Dynatrace API. Thus, all you need is an API Token and the API base URL of your Dynatrace environment.
Integration of Dynatrace in Steadybit
With the Problem Check you can integrate your Dynatrace problems into your experiments. Check that your observability strategy is working as expected by verifying that Dynatrace notices a problem which is injected by Steadybit.
With the Create Maintenance Window you can mute your alerting during an experiment to avoid false alarms and avoid incident processes.
Integration of Steadybit in Dynatrace
The extension automatically reports experiment executions to Dynatrace which helps you to correlate detected anomalies in Dynatrace. Furthermore, you can get a dashboard to see amount of experiment executions in your Dynatrace environment.
Installation and Setup
To integrate the Dynatrace extension with your environment, follow our setup guide.
Dynatrace should detect a crash looping as problem
Verify that Dynatrace alerts you on pods not being ready to accept traffic for a certain amount of 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 Dynatrace has no problems for an entity and doesn't alert already on non-ready containers. As soon as one of the containers is crash looping, caused by the Steadybit attack crash loop, Dynatrace should detect the problem and alert to ensure your on-call team is taking action.
Solution Sketch
- Kubernetes liveness, readiness, and startup probes
Kubernetes cluster
Kubernetes pods