System License - Complete System Monitoring

The System License in ELM Enterprise Manager is the flagship offering from TNT Software, offering the most comprehensive set of monitoring and alerting features. Servers with specific roles within an organization often require special monitoring. The System license offers the widest selection of features of all six licenses in ELM Enterprise Manager.

Listed below are the monitoring features found in the System license. Notifications and Reporting features are shared across all licenses within ELM Enterprise Manager.

Event Log Alarms

The Event Alarm compares the new event against a customized Event Filter. If the event matches or fails to match the criteria the specified number of times within the specified time period, the Action is executed.

This is a convenient tool to detect the absence of a system back-up confirmation event.

Looking for more details?
Check out the ELM Help Guide pages on Event Alarm.

Event Collector

The Event Collector monitors all Windows event logs and when an event match to a specified Event Filter is determined, it is expanded and transferred to the ELM Server. The collected events are reliably stored in the Primary database for reporting, Filtered to create concise Views, and used to trigger Notifications. Typically, very general Filters are configured to ensure all the data is available for accurate analysis.

Looking for more details?
Check out the ELM Help Guide pages on Event Collector.

Event File Collector

The Event File Collector operates to collect and store the native event log files. (.EVT and .EVTX). These files are securely stored by default in the EVT File sub-directory under the ELM Enterprise Manager installation folder. They provide an authentic source for event log management.

Looking for more details?
Check out the ELM Help Guide pages on Event File Collector.

File Monitor

The File Monitor scans ASCII or plain text (flat) files or groups for files on a scheduled basis for a specified character string. When a match is found, an Action can be triggered such as a notification sent.

Examples of non-circular files include:

• Microsoft ISA Server log files
• Internet Information Services log files
• SQL Server error logs
• Backup software log files
• Anti-virus software log files
• Static .html files
• User-created flat files

Looking for more details?
Check out the ELM Help Guide pages on File Monitor.

SNMP Alarm

The SNMP Alarm includes a MIB browser that queries a SNMP Object ID (OID) and triggers an Action if the value is greater than, less than, or equal to a specified value. It extends the status monitoring of ELM beyond Windows systems and into SNMP supported network devices.

Looking for more details?
Check out the ELM Help Guide pages on SNMP Alarm.

SNMP Collector

The SNMP Collector monitors on a scheduled basis the SNMP Object ID's and returns the values to the ELM Server. They are stored in the Primary Database for reporting and trending.

Looking for more details?
Check out the ELM Help Guide pages on SNMP Collector.

SNMP Receiver

The SNMP Receiver is configured to process SNMP Traps from network devices. These traps can be translated against stored .mibs and converted into a Windows event log format. Like Windows events, they are stored in the Primary database for reporting, Filtered to create concise Views and used to trigger a Notification. Use ELM event log management technologies monitor non-Windows systems.

Looking for more details?
Check out the ELM Help Guide pages on SNMP Receiver.

Syslog Receiver

The Syslog Receiver is configured to process Syslog messages from network devices and UNIX-based systems. Supporting both UDP and TCP, these messages are converted using the standard Windows event log format. Like Windows events, they are stored in the Primary database for reporting, Filtered to create concise Views and used to trigger a Notification. When used to supports firewalls, they fortify the security barrier around Windows networks.

Looking for more details?
Check out the ELM Help Guide pages on Syslog Receiver.

Inventory Collector

The Inventory Collector gathers 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 Programs and Features applet in the Windows Control Panel.

The Inventory Collector also allows you the flexibility to add specific services to the Inventory or exclude certain products (by default all products are included in the inventory).

Looking for more details?
Check out the ELM Help Guide pages on Inventory Collector.

Performance Alarms

Performance Alarms monitor any published performance counter for a condition that is greater than, less than or equal to a threshold value for the specified duration. By using Performance Alarms, you can be alerted when disk space, memory or CPU has reached unexpected or out-of-bound levels.

Looking for more details?
Check out the ELM Help Guide pages on Performance Alarms.

Performance Collector

The Performance Collector supports proactive system management and resource trending. Any published performance objects, counters and/or instances can be collected at a set frequency on a scheduled basis, securely stored and aggregated for informative reporting.

Looking for more details?
Check out the ELM Help Guide pages on Performance Collector.

Ping Monitor

The Ping Monitor sends custom ICMP echo requests to verify TCP/IP connectivity and the Quality of Service. It provides an early warning alert of a problem with the remote system's status.

Looking for more details?
Check out the ELM Help Guide pages on Ping Monitor.

Process Monitor

