Ability to monitor the Directory
Server using Netscape Console.
|
Try
This:
Navigate to the Directory
Server branch on your console. |
See Chapter 10, Managing
You Directory Server, of the Administrator's Guide.
|
Try
This:
Use Netscape Console to observe
the total number of connections to this server since server startup. |
Try
This:
Use Netscape Console to observe
the Current Resource Usage for Active Threads. |
Try
This:
Use Netscape Console to view
General
Information about the database. |
Try
This:
Use Netscape Console to observe
the Entry cache hits on your server. |
Try
This:
Use Netscape Console to observe
the tables for each index file that makes up your database. How do
these tables compare with the indexes identified in the Configuration section
of this WBT. |
|
Monitoring Your Server
You can monitor your directory server's current activities
from either the server console or the command line. You can monitor database
and cache activities in the same manner. The following section describes
how to monitor your server's activity from the Server Console.
Monitoring Your Server from the Server Console
To monitor your server's activities through the server console:
On the Console, in the left pane, through the tree, open the host, open
the server group and double click on the Directory Server.
From the resulting display, select the Status tab and
click Performance Counters in the navigation tree in the left pane.
The Server 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 Refresh to refresh the currently displayed information.
If you want the server to continuously update the displayed information,
select the Continuous check box and then click Refresh.
General Information
Note the general information under the Server tab.
This a place you could look if you wanted to know the software version
of your server. You can also find the server's machine data tree
DN, the server host name, the server port number, the current change log
number, and other useful information.
Resource Usage
You monitor your resource usage through three tables that appear
below the general information.
The first of these is the Resource Summary table which provides
the resource-specific information.
Resource |
Usage Since Startup |
Average Per Minute |
Connections |
Total number of connections to this server since
server startup. |
Average number of connections per minute since
the server started. |
Operations Initiated |
Total number of operations initiated since server
startup. Operations are any client requests for server action, such as
searches, adds, and modifies in the directory tree. It is likely that multiple
operations will be initiated for each connection. |
Average number of operations per minute since
the server started. |
Operations Completed |
Total number of operations completed by the server
since server startup. |
Average number of operations per minute since
the server started. |
Entries sent to clients |
Total number of entries sent to clients since
the server started. Entries are sent to clients as the result of search
requests. |
Average number of entries sent to clients per
minute since the server started. |
Bytes sent to clients |
Total number of bytes sent to clients since the
server started. |
Average number of bytes sent to clients per minute
since the server started. |
Current Resource Usage
This is the second of the three main tables displayed when
you monitor your server.
Resource |
Current Total |
Active Threads |
Current number of active threads. Each thread
represents a single operation currently active in the server. Additional
threads may also be created by internal server housekeeping tasks, such
as replication. |
Open Connections |
Total number of open connections. Each connection
can account for multiple operations, and therefore multiple threads. |
Remaining available connections |
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. The latter value is determined by the operating
system, and is expressed as the number of file descriptors available to
a task. Refer to your operating system documentation for more information
on file descriptors. |
Threads waiting to write to client |
Total number of threads waiting to write to the
client. This happens anytime the server must pause while sending data to
a client. Reasons for this are a slow network, a slow client, or an extremely
large amount of information being sent to the client. |
Threads waiting to read from client |
Total number of threads waiting to read from
the client. This happens 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 a slow client. |
Thread Concurrency |
Meaningful on Solaris 2.x only. Provides an indication
of the level of thread concurrency. |
Databases in use |
Total number of databases being serviced by the
server. Currently, this value is always 1. |
Connection Status
This is the third of the three main tables displayed when you
monitor your server. This table provides information on the amount of resources
in use by each currently open connection. Values are:
Time opened: Indicates the time on the server when the connection
was initially opened.
Operations: Indicates the number of operations initiated by this
connection, and the number of those operations completed by the server.
Bind DN: Indicates the distinguished name used by the client to
connect to the server. If the client has not authenticated to the server,
not
bound is shown in this field.
Read/Write: Indicates whether the server is currently blocked for
read or write access to the client. Possible values are:
Not blocked indicates that the server is idle, actively sending data to
the client, or actively reading data from the client.
Blocked indicates that the server is trying to send data to the client
or read data from the client, but the server cannot. The probable cause
for being blocked is a slow network or a slow client.
Monitoring Database Activity from the Server Console
You can monitor your database's current activities from the
server console or from the command line.
From the Status tab, select the Database tab.
General Information (Database)
Note
the general information area. It consists of:
Database—identifies the type of database that you are monitoring.
Config DN—identifies the distinguished name that you can use to obtain
these results using the ldapsearch.
Summary Information Table
The Summary Information table provides information about the
following:
Performance Metric |
Current Total |
Read-only status |
Indicates whether the database is currently in read-only mode. Your
database is in read-only mode when your readonly slapd.conf parameter is
set to on. |
Entry cache hits |
Indicates the total number of successful entry cache lookups. That
is, the total number of times the a server could process a search request
by obtaining data from the cache rather than by going to disk. |
Entry cache tries |
Indicates the total number of entry cache lookups since the directory
server was last started. That is, this is the total number of search operations
performed against your server since server startup. |
Entry cache hit Ratio |
Ratio that indicates the number of entry cache tries to successful
entry cache lookups. This number is based on the total lookups and hits
since the server was last started. The closer this value is to 100% the
better. Whenever a search operation attempts to find an entry that is not
resident in the entry cache, the directory server has to perform a disk
access to obtain the entry. Thus, as this ratio drops towards zero,
the number of disk accesses increases and directory server search performance
drops. |
Current number of entries in entry
cache |
Indicates the total number of directory entries currently resident
in the entry cache. |
Maximum number of entries in entry cache |
Indicates the maximum number of directory entries that are allowed
to be maintained in the entry cache. This value is managed by the Maximum
Entries in Cache parameter in slapd.conf. |
Database Cache Information Table
The Database Cache Information table provides the caching
information as described below.
Performance Metric |
Current Total |
Hits |
Indicates the number of times the database cache successfully supplied
a requested page. |
Tries |
Indicates the number of times the database cache was asked for a page. |
Hit ratio |
Indicates the ratio of database cache hits to database cache tries.
The closer this value is to 100%, the better.
Whenever a directory operation attempts to find a portion of the database
that is not resident in the database cache, the directory server has to
perform a disk access to obtain the appropriate database page. Thus, as
this ratio drops towards zero, the number of disk accesses increases and
directory server performance drops. |
Pages read in |
Indicates the number of pages read from disk into the database cache. |
Pages written out |
Indicates the number of pages written from the cache back to disk.
A database page is written out to disk whenever a read-write page has been
modified and then subsequently evicted from the cache. Pages are evicted
from the database cache when the cache is full and a directory operation
requires a database page that is not currently stored in cache. |
Read-only page evicts |
Indicates the number of read-only pages discarded from the cache to
make room for new pages. |
Read-write page evicts |
Indicates 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. |
Database File-Specific Table
The server displays a table for each index file that makes
up your database. Each of the tables provides the information described
below.
Performance Metric |
Current Total |
Cache hits |
Number of times that a search result resulted in a cache hit on this
specific file. That is, a search that required data from this file was
performed and the required data was successfully obtained from the cache. |
Cache misses |
Number of times that a search result failed to result in a cache hit
on this specific file. That is, a search that required data from this file
was performed and the required data could not be found in the cache. |
Pages read in |
Indicates the number of pages brought to the cache from this file. |
Pages written out |
Indicates the number of pages for this file written from cache to disk. |
|