The following sections describe the components and the data that can be monitored:
Jobs are administrative functions that can be scheduled for processing at some future date or on a recurring basis. You can monitor the configuration details of jobs at driver set and driver level such as job CN, status of a job, and when a job is scheduled to run.
To view information about the jobs configured in OpenText Identity Manager, perform a search on the following entry:
cn=job_stats,cn=idm,cn=monitor
To view information about all jobs configured at a driver set level, perform a search on the following entries:
cn=driverset,cn=job_stats,cn=idm,cn=monitor
To view information about a specific job configured at a driver set level, perform a search on the following entry:
cn=<Name of the job>,cn=driverset,cn=job_stats,cn=idm,cn=monitor
For example, cn=StatisticsJob,cn=driverset,cn=job_stats,cn=idm,cn=monitor
To view information about jobs configured for all drivers in a driver set, perform a search on the following entry:
cn=drivers,cn=job_stats,cn=idm,cn=monitor
To view information about jobs configured for a driver, perform a search on the following entry:
cn=<Name of the driver>,cn=drivers,cn=job_stats,cn=idm,cn=monitor
To view information about a specific job configured for a driver, perform a search on the following entry:
cn=<CN of the job>,cn=<CN of the driver>,cn=drivers,cn=job_stats,cn=idm,cn=monitor
A sample LDAP search output is below. The search displays nextScheduledRun timestamp in the epoch format.
dn: cn=StatisticsJob,cn=DriverSet,cn=JOB_STATS,cn=IDM,cn=Monitor nextScheduledRun:1485631800 configuration: enabled status: stopped containment: DirXML-DriverSet JobDN: CN=StatisticsJob,CN=driverset1,O=system objectclass: Top objectclass: extensibleObject dn: cn=PermissionOnboarding,cn=Active Directory Driver,cn=drivers,cn=JOB_STATS,cn=IDM,cn=Monitor nextScheduledRun: 0 configuration: enabled status: stopped containment: DirXML-Driver JobDN: CN=PermissionOnboarding,CN=Active Directory Driver,CN=driverset1,O=system objectclass: Top objectclass: extensibleObject
In this example, nextScheduledRun: 0 means that the job is not scheduled to run.
You can monitor the current state of the JVM such as memory, thread, runtime, class loader, and garbage collection. This information helps you debug or troubleshoot Java issues such as threading, classpath, and memory buildup. To view this information, perform a search operation on the following entry:
cn=jvm_stats,cn=idm,cn=monitor
You can view your operating system’s information such as name, version, architecture, processors, and the load it can take. To monitor this information, perform a search operation on the following entry:
cn=operating_system_stats,cn=jvm_stats,cn=idm,cn=monitor
For information about the current memory allocation of the JVM, perform a search operation on the following entry:
cn=memory_stats,cn=jvm_stats,cn=idm,cn=monitor
To view the class loader of the JVM, perform a search operation on the following entry:
cn=classloader_stats,cn=jvm_stats,cn=idm,cn=monitor
For information about garbage collection of the JVM, perform a search operation on the following entry:
cn=garbage_collection_stats,cn=jvm_stats,cn=idm,cn=monitor
For information about thread statistics of the JVM, perform a search operation on the following entry:
cn=thread_stats,cn=jvm_stats,cn=idm,cn=monitor
For information about runtime statistics of the JVM, perform a search operation on the following entry:
cn=runtime_stats,cn=jvm_stats,cn=idm,cn=monitor
NOTE:For certain objects, OpenText Identity Manager restricts the search only to the parent object. For example, thread_stats object has only one child node as thread_info. Searching under thread_info is restricted. This implies that you should not construct a search string such as cn=thread_info,cn=thread_stats,cn=jvm_stats,cn=idm,cn=monitor, which will not return you the expected result. Similarly, the runtime_stats object contains system_properties. It does not allow you to separately search for system_properties. To monitor these details, you must search for runtime_stats.
A sample LDAP search output is below.
dn: cn=classloader_stats,cn=jvm_stats,cn=idm,cn=monitor total_loaded_class_count: 2393 unloaded_class_count: 0 loaded_class_count: 2393 objectclass: Top objectclass: extensibleObject dn: cn=Copy,cn=collectors,cn=garbage_collection_stats,cn=jvm_stats,cn=idm,cn=monitor collection_time: 54 ms collection_count: 4 objectclass: Top objectclass: extensibleObject dn: cn=MarkSweepCompact,cn=collectors,cn=garbage_collection_stats,cn=jvm_stats,cn=IDM,cn=Monitor collection_time: 0 ms collection_count: 0 objectclass: Top objectclass: extensibleObject dn: cn=heap,cn=memory_stats,cn=jvm_stats,cn=idm,cn=monitor total: 494.94 MB used: 16.188 MB comitted: 123.75 MB initial: 128.00 MB objectclass: Top objectclass: extensibleObject dn: cn=non_heap,cn=memory_stats,cn=jvm_stats,cn=idm,cn=monitor total: -1.0000 Bytes used: 22.064 MB comitted: 22.688 MB initial: 2496.0 KB objectclass: Top objectclass: extensibleObject dn: cn=operating_system_stats,cn=jvm_stats,cn=idm,cn=monitor average_load: 1.0 processors: 1 arch: amd64 version: 3.0.76-0.11-default name: Linux objectclass: Top objectclass: extensibleObject dn: cn=runtime_stats,cn=jvm_stats,cn=idm,cn=monitor uptime: 36 days 4 hours 27 minutes 1 seconds 8 milliseconds start_time: 1478854892218 objectclass: Top objectclass: extensibleObject dn: cn=system_properties,cn=runtime_stats,cn=jvm_stats,cn=idm,cn=monitor sun.boot.class.path: ... ...
You can monitor a driver set’s information such as driver set DN, the number of drivers the driver set holds, the running state of drivers, and how they are configured to run.
cn=driverset_stats,cn=idm,cn=monitor
To monitor information about all the drivers in a driver set, perform a search operation on the following entries:
cn=drivers,cn=driverset_stats,cn=idm,cn=monitor
To monitor the statistics of a specific driver such as driver CN, the state of the driver, driver start option, and if the driver is running or down, perform a search operation on the following entries:
cn=<CN of the driver>,cn=drivers,cn=driverset_stats,cn=idm,cn=monitor
OpenText Identity Manager does not allow you to separately search for ProcessedOperationsCount under a driver. To monitor this attribute, perform a subtree search on the driver.
A sample LDAP search output is below.
dn: cn=driverset_stats,cn=IDM,cn=Monitor Startupoption_auto-start_count: 0 Startupoption_manual_count: 10 Startupoption_disabled_count: 1 shutdownpending: 0 starting: 0 running: 0 stopped: 11 numberofdrivers: 11 driversetdn: CN=driverset1,O=system objectclass: Top objectclass: extensibleObject dn: cn=Active Directory Driver,cn=drivers,cn=driverset_stats,cn=IDM,cn=Monitor startoption: manual type: remote downtime: 6 days 4 hours 27 minutes 2 seconds 9 milliseconds driver-state: stopped driverdn: CN=Active Directory Driver,CN=driverset1,O=system objectclass: Top objectclass: extensibleObject dn: cn=publisher,cn=ProcessedOperationsCount,cn=Active Directory Driver,cn=drivers,cn=driverset_stats,cn=IDM,cn=Monitor check-password: 14 add: 1 query: 70 modify: 98 objectclass: Top objectclass: extensibleObject
Using the monitoring feature you can execute search operations using specific entries to monitor the condition of the JVM and get statistics for elements such as memory usage, thread activity, runtime statistics, class loader status, garbage collection, and operating system. You can use this data for debugging or addressing Java-related issues.
IMPORTANT:To receive the cluster setup JVM statistics for user application, you must add the following property in all the cluster nodes in the ism.configuration.properties file: com.netiq.cluster.internalNodes = {\"nodes\":[{\"ip\":\"<serverIP>\",\"port\":\"<port>\"},{\"ip\":\"<serverIP>\",\"port\":\"<port>\"}]}.
For example, com.netiq.cluster.internalNodes = {\"nodes\":[{\"ip\":\"12.345.678.90\",\"port\":\"8543\"},{\"ip\":\"56.789.123.50\",\"port\":\"8543\"}]}.
You must add the property in the default locations:
Linux: /opt/netiq/idm/apps/tomcat/conf/ism-configuration.properties
Windows: C:\NetIQ\IDM\apps\tomcat\conf\ism-configuration.properties
To view the JVM statistics for user applications, perform a search using the following entry:
cn=jvmstats_info,cn=userapp_stats,cn=idm,cn=monitor
You can monitor information about the health of the User Application such as currently running threads, memory consumption, and cache information. Note that memory_info, thread_info, and cache_info does not provide information for clustered environment.
To view the health statistics of the User Application, perform a search on the following entry:
cn=userapp_stats,cn=idm,cn=monitor
To monitor the system memory and memory consumed by the JVM, perform a search on the following entry:
cn=memory_info,cn=userapp_stats,cn=idm,cn=monitor
NOTE:memory_info contains several child objects such as jvmmemoryusage and jvmmemorypool. However, OpenText Identity Manager restricts the search to the parent object (memory_info)only.
To monitor the threads that cause heavy utilization of the CPU, perform a search with the following entry:
cn=thread_info,cn=userapp_stats,cn=idm,cn=monitor
To view the current number of live threads, perform a search on the following entry:
cn=thread_count,cn=thread_info,cn=userapp_stats,cn=idm,cn=monitor
To view the cache information, perform a search on the following entry:
cn=cache_info,cn=userapp_stats,cn=idm,cn=monitor
A sample output looks like this:
dn:cn=62614,cn=classLoaderStats,cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=u serapp_stats,cn=IDM,cn=Monitor unloadedClassCount: 25 totalLoadedClassCount: 62639 objectclass: Top objectclass: extensibleObject # Node_1, nodesStats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monito r currentTimeStamp: 2024-04-05 07:17:15.054 objectclass: Top objectclass: extensibleObject # G1 Old Generation, garbageCollectorStats, Node_1, nodesStats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=G1 Old Generation,cn=garbageCollectorStats,cn=Node_1,cn=nodesStats,cn=j vmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor collectionTime: 0 collectionCount: 0 objectclass: Top objectclass: extensibleObject # G1 Young Generation, garbageCollectorStats, Node_1, nodesStats, jvmstats_info , userapp_stats, IDM, Monitor dn: cn=G1 Young Generation,cn=garbageCollectorStats,cn=Node_1,cn=nodesStats,cn =jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor collectionTime: 2873 collectionCount: 59 objectclass: Top objectclass: extensibleObject # Node_1, nodesStats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monito r ipAddressAndPort: 10.71.39.111:-1 objectclass: Top objectclass: extensibleObject # memoryStats, Node_1, nodesStats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=memoryStats,cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=userapp_stats,c n=IDM,cn=Monitor commitedVirtualMemory: 1818044 objectclass: Top objectclass: extensibleObject # CodeHeap 'non-nmethods', jvmMemoryPool, memoryStats, Node_1, nodesStats, jvms tats_info, userapp_stats, IDM, Monitor dn: cn=CodeHeap 'non-nmethods',cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=no desStats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 3902 usedMemory: 1794 totalMemory: 5696 objectclass: Top objectclass: extensibleObject # CodeHeap 'non-profiled nmethods', jvmMemoryPool, memoryStats, Node_1, nodesSt ats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=CodeHeap 'non-profiled nmethods',cn=jvmMemoryPool,cn=memoryStats,cn=Nod e_1,cn=nodesStats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 90616 usedMemory: 29448 totalMemory: 120064 objectclass: Top objectclass: extensibleObject # CodeHeap 'profiled nmethods', jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=CodeHeap 'profiled nmethods',cn=jvmMemoryPool,cn=memoryStats,cn=Node_1, cn=nodesStats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 35801 usedMemory: 84199 totalMemory: 120000 objectclass: Top objectclass: extensibleObject # Compressed Class Space, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmst ats_info, userapp_stats, IDM, Monitor dn: cn=Compressed Class Space,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nod esStats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 1003995 usedMemory: 44581 totalMemory: 1048576 objectclass: Top objectclass: extensibleObject # G1 Eden Space, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=G1 Eden Space,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesStats,c n=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 52224 totalMemory: 0 objectclass: Top objectclass: extensibleObject # G1 Old Gen, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, us erapp_stats, IDM, Monitor dn: cn=G1 Old Gen,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesStats,cn=j vmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 748903 usedMemory: 299673 totalMemory: 1048576 objectclass: Top objectclass: extensibleObject # G1 Survivor Space, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_i nfo, userapp_stats, IDM, Monitor dn: cn=G1 Survivor Space,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesSta ts,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 7168 totalMemory: 0 objectclass: Top objectclass: extensibleObject # Metaspace, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, use rapp_stats, IDM, Monitor dn: cn=Metaspace,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesStats,cn=jv mstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 376517 totalMemory: 0 objectclass: Top objectclass: extensibleObject # HeapMemoryUsage, jvmMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats_in fo, userapp_stats, IDM, Monitor dn: cn=HeapMemoryUsage,cn=jvmMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesStat s,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 689511 usedMemory: 359065 totalMemory: 1048576 objectclass: Top objectclass: extensibleObject # NonHeapMemoryUsage, jvmMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats _info, userapp_stats, IDM, Monitor dn: cn=NonHeapMemoryUsage,cn=jvmMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesS tats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 536541 totalMemory: 0 objectclass: Top objectclass: extensibleObject # physicalMemory, systemMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats_ info, userapp_stats, IDM, Monitor dn: cn=physicalMemory,cn=systemMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesSt ats,cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 3225320 usedMemory: 5162764 totalMemory: 8388084 objectclass: Top objectclass: extensibleObject # swapMemory, systemMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats_info , userapp_stats, IDM, Monitor dn: cn=swapMemory,cn=systemMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesStats, cn=jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor freeMemory: 3204888 usedMemory: 6493916 totalMemory: 9698804 objectclass: Top objectclass: extensibleObject # Windows Server 2022, operatingSystemStats, Node_1, nodesStats, jvmstats_info, userapp_stats, IDM, Monitor dn: cn=Windows Server 2022,cn=operatingSystemStats,cn=Node_1,cn=nodesStats,cn= jvmstats_info,cn=userapp_stats,cn=IDM,cn=Monitor systemAverageLoad: -1 arch: amd64 processorsCount: 2 version: 10.0 objectclass: Top objectclass: extensibleObject # 20381464, runtimeStats, Node_1, nodesStats, jvmstats_info, userapp_stats, IDM , Monitor dn: cn=20381464,cn=runtimeStats,cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=us erapp_stats,cn=IDM,cn=Monitor startTime: 1712261253 objectclass: Top objectclass: extensibleObject # search result search: 2 result: 0 Success # numResponses: 21 # numEntries: 20
With the monitoring feature, you can monitor the workflows and the condition of the JVM and gather information about various aspects using specific search entries. You can get statistics on JVM’s memory usage, thread activity, runtime details, class loader status, garbage collection, and the operating system. Additionally, you can get information about the overall count of workflows, those in progress, completed, failed, terminated, or requested within the last 10 seconds, 1 minute, and 5 minutes.
To know the workflow statistics, perform a search using the following entry:
cn=workflowstatistics_info,cn=workflow_stats,cn=idm,cn=monitor
The following is a sample workflow statistics search output:
dn: cn=workflowstatistics_info,cn=workflow_stats,cn=IDM,cn=Monitor currentTimeStamp: 2024-04-01 08:09:37.793 newRequestsInLast10Secs: 0 newRequestsInLast1Min: 1 newRequestsInLast5Mins: 1 inProgressWorkflows: 1 terminatedWorkflows: 1 failedWorkflows: 0 completedWorkflowsInLast10Secs: 0 completedWorkflowsInLast1Min: 0 completedWorkflowsInLast5Mins: 1 completedWorkflows: 2 totalWorkflows: 4 objectclass: Top objectclass: extensibleObject # search result search: 2 result: 0 Success # numResponses: 88 # numEntries: 87
IMPORTANT:To receive the cluster setup JVM statistics for workflow, you must add the following property in all the cluster nodes in the ism.configuration.properties file: com.netiq.cluster.internalNodes = {\"nodes\":[{\"ip\":\"<serverIP>\",\"port\":\"<port>\"},{\"ip\":\"<serverIP>\",\"port\":\"<port>\"}]}.
For example, com.netiq.cluster.internalNodes = {\"nodes\":[{\"ip\":\"12.345.678.90\",\"port\":\"8543\"},{\"ip\":\"56.789.123.50\",\"port\":\"8543\"}]}.
You must add the property in the default locations:
Linux: /opt/netiq/idm/apps/tomcat/conf/ism-configuration.properties
Windows: C:\NetIQ\IDM\apps\tomcat\conf\ism-configuration.properties
To know the JVM statistics for workflows, perform a search using the following entry:
cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor
To monitor the system memory and memory consumed by the JVM, perform a search on the following entry. Note that memory_info, thread_info, and cache_info does not provide information for clustered environment.
cn=memory_info,cn=workflow_stats,cn=idm,cn=monitor
NOTE:memory_info contains several child objects such as jvmmemoryusage and jvmmemorypool. However, OpenText Identity Manager restricts the search to the parent object (memory_info)only.
To monitor the threads that cause heavy utilization of the CPU, perform a search with the following entry:
cn=thread_info,cn=workflow_stats,cn=idm,cn=monitor
To view the current number of live threads, perform a search on the following entry:
cn=thread_count,cn=thread_info,cn=userapp_stats,cn=idm,cn=monitor
To view the cache information, perform a search on the following entry:
cn=cache_info,cn=workflow_stats,cn=idm,cn=monitor
The following is a sample JVM statistics search output for workflow:
dn: cn=62618,cn=classLoaderStats,cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=w orkflow_stats,cn=IDM,cn=Monitor unloadedClassCount: 25 totalLoadedClassCount: 62643 objectclass: Top objectclass: extensibleObject # Node_1, nodesStats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monit or currentTimeStamp: 2024-04-05 07:17:56.996 objectclass: Top objectclass: extensibleObject # G1 Old Generation, garbageCollectorStats, Node_1, nodesStats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=G1 Old Generation,cn=garbageCollectorStats,cn=Node_1,cn=nodesStats,cn=j vmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor collectionTime: 0 collectionCount: 0 objectclass: Top objectclass: extensibleObject # G1 Young Generation, garbageCollectorStats, Node_1, nodesStats, jvmstats_info , workflow_stats, IDM, Monitor dn: cn=G1 Young Generation,cn=garbageCollectorStats,cn=Node_1,cn=nodesStats,cn =jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor collectionTime: 2873 collectionCount: 59 objectclass: Top objectclass: extensibleObject # Node_1, nodesStats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monit or ipAddressAndPort: 10.71.39.111:-1 objectclass: Top objectclass: extensibleObject # memoryStats, Node_1, nodesStats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=memoryStats,cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=workflow_stats, cn=IDM,cn=Monitor commitedVirtualMemory: 1818264 objectclass: Top objectclass: extensibleObject # CodeHeap 'non-nmethods', jvmMemoryPool, memoryStats, Node_1, nodesStats, jvms tats_info, workflow_stats, IDM, Monitor dn: cn=CodeHeap 'non-nmethods',cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=no desStats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 3902 usedMemory: 1794 totalMemory: 5696 objectclass: Top objectclass: extensibleObject # CodeHeap 'non-profiled nmethods', jvmMemoryPool, memoryStats, Node_1, nodesSt ats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=CodeHeap 'non-profiled nmethods',cn=jvmMemoryPool,cn=memoryStats,cn=Nod e_1,cn=nodesStats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 90602 usedMemory: 29462 totalMemory: 120064 objectclass: Top objectclass: extensibleObject # CodeHeap 'profiled nmethods', jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=CodeHeap 'profiled nmethods',cn=jvmMemoryPool,cn=memoryStats,cn=Node_1, cn=nodesStats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 35753 usedMemory: 84247 totalMemory: 120000 objectclass: Top objectclass: extensibleObject # Compressed Class Space, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmst ats_info, workflow_stats, IDM, Monitor dn: cn=Compressed Class Space,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nod esStats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 1003993 usedMemory: 44583 totalMemory: 1048576 objectclass: Top objectclass: extensibleObject # G1 Eden Space, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=G1 Eden Space,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesStats,c n=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 70656 totalMemory: 0 objectclass: Top objectclass: extensibleObject # G1 Old Gen, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, wo rkflow_stats, IDM, Monitor dn: cn=G1 Old Gen,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesStats,cn=j vmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 747879 usedMemory: 300697 totalMemory: 1048576 objectclass: Top objectclass: extensibleObject # G1 Survivor Space, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_i nfo, workflow_stats, IDM, Monitor dn: cn=G1 Survivor Space,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesSta ts,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 7168 totalMemory: 0 objectclass: Top objectclass: extensibleObject # Metaspace, jvmMemoryPool, memoryStats, Node_1, nodesStats, jvmstats_info, wor kflow_stats, IDM, Monitor dn: cn=Metaspace,cn=jvmMemoryPool,cn=memoryStats,cn=Node_1,cn=nodesStats,cn=jv mstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 376564 totalMemory: 0 objectclass: Top objectclass: extensibleObject # HeapMemoryUsage, jvmMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats_in fo, workflow_stats, IDM, Monitor dn: cn=HeapMemoryUsage,cn=jvmMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesStat s,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 670055 usedMemory: 378521 totalMemory: 1048576 objectclass: Top objectclass: extensibleObject # NonHeapMemoryUsage, jvmMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats _info, workflow_stats, IDM, Monitor dn: cn=NonHeapMemoryUsage,cn=jvmMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesS tats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 0 usedMemory: 536652 totalMemory: 0 objectclass: Top objectclass: extensibleObject # physicalMemory, systemMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats_ info, workflow_stats, IDM, Monitor dn: cn=physicalMemory,cn=systemMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesSt ats,cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 3225340 usedMemory: 5162744 totalMemory: 8388084 objectclass: Top objectclass: extensibleObject # swapMemory, systemMemoryUsage, memoryStats, Node_1, nodesStats, jvmstats_info , workflow_stats, IDM, Monitor dn: cn=swapMemory,cn=systemMemoryUsage,cn=memoryStats,cn=Node_1,cn=nodesStats, cn=jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor freeMemory: 3203372 usedMemory: 6495432 totalMemory: 9698804 objectclass: Top objectclass: extensibleObject # Windows Server 2022, operatingSystemStats, Node_1, nodesStats, jvmstats_info, workflow_stats, IDM, Monitor dn: cn=Windows Server 2022,cn=operatingSystemStats,cn=Node_1,cn=nodesStats,cn= jvmstats_info,cn=workflow_stats,cn=IDM,cn=Monitor systemAverageLoad: -1 arch: amd64 processorsCount: 2 version: 10.0 objectclass: Top objectclass: extensibleObject # 20423407, runtimeStats, Node_1, nodesStats, jvmstats_info, workflow_stats, ID M, Monitor dn: cn=20423407,cn=runtimeStats,cn=Node_1,cn=nodesStats,cn=jvmstats_info,cn=wo rkflow_stats,cn=IDM,cn=Monitor startTime: 1712261253 objectclass: Top objectclass: extensibleObject # search result search: 2 result: 0 Success # numResponses: 21 # numEntries: 20