You can identify the resources that Java Agent utilizes while instrumenting an application. You can use the agent-free-performance-report-for-window node property to stop the agent operation for some time. This will disable all the agent services however, the JVM metrics are still recorded. When agent service resumes, you can see and compare the before and after resource consumption of the agent.
Before You Begin
Important
Ensure that you understand the following points before you configure this option:
All agent services will be suspended for the time you specify in the node property. The applications will continue to run without the agent monitoring.
No application data will be reported to the Controller during this time. This pause in data reporting can cause false alerts.
The agent records JVM resource consumption data during the downtime. You can see this data in the Controller UI.
When the agent services are resumed, you can use the metric browser or live preview to view and compare the consumption data.
Configure the Java Agent for the Resource Usage Report
In the Controller UI, go to the application for which you want to see the agent resource usage.
Select Tiers & Nodes. It lists the tiers and nodes of the application. For more information about tiers and nodes, see Tiers and Nodes.
Expand the tier and double-click the node that you want to edit.
In the node dashboard, click Actions > Configure App Server Agent. It displays the App Server Agent Configuration panel.
In App Server Agent Configuration, select the node from the left-hand navigation.
Select Use Custom Configuration.
Click + to open the Create Agent Property panel.
Specify agent-free-performance-report-for-window as the name.
Click the Type drop-down and select Integer.
In the Value field, specify the number of minutes for which you want to suspend the agent services. You can specify a value from 5 to 30. For example, if you specify 10, the agent services will be stopped for 10 minutes and then resumed.
Important
You must delete this node property after the resource utilization data is collected. If this node property is not deleted, it will disable the agent services and that will lead to application monitoring loss.
When the agent services are suspended, you can see that no data is reported to the Controller.
When the agent services are resumed, you can see the difference between before and after resource utilization of the agent. The following is an example of process CPU usage percentage. Similarly, you can check and compare other metrics.
