Event Collectors are used to collect events from the event logs on Windows NT, Windows 2000, Windows XP and Windows Server 2003. 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.

The Inventory Collector is used to gather data about what is installed on each Windows-based Agent. You can collect data on the Windows operating systems, installed services, and applications that have been installed and added to the Add or Remove Programs applet in the Windows Control Panel.

This Monitor Item is used to collect and store performance data from Windows NT, Windows 2000, Windows XP and Windows Server 2003. You can use multiple Performance Collectors that contain different groups of counters, or a single Performance Collector that contains all of the counters you want to collect.

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, Windows XP and Windows Server 2003 Agents.

An Exchange Monitor enables you to perform end-to-end monitoring of Microsoft Exchange 5.5, Exchange 2000 and Exchange Server 2003. 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.

The IIS Monitor is used to monitor Internet Information Server 4.0 and Internet Information Services 5.0 and later. The IIS Monitor periodically checks for state changes, broken paths, failed requests, and connection attempts from blocked addresses (e.g., addresses blocked via IIS security).

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.

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, Windows XP and Windows Server 2003. 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.

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.

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.

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.

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.

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.

Web Page Monitors are used to monitor HTTP and HTTPS URLs. An HTTP or HTTPS connection to 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.

The Link Monitor periodically spiders/crawls your Web site using the URL you specify as a starting point. It can check for broken links and Quality of Service.

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.

An ELM Server Monitor enables Service Agents to perform regular heartbeat checks on the ELM Server. If the ELM Server does not respond or is slow in responding, a variety of actions and notification options can be triggered.

This report displays Windows 2000 and Windows 2003 Active Directory performance and event log information.

This report displays Windows 2000 and Windows 2003 Active Directory search statistics and activity information.

This report displays BizTalk Server 2002 statistics and activity information.

This report displays collected performance data for Microsoft Exchange servers.

This report displays collected performance data for Microsoft Exchange clients.

This report displays Internet protocol (SMTP, POP3, IMAP4, HTTP, NNTP) usage and connection statistics for the selected Microsoft Exchange 2000 and Microsoft Exchange 2003 servers.

This report displays collected performance data for Microsoft Exchange servers.

This report displays collected performance data related to public folder replication for Microsoft Exchange 2000 and Exchange 2003 servers.

This report displays collected performance data for Microsoft Exchange servers.

This report displays resource (CPU, memory, disk) usage statistics for the selected Microsoft Exchange 2000 and Microsoft Exchange 2003 server(s).

This report displays collected data for Microsoft Exchange ActiveSync and Outlook Mobile Access.

This report displays Internet Information Server performance and activity information.

This report displays Internet Security and Acceleration Server 2000 statistics and activity information.

This report displays Internet Security and Acceleration Server 2004 statistics and activity information.

This report displays Microsoft Identity Integration Server 2003 statistics and activity information.

This report displays resource (CPU, memory, disk) usage and event log data for the selected SharePoint Portal Server 2003 computer(s).

This report displays statistics SQL Server performance.

This report displays Windows MSMQ statistics for the selected Microsoft Windows Servers.

This report displays Windows DNS Server statistics and activity information.

This report displays Windows RMS Activity statistics for the selected Microsoft Windows 2003 Servers.

These events describe high-level changes to the user-accounts database, which represent computers, such as Computer Account Created, or Deleted.

These events describe a single logon or logoff attempt, whether successful or unsuccessful. Included in each logon description is an indication of what type of logon (that is, interactive, network, or service) was requested or performed.

These events describe both successful and unsuccessful accesses to protected objects.

These events describe both successful and unsuccessful attempts to use privileges. The category also includes information about when some special privileges are assigned. These special privileges are audited only at assignment time, not at the time of use.

These events describe high-level changes to the user-accounts database, such as User Account Created or Group Membership Change.

This report displays events related to Windows Group Policy.

This report displays information about software inventory and installed applications.

This report displays information about operating systems.

This report displays statistics about server and application outages, server restarts, and application uptime.

This report displays statistics about alerts received by the ELM Server.

This report displays statistics about event sources and types.

This report displays Network Interface and NBT Connection performance data from specified Windows computers.

This report displays process specific performance metrics.

This report displays server performance metrics for Disk, CPU, and Memory.