ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Threshold Events are not triggering

book

Article ID: 198939

calendar_today

Updated On:

Products

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

Issue/Introduction

I am not able to see Events trigger in Performance Center. I have checked the Threshold Monitoring page but none appear for any rules

Cause

The following error can be seen in the Data Aggregator Exception and karaf logs:

2020-08-27 10:22:52,0902020-08-27 10:22:52,090 | ERROR | ExceptionLog | A NEW application exception occurred (Key=4e6f63e96b050634b70c6277ab9625741f3b0f58) : ThresholdScheduleTask caught exception  | (ExceptionLogger.java:99) 
java.lang.NullPointerException
    at com.ca.im.dm.core.aggregator.alarm.impl.FilteredEventProfileDAOImpl.buildAlarmRuleCriteria(FilteredEventProfileDAOImpl.java:935)[221:com.ca.im.aggregator.loader:3.7.7.RELEASE-537]
    at com.ca.im.dm.core.aggregator.alarm.impl.FilteredEventProfileDAOImpl.populateAlarmRuleDTOs(FilteredEventProfileDAOImpl.java:495)[221:com.ca.im.aggregator.loader:3.7.7.RELEASE-537]
    at com.ca.im.dm.core.aggregator.alarm.impl.FilteredEventProfileDAOImpl.buildFilteredEventProfileDTO(FilteredEventProfileDAOImpl.java:221)[221:com.ca.im.aggregator.loader:3.7.7.RELEASE-537]
    at com.ca.im.dm.core.aggregator.alarm.impl.FilteredEventProfileDAOImpl.getFilteredEventProfiles(FilteredEventProfileDAOImpl.java:1130)[221:com.ca.im.aggregator.loader:3.7.7.RELEASE-537]
    at com.ca.im.dm.core.aggregator.alarm.schedule.impl.ThresholdRequestHandlerImpl.performThresholdEvaluation(ThresholdRequestHandlerImpl.java:51)[221:com.ca.im.aggregator.loader:3.7.7.RELEASE-537]
    at com.ca.im.dm.core.aggregator.alarm.schedule.impl.ThresholdScheduleTask.performTask(ThresholdScheduleTask.java:99)[221:com.ca.im.aggregator.loader:3.7.7.RELEASE-537]
    at com.ca.im.dm.core.aggregator.alarm.schedule.impl.ThresholdScheduleTask.run(ThresholdScheduleTask.java:66)[221:com.ca.im.aggregator.loader:3.7.7.RELEASE-537]
    at com.ca.im.core.concurrent.DelegatingRunnable.run(DelegatingRunnable.java:29)[166:com.ca.im.common.core.util:3.7.7.RELEASE-537]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_222]
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_222]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_222]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_222]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_222]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_222]
    at java.lang.Thread.run(Thread.java:748)[:1.8.0_222]

This is due to the rules not being fully filled out yet somehow saved.  This can happen when using REST and not transmitting the full entries.

Environment

Release : 3.7

Component : IM Reporting / Admin / Configuration

Resolution

Access the Performance Center GUI and fill out the Threshold Monitoring rules fully, to include the logic values.