What is a problem?

This page describes StackState version 4.3.

The StackState 4.3 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.3 version range to upgrade to a more recent release.

Go to the documentation for the latest StackState release.


When a component or relation reports a DEVIATING (orange) or CRITICAL (red) state, StackState will identify this as a problem in your IT environment. As StackState is aware of the connections and dependencies between components in the topology, related unhealthy state changes can be grouped together into a single problem with a single root cause. This is helpful because it will:

  • Speed up problem investigation - all unhealthy elements affected by a single root cause can be found in a dedicated sub-view.

  • Reduce noise - the evolution of the problem can be be tracked as a single entity, rather than a collection of individual, unhealthy elements.

What is a StackState problem?

A problem in StackState is the collection of unhealthy components that can be attributed to a single root cause. A problem is created when a component's health state changes to DEVIATING or CRITICAL. All other components in the landscape with an unhealthy state that can be attributed to the same root cause will be added to the same problem. A problem contains the following components:

  • A single root cause - this is the unhealthy component at the bottom of the dependency chain.

  • Any number of contributing causes - these are all of the unhealthy components that depend on the root cause.

It is possible for a single unhealthy component to be a contributing cause in two separate problems. If there are two potential root cause components for a component's unhealthy state, StackState will see this as two separate problems.

Problem resolution

When the root cause and all contributing cause components have changed to a CLEAR (green) health state, the problem is considered as resolved and will no longer be visible in the StackState UI. A Problem resolved event will be generated.

If the components change back to an unhealthy state in the future, this will be reported as a new problem in StackState.

Changes to problem root cause

Updates to the health state of components in the landscape may result in a change to the root cause of problems. Perhaps an existing root cause switches to a healthy state or a previously healthy upstream dependency switches to an unhealthy state.

Two problems, one root cause

If a component switches its state to unhealthy and would become the new root cause for more than one existing problem, StackState will combine all of these problems into one problem. The original problems will all be incorporated into the oldest problem with the same root cause (subsumed) and the oldest problem will have its root cause updated to be the new root cause component. This would happen, for example, if an upstream dependency of two root cause components switched to an unhealthy state.

The following events will be generated:

  • One Problem updated event for the oldest problem.

  • Problem subsumed events will be generated for all other problems.

One problem, two root causes

If the root cause component of a problem switches its state to healthy, the next unhealthy component at the bottom of the dependency chain will become the new root cause. If there are two or more potential new root causes, StackState will split the problem. As each problem can only have one root cause, a new problem will be created for each potential root cause.

The following events will be generated:

  • One Problem updated event for the problem whose new root cause with the oldest health state change timestamp of all new root causes.

  • Problem created events for all other new problems.

See also

Last updated