Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Server & Application Monitor (SAM) > Manually repair alerts in SAM v6.2

Manually repair alerts in SAM v6.2

Table of contents


This article describes how you can manually fix the following alerts in SAM v6.2:

  • High CPU Utilization with Top 10 Processes
  • High Physcial Memory Utilization with Top 10 Processes
  • High Virtual Memory Utilization with Top 10 Processes

Follow these steps if:

  • you have SAM v6.2 Hotfix 1 or newer
  • you use one or more of the above mentioned alerts
  • you receive email notifications from these alerts, but they are missing a list of the 10 most CPU/memory intensive processes
  • when editing the alerts, you see that the action Execute program does not contain the parameter -alertid=${N=Alerting;M=AlertID} in theNetwork path to external program field.

Requirements: Hotfix 1 installed in SAM v6.2.


SAM version 6.2


1. Install SAM v6.2 Hotfix 1 on both the Main and additional pollers.
2. Open the Web Console.

3. Go to Settings > Manage Alerts.
4. Go to the alert/s in question and edit each of them accordingly.
Note: If the below message appears, disable the original alert and create a new copy before doing the next steps. This is to avoid duplicate notifications.
5. In Triger Action, edit the first action which is Execute program:

APM\SolarWinds.APM.RealTimeProcessPoller.exe -n${NodeId}... 

Note: The parameter may vary.

Properties, Trigger Condition, Reset Condition and Time of Day can be edited as well before Trigger Action. Reset Action and Summary will follow.
6. In the Configure Actiondialog box, modify the Network path to external program field and replace -alert=${AlertDefID} with -alertid=${N=Alerting;M=AlertID}.
7. Save the changes and do the same for all other affected alerts.

Last modified