The MultiHostProcess agent is needed if the VMWare agent is installed and no Infrastructure (IC) agent is running. The VMWare agent is able to collect most of the operating system metrics, but it is failing to collect process metrics. The MultiHostProcess agent is filling this gap and is collecting the process metrics. Each MultiHostProcess agent is able to collect the process metrics for several hosts, so only one MultiHostProcess agent is needed.
If an IC and database agent is also installed on the system, no MultiHostProcess is needed as the IC agent is collecting the needed process metrics. The correct way to set this up is:
NOTE:
When running IC agent and MultiHostProcess agent in parallel, it will produce topology churn as both agents are collecting the same process metrics.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center