1 Reply Latest reply on Apr 18, 2008 10:22 AM by chris.lapoint

    Member alerts after the dependency recovers

      Hi Folks,

      I am trying to get my head around the alerts that are being generated out of our production 8.5 environment.

      Simplified Setup:
      Group:             Group A
      Dependency:    Server A Ping
      Member:          Server A Port 80

      Scenario:
      Server A Ping becomes unavailable and moves into a warn state.
      Server A Port 80 becomes unavailable and moves into a warn state.
      Server A Ping becomes unavailable and moves into a down state.
      Server A Port 80 stays in a warn state because of its dependencies
      Server A is rebooted.
      Server A Ping returns to a green state.
      Server A Port 80 moves to a down state as the server is not fully up
      Server A Port 80 Alerts
      Server A Port 80 Recovers very soon after

       
      When a dependency is down, shouldn't its stay in its top level state?

      Cheers
      Brock
       

        • Re: Member alerts after the dependency recovers
          chris.lapoint

          From our ipMonitor guru's Matt and Peter in dev:


          When any dependency is ‘down’ ipMonitor will record failures, but those failures will not count towards its alerting (and remedial actions). In this example, while the dependency was down, ipMonitor correctly suppressed alerts while it continued to collect monitoring telemetrics. When the dependency came back up, ipMonitor tested port 80 shortly after and found it still failing. Next, ipMonitor counted that failure towards alerting … and then it kicked off an alerting sequence.  Dependencies are about alert suppression.


          Here's a link to a tutorial that explains dependencies and alert suppression in more detail: 


          http://support.ipmonitor.com/tutorials/b0de9ea341914c28a1565f859589d420.aspx