6 Replies Latest reply on Jun 10, 2010 5:08 PM by simonpt

    Alerts skipped - why?

      Setup - a basic install of IPMonitor, lots of monitors running seemingly well.

      I created a simple alert - send email to italert@mycompany.com using the Down Devices smartgroup.  Caused a failure, which was picked up, the monitor goes red, but no email is sent.  Here's what I see in the log file:

      2010-05-28 13:21:18 profile used | name(Alerting - IpMonitor@mycompany.com)
      2010-05-28 13:21:18 alert skipped | name(italert@mycompany.com) type(email)
      2010-05-28 13:21:18 alerting unavailable | name(E$ Drivespace) type(drive space) id(2767232618924)
      2010-05-28 13:21:18 monitor test failed | critical(true) error(The drive or share doesn't have enough free space; rtt: 52ms; space: 13 GB, 629.00 MB; avail: 4.61%) name(E$ Drivespace) type(drive space) id(2767232618924)

      Why is the alert getting skipped?  Any ideas?


        • Re: Alerts skipped - why?

          Hi Bmurching,

          Although I've responded to you via the support case you opened, I'll also respond here for the sake of others that might experience similar situations.

          In order to see what gets triggered and when, simply perform the following:
          1. Go to the "Devices" tab.
          2. Go to "All Managed Devices".
          3. Click the Device in question and then one of its Monitors.
          4. Once on the settings page for the Monitor, click "Downtime Simulator".
          This should indicate what Alerts/Actions get triggered and when.  Let me know if this represents the behavior you are expecting or not.

          One other thing that I forgot to mention is to check for Dependencies above the failing Monitor.  See if perhaps any parent groups have members that are failing which may be a Dependency for the group.  If so, Alerting for failing members under that group will be supressed.

          Let me know if this helps.
          Chris Foley - SolarWinds - Support Specialist
          Support:866.530.8040 || Fax:512.857.0125
          network management simplified  |  solarwinds.com

            • Re: Alerts skipped - why?

              I got the answer from Chris through support.  The issue is that my alerts were configured for the "Down Monitors" smart group.  Apparently when a monitor individually goes down, there may be a delay before it is included in the Smart Group.  As a result, when it goes down, the alerts may be tested and skipped before they show up in the smart group, causing messages not to be sent.

              Therefore: do not use smart groups for your alert targets.

              1 of 1 people found this helpful
                • Re: Alerts skipped - why?

                  Good tip!

                  Chris, what is the long-term fix for this?  Using smart groups is brilliant for managing alerts on many monitors.  Will Solarwinds officially discourage their use in this way or will they be improved to work better with alerts?

                  Thanks - Simon

                    • Re: Alerts skipped - why?

                      A Monitor in a Down state is defined as a Monitor that is failing and has triggered Alerts.  If an Alert is based on a SmartGroup of Monitors that are in a Down state, you are creating a Catch 22.  The Monitor is not "Down" because it has not triggered Alerts.  The Monitor has not triggered Alerts because it is not "Down".

                      Having that said, one should not configure Alerts based on a SmartGroup for Monitors that are Down.  Any other SmartGroups are fine.

                      Hope this makes sense.

                      Chris Foley - SolarWinds - Support Specialist
                      Support:866.530.8040 || Fax:512.857.0125
                      network management simplified  |  solarwinds.com