References > Template Reference > Lotus > Lotus Domino Server Statistics

Lotus Domino Server Statistics

This template assesses the overall performance of a Lotus Domino Server by using the SNMP protocol.

Prerequisites

SNMP enabled on the operating system. SNMP adapter enabled on Lotus Domino.

Credentials

None. The SNMP public string assigned to the node is used.

To enable the SNMP adapter on Lotus Domino, navigate here: http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.help.domino.admin.doc%2FDOC%2FH_COMPLETING_SNMP_CONFIGURATION.html.

Monitored Components

For details on monitors, see SAM Component Monitor Types.

Some components may not have preset warning or critical threshold values. You can add your own threshold limits as necessary.

Available Resources (%)

This monitor returns the current percentage index of a server's availability.  The value range is 0-100.  Zero (0) indicates no available resources. A value of 100 indicates that the server is completely available.

OID: 1.3.6.1.4.1.334.72.1.1.6.3.19.0

Open User Sessions

This monitor returns the number of users with sessions open on the server.

OID: 1.3.6.1.4.1.334.72.1.1.6.3.6.0

Peak Open User Sessions

This monitor returns the peak number of concurrent users with open sessions since the server was started.

OID: 1.3.6.1.4.1.334.72.1.1.6.3.11.0

Dropped Session Count

This monitor returns the number of dropped sessions.

OID: 1.3.6.1.4.1.334.72.1.1.6.3.1.0

DB Cache Rejection Count

This monitor returns the number of times a database is not placed into the cache when it is closed because lnDBCacheCurrentEntries equals or exceeds lnDBCacheMaxEntries*1.5.  This number should stay low. If this number begins to rise, you should increase the NSF_DbCache_Maxentries settings.

OID: 1.3.6.1.4.1.334.72.1.1.10.21.0

LDAP Tasks Running

This monitor returns the number of LDAP server tasks currently running.

OID: 1.3.6.1.4.1.334.72.1.1.21.10.0

Peak Transactions per Minute

This monitor returns the peak number of transactions that took place in any given minute since the server was started.

OID: 1.3.6.1.4.1.334.72.1.1.6.3.3.0

Max Mail Delivery Time (sec)

This monitor returns the maximum time for mail delivery in seconds.

OID: 1.3.6.1.4.1.334.72.1.1.4.12.0

Note: If the counter returns with the error “No such name,” you should send a test email. The counter should be accessible at this point.

Pending Mail Messages

This monitor returns the number of mail messages pending.

OID: 1.3.6.1.4.1.334.72.1.1.4.31.0

Note: If the counter returns with the error “No such name,” you should send a test email. The counter should be accessible at this point.

Server Transactions per Minute

This monitor returns the average number of transactions per minute since the server was started.

OID: 1.3.6.1.4.1.334.72.1.1.6.3.2.0

Number of Undeliverable Messages

This monitor returns the number of dead (undeliverable) mail messages.

OID: 1.3.6.1.4.1.334.72.1.1.4.1.0

Total Mail Failures

This monitor returns the total number of routing failures since the server started.

OID: 1.3.6.1.4.1.334.72.1.1.4.3.0

Note: If the counter returns with the error “No such name,” you should send a test email. The counter should be accessible at this point.

Number of Waiting Messages

This monitor returns the number of mail messages waiting to be routed.

OID: 1.3.6.1.4.1.334.72.1.1.4.6.0

Number of Messages on Hold

This monitor returns the number of mail messages in message queue on hold.

OID: 1.3.6.1.4.1.334.72.1.1.4.21.0

Database Cache Hit

This monitor returns the number of times an lnDBCacheInitialDbOpen is satisfied by finding a database in the cache. A high “hits-to-opens” ratio indicates the database cache is working effectively, since most users are opening databases in the cache without having to wait for the usual time required by an initial (non-cache) open. If the ratio is low, the administrator can increase the NSF_DBCACHE_MAXENTRIES settings.

OID: 1.3.6.1.4.1.334.72.1.1.10.17.0

Database Initial Opens

This monitor returns the number of times a user/server opened a database that was not already being used by another user/server. By comparing this number to lnDBCacheHits, administrators can gauge the effectiveness of the cache.

OID: 1.3.6.1.4.1.334.72.1.1.10.18.0

Access Denial of Agent Manager

This monitor returns the number of times the agent manager failed to execute a given task, probably due to ACL restrictions.

OID: 1.3.6.1.4.1.334.72.1.1.11.1.0

If the counter returns with the error “No such name,” you should send a test email. The counter should be accessible at this point.

Unsuccessful Runs of Agent Manager

This monitor returns the number of tasks the agent manager has unsuccessfully run during the course of the day.

OID: 1.3.6.1.4.1.334.72.1.1.11.4.0

If the counter returns with the error “No such name,” you should send a test email. The counter should be accessible at this point.