Result Values

Owned by Caleb Miller
Last updated: Jun 07, 2023 by John Ward (Unlicensed)
3 min read

Result Values

In Synthetic Monitoring, various processes and formulas are used to calculate result values.

Result Severity

Check results can be assigned different severities, depending on the resulting value.

Term

Definition/Comments

Term

Definition/Comments

Result

When a check runs, it returns a result—for example, a response time value.

Severity

Depending on the check type, the result value will result in a severity level for the check, displayed in the various views in Synthetic Monitoring.

Severity is a level indicator used to indicate the status of a check based on the results. The severity is used in various displays and alerts, notifications, and events.

Check Status

Four colors represent the current check status

  • Green: Information

  • Yellow: Warning

  • Orange: Error

  • Red: Fatal

The colors are used in any context where the check status is displayed.

Configuration

The configuration of the check affects how the value is converted into a severity.

The result interpretation settings apply some modifications to the result. For example, You can ignore particular combinations of file types and HTTP response codes.

A failed check will, by default, get the severity Fatal.

This can be configured to a different severity with the Check Fail Severity setting.

Preserve Value

With the Preserve Value setting enabled, the returned value will be used and included in aggregated/calculated values.

Note: When a check has failed, the return value is considered Null, and there is no value to store.

Thresholds

The various Threshold settings are used to select a severity for the check result.

The thresholds define an upper (High) and lower (Low) bound on the result for Warning and Error. Values above and below these bounds will cause the corresponding severity.

Note: Preserve that value must enable the thresholds to have any effect since it uses the result value.

Mapping

In addition to the thresholds, you can also configure Severity Mapping to customize rules to assign severities to different error types.

Result Value SLA

In Synthetic Monitoring, SLA is calculated according to a formula, based on the duration of the result types.

Calculation

SLA calculations are affected negatively by the number of Fatal and Error results in a check.

The formula is:

(info + warning) / total

Item

Description

Item

Description

Info

The duration that the check has the severity Information.

Warning

The duration that the check has the severity Warning.

Total

The sum of the duration of all the severities including Information, Warning, Error and Fatal.

Example:

Let´s say that for the period of 11:00 – 12:00 our check has the following severities:

11:00-11:10 Error, duration = 10 min

11:10-11:20 Fatal, duration = 10 min

11:20-11:40 Warning, duration = 20 min

11:40-11:50 Error, duration = 10 min

11:50-12:00 Information, duration = 10 min

The SLA calculation for this example would look like this:

(10 min Information + 20 min Warning) / 60 min Total = 0.5 = 50% SLA

 

Data Retention

Your monitoring results are stored on Apica servers for a limited time. The storage time varies with the type of data.

1. Checks

1A. All Checks

  • Check Result Graph: 65 days

1B. Check Specific Data Retention

Firefox, Chrome, iPhone (Mobile Website), iPad (Mobile Website), Android (Mobile Website), Windows Phone (Mobile Website)

ZebraTester, Mobile browser, iPhone (Mobile App), iPad (Mobile App), Android (Mobile App), Windows Phone (Mobile App)

Internet Explorer

Command Check, Ping, Port, DNS, Appdynamics, Traceroute, FTP, New Relic, SSL:

Analyze Metrics

Response time and Return Value (Only for the 3rd dropdown):

Response time and Return Value for the 4th drop-down:

All Other Metrics

Analyze Trends

Can't find what you're looking for? Send an E-mail to support@apica.io