Problem
Users with on-premise Controllers using Java Machine Agents report that no hardware metrics are showing on the Controller UI.
To troubleshoot this issue, review the Machine Agent logs. The following error message indicates that the Agent is not able to publish the metrics:
[Worker-2] 16 Mar 2017 07:56:38,042 WARN MetricOutputHandler - Metric Reporter type mismatch for metric [Hardware Resources|CPU|%Idle]
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricReporterTypeMismatchException: Aggregator of AVERAGE already exists for metric Metric Identifier[Hardware Resources|CPU|%Idle] ID[0]
[Worker-2] 16 Mar 2017 07:56:38,042 WARN MetricOutputHandler - Metric Reporter type mismatch for metric [Hardware Resources|CPU|%Busy]
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricReporterTypeMismatchException: Aggregator of AVERAGE already exists for metric Metric Identifier[Hardware Resources|CPU|%Busy] ID[0]
Solution
First, verify that both of the monitors are enabled within the monitor.xml file, which is located at <machine-agent-install-dir>\monitors\JavaHardwareMonitor\monitor.xml and <machine-agent-install-dir>\monitors\HardwareMonitor\monitor.xml .
If both monitors are enabled, disable the JavaHardwareMonitor property by configuring the enabled flag with a value of "false" in the \JavaHardwareMonitor\monitor.xml file.
Then restart the Machine Agent's Java process.
