logmon_mcs_template not successfully activating/deploying

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We were using logmon - working with MCS for enhanced profile deployment, testing, and deployment confirmation. We followed the same auto-migrate process we followed for processes but, it displayed an error 'No such probe template' even though all of the mcs template versions were present in the local archive.

Environment

• DX UIM 23.4 CU2
• logmon 5.02
• logmon_mcs_template 4.24, displays as 4.24.1 under OC Monitoring Config
• Log Monitoring (Enhanced)

Cause

• Needed to migrate from legacy template to enhanced

Resolution

To work around the issue of the logmon_mcs_template not successfully activating/deploying

 

   select * from SSRV2ProbeTemplatesPackage where probe_name = 'logmon'

 

We used the PU callback 'one-step migrator' which worked for the logmon probe and version 4.24.

 

'Customize Monitoring' menu - displays Watcher, Format, Exit Code and Exclude rules.

 

When testing, check to make sure the logmon MCS configuration is correct and the actual file location your using for the test is correct (drive, file system and use the absolute path), otherwise the rules in OC may display as 'Pending.'

 

Testing of the test profile was successful for F:\tmp\<absolute_path> as we saw the alarm was generated but the alarm variables specified were doubled, so they don't need to be specified in the MCS config window.

 

Tip: Set monitoring interval in the Setup_logmon higher than 60, try 120 (2 mins).

Additional Information

There is no 'formal' MCS alarm policy required for logmon unless you define and use custom logmon variables.

 

KB Article reference for working with logmon variables:

How to use and configure variables in logmon probe profiles