Troubleshooting steps if the Windows server monitoring agent is using high amount of CPU/memory
High memory/CPU usage by the Windows server monitoring agent might be caused by an Antivirus scanning the agent files.
Please check if there is an Antivirus on your server. If yes, exclude our server monitoring agent directory from the Antivirus software by considering the Site24x7 agent as a trusted application. This will help the Site24x7 agent to use less memory or CPU for collecting the performance metrics.
Related Articles
How to uninstall the Site24x7 Windows Server Monitoring Agent
Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...
How to view perfmon counters in Windows?
To monitor specific Windows performance (perfmon) counters with Site24x7's plugin integration, you need to get the names of the performance counters from the Windows Performance Monitor on your server. Follow the steps below to get the names of the ...
Troubleshooting false positive alerts in monitoring
Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...
Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers
Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...
No data for service and process in Windows server monitor
If you see "No Data" for process and service metrics (such as CPU or memory usage of monitored services) in the Site24x7 Windows server monitor user interface, follow the troubleshooting steps below. Run PowerShell Commands Open PowerShell as ...