Triggers

You can populate the data in a report based on certain conditions. When those conditions are met, the trigger is executed. Based on your requirements, you can modify threshold values by using REST APIs.

The following triggers are available:

High CPU Trigger

ID	bw.montr.trigger.HighCPUTrigger
Threshold	highCpuThresholdPercent: 80 highCpuDurationMins: 5
Description	The trigger measures high CPU usage situation. The trigger conditions are met when CPU usage is equal to or greater than 80% and the situation has lasted for more than (including) 5 minutes.

High Memory Trigger

ID	bw.montr.trigger.HighMemoryTrigger
Threshold	highMemoryThresholdPercent: 80 highMemoryDurationMins: 5
Description	The trigger measures high memory usage situation. The trigger conditions are met when memory usage is equal to or greater than 80% and the situation has lasted for more than (including) 5 minutes.

Out of Memory Trigger

ID	bw.montr.trigger.OutOfMemoryTrigger
Threshold	outOfMemoryThresholdPercent: 95
Description	The trigger measures very high memory usage situation (very close to out of memory). The trigger condition is met when memory usage is equal to or greater than 95%.

High Live Threads Trigger

ID	bw.montr.trigger.HighLiveThreadsTrigger
Threshold	highLiveThreadsThreshold: 500 highLiveThreadsDurationMins: 5
Description	The trigger measures high number of live threads situation. The trigger conditions are met when the number of live threads (including both daemon and non-daemon threads) is equal to or greater than 500 and the situation has lasted for more than (including) 5 minutes.

High JMS Queue Pending Messages Trending Trigger

ID	bw.sharedresource.trigger.HighQueuePendingMessagesTrendingTriggerAction
Threshold	queuePendingMessagesCountMinValueThreshold: 1000 queuePendingMessagesTrendingPercentThreshold: 300 queuePendingMessagesDurationMinutesThreshold: 5
Description	The trigger measures the delay of processing JMS messages situation by checking the trending of pending messages in JMS queues that are accessed by activities in each ActiveMatrix BusinessWorks application. The trigger conditions are met when the pending messages in a JMS queue has increased by more than (including) 300 percent in recent 5 minutes with minimum pending messages of 1000.

High JMS Queue Pending Messages Count Trigger

ID	bw.sharedresource.trigger.HighQueuePendingMessagesCountTriggerAction
Threshold	queuePendingMessagesCountThreshold: 10000 queuePendingMessagesDurationMinutesThreshold: 5
Description	The trigger measures the delay of processing JMS messages situation by checking the number of pending messages in JMS queues that are accessed by activities in each ActiveMatrix BusinessWorks application. The trigger conditions are met when the number of pending messages in a JMS queue is equal to or greater than 10000 and the situation has lasted for more than (including) 5 minutes.