This is used to monitor an ELM Service Agent. Agent Monitors perform regular heartbeat checks on Service Agents. If the Server Agent does not respond or is slow in responding, a variety of actions and notification options can be triggered.

You can use a Cluster Monitor to watch cluster system and cluster registry events. The Cluster Monitor can report on messages generated by any or all of the Cluster APIs: cluster events, quorum events, network events, node events, group events, resource events and registry events.

Event Alarms are used to trigger action and/or notification when an event does or does not occur. Event Alarms can be configured for Windows NT, Windows 2000 and Windows XP Agents.

Event Collectors are used to collect events from the event logs on Windows NT, Windows 2000, and Windows XP. You can specify the events you want to collect based on a variety of event criteria, including event type, source, event ID, and event details.

An Exchange Monitor enables you to perform end-to-end monitoring of Microsoft Exchange 5.5 and/or Exchange 2000. This type of monitoring allows you to specify a custom quality of service (QoS) threshold for internal email delivery, and to be notified when that threshold is not met.

File Monitors are used to parse plain text log files and report when a match is found or not found. You can monitor individual log files, an entire directory of files, or an entire directory tree of files.

This monitor is used to monitor a specific FTP URL. An FTP connection to this URL is attempted at the specified interval. If the response is negative or slower than expected a variety of notification options can be triggered.

If you need to monitor a TCP port on any TCP/IP-based system or device, you can use a TCP Port Monitor to do so. Simply specify the port you wish to monitor and the expected response time in seconds.

Performance Alarms monitor performance objects, counters and instances and can generate a variety of actions and notification options when a counter or instance of a counter is greater than, less than or equal to your specified threshold for your specified duration.

This Monitor Item is used to collect and store performance data from Windows NT, Windows 2000, and Windows XP. A Collection Set is a group of performance counters that are collected at the same time. You can use multiple Performance Data Collection Sets that contain different groups of counters, or a single Performance Data Collection Set that contains all of the counters you want to collect.

The Ping Monitor is used to send period ICMP echo requests to the Agent(s) being monitored. You can specify the size of the echo request packets and the number of packets that are sent. Ping monitors can check availability and quality of service.

POP3 Monitors are used to periodically check a POP3 mailbox for availability. A POP3 connection to the this mailbox is attempted at the specified interval. If the response is negative or slower than expected, a variety of actions and notification options can be triggered.

If you need to monitor individual processes, you can do so with a Process Monitor. The Process Monitor is multi-functional; it can let you know when a process has exceeded the threshold of CPU usage you specify, and it can track when processes are instantiated or terminated.

Service Monitor items are used to monitor individual services and devices on Windows NT, Windows 2000, or Windows XP. Service Monitors can generate notification when a service or device is stopped, started, paused or resumed. In addition, Service Monitors can alert you when it finds a service or device set to Automatic startup that is not running.

SMTP Monitors are used to keep tabs on SMTP Servers. An SMTP connection to the server is attempted at the specified interval. If the response is negative or slower than expected a variety of actions and notification options can be triggered.

ELM includes an SNMP Monitor that enables you to query an SNMP Object ID (OID) and trigger notification if the value is greater than, less than or equal to a specified value. The SNMP Monitor includes an object browser that enables you to query the objects on an SNMP-capable computer, and select specific objects for monitoring.

Using SQL Monitors, you can periodically execute SQL queries against a database and generate a variety of notification options if the results returned are different from what is expected. SQL Monitors support both Windows NT and SQL Server authentication, making them easy to fit into your existing SQL security environment.

Web Page Monitors are used to monitor HTTP and HTTPS URLs. An HTTP or HTTPS connection the URL is attempted at the specified interval. If the response is negative, slower than expected, or if the content has been changed, a variety of actions and notification options can be triggered.

If you are using Windows Management Instrumentation--the Microsoft implementation of Web-Based Enterprise Management (WBEM)--you can use WMI Monitors to query a WMI namespace and database. If the results of the query change, or if a property of the item in the query changes, a variety of actions and notification options can be executed.

The ELM Server can receive SNMP Traps and display them with and without Object IDs as part of the trap messages. Incoming traps are treated as events, enabling you to apply Event Filters, Event Views, Personal Views, and Rules to them.

The ELM Server can receive Syslog messages from any TCP or UDP-based Syslog client. Incoming Syslog messages are treated as events, enabling you to apply Event Filters, Event Views, Personal Views, and Rules to them.