Understanding Status Filters

Olivia McCormack
Olivia McCormack
  • Updated

While you're Setting up Ticket Rules in Backup Radar, you'll choose between two filters (Statuses and No successful results detected in __ days).
Status.png

These filters are a key part of your Ticket Rules, and what will and won't trigger an alert. While it's not possible to enable both filters in the same Ticket Rule, you can always create two rules for the same backup(s) if you would like to utilize the functionality of both filters.

In this article, we'll talk about how both filters work so you can ensure you're making the best decision while setting up your Ticket Rules.

Statuses Filter

The Statuses filter allows you to specify which specific status(es) Backup Radar should generate tickets for:

Statuses.png
a. Failure: All results for the day were failures. If your backup receives multiple, differing results in a 24-hour period, this status is based on an overall, calculated daily status*.
b. No Result: No results were received on a day the backup was scheduled to run. See Understanding the "No Result Threshold" setting for details on how this status works.
c. Pending: No results were received on a day the backup was scheduled to run, but the backup is within its user-defined "No Result Threshold". See Pending Status FAQ for details on how this status works.
d. Success: All results for the day were successful. If your backup receives multiple, differing results in a 24-hour period, this status is based on an overall, calculated daily status*.
e. Warning: All results for the day were a warning. If your backup receives multiple, differing results in a 24-hour period, this status is based on an overall, calculated daily status*.

*The daily statuses are based on a status calculation across all individual results received that day. See Working with Status Calculation for details on how these overall, calculated daily statuses work.

 

No Successful Results Filter

The No successful results filter allows you to specify exactly how many consecutive days should pass without a successful backup status before a ticket is created for that particular Ticket Rule.

Unlike the Status filter, the No successful results filter is based on individual backup results and not an overall daily status.

No successes detected in __ days.png
a. No successful results detected in __ days: Set this to match your preferred threshold of no successes before you'd like to be notified. For example, setting the No Successes filter to 3 will mean that a ticket is created when the backup has not achieved any successful results at any point for 3 consecutive days.
b. Enable continuous alerting (on subsequent days): Choose this option if, after your initial alert, you would like to be continuously alerted every day until a success status is recorded. 

 

Any questions? Reach out to our friendly, neighborhood support team by submitting a support ticket.

Was this article helpful?

4 out of 4 found this helpful

Have more questions? Submit a request