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

Inbuilt functionality to filter 'Events'

Hi folks,

I have requirement to monitor some Polycom Video conferencing units in quite a specific manner. The requirement is to primarily monitor up/down status. Initially when a polycom VC unit goes down the customers want a mail to be sent to the voice team mail box, if the node has not come back up within a few hours only then wouldthey like an event posted in the message centre for the NOC to see.

Building this alert was the easy part but when a VC unit goes down it still shows up in the 'Nodes with problems' resource and basic events are generated in message centre as soon as it goes down. This negates the 2 hour waiting period I have specified in the advanced alert.

I understand the difference between Advanced alerts and events but is there any way I can suppress particular events from being displayed in the 'nodes with problems resource' and the message centre.

I have read similar topics that refer to a custom 'event' filtering resource, this is not an option for us as I don't want to start messing with the standard build of NPM, also using SQL filtering on the 'Nodes with problems' resource is not a solution either I would like to some how suppress the events at source.

Cheers

Find more posts tagged with

Accepted answers

All comments

Questionario

you could set a filter to only show nodes where lastup is longer than X hours or create a custom report for this and put the report as a resource on the website

these are the best options you have, there is no possibility of suppressing this at the source (which would be more messing around with NPM than using NPM for what it is made for: customizing!)

PS: if you filter the resource on that view, that filter only applies to that single resource, if you use the same resource on a different view, the filter will not be applied there unless you configure it there too... again if you dont want this you can also create a custom report that looks similar to the nodes with problems resource and put that report in your view!

Ciag

Thanks for your reply Questionario :- )

Yeah that's just one of the reasons why I mentioned SQL filtering of the 'nodes with problems' is not an option. Using custom reports is not a solution either unfortunately as the functionality of the web output isn't the same as the 'nodes with problems' I would not be willing to replace it with a custom report plus my difficulty is not with creating time delayed triggers, that part is already done using advanced alerts.

I agree that NPM is very much about customsing but I don't agree that having the ability to adjust, filter or supress the basic event triggers is not what NPM is about; it's very much what Orion is about and having that control in itself is a clear form of customisation. Not all networks were created equal lol

Having the ability to notify users about the status of node, interface, operations etc based solely on advanced alerts triggers is primarily what I was seeking. Thanks for your suggestions :-)

Questionario

Hi Ciag,

could you elaborate on why you dont want to use the built-in filtering though?

Questionario

hmmm... maybe I misunderstood you...

could it be possible that you dont mean the "nodes with problems" resource but the messages written to the event logs instead? you can delay these by 2 hours as well in their options in the alert.