5/1/2023 0 Comments Xversion hot momIf you find the error in the WEBVIEW-HOME/logs/IntroscopeWebview.log: Open the Introscope_Enterprise_Manager.lax,, update lax.nl. property If you find the OutOfmemory exception in the EM-HOME/logs/IntroscopeEnterpriseManager.log: These are hot properties, there is no need to restart the Introscope EM.Ĭ) Check each of the "Best practices" covered in the next section If this was the case, restore the values. You can find out this by reviewing the EM_HOME/logs/perflog.txt ( and columns) from MOM and collectors.ī) Check if any of the below clamps in the EM_HOME/config/apm-events-thresholds-config.xml has recently been increased: Timeslice data is being aggregated into longer periods."įind out if the messages are due to a recent change in the MOM and Collectors to accommodate the loadĪ) Check if the number of agents and/or live metrics has increased "Outgoing message queue is moving slowly" NOTE: Default Trace DB home location is /traces, if you are unsure open the config/IntroscopeEnterpriseManager.properties, check the .dir propertyĥ. Start the EM - this process will re-index the db, however, if the traces db is corrupted you need to start the EM with a new traces db as below This message indicates that the Trace database or index is corrupted "Uncaught Exception in Enterprise Manager: In thread Lucene Merge Thread #1 and the message is .MergePolicy$MergeException: java.io.IOException" Increase HD space as soon as possible to prevent a database (smartstor, traces, heuristic) corruption. Java.io.IOException: No space left on device You can increase the current setting as below for example: Make sure the maximum number of open files is at least 4096 in both MOM and Collectors, you can check the current setting by using "ulimit -a" "java.io.IOException: Too many open files" These important adjustments are required when, sending messages, usually between collectors and MOM, becomes a bottle neck for performance. Increasing the thread pool size allows you to have more worker threads to send outgoing messages. NOTE: Increasing the outgoing message queue allows you to have a bigger buffer. =10Ī restart of the EMs is required for the changes to take effect. Add the below 2 properties in all the EMs (MOM and collectors) If it is already 8000, increase the value by 2000, adjust the value as required Set transport.outgoingMessageQueueSize=8000 Open the the EM-HOME/config/IntroscopeEnterpriseManager.properties "Timed out adding to outgoing message queue. Recommendation: increase .limit (default value 50000) "The Agent is exceeding the per-agent metric clamp " "Reporting Clamp hit for MaxAgentConnections limit to MOM" "Collector reported Clamp hit for MaxAgentConnections limit." "The EM has too many live metrics reporting from Agents and will stop accepting new metrics from Agents." Make sure to apply the change in all the EMs (MOM and collector) Increase .limit (default value in 10.7SP3 is 30000000)ĮM_HOME/config/apm-events-thresholds-config.xml "The EM has too many historical metrics reporting from Agents and will stop accepting new metrics from Agents. Source: EM-HOME/log/IntroscopeEnterpriseManager.log If you notice a performance degradation after applying any of the below recommendations, for example, MOM-Collector disconnections, OutOfMemory issues, unable to connect to the workstation, empty dashboards, etc, undo the changes and contact Broadcom Support Team for advice.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |