Not getting any threshold events in CA Performance Center (CAPC) or Threshold Monitoring is Disabled

book

Article ID: 37241

calendar_today

Updated On:

Products

CA Infrastructure Management CA Infrastructure Management CA Performance Management - Usage and Administration

Issue/Introduction

After setting a number of Thresholds in the Monitoring Profiles (MP) Event Rules, no threshold events are being triggered even though there are many devices in the groups to which the associated MP has been attached. There are several ways this can happen and checking why which are described below.
 
When any given metric family takes over 80% of a poll cycle to complete, the threshold monitoring engine transitions to a degraded state.  At this point, an event is generated on the Data Aggregator indicating that if the evaluations continue to take over 80% of a poll cycle, threshold evaluation will be disabled if this persists for 15 minutes.

Environment

CAPM 3.x

Resolution

Threshold evaluations are not resumed automatically after they are suspended even if the product is restarted.


Follow these steps to check and see if threshold events were shut off.

  1. Enter the following information into a REST client (or WEB browser): http://DA_host:port/rest/thresholdmonitoring/config


    If ThresholdMonitoringLimiterEnabled is false as in the example below, then threshold monitoring was automatically shut off and you will need to reset it to resume processing threshold events

    <ThresholdMonitoringLimiterEnabled>false</ThresholdMonitoringLimiterEnabled>

  2. To reset threshold monitoring perform the following steps. Take note of the ID value of the ThresholdMonitoringConfiguration item from the output above. For example:

    <ThresholdMonitoringConfigurationList>
        <ThresholdMonitoringConfiguration version="1.0.0">
           <ID>16</ID>
           <ThresholdMonitoringEnabled>false</ThresholdMonitoringEnabled>
           <PercentOfPollCycleThreshold>50</PercentOfPollCycleThreshold>
           <ThresholdMonitoringLimiterEnabled>False</ThresholdMonitoringLimiterEnabled>
           <RecoveryIntervalInMinutes>15</RecoveryIntervalInMinutes>
        </ThresholdMonitoringConfiguration>
    </ThresholdMonitoringConfigurationList>

  3. Open a REST client editor or HTTP tool that sends requests and gets responses.

  4. Set the Content-type to application/xml. Enter the following filter criteria: URL: http://DA_host:port/rest/thresholdmonitoring/config/ID

    where ID is the identification number that is assigned to the ThresholdMonitoringConfiguration item mentioned above, which in this example is 16.

    HTTP method = PUT

    To Resume threshold evaluations, place the following in the Body tab of the HTTP Request pane:

        <ThresholdMonitoringConfiguration version="1.0.0">
             <ThresholdMonitoringEnabled>true</ThresholdMonitoringEnabled>
        </ThresholdMonitoringConfiguration>

    Then execute the put and events should resume. The following is an example of enabling monitoring using rest from the Data Aggregator command-line using the same id as noted in the examples above:

    curl -X PUT -H "Content-Type: application/xml" -d '<ThresholdMonitoringConfiguration version="1.0.0"><ThresholdMonitoringEnabled>true</ThresholdMonitoringEnabled></ThresholdMonitoringConfiguration>' http://127.0.0.1:8581/rest/thresholdmonitoring/config/16

Additional Information

For further information on threshold events and threshold event monitoring monitoring event processing see the following wiki article. 

Broadcom TechDocs : CAPM 3.7.x - Threshold Monitoring and Threshold Limiter Behavior