Super Contributor.. hiteshkumar Super Contributor..
Super Contributor..
84 views

log monitoring with entire file instead of each line

Jump to solution

Hi,

I have deployed log monitoring policy but the event giving based on log line Suppose ie: <*>abc<*> word i need to search in entire log file instead of every line. 

Please suggest the way-out.


If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

Regards,

Hitesh Kumar
0 Likes
1 Solution

Accepted Solutions
Super Contributor.. hiteshkumar Super Contributor..
Super Contributor..

Re: log monitoring with entire file instead of each line

Jump to solution

Solution or workaround :

It is working when diverting the count of that keyword by using |grep <keyword> |wc -l >/<save location> to another file and monitoring that file with greater than 0 or as per requirement 🙂 .


If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

Regards,

Hitesh Kumar
0 Likes
3 Replies
Outstanding Contributor.. andreask Outstanding Contributor..
Outstanding Contributor..

Re: log monitoring with entire file instead of each line

Jump to solution

The structured Logfile Policytype allows multi line parsing.

In the marketplace you find a package called "sample polices" there is a sample how to do multiline parsing.

0 Likes
Super Contributor.. hiteshkumar Super Contributor..
Super Contributor..

Re: log monitoring with entire file instead of each line

Jump to solution

Can we monitor the "0" only with log file. If in the file, there will be digit 0 then i need alert otherwise alert not required.

I am little afraid to go on production since 10, 20, 30.... contains the "0" 


If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

Regards,

Hitesh Kumar
0 Likes
Super Contributor.. hiteshkumar Super Contributor..
Super Contributor..

Re: log monitoring with entire file instead of each line

Jump to solution

Solution or workaround :

It is working when diverting the count of that keyword by using |grep <keyword> |wc -l >/<save location> to another file and monitoring that file with greater than 0 or as per requirement 🙂 .


If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

Regards,

Hitesh Kumar
0 Likes
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.