Monitor Search

Edit online

Monitor search does not actively query for status but it simply reports the current status that is available to the proxy server. If a back-end server is down and the proxy server has not discovered it yet then it will not be reported in the search result.

Administrators can use monitor search to determine the current status of the proxy server. A monitor search for cn=partitions, cn=proxy, cn=monitor returns one entry for each split point, partition, and server in each partition.
Note:
  • On a proxy server the cn=monitor search displays operations as completed before they are really completed. If operation counts are needed to detect actual completed operations, the cn=proxy,cn=monitor search must be used.
  • In a proxy server environment a single request from a client can map to multiple different kinds of requests in the proxy environment. For example, a bind maps to a compare, search, and a series of extended operations to evaluate group membership.

An example of monitor search for the searchbase cn=partitions, cn=proxy, cn=monitor is given below:

idsldapsearch -D <adminDN> -w <adminpw> -h <servername> -p <portnumber>
–b cn=partitions,cn=proxy,cn=monitor -s base objectclass=*

This command returns the following information:

Split Point Entry:
ibm-slapdProxySplitName= <configured name>, cn=partitions, cn=proxy, cn=monitor
ibm-slapdProxyPartitionBase= <configured base>
ibm-slapdProxyHighConsistencyEnabled = <true|false>
ibm-slapdProxyCurrentTier = <tier number> the current tier that the proxy 
server uses to process operations.

Partition Entry:
ibm-slapdProxyPartitionIndex= <index value>,ibm-slapdProxySplitName= <configured name>, 
cn=partitions,cn=proxy, cn=monitor
ibm-slapdProxyPartitionStatus : (active, readonly, unavailable)
ibm-slapdProxyPartitionIndex= <index value>

Server Entry:
ibm-slapdPort= <port> + ibm-slapdProxyBackendServerName= <server URL>,
ibm-slapdProxyPartitionIndex= <index value> ibm-slapdProxySplitName= <configured name>, 
cn=partitions, cn=proxy, cn=monitor 
ibm-slapdServerStatus: (active, unavailable)
ibm-slapdProxyCurrentServerRole: (primarywriteserver, readonlyserver, writeserver, notactive)
ibm-slapdProxyConfiguredRole: (primarywriteserver, readonlyserver, writeserver)
ibm-slapdProxyNumberofActiveConnections: <connection count>
where
  • ibm-slapdProxyPartitionStatus:
    • active: If atleast one write server is active.
    • readonly: If no write servers are active, but atleast one read server is active.
    • unavailable: No servers are active in the partition.
  • ibm-slapdServerStatus:
    • active: The server is up and the proxy server has established connections to the server.
    • unavailable: The server is either started in configuration mode, or the proxy server is unable to establish a connection to the server with the proper authority.
  • ibm-slapdProxyCurrentRole:
    • primarywriteserver: The server is active and receiving all the write requests. If high consistency is enabled the server is also receiving all the read requests.
    • readonlyserver: The server is active and available for read only requests. The server will only be used if high consistency is disabled, or all the write servers are down.
    • writeserver The server is active and available. If high consistency is enabled, this server will not be used until failover. If high consistency is disabled, this server will be used as a read server until a failover situation.
    • notactive: This means that the server is currently not being used in this partition. This can mean one of two things: the server is unreachable, or the server is up, but has not been restored in this partition.
  • ibm-slapdProxyConfiguredRole: This is the role that the server was configured. If no roles were specifically configured this value is set based on the proxy server's own discovery algorithm at start up.
  • ibm-slapdProxyNumberofActiveConnections: This is the actual number of connections that are open to the backend server.
Note: If the connection is secure, ibm-slapdSecurePort attribute will be used instead of ibm-slapdPort.
A monitor search for cn=proxy,cn=monitor will provide counters for each kind of operation requested and completed by the proxy back-end. The filter supported by this search is objectclass=*. The counters related to all the back-end servers configured in the proxy server is given as an output of the monitor search. Following counters are returned by the proxy backend monitor search:
  • ops_requested – The number of operations requested by the Proxy Backend.
  • ops_completed - The number of operations completed by the Proxy Backend.
  • search_requested - The number of search operations requested by the Proxy Backend.
  • search_completed - The number of search operations completed by the Proxy Backend.
  • binds_requested - The number of bind operations requested by the Proxy Backend.
  • binds_completed - The number of bind operations completed by the Proxy Backend.
  • unbinds_requested - The number of unbind operations requested by the Proxy Backend.
  • unbinds_completed - The number of unbind operations completed by the Proxy Backend.
  • adds_requested - The number of add operations requested by the Proxy Backend.
  • adds_completed - The number of add operations completed by the Proxy Backend.
  • deletes_requested - The number of delete operations requested by the Proxy Backend.
  • deletes_completed - The number of delete operations completed by the Proxy Backend.
  • modrdns_requested - The number of modrdn operations requested by the Proxy Backend.
  • modrdns_completed - The number of modrdn operations completed by the Proxy Backend.
  • modifies_requested - The number of modify operations requested by the Proxy Backend.
  • modifies_completed - The number of modify operations completed by the Proxy Backend.
  • compares_requested - The number of compare operations requested by the Proxy Backend.
  • compares_completed - The number of compare operations completed by the Proxy Backend.
  • abandons_requested - The number of abandons operations requested by the Proxy Backend.
  • abandons_completed - The number of abandons operations completed by the Proxy Backend.
  • extops_requested - The number of extended operations requested by the Proxy Backend.
  • extops_completed - The number of extended operations completed by the Proxy Backend.
  • unknownops_requested - The number of unknown operations requested by the Proxy Backend.
  • unknownops_completed - The number of unknown operations completed by the Proxy Backend.
  • total_connections - The number of connections between the proxy backend and backend servers configuredfor the proxy server.
  • total_ssl_connections - The number of ssl connections between the proxy backend and backend servers configured for the proxy server.
  • used_connections - The number of used connections between the proxy backend and backend servers configuredfor the proxy server.
  • used_ssl_connections - The number of used ssl connections between the proxy backend and backend servers configuredfor the proxy server.
  • total_result_sent – The number of results sent by the proxy backend to the client since the proxy server was started.
  • total_entries_sent - The number of entries sent by the proxy backend to the client since the proxy server was started.
  • total_success_result_sent - The number of success results sent by the proxy backend to the client since the proxy server was started.
  • total_failed_result_sent - The number of failed results sent by the proxy backend to the client since the proxy server was started.
  • total_references_sent - The number of references sent by the proxy backend to the client since the proxy server was started (related to referrals).
  • transactions_requested - The number of transaction operations requested by the Proxy Backend.
  • transactions_completed - The number of transaction operations completed by the Proxy Backend.
  • transaction_prepare_requested - The number of prepare transaction operations requested by the Proxy Backend.
  • transaction_prepare_completed - The number of prepare transaction operations completed by the Proxy Backend.
  • transaction_commit_requested - The number of commit transaction operations requested by the Proxy Backend.
  • transaction_commited - The number of commit transaction operations completed by the Proxy Backend.
  • transaction_rollback_requested - The number of rollback transaction operations requested by the Proxy Backend.
  • transaction_rollbacked - The number of rollback transaction operations completed by the Proxy Backend.