eG Monitoring
 

Measures reported by SiebelCompStsTest

Components refer to the various tasks or programs that run on the Siebel server and perform the work requested by the user. For example, the object manager is one of the key components on a Siebel server. The requests to every application executing on a Siebel server are typically handled by one/more object managers. If the object manager required by an application is not running, then the Siebel server will be forced to reject all requests for that application, causing the end-user to suffer. The SiebelCompStsTest test monitors each of the object managers to ascertain their current state and load.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Run_state Indicates the number of invocations of the notification handler that failed for this component.   The values that this measure can report and their corresponding numeric values are tabulated below:

Numeric Value Measure Value
0 StartingUP
1 Online
2 Running
3 Offline
4 ShuttingDown
5 ShutDown
6 Unavailable

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the current state of this Siebel Object Manager. However, in the graph of this measure, the current status will be represented using the numeric equivalents only.
Max_mts_server Indicates the maximum number of MTServer per component per server. Number An MTServer is a multi-threaded component process. A high value for this measure is indicative of too many users logging into the Siebel server.
Active_mts_server Indicates the number of MTServers that are currently active on this Object Manager. Number The value of this measure should be close to the Max_mts_server measure.
MTS_usage_factor Indicates the percentage of MTServers that are being actively used by this Object Manager Percent Ideally, the value of this measure should be between 90-100%. A far less value indicates that the object manager is grossly under-utilizing the MTServers. This happens when the object manager does not have enough tasks to run, and is more or less idle.