Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

NPM vs SAM

I'm running into an issue where I had the NPM set up, with global thresholds, but now I am setting up nodes in the SAM. I have sql servers that I've now set with the sql template, but the cpu, disk, memory is still alerting/alarming on the thresholds set in the global settings. I want to have global settings in place to catch any server we add, but would like to have them overridden by the SAM settings, if we drop a template on them. How can I accomplish that?

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Without seeing the alerts it's hard to say for certain, but there is a difference between application and node based alerts. Alerts for application CPU/Memory usually involve a monitored process or service that is consuming a lot of resources. This may explain why you are receiving an alert, but honestly it's just a guess. Is there a particular component that is causing these alerts to trigger? You need not remove the entire application. In most cases it's simply a matter of tuning the application thresholds for that node or globally at the template level.

prichertjda

The issue is that the global node alert is set for 85% alert 90% alarm, and we want the alert to be sent only on the application settings of 90% alert 95% alarm, but if we turn off the global node alert on this, the SAM pulls no information. So how do I get the SAM alert to override the Global Node alert.

silverbacksays

NPM thresholds pertain to the node, i.e. the device that you are polling. These thresholds are for the OVERALL CPU/Memory utilization of the device itself.

SAM thresholds seen in the application templates pertain to the individual APPLICATION COMPONENT(S) you have chosen to monitor on the parent server.

If you want the application thresholds to fire off an alarm before the the global thresholds, all you can do (without resorting to using custom properties) is to have the NPM thresholds set HIGHER than the application thresholds specified.

Alternatively, you could setup an advanced alert which fires off when node x has CPU usage equal than or greater than 90% AND when application y component x has CPU usage greater than or equal to 95%

This will mean that this specific alert will only fire off when both NPM and SAM thresholds are breached at the same time, which would fulfil your requirements.

aLTeReGo

For each individual node can either inherit from the Global Thresholds for CPU/Memory OR they can use specific thresholds defined at the node level, but not both.

Node Thresholds: [Node Details -> Edit Node]

Node Thresholds.png

Global Thresholds: [Settings -> Orion Thresholds]

Orion Global Thresholds.png

prichertjda

Thanks all. That's what I suspected, but was hoping there was a way to just have one override the other. Makes sense though.