Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

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
23:05, 30 Nov 2016