Ad Widget

Collapse

Notifications Only When Resolved

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mattwv
    Junior Member
    • Jan 2020
    • 1

    #1

    Notifications Only When Resolved

    Hi There

    Having some weirdness with notifications. I have tried this with email and a number of webhook pushes (ie Opsgenie and Pushover), with actions setup, etc.

    When a particular check triggers, the action seems to be attempted for email and the push services - but there are weird errors:

    10157:20200102:092924.213 Pushover notification failed : Error: cannot get URL: Timeout was reached.
    10154:20200102:092924.735 failed to send email: Timeout was reached: Resolving timed out after 40557 milliseconds


    HOWEVER when the issue is resolved, I successfully receive the resolved notifications on all services. Initially I thought it was some kind of name resolution issue however since the actions are working for when the issue is resolved, I would more or less eliminate that as being a problem. Further since the resolved actions are working, I would think it would be safe to say that the actual configuration of the actions is also OK.

    Any suggestions as to why the actual sending of notification when something goes down (only) would be an issue?

    Thanks,
    Matt
  • aasami
    Junior Member
    • Aug 2018
    • 1

    #2
    Hi! I have the same problem for notifications via Telegram. Have you ever found a solution for your problem?
    I can not figure out why on earth I get Resolved messages OK, but not actual problem reports. Any clue is welcome. Thanks

    Comment

    • chlmun
      Junior Member
      • Aug 2022
      • 1

      #3
      Hi, I'm facing the same issue. Did any of you find a solution that you can share? Thanks

      Comment

      • FNog
        Junior Member
        • Jan 2022
        • 2

        #4
        Just today faced a similar error which, while searching for "Timeout was reached: Resolving timed out", led me to this topic.

        Turns out it was a dns server that was misbehaving, taking more than the configured timeout (5s) to resolve addresses.

        DNS issue solved => triggered zabbix problems also solved.

        Comment

        Working...