| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Availability |
Whether a
successful response is received from the LDAP server in response to
the emulated user request. |
Percent
|
An availability
problem can be caused by different factors – e.g., the server
process may not be up, a network problem may exist, or there could be
a configuration problem with the LDAP server. |
| Response_time |
Time taken (in
seconds) by the server to respond to a request. |
Secs
|
An increase in
response time can be caused by several factors such as a server
bottleneck, a configuration problem with the LDAP server, a network
problem, etc. |
| Current_connections
|
Number of
connections currently being processed by the LDAP server. |
Number
|
A high value
could result whenever the server is experiencing a problem (due to
overload, or because of application problems). |
| Connection_rate |
Quantifies the
workload in terms of connections per second to the LDAP server. |
Conns/Sec
|
This value
directly represents the user workload. |
| Operations_outstanding |
The number of
outstanding requests waiting for processing by the LDAP server |
Number
|
A consistent
non-zero value of this metric is indicative of a server bottleneck. |
| Data_xmit_rate |
Quantifies the
traffic handled by the LDAP server in Kbytes/sec. |
KB/Sec
|
Typically, an
increase or decrease in connection rate will result in a corresponding
change in the data transmission rate. A deviation from this rule
signifies a possible change in the characteristics of applications
accessing the LDAP server, or a change in the organization of the LDAP
schema. |
| Tcp_connection_availability
|
This measure
indicates whether the test managed to establish a TCP connection to
the server. |
Percent |
Failure to
establish a TCP connection may imply that either the web server
process is not up, or that the process is not operating correctly. In
some cases of extreme overload, the failure to establish a TCP
connection may be a transient condition. As the load subsides,
the server may start functioning properly again.
If the Tcp_connection_availability is 100% but Availability is 0,
this could indicate a problem with the server configuration.
Alternatively, the search string provided as a parameter to the
LdapTest may not be supported by the corresponding LDAP server. In
this case, configure the test based on the directory structure
configured for the target LDAP server (i.e., change the "cn=monitor"
value with an appropriate alternative).
|