|
IT Automation
Report & Document Viewing
|
not logged in
|
|
|
|
|
Monitor
|
|
Monitor your hardware and applications. Customize events to alert on your unique
conditions. Capture and interogate SNMP traps. Check for resource levels and availability.
Integrates with Exchange Server and sendmail for email content monitoring.
|
|
Alert
|
|
Alerts are triggered from applications, events, email, and SNMP traps. Notify your people
using text, email, pagers and interactive voice. Supports SMTP email, SMS text,
TAP, SNPP, and Dialogic telephony.
|
|
Escalate
|
|
When no response is received after the time period you specify, the alert is sent
to others in the alert list you setup by problem type. Alerts can continue in a
loop, be broadcast to everyone at once, or automatically cancel themselves.
|
|
|
|
|
|
PageAlert is notification and alerting software, providing advanced messaging
and escalation management with
built-in event and SNMP trap monitoring.
|
|
Working alone or with your existing system monitoring products, PageAlert automatically
transmits text/voice/paging alerts to the appropriate people as soon as a problem
occurs, and then escalates if no response is received.
|
|
|
|
Notifications from your applications and operating systems
can be automatically sent as voice, text, email, or paging messages as soon as problems
are detected.
|
|
PageAlert's core funtionality keeps IT personnel informed of exceptions,
problems and events such as system and hardware failures, application errors, threshold
exceptions, and completed tasks.
|
|
|
|
Expand the headings below by clicking on them.
|
|
PageAlert Server: Alerting
Using the PageAlert Administration program, you create notification patterns
and associate personal devices with those patterns. When a trigger message into
PageAlert matches one of the patterns, the devices associated with pattern are activated
for the alert. You control the style and data sent to the alert device. You can
mix any combination of device and protocol types, in any order, with variable delays
and cancellation options.
PageAlert Server: Event Monitoring
PageAlert includes built-in event monitoring, with monitors for network conditions,
disk space, memory, and other hardware conditions. PageAlert's event monitoring,
along with its alerting capabilities form a powerful event notification system.
Click here to go to the PageAlert Event Monitors Page
PageAlert Server: Integration
PageAlert may be combined with products such as HP's OpenView and others, to provide
key escalation capabilities.
PageAlert Server is the software that analyzes and performs alert notifications.
The PageAlert server software runs on a Windows platform and includes these interfaces
- Administration, for maintaining your notification tables
- Monitor, for viewing and controlling your active alerts
- Log viewing, for viewing the audit trail
- Test interfaces, for testing alert triggers and SMTP email
- Voice editing interface for voice prompts
PageAlert Server: License
PageAlert server is licensed for one or more Windows platforms. Most sites require
only a single system.
PageAlert Server: Web Interface
PageAlert includes a web interface that may be used for monitoring and controlling
alerts on the server. The web interface is an ASP.NET application. Also included
with the server is the PageAlert client software for use on the server. This means
that if your integration occurs on the PageAlert server, no other PageAlert client
software is required.
PageAlert Client Triggers
PageAlert clients, which trigger alerts from your applications, scripts, or provide
customized triggers, are available for most every environment, including UNIX, Linux,
Windows and MPE. PageAlert client trigger software is licensed when one or more
other systems are required to send alert triggers to the PageAlert server. If PageAlert
resides on the same system that the triggers would come from, no PageAlert client
software is required.
|
|
|
- Notification protocols include email (SMTP), SMS (Short Message Service
to cell phones)), numeric paging, internet paging (SNPP), alphanumeric
paging via modem (TAP), and interactive voice response (IVR).
- Escalation paths- if one user doesn't respond, the next user or users in the notification
chain will be notified.
- Alert triggers run on HP, Sun, IBM, Linux, Windows and MPE/iX.
- PageAlert has a browser and a Windows® interface for activity checking and control
of alerts.
- Start/stop actions can be specified for any alert. This allows a program
or script to be executed whenever an alert is triggered or canceled, and allows
integration with trouble ticket systems.
- Confirmation and acknowledgement- when configured, users must confirm and acknowledge
receiving the alert message. Without a confirmation, PageAlert will continue
to send the alert using the escalation path you have configured.
- PageAlert's Monitor feature allows you to define and set up event triggers
and both polling and persistent scripts and programs that PageAlert will run for
you. These programs and scripts can be used for monitoring various resources,
such as a Web server or a network hub, and then triggering a PageAlert notification
when a specified event occurs on the resource.
- Broadcast notifications- alerts can be broadcast to multiple personnel and
devices simultaneously.
- PageAlert integrations are available for HP OpenView® Operations for
Windows (OVOW) and UNIX, and OpenView Network Node Manager® (NNM), Fluke OptiView,
and Big Brother to escalate messages from these systems. Also available is Exchange
Server email content monitoring and individual mailbox monitoring.
|
|
|
|
|
Architecture
|
Client/Server. PageAlert Client machines send alert trigger messages to the PageAlert
Server, which then start an alert. PageAlert Server is responsible for sending out
the alert. PageAlert Client software is responsible for monitoring your hardware
and applications.
|
|
Device Protocols
|
- TAP (Telocator Alphanumeric Protocol) for numeric and alpha-numeric pagers;
- SNPP (Simple Network Paging Protocol) for one and two-way alpha pagers;
- SMTP (Simple Mail Transfer Protocol) for external and internal email to desktops
and cellphones;
- SMS (Short Message Service) for text messages over cellular carriers using a GSM/GPRS
modem.
- IVR (Interactive Voice Response) voice alerts for any pushbutton phone (requires
a Dialogic telephony board).
|
|
Protocol Requirements
|
- TAP - Modem and at least 1 phone line.
- SNPP - Internet connection.
- SMTP - Internal LAN connection and access to SMTP server.
- SMS - GSM/GPRS modem.
- IVR - Dialogic telephony board and at least 1 phone line.
|
|
Database
|
Microsoft Access or Microsoft SQL.
|
|
Device Profile Escalation Styles
|
- Profiles alerted once in turn, automatic cancelation.
- Profiles in turn, repeating until canceled.
- Profiles alerted once in turn, repeating independently.
- Broadcast to all profiles at once.
|
|
Operating systems
|
PageAlert Server - Windows XP SP3 or later, Windows Server 2003 or later
PageAlert Clients - HP-UX, 11.0 and later; AIX, 5.1L and later; Solaris 7 and later;
Redhat 7 and later and Fedora 7 and later; Windows XP and later.
|
|
Hardware Architecture
|
PageAlert Server - x86/x64
PageAlert Clients - HP, HP-PA & Integrity; IBM, pServer & p series; Sun,
Sparc/sun4u; x86/x64.
|
|
Interfaces
|
PageAlert Server - Windows dialogs for administration, monitoring, logging, and
testing.
PageAlert Client - Command line interface
|
|
Disk Space
|
PageAlert Server - Installation: 60MB approximate; Usage: 100MB typical
|
|
Security
|
Server->server and client->server connections encrypted.
|
|
Licensing
|
PageAlert Server - each installed machine
PageAlert Client - each installed machine
|
|
|
|
|
|