UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.

enhance metric logfile policy to allow to store more than one metrik per line

Idea ID 2847691

enhance metric logfile policy to allow to store more than one metrik per line

often 3rd party applications create logs with performance date like:

"metrik1_value, metrik2_value, metrik3 _value,..."

at the moment structurelogfile policy for metrics condition matching stops after a matched condition. so only the first metrik can be stored

to parse all of this metriks it will be helpful to add an option to not stop evaluation on matched conditions, so that more than one metrik can be processed.

workaround at the moment is to create for each metrik a policy that parse the same file. its a bit unefficent.

3 Comments
Fleet Admiral Fleet Admiral
Fleet Admiral

found a dirty hack with "store records on unmatched conditions" checkbox.

Micro Focus Expert
Micro Focus Expert
Status changed to: Needs Clarification

Hi,

I'm not sure why you say its not possible.  Have you looked at the policy documentation which describes such scenarios:

https://docs.microfocus.com/itom/Operations_Bridge_Manager:2020.10/OmucptStructuredlogfile

Metrics and Generic Output only. Log file structure definition with recurring fields

The "Recurring fields" configuration parameter is useful in case when more than one performance value is present within a single log file line. This is actually a word list that contains the recurring part from the log line. Each recurrence creates a record in the store.

Example 3: Extract the log file structure from the following log file lines by using also the recurring fields:

1380004749|tcpc113.RIESLING.INTERN|LogicalDisk|C:|% Free Space|66.379264831543|Current Disk Queue Length|0|Avg. Disk sec/Transfer|0.000484383897855878

1380004748|tcpc113.RIESLING.INTERN|Network Interface|10|Bytes Total/sec|55230.0703125|Current Bandwidth|1000000000

This is done by defining the fields from which the log file line is logically constituted, and then identifying which of them can be addressed as static fields, and which can be described as a variable part that consists of an arbitrary number of countername-countervalue pairs. These are the recurring fields. The log file lines in this example are constituted logically from the following fields:

timestamp|hostname|entitytype|entityid|countername_1|countervalue_1|countername_2|countervalue_2|countername_3|countervalue_3

timestamp|hostname|entitytype|entityid|countername_1|countervalue_1|countername_2|countervalue_2

Thanks & Regards,

Mamta

Captain Captain
Captain

Hi Mgoyal,

 

the documentation is not clear and need clarification too but anyway. 

Thanks for sharing this part but the problems is more further in the documentation. 

As the policy stop when1 rule match, please tell us how configure the rule to get all metrics from one line with only 1 policy ?

I think, that the point of this idea.

To be clear, If I took the exemple from the documentation I want 1 Policy to read this line :

1380004749|tcpc113.RIESLING.INTERN|LogicalDisk|C:|% Free Space|66.379264831543|Current Disk Queue Length|0|Avg. Disk sec/Transfer|0.000484383897855878

and get then store the value of each metrics.  with only 1 policy for all metrics

 

thanks in advance

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.