JOC_3 Absent Member.
Absent Member.
20 views

Is it possible to trap NT eventlog messages using OVO by event TYPE?

Jump to solution
I want to trap all WARNING and ERROR type messages from NT Server 4 event logs using OVO 6.1. on HPUX.

Anyone know of this is possible? It would save a lot of time, rather than doing pattern-matching for each eventuality.

Thanks!
0 Likes
1 Solution

Accepted Solutions
Highlighted
Alan Deger Absent Member.
Absent Member.

Re: Is it possible to trap NT eventlog messages using OVO by event TYPE?

Jump to solution
Sure, just modify (or copy) your "SysEvLog (NT)" template (for example) and create one (or two) new condition(s). Your match criteria should only contain a Severity with the "warning" and/or "critical" values selected (I have two such conditions, one labeled "All Other Warning Messages, the other "All Other Error Messages"). Note that NT/2000's "warning" severity maps directly to OV's "warning" and that "error" maps to NT/2000's "critical" severity.

Make sure that these conditions are at the bottom of your condition list (since they'll short circuit any other more specific conditions).

Note also that these "catch-all" conditions will make multiple templates that operate on any one log (e.g., system, application or security) problematic.

Hope this helps,
ard
1 Reply
Highlighted
Alan Deger Absent Member.
Absent Member.

Re: Is it possible to trap NT eventlog messages using OVO by event TYPE?

Jump to solution
Sure, just modify (or copy) your "SysEvLog (NT)" template (for example) and create one (or two) new condition(s). Your match criteria should only contain a Severity with the "warning" and/or "critical" values selected (I have two such conditions, one labeled "All Other Warning Messages, the other "All Other Error Messages"). Note that NT/2000's "warning" severity maps directly to OV's "warning" and that "error" maps to NT/2000's "critical" severity.

Make sure that these conditions are at the bottom of your condition list (since they'll short circuit any other more specific conditions).

Note also that these "catch-all" conditions will make multiple templates that operate on any one log (e.g., system, application or security) problematic.

Hope this helps,
ard
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.