@Shiva Ravichandran , From your description, I know the MonitoringHost.exe consumes high CPU on SCOM Gateway server with Windows Server 2008 R2 Version. If there's any misunderstanding, please let us know.
For windows server 2008 R2, there's some known issue with CPU. we can see if it met our situation:
https://support.microsoft.com/en-us/topic/operations-manager-agents-consume-100-percent-of-cpu-resources-for-the-monitoringhost-exe-process-a0523d63-aead-a4cf-0a29-387b7147ed49
https://support.microsoft.com/en-us/topic/the-monitoringhost-exe-process-may-consume-all-the-cpu-resources-when-a-large-amount-of-performance-data-is-created-by-using-a-managed-data-source-module-in-system-center-operations-manager-2007-02b514c3-9c69-a2ab-d03c-63f4d177c4a3
However, if it is not, could you collect the following information to clarify?
- Could you let us know the SCOM version?
- When did this issue happen? Have we changed anything before the issue occurring? Have we imported any new MPs?
- Check the Operations Manager event log during the high CPU time to see if there's any finding.
Meanwhile, we suggest to install all the latest hotfixes for the Windows 2008 R2 server and clear cache to see if it can help.
https://learn.microsoft.com/en-us/system-center/scom/manage-clear-healthservice-cache?view=sc-om-2019
If there's any update, feel free to let us know.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.