Monitoring the Database from the Command Line
You can monitor your directory server's database activities from any LDAP client by specifying the following parameters:
objectClass=*
and a search base of
cn=monitor,cn=ldbm and a scope of base
For example:
blueprints# ldapsearch -h blueprints.com -s base -b "cn=monitor,cn=ldbm" "(objectclass=*)"
cn=monitor,cn=ldbm objectclass=top objectclass=extensibleObject cn=monitor database=ldbm readonly=0
entrycachehits=2 611
entrycachetries=2 93 9
entrycachehitratio=8 8
currententrycachesize=3 05
maxentrycachesize=100 00 0
dbchehits=2046
dbcachetries=22 51
dbcachehitratio=9 0
dbcachepagein=2 05
dbcachepageout=6 0
dbcacheroevict=0
dbcacherwevict=0
dbfilename-0=uid.db2
dbfilecachehit-0=4 6
dbfilecachemiss-0=3
dbfilepagein-0=3
dbfilepageout-0=6
blueprints#
When you monitor your server's activities in this way, you see the following information:
database — The type of database you are currently monitoring.
read-only — State of the database, that is, whether in read-only mode. A value of 0 means the server is not in read-only mode; 1 means it is in read-only mode.
The other parameters displayed are listed in TABLE 10-7 along with a cross-reference to the performance metric it represents.
|
TABLE 10-7 Displayed Parameters | |
|
Parameter |
Performance Metric |
|
entrycachehlts |
Entry cache hits |
|
entrycachetrles |
Entry cache tries |
|
entrycachehitratio |
Entry cache hit ratio |
|
currententrycacheslze |
Current number of entries |
|
maxentrycachesize |
Maximum number of entries |
|
dbchehlts |
Hits |
|
dbcachetrles |
Tries |
|
dbcachehitratio |
Hit ratio |
|
dbcachepageln |
Pages read in |
|
dbcachepageout |
Pages written out |
|
dbcacheroevlct |
Read-only page evicts |
|
dbcacherwevlct |
Read-write page evicts |
|
dbfilecachehit |
Cache hits |
|
dbfilecachemiss |
Cache misses |
|
dbfilepagein |
Pages read in |
|
dbfllepageout |
Pages written out |
Post a comment