|
Contact For Your Server Monitoring and Windows Event Log Management Solutions
|
Now, with the new flexible licensing model in ELM Enterprise Manager 6.0, you have the ability to purchase and install the licenses that fit the best given the monitoring capabilities you need. For example, on Windows Servers where you just want event logs, you could use Event Licenses. On those network devices you would use Log Licenses; and now you can also choose to run System Licenses on the machines where you need more comprehensive monitoring of events, applications, processes, services and status/health.
Click here to compare features in ELM Enterprise Manager 6.0 Click here for sample scenarios of a mixed license environment
Log Management Features Available In ELM Enterprise Manager 6.0
|
|
||||||||||||||||||||||||||||||||||||||
|
![]() |
|||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||
Examples of non-circular files include:
|
|
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.

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.

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.
Warning
TEST3
1/19/2010 7:49:13 PM
1/19/2010 7:49:13 PM
{0A282598-0136-4222-ADCC-431B9DDE30BC}
2000
SNMP
None
SPECIFIC TRAP
None
Enterprise specific trap id 0
Host Address: TEST3.tnttestlab.com (127.0.0.1)
.iso.org.dod.internet.private.enterprises.lanmanager.2.1 = TEST3
.iso.org.dod.internet.private.enterprises.lanmanager.2.2 = 0
.iso.org.dod.internet.private.enterprises.lanmanager.2.3 = Audit Success
.iso.org.dod.internet.private.enterprises.lanmanager.2.4 = Application
.iso.org.dod.internet.private.enterprises.lanmanager.2.5 = Source
.iso.org.dod.internet.private.enterprises.lanmanager.2.6 = Category
.iso.org.dod.internet.private.enterprises.lanmanager.2.7 = Username
.iso.org.dod.internet.private.enterprises.lanmanager.2.8 = This is a test event message.
Warning
TEST3
1/19/2010 7:49:41 PM
1/19/2010 7:49:41 PM
{30202DE3-57EB-4B93-B63A-4DB9408A972A}
2000
SNMP
None
SPECIFIC TRAP
None
Enterprise specific trap id 0
Host Address: TEST3.tnttestlab.com (127.0.0.1)
TEST3
0
Audit Success
Application
Source
Category
Username
This is a test event message.
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.

![]()
Copyright © 1996-2010