Triggers
You can populate the data in a report based on certain conditions. When those conditions are met, the trigger run's. Based on your requirements, you can modify threshold values by using REST APIs.
http://<host>:<port>/monitor
as a base URL for all the REST APIs provided.The following triggers are available:
High CPU Trigger
ID | bw.montr.trigger.HighCPUTrigger |
Threshold |
highCpuThresholdPercent: 80 highCpuDurationMins: 5 |
Description | The trigger measures the 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 the 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 a 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 a 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 TIBCO BusinessWorks Container Edition 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 a 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 TIBCO BusinessWorks Container Edition 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. |
High JMS Queue Pending Messages Count Trigger
ID | bw.sharedresource.trigger.HttpConnectorAcceptorThreadCountThresholdTriggerAction |
Threshold | - |
Description | The default value of the HTTP Acceptor Thread Count Configuration on the HTTP Connector Shared Resource is 1. Jetty provides a formula for the maximum number of acceptor threads that can be allocated based on the available machine processors.
The trigger checks the under-utilized acceptor threads. This means that the trigger condition is met when the configured value is less than the MAX allowed acceptor thread count value. |
HTTP Connector Acceptor Thread Count Threshold Trigger
ID | bw.sharedresource.trigger.HttpConnectorAcceptorThreadCountThresholdTriggerAction |
Threshold | - |
Description | The default value of the HTTP Acceptor Thread Count Configuration on the HTTP Connector Shared Resource is 1. Jetty provides a formula for the maximum number of acceptor threads that can be allocated based on the available machine processors.
The trigger checks the under-utilized acceptor threads. This means that the trigger condition is met when the configured value is less than the MAX allowed acceptor thread count value. |
HTTP Connector Executor Threadpool Utilization Threshold Trigger
ID | bw.sharedresource.trigger.HttpConnectorExecutorThreadpoolUtilizationThresholdTriggerAction |
Threshold |
executorThreadpoolUtilizationThreshold: 85.0 highThreadpoolUtilizationDurationMinutesThreshold: 5.0 |
Description | The trigger measures the threadpool utilization while processing the incoming HTTP requests. The trigger conditions are met when the threadpool utilization is more than (including) 85% over the span of 5 minutes by default. |
HTTP Connector Queue Utilization Threshold Trigger
ID | bw.sharedresource.trigger.HttpConnectorQueueUtilizationThresholdTriggerAction |
Threshold | connectorThreadpoolQueueUtilizationThreshold: 85.0 |
Description |
The blocking queue size for the Jetty server in TIBCO BusinessWorks Container Edition 2.x can be set using the System property, bw.engine.http.jetty.blockingQueueSize=<Integer Value>. The trigger measures this jetty blocking queue utilization percentage. The trigger conditions are met when the blocking queue size is more than (including) 85% full by default. |