Log License - Events, Syslog and SNMP Focused

The Log License in ELM Enterprise Manager is geared for the collection and management of Windows Events as well as receiving Syslog and SNMP messages. When you have a server with special "mixed" log management needs, the Log license is a smart choice.

Listed below are the monitoring features found in the Log 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.

Event Log 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.

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.

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.

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