Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > User Device Tracker (UDT) > UDT Administrator Guide > Use Orion Platform advanced alerts > Escalated alert example

Escalated alert example

Table of contents
No headers
Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Jan 30, 2017

Views: 6 Votes: 0 Revisions: 2

WidgetCo is a business with a small IT staff, consisting of two technicians and an IT manager. To ensure that issues are addressed appropriately, the IT manager has created multiple escalated alerts for a range of potential network events, including device failures and excessive disk space or bandwidth usage. Typically, the escalated alerts configured by the WidgetCo IT manager proceed as follows:

  1. As soon as SolarWinds UDT recognizes an alert condition, SolarWinds UDT generates both an email and a page that are sent to one of the two technicians. An entry is also recorded in the Orion events log.
  2. If the alert is not acknowledged in the Orion Web Console within 20 minutes, a second alert is fired, generating another email and another page, both sent to both technicians. An entry is also recorded in the Orion events log.
  3. If the second alert is not acknowledged within 20 minutes, SolarWinds UDT fires a third alert that sends both an email and a page to both technicians and to the IT manager. An entry is also recorded in the Orion events log.

Escalated alerts ensure that everyone on the WidgetCo IT staff is notified of any significant network alert conditions within 45 minutes without burdening the IT manager with excessive alert notifications. The following section provides a procedure to create a similar escalated alert scheme.

Last modified
20:03, 29 Jan 2017