@PublicAPI(stability=PRIVATE)

Package org.opends.server.monitors

Contains various Directory Server monitor provider implementations.

See:
          Description

Class Summary
BackendMonitor This class implements a monitor provider that will report generic information for an enabled Directory Server backend, including its backend ID, base DNs, writability mode, and the number of entries it contains.
ClientConnectionMonitorProvider This class defines a Directory Server monitor provider that can be used to obtain information about the client connections established to the server.
ConnectionHandlerMonitor This class implements a monitor provider that will report generic information for an enabled Directory Server connection handler, including its protocol, listeners, and established connections.
DatabaseEnvironmentMonitor A monitor provider for a Berkeley DB JE environment.
EntryCacheMonitorProvider This class defines a Directory Server monitor provider that can be used to obtain information about the entry cache state.
MemoryUsageMonitorProvider This class defines a monitor provider that reports information about Directory Server memory usage.
StackTraceMonitorProvider This class defines a Directory Server monitor provider that can be used to obtain a stack trace from all server threads that are currently defined in the JVM.
SystemInfoMonitorProvider This class defines a Directory Server monitor provider that can be used to collect information about the system and the JVM on which the Directory Server is running.
TraditionalWorkQueueMonitor This class defines a Directory Server monitor that can be used to provide information about the state of the work queue.
VersionMonitorProvider This class defines a monitor provider that reports Directory Server version information.
 

Package org.opends.server.monitors Description

Contains various Directory Server monitor provider implementations. Monitor providers may be used to collect and report information about the state of various components of the Directory Server. The primary uses for this information are diagnostic (for helping to identify potential problems within the server) and statistical (for tracking information about the volume and rate of processing that the server performs).