|
|
|
|
|
|
|
|
|
|
 Zoom
| Loading… |
|
|
Notify.com Alarm Management receives alarm data from virtually any source; then processes that data to ensure
critical events
are responded to quickly.
Alarm data inputs include...
–
Output from
system and network management
applications
–
Email
messages
–
SMS
text messages
–
Any text-based file, including system and user generated
Log Files
–
SQL
Queries
–
PLC devices, and any equipment using RS-232
Serial Ports
–
NASA's
GMSEC
Message Bus
But most importantly, Notify.com Alarm Management can be interfaced to
any Operating System
,
application
or
device
, using the Notify.com Alarm Management
HTTP POST API
|
|
|
|
|
Zoom
| Loading… |
|
|
Notify.com
Blueprints
define the layout of alarm data, coming from a particular source.
Each delimited piece of data is called a
Blueprint field
.
Blueprint fields can be typed as either
Text
or
Number
. Field typing determines the relational operations available when using this Blueprint to create Notify.com
Alarms
.
|
|
|
|
|
Zoom
| Loading… |
|
|
Notify.com
Escalations
define the people that are notified when a Notify.com Alarm fires.
Each level of the escalation chain can specify
any combination of
User, Groups, Subscriptions or Custom Actions. The
Wait Interval
determines the number of minutes before the next level of the Escalation is executed.
When Escalations are stopped, Notify.com
logs the name
of the user that responded, and
the method
they used to terminate the Escalation.
|
|
|
|
|
Zoom
| Loading… |
|
|
Notify.com Administrators can enable an optional feature referred to as
One Touch Reply
.
This capability allows users to Stop a running Escalation, with a single response to the system—they do not need to enter the associated Escalation ID.
Users simply click the
acknowledge button
on their Push notification,
reply
to their SMS text message or Email, or
press a defined key sequence
on the telephone keypad when receiving a voice call, and the Notify.com Escalation is stopped.
|
|
|
|
|
Zoom
| Loading… |
|
|
Notify.com
Alarms
tie together a Blueprint and Escalation.
Selected
Alarm fields
are compared to actual data received, to determine if a significant event has occured. When an Alarm fires, the designated Escalation is executed.
|
|
|
|
|
Zoom
| Loading… |
|
|
Alarm Field Tokens
allow you embed the actual values associated with incoming data, into the Alarm message sent to users in the Escalation.
|
|
|
|
|
Zoom
| Loading… |
|
|
Static Tokens
embed useful information into the Alarm Message, such as current time-stamp values, and the unique ID associated with the Escalation.
|
|
|
|
|
Zoom
| Loading… |
|
|
Notify.com
Alarm Suppression
prevents notifying people multiple times, when the same Alarm is fired in rapid succession.
The Alarm Suppression feature is enhanced by the use of the
{StartCompare}
and
{EndCompare}
Static Tokens. By specifying a substring of the Alarm Message for comparison, values such as time-stamps will be ignored.
|
|
|
|
|
Zoom
| Loading… |
|
|
Notify.com
Custom Actions
provide the ability to interface routines, specific to your organization, into Notify.com Escalations.
|
|
|
|
|
Zoom
| Loading… |
|
|
Notify.com is self-monitoring.
Every Notify.com component is embedded with a unique
Heartbeat
, that periodically assures the system it is operational. The loss of a component is immediately detected, and system administrators are alerted to the failure.
Notify.com Heartbeat Monitoring is
easily interfaced to any application
, running on any Operating System.
|