REV MESSAGE can 'listen' to the E1 root logs on the E1 Web Server(s).

The 'listening' can be performed:

• In Real time – i.e. as they arrive in the log,
• Historically – after the fact and can be done on any Server type – e.g. LINUX Logs on WINDOWS.

As Log Entries are detected/read they are checked against pre-defined Rules to exclude any non-critical Log Entries – so ONLY critical Log Entries and processed.

The raw E1root log could be like:

As REV MESSAGE 'listens' to the logs it will translate the Log Entries and then check them against the E1 exclusion rules:

There are also Message Text Rules for exclusion:

As we can see in the example of the E1root log above:

• All the JDE Severity MANDATORY Log entries would be excluded from processing,
   
• JDE Severity SEVERE Log entries with:
  WARNING!!!! Password
  would be excluded from processing due to the Exclusion Rule entry Sequence 5,
   
• JDE Severity WARN Log entries with:
  SecurityServer already exists
  would be excluded from processing due to the Exclusion Rule entry Sequence 10,
   
• JDE Severity WARN Log entries with:
  ClassNotFoundException
  would be excluded from processing due to the Exclusion Rule entry Sequence 15.

We are only wanting to process critical messages such as:

These will then sent to REV MESSAGE for processing.