Alerting for CPU & Memory on Individual Switchs in a Stack

Thanks for posting this information, exactly what I needed! I would also like to see this implemented as a feature in Solarwinds.

I'd like to add that I had to change up the join conditions in order to prevent multiple alerts:

JOIN [dbo].[NPM_SwitchStackMember] ss ON ss.NodeID = nodes.NodeID

JOIN [dbo].[MemoryMultiLoad_Current] c ON ss.MemberID=c.[Index] AND c.NodeID=ss.NodeID

WHERE c.AvgPercentMemoryUsed > '90'

Hope this helps! Thanks again for sharing!

Rebump.

For your Alert, in the Trigger Condition, use "Custom SQL Alert":

For Memory the SQL is:

JOIN [dbo].[MemoryMultiLoad_Current] c ON Nodes.NodeID = c.NodeID

JOIN [dbo].[NPM_SwitchStackMember] ss ON Nodes.NodeID = ss.NodeID

WHERE c.AvgPercentMemoryUsed > '80'

We set it to greater than 80%...and that looks at  each individual switch. Adjust that value as needed.

For CPU, create a different alert the same way... and the SQL is:

JOIN [dbo].[CPUMultiLoad_Current] c ON Nodes.NodeID = c.NodeID

JOIN [dbo].[NPM_SwitchStackMember] ss ON Nodes.NodeID = ss.NodeID

WHERE c.AvgLoad > '70'

These will get you alerts for the individual CPU or Memory of the switches in the Stacks.

Can you share your SQL query? We've had memory leaks on 3650s, but we haven't been able to get good alerts on increasing memory The issue is on the stack master but it looks like Orion averages out the memory across the stack.

Custom SQL Alert?  Talk about a hassle!

But I'm pressed you've got the skillset to make it work.

+1

Appreciate it.. i actually do have a work around to get the data into an alert.... by using a custom sql alert to pull the data (which is in different sql tables, of course).... Custom SQL alerts are pretty limited due to the Select From being pre-populated...., but it does the job).  Just requesting the feature as I felt it should have already been there.

I can't disagree with your logic.

Here's hoping my suggestions could possibly get you results today instead of waiting months or years for SW to change their solution.

Yep, that would be a good option... but Unfortunately, not all the instances we co-mange are sending Traps or Syslog to Orion... possibly in the future.  And I have no issue using UnDPs or Traps/Syslog to build out the alerts... Just think that this is a feature that should be included out of the box... Orion is already pulling the data, and already displays info for these individual members... why not be able to easily build alerts on whats there?

You're right.

But where you can't have what you need, maybe you can build what you want with a UnDP.  Agreed, it shouldn't be required.

Your stack should fire off a trap or syslog message when one of the units' CPU or Memory hits a threshold.  You can easily build an Alert based on the info in that trap or syslog message, if you don't want to dig into UnDP's.

Orion is already pulling the cpu and memory values for the individual switches (as you can see if you view the stack details on a Node).... I don't see why I would need to pull this info again via a (UnDP) and double the space in the database... then go through the process of building an alert on the custom poller. I just want to be able to alert on the data that is already existing in a an easy manner... There is an option when building alerts for Stack Member details... being able to alert on the member CPU and Memory should be included in this.  Having to do a bunch of one of solutions might be fine in a smaller environment, but wont scale well (multiple instances of Orion, co-managed instances, databases exceeding 1TB, monitoring a hundred thousand nodes, etc.) I am all for a UnDP when its needed.... but simple tasks should stay simple.