Disable Extended JMX Metrics Collection

Extended JMX metrics collection is enabled by default. You can disable it to reconfigure metrics collection paths (directory structure and port numbers) or for troubleshooting concerns such as the load on a monitored object.

Important: A single global control switch enables/disables extended JMX metrics collection and custom program monitoring. To continue custom programming, you cannot disable extended JMX metrics collection. Instead, edit your rules file to remove all JMX metrics definitions, and skip the steps in this procedure.

Procedure

Beginning with any host where Pepperdata is running, add the property that controls extended JMX metrics collection to the Pepperdata site file, pepperdata-site.xml, and set its value to false.

By default, the Pepperdata site file, pepperdata-site.xml, is located in /etc/pepperdata. If you customized the location, the file is specified by the PD_CONF_DIR environment variable. See Change the Location of pepperdata-site.xml for details.
```
<property>
  <name>pepperdata.agent.program.monitor.enabled</name>
  <value>false</value>
</property>
```
Malformed XML files can cause operational errors that can be difficult to debug. To prevent such errors, we recommend that you use a linter, such as xmllint, after you edit any .xml configuration file.
Restart the PepAgent.

You can use either the service (if provided by your OS) or systemctl command:
- sudo service pepagentd restart
- sudo systemctl restart pepagentd
Repeat steps 1 and 2 on every host where Pepperdata is running.