Use logmon to Collect QoS Data
search cancel

Use logmon to Collect QoS Data


Article ID: 34954


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Logmon is a versatile probe allowing you to scan log files, web output and even issue a command and scan the output from that command. This article describes configuration options needed to scan a file and create a QoS entry based on output from that file.


Any logmon probe version


o1. Create a new logmon profile. On General tab you need to select the Mode, File, Interval and the function of the profile. 

 This can be to Generate Quality of Service, Generate alarm or both.


The cat mode will always scan the complete log file from beginning to end-of-file mark. 

 The update mode will only scan the log file from the last position forward to end-of-file make. 

The command mode will cause logmon to run a command and scan the output, via sysout, of that command.

2. Select a format for this profile from the Format Rules tab. A format need only to be defined if a single log entry consists of more than one line. 

 Jave exceptions are a good example of when formats are required.


3. Configure the Watcher rules. This is where the work of logmon is really done. The watcher tells the probe what to look for when scanning the log file. Here is a screen capture of the log file we want to scan with this watcher. 

Since we want to create a QoS entry we need to isolate the numeric value. Here is a look at our watcher rule to do just that:

By enclosing our numeric expression \d in parenthesis we create a Match Expression which can be used to configure a variable. We will then use the variable in our QoS definition.


4. Configure a QoS entry for the data you have collected. This is done in two locations. You first need to define the QoS under the setup tab. 


The QoS Name will be appended to a general heading QOS_LOGMON. The QoS Description, QoS Unit and Unit abbreviatio need to be something meaningful to you. You next need to tie this QoS entry into your watcher rule under the QoS tab. 


In this case the variable var will be used as the value. The QoS will be QOS_LOGMON_QOS_TICKETS and the target will be mn56c. 


Here is what that entry looks like in Service Level Manager:


All QoS objects need to be numeric. Each watcher rule can only collect one QoS. Each QoS needs to be linked with its own definition.