We found lot of errors mentioned below. Queue Capacity seems be getting breached after metaspace limit is breached up. however need debug logs during the problematic time period to detect this, restart resolves the issue temporarily.  PRODCUSTOMXYZ01==> [AD Thread-Metric Reporter0] 24 Jul 2024 18:51:06,818 DEBUG ManagedMonitorDelegate - Adding metric to the Queue to publish [Custom Metrics|Log Monitor|InfraDB_Logs|Search String|ORA-0.1502|Occurrences] PRODCUSTOMXYZ01==> [extension-scheduler-pool-1] 24 Jul 2024 18:50:46,365 DEBUG SimMetricsService - Not reporting metric with name Hardware Resources|Process|ora_p00i_XYZApp|Faults|Minor Faults/sec, its value is unknown. ... View more

Facing the same error with Machine agent 23.6. Server Insight is already enabled at Machine agent end. ... View more

This issue was resolved by increasing the MetaSpace value to 256MB instead of default value 64MB. ... View more

I am facing the same error with Log Extension: Error MonitorExecutorServiceModule-Log Monitor - Queue Capacity reached!! Rejecting runnable tasks. Error StreamReaderRunnable - Error reading stream Error: Error response from Controller: Connection back off in effect. Any advise to find the root cause. Post restart queue data comes until queue fills back again. Max Heap Memory: 1 GB, Max Metric Limit: 7000. Number of threads: 80 Any Advise to resolve these errors? ... View more