|
|
|
 |
 |
Event Log Monitoring |
| |
| The Windows Event Log is an important source for
application status information. When properly integrated
with the Windows operating system, applications can
report their errors to the Event log by recording an
event entry into the Application log. Furthermore,
details on failing operating system components and
hardware can be found in the System log. On Windows
2000 or newer server operating systems, the Active
Directory has its own directory and replication log. |
| MonitorMagic can access both local and remote Windows
Event logs and scan its contents. Every event entry
has its own source, ID, severity and desciption, which
can be used to detect possible incidents. MonitorMagic
can be triggered to alert on every event property or
attribute and take action when necessary. |
| |
|
| |
 Example
1: Norton AntiVirus Corporate Edition
|
| 1. Downloading virus definition updates |
| 2. Virus definition updates have been loaded correctly |
| 3. Failed to update virus definition updates |
| |
Example
2: BrightStor ARCServe Backup Windows
|
| 1. Bad job failures |
| 2. Media errors |
| 3. Missing job errors |
|
Event
Log Reporting
|
 No
additional software needed; no
need to install Crystal Reports |
Dynamic
reporting system; automatically
suits your network
|
|
|
Company-tailored
report templates
|
|
|
Automatic
report generation and distribution
|
|
|
|
|
| |
Sample
HTML reports
|
| Report 1: All
systems error events |
| Report 2: All
systems overview per computer |
| Report 3: All
systems overview per resource |
| |
|
|
