All Monitors

Top  Previous  Next

Monitor Items control the different types of information collected by ELM. For example, to collect events from a Windows computer, you would use an Event Collector; to monitor services, you would use a Service Monitor; and to watch a performance counter threshold, you would use a Performance Monitor. Below are the Monitor Items included in ELM Enterprise Manager.

The All Monitors container displays all of the configured monitor items.  To disable all of the monitor items at the same time, right click the All Monitors container and select Disable.  This disables all of the monitor items at the container level and doesn't change the specific monitor items settings.

Data Collector and Real-Time Monitors

Event Collector - Event Collectors collect events from the event logs on Windows 2000, Windows XP, Windows Server 2003, Vista, Windows 7, and Windows Server 2008. You can specify the events to collect based on a variety of event criteria, including event type, source, event ID, and event details.

Event File Collector - Event File Collectors collect raw .evt or .evtx logs on Windows 2000, Windows XP,  Windows Server 2003, Vista, Windows 7, and Windows Server 2008. You can specify which logs to collect, and optionally clear the Event Logs at each collection interval. Collected .evt files can be compressed and signed if a signing certificate is available.

Inventory Collector - The Inventory Collector gathers details on the Agent operation system and on applications that have been installed on the Agent. Only applications that appear in the 'Add or Remove Programs' or 'Programs and Features' applet in the Windows Control Panel will be inventoried. This Monitor Item is for Windows Agents only.

Performance Collector - The Performance Collector collects and stores performance data from Windows 2000, Windows XP, Windows Server 2003, Vista, Windows 7, and Windows Server 2008. A Performance Collector is a group of performance counters that are collected at the same time. You may 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.

Application and Server Status Monitoring

Cluster Monitor - Cluster Monitor watches cluster system and cluster registry events. The Cluster Monitor thread can monitor any or all of the seven Cluster APIs: cluster events, quorum events, network events, node events, group events, resource events and registry events.

Event Monitor - Event Monitors trigger action and/or notification when an event does or does not occur. Event Monitors can be configured for Windows 2000, Windows XP, Windows Server 2008, Vista, Windows 7, and Windows Server 2008.

File Monitor - File Monitor monitors individual log files, an entire directory of files, or an entire directory tree of files. Monitored files must be text (ASCII)-based and non-circular in nature (i.e., they do not overwrite themselves after a certain size, etc., is reached).

IIS Monitor - The IIS Monitor monitors Internet Information Services 5.0 (Windows 2000), 5.1 (Windows XP) and 6.0 (Windows 2003) only. The IIS Monitor periodically checks the state of IIS for state changes and broken paths. It executes a File Monitor internally (no separate File Monitor configuration necessary) to parse the IIS log files for failed requests and connection attempts from blocked addresses (e.g., addresses blocked via IIS security).

Performance Monitor - Performance Monitors monitor performance objects, counters and instances and can generate a variety of Notification Methods when a counter or instance of a counter is greater than, less than or equal to a specified threshold for a specified duration.

Process Monitor - The Process Monitor monitors individual processes. 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 initiated or terminated.

Service Monitor - Service Monitor items monitor individual services and devices on Windows 2000, Windows XP, Windows Server 2003, Vista, and Windows Server 2008. Service Monitors can generate action or notification when a service or device is stopped, started, paused or resumed. The Service Monitor can write an event when it finds a service or device set to Automatic startup that is not running.

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

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

Cross Platform Monitoring

Syslog Receiver - The ELM Server can receive Syslog messages from any TCP or UDP-based Syslog client.

SNMP Monitor - SNMP Monitor queries an SNMP Object ID (OID) and triggers 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.

SNMP Collector - The SNMP Collector collects and stores values from one or more OIDs provided by an SNMP agent. You may use multiple SNMP Collectors that contain different groups of OIDs, or a single SNMP Collector that contains all of the OIDs you want to collect.

SNMP Receiver - The ELM Server can receive SNMP Traps and display them with and without Object IDs as part of the trap messages.

Internet Service Monitoring

FTP Monitor - The FTP Monitor monitors a specific FTP URL. If you are using a Service Agent, the Service Agent will periodically establish an FTP connection to the URL and port specified. If you are using a Virtual Agent or an IP Agent, the FTP polling is performed by the ELM Server. If the response is negative, or slower than expected, a variety of actions and notification options can be triggered.

TCP Port Monitor - Port Monitor monitors a TCP port on any TCP/IP-based system or device. Specify the port you wish to monitor and the expected response time, in seconds.

Ping Monitor - The Ping Monitor sends 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.

SMTP Monitor - The SMTP Monitor connects to the SMTP Server and times the initiating conversation from connection, through "EHLO," to "250 OK."  Enabled Actions are executed depending on successful, slow, or failed responses.   If you are using a Virtual Agent or an IP Agent, the SMTP polling is performed by the ELM Server. If the response is negative or slower than expected a variety of notification options can be triggered.

Web Page Monitor - Web Page Monitors monitor web pages (HTTP). The system to which the Web Page Monitor is assigned (e.g., the ELM Server or a Service Agent) periodically fetches the specified URL. 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.

Resiliency Monitoring

Agent Monitor - Agent Monitors perform regular heartbeat checks on Service Agents. If the Service Agent does not respond or is slow in responding, a variety of actions and notification options can be triggered.