Monitoring and Managing a TIBCO BusinessEvents Cluster : Agent Overview

Agent Overview
 
Note that the Running Threads, Deadlocked Threads, and Garbage Collection are process-level metrics, shown here to provide a convenient overall view.
The panel common to all agent types shows the agent overview:
Running Threads
Garbage Collection
Thread Pool Best Performers
The TIBCO BusinessEvents-specific thread pools in the agent, sorted by number of active threads. The fewer running threads in a pool, the better its performance.
Thread Pool Worst Performers
The TIBCO BusinessEvents-specific thread pools in the agent, sorted by number of active threads. The more running threads in a pool, the worse its performance.
Each line represents one thread pool. Usage is in terms of the number of threads in use in each pool. The pane shows a trend of the number of busy (used) threads over time. Four default threads are:
$default.be.mt$: The general thread pool controlled by the property com.tibco.cep.runtime.scheduler.default.numThreads
CacheCluster   handles the Agent and other Cache membership and other properties.
CommonScheduledWorkManager: Any Scheduler created with a single thread uses this default thread pool.
CommonWorkManager: Any WorkManager created with a single thread uses this default thread pool.
Job Queue Best Performers
The best performing TIBCO BusinessEvents-specific job queues. Job queue performance is based on how many jobs are pending in the queue. The fewer the number of pending jobs, the better the performance of the queue.
Job Queue Worst Performers
The worst performing TIBCO BusinessEvents-specific job queues. Job queue performance is based on how many jobs are pending in the queue. The larger the number of pending jobs, the worse the performance of the queue.