Michael:
  Sorry.  I didn't see the original reply, but found it in the archive.  You 
asked:


- icinga core version
- configs of the affected objects
- statehistory in detail
- notification log


1) Icinga 1.5.0
2) 

    define host{
        use                     default-host
        host_name               postgress-db
        alias                    Database-postgress
        address                 10.0.0.32
        hostgroups              databases
        contact_groups          dbAdmin
        }


define host{
        name                            default-host    
        use                             generic-host    
        check_period                    24x7            
        check_interval                  5               
        retry_interval                  1               
        max_check_attempts              2               
        check_command                   check-host-alive 
        notification_period             24x7            
        contact_groups                  nsAdmin-all
        }

define host{
        name                            generic-host    
        notifications_enabled           1               
        event_handler_enabled           1               
        flap_detection_enabled          1               
        failure_prediction_enabled      1               
        process_perf_data               1               
        retain_status_information       1               
        retain_nonstatus_information    1               
        notification_period             24x7            
        register                        0
        }

3)  Not sure where to find this, but while looking through the status.dat log I 
saw this entry under an entry for the host in question:    

         "comment_data=Notifications for this service are being suppressed 
because it was detected as having been flapping between different states (24.2% 
change >= 20.0% threshold).  When the service state stabilizes and the flapping 
stops, notifications will be re-enabled."

  So, I think I might have found my answer.   But for completeness:

4) there was nothing in the notification log indicating notifications were 
sent.  This was one of the first things I checked.  But from what I found in #3 
above, it was probably related to the 'flapping' setting.   I could try 
disabling that to see what happens, unless you see something else which makes 
more sense to adjust?

Thanks again!

Regards,
Joseph Spenner



If life gives you lemons, keep them-- because hey.. free lemons.
"~heart~ Sticker"  fixer:  http://microflush.org/stuff/stickers/heartFix.html



________________________________
 From: Michael Friedrich <michael.friedr...@gmail.com>
To: icinga-users@lists.sourceforge.net 
Sent: Thursday, April 4, 2013 8:02 AM
Subject: Re: [icinga-users] service notification behavior on UP state
 
On 04.04.2013 16:41, Joseph Spenner wrote:
> I've seen this behavior again today, and am getting more curious about it.

please answer my questions in the previous mail first.


> A little more info:
> It seems if a host has a service issue, and has sent some notifications,
> my icinga eventually stops sending notifications. However, the web
> interface still indicates the problem still exists and continues to
> perform the checks-- recording results in the "history" section in the
> web interface. It simply stops sending notifications for that issue.
> I suspect this is a setting somewhere, but not sure which one. Also,
> once the service returns, there is no "OK" or 'all clear' notification
> sent out.
> Can anyone help with which config option could be responsible?
>
> Thanks!
>
>
> ------------------------------------------------------------------------
> *From:* Joseph Spenner <joseph85...@yahoo.com>
> *To:* "icinga-users@lists.sourceforge.net"
> <icinga-users@lists.sourceforge.net>
> *Sent:* Thursday, March 28, 2013 3:19 PM
> *Subject:* [icinga-users] service notification behavior on UP state
>
> I'm running Version icinga-web/v1.5.1 and have been pretty happy with
> everything so far. Today I noticed something unexpected and am curious
> if there's a good explanation. I have a postgress server being monitored
> with some service checks (transaction locks, transaction time,
> transaction idle, etc).
> My transaction locks check also has a 'ignore' period where I configured
> it to "not notify" during backups, since they tend to cause some of my
> checks to fire due to the load from the backups. So, that's all good.
> Today I had a legitimate lock, which occurred after my backups. I got
> notifications, as I would expect. However, after everything was
> corrected, I never got a "OK" notification. I checked the mail logs, and
> noticed none were ever sent. However, there exists an entry in the
> State-History for that check with a green OK. It just never sent an email.
> Is there a special config which might be responsible?
> My "Attempt" threshold is set to 3, which it reached. After that, I
> received 2 more notifications since the issue still existed. But after
> it was resolved, the OK email never got sent.
>
> Any info or explanation would be great.
>
> Thanks!
>
> Regards,
> Joseph Spenner
>
> If life gives you lemons, keep them-- because hey.. free lemons.
> "~heart~ Sticker" fixer: http://microflush.org/stuff/stickers/heartFix.html
>
> ------------------------------------------------------------------------------
> Own the Future-Intel(R) Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest. Compete
> for recognition, cash, and the chance to get your game on Steam.
> $5K grand prize plus 10 genre and skill prizes. Submit your demo
> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.sourceforge.net
> <mailto:icinga-users@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/icinga-users
>
>
>
>
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire
> the most talented Cisco Certified professionals. Visit the
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
>
>
>
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/icinga-users


-- 
DI (FH) Michael Friedrich

mail:    michael.friedr...@gmail.com
twitter:  https://twitter.com/dnsmichi
jabber:  dnsmi...@jabber.ccc.de
irc:      irc.freenode.net/icinga dnsmichi

icinga open source monitoring
position: lead core developer
url:      https://www.icinga.org

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users

Reply via email to