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

Mute application (or component) alerts

I would like to mute application alerts at the application level, not at the node level. Is that possible?

Here is the scenario - we are deploying a new application to a large quantity of VMs. I am using a dynamic query based group to assign the application monitor automatically. I would like to mute alerts on the application before I assign it to the group. That way nodes that are missed or have a problem during our deployment process won't generate hundreds of alerts. During the deployment period, we just want to use reports versus alerts to email/pagerduty.

In testing, it seems if I mute alerts for the application, it only mutes nodes that currently have the application assigned.

I thought about limiting the scope of the alert, but that also seems to be node dependent.

After deployment, once we declare "production", I will remove the mute.

Thanks

Kevin

Find more posts tagged with

Accepted answers

brscott

Use custom properties. Create a custom property for Applications, called something like "AlertingStatus". You can make it a boolean, but I would suggesy make it a list of items with values starting off with just "Enabled" and "Disabled"... or maybe even just "Enabled".

Next assign that custom property and value to ALL existing SAM monitors.

Change the alert so that it will only alert if that custom property is set to "Enabled".

Now when new SAM monitors are created they will not have the custom property, and you can define how you want to get it assigned later.

adam.beedell

A phrase in your application alert like "And ApplicationName not like 'NOTPRODUCTIONYET%' should cover your dev actions. Then rename the template when stable.

All comments

bobmarley

Possibly mute the node first, assign the application, mute the application, unmute the node, allow the application time to poll and determine its current state, then unmute the applications that don't trigger an immediate alert? Or simply mute the node until you get the monitors assigned?

jklundy

That would technically work, but not for our use case. The nodes are otherwise in production, so I can't just mute the nodes. Especially as I don't know when the application will be installed - it could be a week from now.

I use your method for smaller situations or one-offs.

brscott

Next assign that custom property and value to ALL existing SAM monitors.

Change the alert so that it will only alert if that custom property is set to "Enabled".

Now when new SAM monitors are created they will not have the custom property, and you can define how you want to get it assigned later.

adam.beedell

A phrase in your application alert like "And ApplicationName not like 'NOTPRODUCTIONYET%' should cover your dev actions. Then rename the template when stable.

jklundy

Thanks. I think that would work. I use custom properties all the time, just have never used one for Applications.

jklundy

Thanks. I also think this one would work.