Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

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

Manually repair alerts in SAM v6.2

Table of contents

Overview

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.

Environment

SAM version 6.2

Steps


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.
    6255_1.png
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.
    6255_4.png
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.
    6255_2.png
6. In the Configure Actiondialog box, modify the Network path to external program field and replace -alert=${AlertDefID} with -alertid=${N=Alerting;M=AlertID}.
    6255_3_new.png
7. Save the changes and do the same for all other affected alerts.

Last modified
23:05, 30 Nov 2016

Tags

Classifications

Public