The Process Monitor provides a comprehensive view of process activity. It can take Actions when a process CPU has exceeded specified thresholds, when processes are initiated or terminated and when the number of the same process exceed maximum quantities.

Looking for more details?
Check out the ELM Help Guide pages on Process Monitor.

Windows Service Monitor

Service Monitor detects and responds to service and device state changes specifically, starting, started, paused, stopping and stopped. Commonly used with the Command Script notification, you can launch a batch file to restart a failed service. This empowers administrators to combine monitoring with automated corrective action.

Looking for more details?
Check out the ELM Help Guide pages on Service Monitor.

Windows Configuration Monitor

The Configuration Monitor periodically collects System Information (msinfo32) data and takes Action when an addition, deletion or change has been detected. It also populates the System Information in the Agent file. Here historical and cross system analysis provide a valuable troubleshooting tool.

The Agent-System Information folder displays the system information from the last date scanned by default. The filter options for Added/Changed/Deleted are disabled until a compare is performed. A simple right-click in the results pane brings up a menu for the Compare options. System Information can be compared to any system on any date it was scanned. The display will show results as compared to the other agent with color coding showing showing which changes have taken place.

Looking for more details?
Check out the ELM Help Guide pages on Windows Configuration Monitor.

WMI Monitor

The WMI Monitor queries the WMI namespace (typically root\cimv2) and generates Actions when the results of the query change. It’s a powerful tool expanding the data sources to identify system changes or activities.

Looking for more details?
Check out the ELM Help Guide pages on WMI Monitor.

Cluster Server Monitor

Cluster Monitor expands event log management to include the Cluster APIs. These event logs are monitored it real-time. Depending on the event type, specific Actions can be configured including rewriting the event into the Windows Application event log.

Looking for more details?
Check out the ELM Help Guide pages on Cluster Monitor.

Exchange Monitor

The Exchange Monitor performs end-to-end monitoring of Microsoft Exchange including Quality of Service threshold for internal email delivery. When an email message is sent from the source mailbox, an internal clock is started. If the message is not received by the target mailbox within the threshold, an event will be generated. Messages sent between these two mailboxes are automatically removed.

Looking for more details?
Check out the ELM Help Guide pages on Exchange Monitor.

FTP Monitor

The FTP Monitor periodically checks the availability of an FTP site, compares the Quality of Service against a specified threshold and takes an Action if either fails. You will be the first to know of file distribution problems.

Looking for more details?
Check out the ELM Help Guide pages on FTP Monitor.

IIS Monitor

The IIS Monitor periodically checks for a state change, failed request, blocked address attempt and broken link. When they are detected, Actions can be launched. It provides critical information not easily available for proactive management.

Looking for more details?
Check out the ELM Help Guide pages on IIS Monitor.

Web Link Monitor

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

Looking for more details?
Check out the ELM Help Guide pages on Web Link Monitor.

SMTP Monitor

SMTP Monitors establishes an SMTP connection to the server and port specified. It connects to the SMTP Server and times the initiating conversation from "EHLO" to "250 OK." Enabled Actions are executed depending on successful, slow, or failed responses.

Looking for more details?
Check out the ELM Help Guide pages on SMTP Monitor.

SQL Server Monitor

Using SQL Monitors, you can periodically execute SQL queries against a database and take a specified Action when the results returned are different from what is expected. It provides secure flexibility by integrating Windows authentication or Windows and SQL authentication.

Looking for more details?
Check out the ELM Help Guide pages on SQL Server Monitor.

TCP Port Monitor

Monitor any valid port with the TCP Port Monitor. From the ELM Server, a connection to the specific port is initiated and the availability and Quality of Service is determined. An Action is triggered of if it fails or the response time is slower than expected.

Looking for more details?
Check out the ELM Help Guide pages on TCP Port Monitor.

Web Page Monitor

Web Page Monitors establish an HTTP connection to the server and port specified to fetch a URL. If the response is negative, slower than expected, or if the content has been changed since the previous snapshot, specified Actions can be triggered. Be alerted of unauthorized modifications to your websites.

Looking for more details?
Check out the ELM Help Guide pages on Web Page Monitor.

Agent Monitor

The Agent Monitor is part of ELM's built in resiliency or self monitoring and performs heartbeat checks on Service Agents. If the Service Agent does not respond or is slow in responding, actions and notification options can be triggered.

Click here for more information on ELM Resiliency

ELM Server Monitor

The ELM Server Monitor is also part of ELM's built in resiliency or self monitoring and enables Service Agents to perform heartbeat checks on the ELM Server. If the ELM Server does not respond or is slow in responding, actions and notification options can be triggered.

Click here for more information on ELM Resiliency