Content Server Record Changes Test
This test reports the number of append, insert, update, and delete record events that occurred on the Content Server and the time taken by the server to complete each of the aforesaid operations. This not only reveals the workload on the server, but also points you to slowdowns in record-change operations and the type of operation that experienced the maximum latency.
Target of the test : A Teratext Content Server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each type of record-change operation performed on the Teratext Content Server being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed |
Host |
The host for which the test is to be configured |
Port |
The port number at which the specified host listens |
User, Password, Confirm Password |
To monitor the Content Server, the eG agent should connect to the server using the credentials of a user with rights to access the IR-EXPLAIN-1database. Provide the credentials of such a user in the User and Password text boxes, and confirm the password by retyping it in the Confirm Password text box. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Count |
Indicates the total number of record-change operations performed during the last measurement period. |
Number |
This is a good indicator of the workload on the server. |
Average duration |
Indicate the average time taken by this type of operation to complete. |
Secs |
Ideally, the value of this measure should be low. A steady increase in the value of this measure could indicate that record0change operations are not been performed as quickly as desired. Further investigations may be necessary to identify the root-cause of these latencies. |