cn=monitor entry. Various tools can be used to surface the
server’s information including the PingDataMetrics Server, the Administrative Console,
JConsole, LDAP command-line tools, or SNMP. The following information is collected for
PingDataSync. To configure the PingData
PingDataMetrics Server to display PingDataSync
data, see the Ping Identity PingDataMetrics Server Administration Guide.
|Provides information about the operations currently being processed by the server including the number of operations, information about the operation, and the number of active persistent searches.
|Provides general information about the state of the server
backend, including the backend ID, base DN(s), entry counts, entry
count for the
cn=admin data, writability mode, and
whether it is a private backend. The following backend monitors are
|Berkeley DB JE Environment
|Provides information about the state of the Oracle Berkeley DB Java Edition database used by the PingDataSync backend.
|Provides information about all client connections to the server.
|Disk Space Usage
|Provides information about the disk space available to various
components of the server. The disk space usage monitor evaluates the
free space at locations registered through the
DiskSpaceConsumer interface. Disk space
monitoring excludes disk locations that do not have server
components registered. However, other disk locations may still
impact server performance, such as the operating system disk, if it
becomes full. When relevant to the server, these locations include
the server root, the location of the
directory, the location of every log file, all JE backend
directories, the location of the changelog, the location of the
replication environment database, and the location of any server
extension that registers itself with the
|Provides information about the available connection handlers on the server, which include the LDAP and LDIF connection handlers. These handlers are used to accept client connections.
|Provides general information about the server, including product name and server version.
|JVM Stack Trace
|Provides a stack trace of all threads processing within the JVM.
|LDAP Connection Handler Statistics
|Provides statistics about the interaction that the associated LDAP connection handler has had with its clients, including the number of connections established and closed, bytes read and written, LDAP messages, and operations handled.
|Processing Time Histogram
|Categorizes operation processing times into a number of
user-defined buckets of information, including the total number of
operations processed, overall average response time, and number of
processing times between
|Provides general information about the system and the JVM on which the server is running, including host name, operating system, JVM architecture, Java home, and Java version.
|Provides information about the product version, including build ID and revision number.
|Provides information about the state of the PingDataSync work queue, which holds
requests until they can be processed by a worker thread. The work
queue configuration has a
property set to
true by default. This logs
messages for new operations with a
included in the log messages. Its value is expressed in milliseconds
and represents the length of time that operations are held in the
A dedicated thread pool can be used for processing
administrative operations. This thread pool enables diagnosis
and corrective action if all other worker threads are processing
operations. To request that operations be processed using the
administrative thread pool, the requester must have the