/
Compound Check

Compound Check

The Compound Check is a virtual, aggregated check, meaning that there are multiple individual checks, in a specified monitor subgroup, whose statuses/results make up the results of this Compound Check.

Use Case

If you have multiple checks that need to be collectively assessed before creating an event/alert, this is the check type that allows the logic that says, “Whenever X checks are over a certain count/threshold set an aggregate result to all of them.”

Example 1 Global API Application Response: If you have 4 global checks, measuring your API response from 4 different locations, US, EU, APAC, and China but you know that China has a firewall that has caused checks to be periodically down (fatal) for known periods, the Compound Check can create logic that states that 3 of the 4 checks must be in a fatal condition for at least X number of times (or X percentage of the results) before you can declare the API application to be in a Fatal condition.

Example 2 North America Regional Performance over Time: If you have 6 North America checks, measuring your Check-out Cart response times from 6 different locations, 4 US (Northeast, Northwest, Southeast, and Southwest), 2 Canadian (East and West Coasts), the Compound Check can create logic that states that 4 of the 6 checks must be in a slow response/Warning condition least 25% of the results in the last hour before you can send an alert to your operations team to check if your e-commerce application servers might be overloaded.

This will give you the ability to lower your false-positive rates when you set realistic thresholds and have other checks be validators of what may turn out to be a historically unreliable region or network.

Step