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

DFS monitoring - cutting down on the noise

Hi. We're currently using SAM to monitor DFS on our domain controllers. The problem is, it's reeeeeally noisy. Every time a DC is rebooted, e.g. for Windows updates, we get a ton of alerts.

I know we could set up a schedule for the monitors to not trigger an alert during our (weekly, late-night/early-morning) maintenance windows, but is there any other or a better way of handling this? E.g. if the replication partner node is down, don't alert on the DFS stuff, because of course it will also be down?

Thanks.

Orion Platform 2019.2, NPM 12.5, SAM 6.9.0

Find more posts tagged with

Accepted answers

All comments

christopher.t.jones123

this sounds like it could be accomplished with a dependency. you could set one up that states if the node(s) go down then put the status of these application(s) into unreachable which should suppress any alerts you have on status change. You'll essentially receive the one alert for the server being down but not the application monitoring alerts.

jaybone

If I'm understanding how dependencies and groups work, I think I should be able to accomplish it that way as follows?

Group - "XYZ-DC replication partners", rollup set to "worst status" (to force the object to a down state when any of those nodes are down), contains nodes that are replication partners for that DC.

Dependency - Parent = "XYZ-DC replication partners" group, child = the DFS application assigned to XYZ-DC

Is that right?

christopher.t.jones123

that should do it, if you have multiple application monitors you'll likely have to create a group that contains all of them you want to be in scope of this as well.

jaybone

Thanks!

jaybone

This is not working; we're still getting SAM alerts about some DFS stuff (specifically, "Communication with Partner") when a DC is rebooted.

Might be a timing issue? The groups' refrersh frequencies are set to 60 seconds. The DFS monitors are set to 300 seconds. If that 300 seconds comes around and finds DFS problems in the minute between two group status refreshes, could that cause this?

I'm kind of confused also, because the monitored Application doesn't have anything along the lines of a regular alert's "must exist for more than x seconds" value. Might be because the Application is monitoring event logs, so it's not really a state that's being monitored, but a specific event? If that's the case... what's the workaround?