Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Problem Check

Check

Check

Checks if there are any problems in Dynatrace
Install now

Problem Check

Checks if there are any problems in Dynatrace
Check

Check

Install now

Problem Check

Check

Check

Checks if there are any problems in Dynatrace
Install now

Problem Check

Checks if there are any problems in Dynatrace
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 problems in Dynatrace are popping up. Or the opposite.

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

Experiments can be aborted and marked as failed when the Problem 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.

At last, to help you understand the problems' status and how they evolved, the run view also contains a status visualization. Through this visualization, you can see what states the Dynatrace's problems contained throughout the experiment execution.

Use Cases

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

Parameters

ParameterDescriptionDefault
DurationHow long should steadybit check for problems?30s
ConditionIf you pick a condition, the experiment will fail if the condition is not met.No check, only show problems
Condition Check ModeHow often should the status be expected. "At least once" or "All the time""All the time"
Statistics
-Stars
Tags
Dynatrace
Check
Observability
Monitoring
Homepage
hub.steadybit.com/extension/com.steadybit.extension_dynatrace
License
MIT
MaintainerSteadybit
Install now

Useful Templates

See all
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
Crash loop
Dynatrace
Harden Observability
Kubernetes

Kubernetes cluster

Kubernetes pods

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