20.6. Monitoring Server Activity
20.6.1. Monitoring the Server from the Directory Server Console
- Select the Status tab.
- In the navigation tree, select Performance Counters.The Status tab in the right pane displays current information about server activity. If the server is currently not running, this tab will not provide performance monitoring information.
- Click Continuous check box.to refresh the current display. For the server to continuously update the displayed information, select the

Table 20.2. General Information (Server)
Field | Description |
---|---|
Server Version | Identifies the current server version. |
Startup Time on Server | The date and time the server was started. |
Current Time on Server | The current date and time on the server. |

Table 20.3. Resource Summary
Resource | Usage Since Startup | Average Per Minute |
---|---|---|
Connections | The total number of connections to this server since server startup. | Average number of connections per minute since server startup. |
Operations Initiated | The total number of operations initiated since server startup. Operations include any client requests for server action,such as searches, adds, and modifies. Often, multiple operations are initiated for each connection. | Average number of operations per minute since server startup. |
Operations Completed | The total number of operations completed by the server since server startup. | Average number of operations per minute since server startup. |
Entries Sent to Clients | The total number of entries sent to clients since server startup. Entries are sent to clients as the result of search requests. | Average number of entries sent to clients per minute since server startup. |
Bytes Sent to Clients | The total number of bytes sent to clients since server startup. | Average number of bytes sent to clients per minute since server startup. |

Table 20.4. Current Resource Usage
Resource | Current Total |
---|---|
Active Threads | The current number of active threads used for handling requests. Additional threads may be created by internal server tasks, such as replication or chaining. |
Open Connections | The total number of open connections. Each connection can account for multiple operations, and therefore multiple threads. |
Remaining Available Connections | The total number of remaining connections that the server can concurrently open. This number is based on the number of currently open connections and the total number of concurrent connections that the server is allowed to open. In most cases, the latter value is determined by the operating system and is expressed as the number of file descriptors available to a task. |
Threads Waiting to Write to Client | The total number of threads waiting to write to the client. Threads may not be immediately written when the server must pause while sending data to a client. Reasons for a pause include a slow network, a slow client, or an extremely large amount of information being sent to the client. |
Threads Waiting to Read from Client | The total number of threads waiting to read from the client. Threads may not be immediately read if the server starts to receive a request from the client, and then the transmission of that request is halted for some reason. Generally, threads waiting to read are an indication of a slow network or client. |
Databases in Use | The total number of databases being serviced by the server. |

Table 20.5. Connection Status
Table Header | Description | ||
---|---|---|---|
Time Opened | The time on the server when the connection was initially opened. | ||
Started | The number of operations initiated by this connection. | ||
Completed | The number of operations completed by the server for this connection. | ||
Bound as | The distinguished name used by the client to bind to the server. If the client has not authenticated to the server, the server displays not bound in this field. | ||
Read/Write | Indicates whether the server is currently blocked for read or write access to the client. There are two possible values:
|

Note
cn=monitor,cn=database_instance,cn=ldbm database,cn=plugins,cn=config
, as are the other database activities. Monitoring these entries through the command line is covered in Section 20.7.2, “Monitoring Databases from the Command Line”.
Table 20.6. Global Database Cache Information
Table Header | Description |
---|---|
Hits | The number of times the server could process a request by obtaining data from the cache rather than by going to the disk. |
Tries | The total number of database accesses since server startup. |
Hit Ratio | The ratio of cache tries to successful cache hits. The closer this number is to 100%, the better. |
Pages Read In | The number of pages read from disk into the cache. |
Pages Written Out | The number of pages written from the cache back to disk. |
Read-Only Page Evicts | The number of read-only pages discarded from the cache to make room for new pages. Pages discarded from the cache have to be written to disk, possibly affecting server performance. The lower the number of page evicts the better. |
Read-Write Page Evicts | The number of read-write pages discarded from the cache to make room for new pages. This value differs from Pages Written Out in that these are discarded read-write pages that have not been modified. Pages discarded from the cache have to be written to disk, possibly affecting server performance. The lower the number of page evicts, the better. |
20.6.2. Monitoring the Directory Server from the Command Line
ldapsearch
, with the following characteristics:
- Search with the attribute filter
objectClass=*
. - Use the search base
cn=monitor
; the monitoring attributes for the server are found in thecn=monitor
entry. - Use the search scope
base
.
# ldapsearch -D "cn=Directory Manager" -W -p 389 -h server.example.com -x -s base -b "cn=monitor" "(objectclass=*)"
cn=monitor
entry. For information on searching the Directory Server, see Section 14.3, “Using ldapsearch”.
Table 20.7. Server Monitoring Attributes
Attribute | Description | ||||||
---|---|---|---|---|---|---|---|
version | Identifies the directory's current version number. | ||||||
threads | The current number of active threads used for handling requests. Additional threads may be created by internal server tasks, such as replication or chaining. | ||||||
connection:fd:opentime:opsinitiated:opscompleted:binddn:[rw] | Provides the following summary information for each open connection (only available if you bind to the directory as Directory Manager):
| ||||||
currentconnections | Identifies the number of connections currently in service by the directory. | ||||||
totalconnections | Identifies the number of connections handled by the directory since it started. | ||||||
dtablesize | Shows the number of file descriptors available to the directory. Each connection requires one file descriptor: one for every open index, one for log file management, and one for ns-slapd itself. Essentially, this value shows how many additional concurrent connections can be serviced by the directory. For more information on file descriptors, see the operating system documentation. | ||||||
readwaiters | Identifies the number of threads waiting to read data from a client. | ||||||
opsinitiated | Identifies the number of operations the server has initiated since it started. | ||||||
opscompleted | Identifies the number of operations the server has completed since it started. | ||||||
entriessent | Identifies the number of entries sent to clients since the server started. | ||||||
bytessent | Identifies the number of bytes sent to clients since the server started. | ||||||
currenttime | Identifies the time when this snapshot of the server was taken. The time is displayed in Greenwich Mean Time (GMT) in UTC format. | ||||||
starttime | Identifies the time when the server started. The time is displayed in Greenwich Mean Time (GMT) in UTC format. | ||||||
nbackends | Identifies the number of back ends (databases) the server services. | ||||||
backendmonitordn | Identifies the DN of each directory database. |