Monitoring Performance Tool for Manager Health

Overview

This article explains how to use the JetPatch built-in performance monitoring tool (Java Melody) to assess manager health. 

It covers how to read key performance graphs, what data to share with JetPatch support, how to configure a custom Java heap dump location, and how to access system information.

JetPatch uses Java Melody, a third-party monitoring library, to provide health graphs of key performance indicators, including CPU and RAM.

Accessing the Performance Monitoring Tool

• Log in to JetPatch.
• Navigate to: <SERVER-URL>/vmanage-server/monitoring
• Select Week or Month to review performance and monitoring statistics:

• Check Used Memory: Memory allocation should follow a "chainsaw" pattern - memory increases and decreases on a regular cycle. This is expected Java RAM behavior.

  

• Check the CPU % graph. Overall, the CPU should not be constantly above 70%.

• Check the Active Threads graph. 
• The thread count should show regular increases and decreases. 
• Expected range: 40–160.

• Check the Active JDBC Connections graph. 

• The graph should not be constantly trending up without connection deallocations. Expected range: 20–50.

  

What to Share as PDF with JetPatch Support

1. Monitoring PDF: /vmanage-server/monitoring?period=jour
2. Monitoring PDF: /vmanage-server/monitoring?part=processes
3. Monitoring PDF: /vmanage-server/monitoring?part=graph&graph=usedSwapSpaceSize
4. Monitoring PDF: /vmanage-server/monitoring?part=database&request=5
5. Browser Network Statistics HAR file on slow page loading. See: How do I generate the UI logs?

Configuring a Custom HPROF (Java Heap Dump) Location

1. Set the Custom Path
   • Open the properties file:
     • Before version 5.0: /usr/share/tomcat/default/conf/intigua.properties
     • Version 5.0 and later: /usr/share/intigua/services/data/intigua-main/conf/intigua.properties
   • Add or update the following line:

• Make sure /javaheap is an existing mount point. The /javaheap/log directory will be created automatically if it does not exist.
• Verify Disk Space
  • Confirm that the partition hosting /javaheap/log has sufficient space — at least twice the server's total memory.
• Restart the Service
  • Before version 5.0 - restart Tomcat:

• Version 5.0 and later — restart intigua-main:

System Information

1. Log in to JetPatch.
2. Navigate to: <SERVER-URL>/vmanage-server/monitoring

You will find OS version, Java version, memory, disk space, and more. You may need to click Details to see this additional information.

JetPatch is always ready to show the latest performance monitoring and previous data on the 3rd-party library JetPatch utilizes -  Java Melody. 

This module provides health graphs on various KPI: CPU, RAM.