The Redbex <%APPLICATIONSERVER% performance and status can be monitored using the Windows Performance Monitor. The Windows Performance Monitor is included in all versions of Windows operating systems, it allows you to examine how programs you run affect your computer's performance, both in real time and by collecting log data for later analysis.
During installation of the Redbex Application Server the setup program creates a performance counter category named Redbex Application Server and several performance counters within this category. Table 1 lists the created counters and their meaning.
Using the Window's perfmon.exe utility (the graphical user interface to the Windows Performance Monitor included with all versions of Windows) you can monitor all these performance counters (of course also in connection with other Windows performance counters).
The Windows Performance Monitor supports monitoring multiple instances of counters. The performance counters in the Redbex Application Server category make use of this to enable monitoring of multiple instances of the Redbex Application Server separately.
Counter name |
Description |
User session count |
Number of currently open user sessions. This counter includes active, idle and abandoned sessions. |
User sessions/sec |
Number of user sessions created per second. |
API calls/sec |
The number of API calls received by the Application Server per second. This number is a good general indicator of the usage intensity of the Application Server |
API call average processing time |
Average time in milliseconds it takes for a single API call to be processed. This number expresses the average time in milliseconds it takes for the server to answer a single API call from a client. This counter is a good indicator for the general system performance. |
Jobs on queue |
Number of jobs on the job queue. Jobs on the queue do not directly influence the overall performance of the Application Server, however this performance counter can be used to monitor if the server is capable of processing all the jobs queued. |
Jobs running |
Number of jobs that are currently processed. The number of concurrently processed jobs is limited by a global setting. |
Content purging queue size |
Number of items on the content purging queue. A growing purging queue is usually a sign that big numbers of features or observations are marked for deletion in quick succession - i.e. the purging process cannot handle existing requests before new requests are pushed on the queue. |
Content purging average time |
Average time (in milliseconds) a content purging request takes till the data was actually deleted in the Redbex Application Server Database. |
Features created/sec |
Number of features created per second |
Features modified/sec |
Number of features modified per second |
Features marked for deletion/sec |
Number of features marked for deletion per second |
Observations created/sec |
Number of observations created per second |
Observations modified/sec |
Number of observations modified per second |
Observations marked for deletion/sec |
Number of observations marked for deletion per sec |
Data change log entries not persisted |
Number of data change logs entries only stored in memory and waiting to be persisted. This counter can be used to optimize the settings for data change logging. |
Table 1: Performance counters for monitoring Application Server performance
