QOS_CPU_USAGE on Idle - False alarm Issue
search cancel

QOS_CPU_USAGE on Idle - False alarm Issue

book

Article ID: 270320

calendar_today

Updated On:

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 are receiving unwanted and unexpected alarms with the message QOS_CPU_USAGE on Idle.

Environment

  • Release: 20.4

Resolution

We observed there is this target value ~.* in plugin_metric.cfg, but it should have been {device.name} - initially we had this issue and it was fixed in the policy_management code but some of these policies were created a year ago before this fix, so we needed to provide queries to correct the data in the policy_metric table, so thereby it would correct the information in the plugin_metric.cfg.

   select * from PolicyMetric where qos = 'QOS_CPU_USAGE' and probeName = 'cdm'

In short, target's defined as  ~.* was an old issue with policy management that has since been fixed.

We corrected the target in the PolicyMetric table for QOS_CPU_USAGE qos metric.

Related tables:

  • Policy
  • PolicyCondition
  • PolicyMetric
  • SSRV2ProbeTemplatesPackage

Then we updated policies to a 'MODIFIED' state for 21 policies related to the the QOS_CPU_USAGE metric.

We then performed a random check of the plugin_metric.cfg for a few systems and they were then updated with the correct target [device.name] names.

Since there are quite a number of robots that are still generating robot inactive alarms, this issue could possibly still reoccur when one or more of those systems comes back online if the target values are ~.*

Those systems should be identified, and they should be placed into a MODIFIED status, so they refresh their status and target names get updated.

If desired, you can add a nas AO Profile to alert someone if you get any further messages.

Here is a temporary nas AO profile you can use and keep it in place for a few days:

This uses a message string as the filter: (names x'd out for privacy)

   /.*QOS_CPU_USAGE on Idle for xxxxxx.*|xxxxxxxxx.*|xxxxxxx.*/

Add email addresses that are to be alerted.