|
|
|
| |
Event Log Monitor |
| |
EventReporter monitors Windows event
logs. All currently-existing logs are fully supported:
the standard Windows Event Logs, the three new logs
introduced by Windows 2000 as well as custom event logs
and the brand-new Window Vista event logging system.
Also supported are Windows event log files. That
feature supports NAS-devices, which often offer log
information in Windows event log file format (.evt). By
monitoring these files, SAN devices, too, can be
monitored in near-real-time. |
|
|
|
|
|
| |
Event Log Monitor V2 |
| |
EventReporter monitors Windows event
logs. All currently-existing logs are fully supported:
the EventLog Monitor V2 is especially designed for the use with Windows Vista. This makes you capable of using the all-new and advanced EventLog structure of the most recent version of Windows. |
|
| |
|
|
|
|
|
| |
Heartbeat |
| |
Heartbeat can be used for providing a cyclic activity
in which actions can be carried out. It also is useful
for detecting system failures. |
|
| |
|
|
Filtering |
|
|
| |
|
|
|
|
|
| |
Local
Filtering |
| |
EventReporter can locally filter events based on the
any event log property (like event id, severity or even
partial message content). Flexible boolean operations
and nested conditions are supported. That way, you can
discard messages you are not interested in and alert
high-priority message e.g. via email. |
|
| |
|
|
Log
Storage |
|
|
| |
|
|
|
|
|
| |
Write To File |
| |
This option writes event log messages to text files. It
is quite uncommon to use that feature with
EventReporter. However, should it be needed, it is
available. Typically, however, messages are forwarded to
another system or be used to generate alerts. |
|
| |
|
|
|
|
|
| |
Write To Database |
| |
Database logging allows writing all events to a database.
Once they are stored inside the database,
different message viewers as well as custom applications
can easily browse them. Using remote databases is one
way to create a central event repository. In larger
environments, however, approaches via syslog or SETP
might be more useful from a performance point of view. |
|
| |
|
|
|
|
|
| |
Write To Event Log |
| |
It is used to configure logging to the Windows event log. It is primarily included for legacy
purposes. To be honest, this option makes pretty little
sense in most cases with EventReporter. It is included
for compatibility with other products of the
MonitorWare line
as well as for generating internal alarms in advanced
rule sets. |
|
| |
|
|
Alerting |
|
|
| |
|
|
|
|
|
| |
Forward via Email |
| |
Event log information can be delivered via
standard Internet email. This is an excellent option for
alerting in case an important
message occurs. Consequently, that option is an enabler for
smaller organizations or service providers who monitor their client's servers
unattended. |
|
| |
|
|
|
|
|
| |
Net Send |
| |
This helps to send short alert messages to recipient machine via Windows net send facility. |
|
| |
|
|
|
|
|
| |
Play Sound |
| |
This action allows you to play a sound file. This
feature was requested by some users who would like to
physically sound an alert on occurrence of highly
critical events. |
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
| |
Syslog Support |
| |
This is one of the primary uses of EventReporter. With
it, Windows events can be converted to syslog and
sent to any syslog server in the enterprise. The
message format is highly customizable. Event log severity classes are mapped to the
corresponding syslog classes. Syslog facility codes are
fully supported. A single message can be sent to
multiple syslog servers. |
|
| |
|
|
|
|
|
| |
SETP Support |
| |
SETP is Adiscon's protocol for reliably transfering
event messages in native format. It is primarily of use
for those that want to build a larger, centralised event
repository. SETP can optionally be SSL-encrypted. |
|
| |
|
|
|
|
|
| |
Powerful Event Processing |
| |
EventReporter is powerful and flexible rule engine processes all
events based on a configured set of actions. An
unlimited number of rules and actions allows tailoring
to the specific needs.
|
|
|
|
|
|
|
|
| |
Set Status |
| |
Each information unit has certain properties e.g.
EventID, Priority, Facility etc. You can create a new
property and assign any valid desired value as well as
filter to it. This capability is used for advanced
applications, possible to automatically fix problem
situations.
|
|
| |
|
|
|
|
|
| |
Set Property |
| |
With the “Set Property”, some properties of the incoming
message can be modified. This is especially useful if an
administrator would like to e.g. rename two equally
named servers.
|
|
| |
|
|
|
|
|
| |
Send to Communications Port |
| |
It allows to send a string to an attached communications
device, that is it sends a message through a Serial
Port. This can be a very valuable ability depending on
the serially-attached device. Typically, it is is used
in advanced applications and most often to automatically
fix problem situations.
|
|
| |
|
|
|
|
|
| |
Start Program |
| |
With this, an external program can be run. Any valid
Windows executable can be run. This includes actual
programs (EXE files) as well as scripts like batch files
(.BAT) or VB scripts (.vbs). Start Program can, for
example, be used to carry out corrective action when
specific events occur.
|
|
| |
|
|
|
|
|
| |
Multi-Language Client |
| |
The EventReporter client
comes with multiple languages ready to go. Out of the
box, English, German and Japanese are supported.
Languages can be switched instantly. Language settings
are specific to a user.
Additional languages can be easily integrated using
Adiscon's XML based localization technology.
We ask customers interested in an additional language
for a little help with the translation work (roughly 1
hour of work). Adiscon will than happily create a new
version. This service is free!
|
|
| |
|
|
|
|
|
| |
Friendly and Customizable User Interface |
| |
Of course, the configuration program supports
multiple skins.
|
|
| |
|
|
|
|
|
| |
Other Miscellaneous Features |
| |
There are certain features of EventReporter those have added
an amazing power to it. These include ease of use, full
Windows, XP and Vista support, robustness, remote
administration, minimal resource usage, full NT event
log decoding, and double byte character set support. To learn
more about these, please see
other miscellaneous features of EventReporter. |
|
| |
|
|
| |
|
|
