Is there any available documentation explaining the meanings (what is monitored) of every item under cn=Monitor.
In particular, I'm not sure about the exact meaning of: * cn=Log,cn=Monitor * cn=Bytes,cn=Statistics,cn=Monitor (sent Bytes since started?) * cn=PDU,cn=Statistics,cn=Monitor (don't know what PDU means) * cn=Entries,cn=Statistics,cn=Monitor (in my system it shows very high, maybe because of my cn=accesslog and cn=config contexts. It's planned to have Entries per context basis?) * cn=Backload,cn=Threads,cn=Monitor * cn=Runqueue,cn=Threads,cn=Monitor (monitoredInfo always have value (), what are possible values for this attribute) * cn=Read,cn=Waiters,cn=Monitor (in my system it shows 15, did it mean that there was 15 threads waiting to query the DIT? if so, it's strange for me give that this system is only for testing with 2 o 3 clients and such a number of read waiters are very improbable)
Had the OL developers considered adding a description attribute to *,cn=Monitor entries?
Regards, maykel
Maykel Moya wrote:
Is there any available documentation explaining the meanings (what is monitored) of every item under cn=Monitor.
See the Draft Admin Guide which is a work in progress:
http://www.openldap.org/devel/admin/monitoringslapd.html
In particular, I'm not sure about the exact meaning of:
- cn=Log,cn=Monitor
- cn=Bytes,cn=Statistics,cn=Monitor (sent Bytes since started?)
- cn=PDU,cn=Statistics,cn=Monitor (don't know what PDU means)
- cn=Entries,cn=Statistics,cn=Monitor (in my system it shows very high, maybe because of my cn=accesslog and cn=config contexts. It's planned to have Entries per context basis?)
- cn=Backload,cn=Threads,cn=Monitor
- cn=Runqueue,cn=Threads,cn=Monitor (monitoredInfo always have value (), what are possible values for this attribute)
- cn=Read,cn=Waiters,cn=Monitor (in my system it shows 15, did it mean that there was 15 threads waiting to query the DIT? if so, it's strange for me give that this system is only for testing with 2 o 3 clients and such a number of read waiters are very improbable)
Had the OL developers considered adding a description attribute to *,cn=Monitor entries?
Not sure if we have.
Gavin Henry wrote:
Maykel Moya wrote:
Is there any available documentation explaining the meanings (what is monitored) of every item under cn=Monitor.
See the Draft Admin Guide which is a work in progress:
http://www.openldap.org/devel/admin/monitoringslapd.html
In particular, I'm not sure about the exact meaning of:
- cn=Log,cn=Monitor
- cn=Bytes,cn=Statistics,cn=Monitor (sent Bytes since started?)
- cn=PDU,cn=Statistics,cn=Monitor (don't know what PDU means)
Protocol Data Unit. This is a standard term in networking, and should not need further explanation. If you're unfamiliar with it then you need to do more reading.
- cn=Entries,cn=Statistics,cn=Monitor (in my system it shows very high, maybe because of my cn=accesslog and cn=config contexts. It's planned to have Entries per context basis?)
- cn=Backload,cn=Threads,cn=Monitor
- cn=Runqueue,cn=Threads,cn=Monitor (monitoredInfo always have value (), what are possible values for this attribute)
- cn=Read,cn=Waiters,cn=Monitor (in my system it shows 15, did it mean that there was 15 threads waiting to query the DIT? if so, it's strange for me give that this system is only for testing with 2 o 3 clients and such a number of read waiters are very improbable)
Had the OL developers considered adding a description attribute to *,cn=Monitor entries?
The design and contents of cn=monitor is still undergoing change. It's far too early to be worrying about making it user friendly. First we have to actually make it meet our (developer's) minimum needs.
Howard Chu wrote:
Had the OL developers considered adding a description attribute to *,cn=Monitor entries?
In many cases, yes. As you may notice yourself by running a search for "(description=*)" under "cn=Monitor".
The design and contents of cn=monitor is still undergoing change. It's far too early to be worrying about making it user friendly. First we have to actually make it meet our (developer's) minimum needs.
I concur with the above, although I notice that in many cases the layout of the monitor database didn't change for long time. So any attempt to document it (like Gavin's) would be welcome, provided the document itself is considered a work in progress. If you have useful suggestions ("improve the documents" is too broad to be useful), please feel free to jump in; I suggest that you first discuss the topic on the mailing list, and then, as soon as you get to some clearly defined feature request, I recommend you use the ITS http://www.openldap.org/its/ and gather all your suggestions in self-consistent groups before you submit them to the ITS. Separate ITSes for separate features are preferred because they ease tracking.
I believe monitoring is the typical topic that **needs** user feedback, since it is meant to provide information that is primarily useful to the end users. Keep in mind that in our view, monitoring information is mainly meant to be machine-readable, with human-readability as a second choice. For this reason, too pedantic descriptions should definitely be avoided. What the description attribute should hold is sort of a note that a GUI could use to self-document the piece of information it is presenting.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
openldap-software@openldap.org
-
Gavin Henry -
Howard Chu -
Maykel Moya -
Pierangelo Masarati