ColdFusion Test
This tests measures statistics pertaining to a ColdFusion server. The outputs of this test are described below.
Target of the test : A ColdFusion server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each ColdFusion application server.
Parameter | Description |
---|---|
Test period |
How often should the test be executed. |
Host |
The IP address of the host to which this test is to be configured. |
Port |
The port to which the specified Host listens to. |
WebServerPort |
The port number of a web server that is configured with the ColdFusion monitoring capability. This web server has to be one that is already configured to work with a ColdFusion application server. |
SSL |
Select Yes if SSL (Secure Socket Layer) has been enabled, and No if it is not. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Request rate |
Rate of requests to the ColdFusion server. |
Reqs/Sec |
A high request rate is an indicator of server overload. By comparing the request rates across application servers, an operator can gauge the effectiveness of load balancers (if any) that are in use. |
Database access rate |
Rate of database accesses issued by applications executing on the ColdFusion server. |
Reqs/Sec |
An unusually low or high rate of database accesses from one or more applications hosted on the ColdFusion application server may provide hints on anomalies with the applications. |
Data transmit rate |
Rate at which the data is transferred by the application server in response to incoming requests. |
KB/Sec |
A sudden change in data transmit rate can be indicative of a change in the characteristics of key applications hosted on the engine. |
Data receive rate |
Rate at which the data is received by the application server. |
KB/Sec |
A sudden increase or decrease in data rate to the application server is indicative of either an increase or decrease in popularity of applications hosted on the ColdFusion application server. |
Requests queued |
Number of requests queued waiting for service from the ColdFusion application server. |
Number |
An increase in requests queued can indicate a bottleneck at the application server. The problem may be caused either because of an application server problem, a problem with specific applications hosted on the ColdFusion server, or because of backend problems (e.g., with the database server, payment gateway, etc.). |
Requests running |
Number of requests currently being processed by the application server. |
Number |
An increase in requests running may indicate an increase in user workload (to be sure, correlate this value with the data transmit and receive rates). Alternatively, a slowdown at the application server may also cause the requests that are simultaneously executing to increase. |
Requests timeout rate |
Rate at which requests are timing out while waiting for service from the ColdFusion server. |
Reqs/Sec |
An increase in the time out rate of requests is a clear indication of a problem with one or more applications executing on a ColdFusion server. Requests may time out because of an application problem, because of failure to access external servers (e.g., databases, payment gateways), or because of server overload. By determining whether all of the web transactions that use the ColdFusion server are experiencing problems, an operator can determine if the problem is related to the application server or with specific applications. |
Avg queue time |
Average time in seconds spent by a request waiting for service by the ColdFusion server. |
Secs |
An increase in queuing delay reflects a server bottleneck. |
Avg response time |
Average time (in seconds) for processing a request at the server. |
Secs |
An increase in response time can occur because there are too many simultaneous requests or because of a bottleneck with any of the applications executing on the server. |
Avg database access time |
Average time (in seconds) for database accesses from applications executing on the ColdFusion server. |
Secs |
A large value of DB access time can be caused by poor query construction, bottlenecks at the database server(s), etc. |