Event Check

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

Experiments can be aborted and marked as failed when the Events 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 events are triggered during incidents.

Parameters

Parameter	Description	Default
Duration	How long should steadybit check for events ?	30s
Condition	If you pick a condition, the experiment will fail if the condition is not met.	No check, only show events
Condition Check Mode	How often should the status be expected. "At least once" or "All the time"	"All the time"
Event Type Filter	Which events should be reported	"INCIDENT", "ISSUE"
Event Severity Filter	Which severity should be reported	"Warning"

Statistics

-Stars

Instana should detect a crash looping as incident

Intent

Verify that Instana alerts you that pods are not ready to accept traffic for some 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 Instana has no critical events for an application perspective. As soon as one of the containers is crash looping, caused by the Steadybit attack crash loop, Instana should detect this via a critical event to ensure your on-call team is taking action.