Workload status configuration

You can configure your workload status using three methods:

• Static: Manually set a fixed status for maintenance windows or other scenarios where you want to communicate a specific workload state
• Automatic: Status is calculated from rules you configure to determine the status of each entity group and the overall workload
• Alert policy and conditions: Set up custom policies and conditions to determine workload health status based on alert states

To manage workload status settings:

1. Navigate to your workload
2. In the left sidebar under SETTINGS, click Configure health status
3. The Workload status setup page will open, showing the three setup method options

Configure the automatic workload status

Automatic status calculation uses the status of each entity in your workload to determine a single, overall workload status value based on rules you define.

Not all entities in a workload are equally important from a performance, errors, or availability perspective:

• You might want your workload to show as disrupted if an essential synthetic monitor or service has a critical incident going on.
• However, if your host infrastructure has a certain redundancy and resilience to outages, you might not need to change your workload status from Operational just because a single host has an alert incident going on.

How automatic status works

The automatic status configuration uses a rule-based system where:

• Each rule evaluates a group of entities (based on entity type, tags, GUIDs, or combinations)
• Each rule produces a status based on the entity statuses in that group
• The result of the workload status equals the worst status of all rule results

By default, when you create a workload, the following rules to calculate its status are added:

1. For entity types close to the digital experience (that is, synthetic monitors, browser applications, mobile applications, and services), the worst available status is propagated.
2. For any other entity type, which are basically infrastructure entities, the best available status is propagated.

To configure automatic status:

1. On the Workload status setup page, select the Automatic option
2. The Automatic Status Configuration section will expand, showing:
   • A toggle to enable or disable automatic status calculation
   • The rules that determine entity group status and overall workload status
   • A preview showing the current workload status based on your configuration
3. Enable the toggle if it's not already on
4. Review the existing rules or add new ones as needed

Create custom rules

To customize the automatic workload status, you can define your own rules. A rule consists of a group of entities and a roll up mode:

1. Define the group of entities based on entity types, tag values, GUIDs, or a combination of all of them.
2. Decide how to propagate the status of these entities to the group status:

• Roll up the best status: the group status matches the less critical status of all belonging entities. Use this option when you want the group status to be operational as long as at least one entity in the group is still operational.
• Roll up the worst status: the group status matches the most critical status of all belonging entities. Use this option when you want the group status to indicate a degradation or a disruption of service as soon as one entity in the group is not operational. You can also decide to roll up the worst status only after a certain amount of entities are not operational.

3. Save the rule and proceed to create another one if you need to.

The final workload status equals the worst status among all the individual group statuses.

A rule for remaining entities

For an easier and more dynamic status configuration, you can use a roll-up type for all entities that aren't evaluated in any other rule that you have defined before. In particular, if you don't add any other rule at all, the rule for remaining entities will take into account all the entities in the workload.

When combined with the grouping by entity type option, this special rule allows you to get a general sense of how each entity type in your workload is doing, without having to configure a rule for each entity type. Therefore, we recommend that you always set a rule for all remaining entities grouped by type, and roll up their worst status to quickly detect when all entities in a layer of your workload stack are not operational.

Configure alert policy and conditions

The third method for determining workload health status is to set up custom alert policies and conditions. This method allows you to define specific conditions that will trigger workload health status changes based on alert states.

To configure alert policy and conditions:

1. On the Workload status setup page, select the Alert policy and conditions option
2. Click Configure to open the Workload health status conditions page
3. On the conditions page, you can:
   • Search for existing conditions by name, condition ID, or policy name
   • Filter conditions using the dropdown filters for Condition Name and Policy Name
   • Create new alert policy: Click + New alert policy to define a new policy
   • Create new alert condition: Click + New alert condition to add specific conditions

The status of these conditions will determine workload health. Any issues created by these conditions will make the workload report as unhealthy.

Set a static workload status

If you want to communicate the status for your workload regardless of any automatic calculation based on rules, you can set a static status value for your workload from one of the available status values.

This is useful during maintenance tasks to communicate to other teams that the status of your workload is disrupted, to provide further information, or to give the time you expect the workload to be operational again.

To set up a static workload status:

1. On the Workload status setup page, select the Static option
2. Click Configure to open the Set static status panel
3. In the Select status dropdown, choose a status value (such as Operational, Degraded, Critical, or Disrupted)
4. Optionally, enter a short summary in the Summary field to help identify the status at a glance
5. Optionally, provide a detailed description in the Description field explaining what's happening to the workload
6. Click Save to apply the static status
7. Back on the main status setup page, click Save to confirm your configuration

Any configured static status always overrides any other status values calculated automatically. Static status is particularly useful when you want to override automatic rules and communicate a certain status during maintenance windows or other planned events.

Understand the status value

On the Workload status setup page, you can see how the status calculation is configured and the result of all the rules and/or static statuses that determine the global workload status value.

Preview panel

The Preview panel on the right side of the page shows:

• Unsaved changes indicator: A banner appears when you have pending configuration changes
• Entity status: The current status of entities in your workload
• Workload status: The calculated overall status (e.g., "Operational") with a colored indicator
• Status explanation: Details about which rules or conditions determine the current status

Any change that you make to the status configuration will become effective only once you save the changes. The preview updates in real-time as you modify your configuration, showing you what the status result would be if you saved the configuration at that point.

To save your configuration:

1. Review the preview to ensure the status calculation matches your expectations
2. Click Save in the bottom right of the page
3. The new configuration will take effect immediately

Status calculation order

When multiple configuration methods are active:

1. Static status always takes precedence and overrides any automatic or alert-based calculations
2. If no static status is set, Automatic rules or Alert policy and conditions determine the status based on your configuration
3. The workload status equals the worst status among all evaluated rules or conditions