Nagios Acknowledgement behaviors

Not Yet Reviewed

When an alert is sent to xMatters and is acknowledged, after 1 minute the alert will fire again. I believe this is due to the interval of the host/service check in nagios. 

My question is can this be changed to say once someone has acknowledge an alert, can we stop that from repeating every x minutes, but still show as a problem in Nagios ?

I am trying to get a better understanding of how that works. The code shows 

 

ACKNOWLEDGE_HOST_PROBLEM;<host_name>;<sticky>;<notify>;<persistent>;<author>;<comment>
nagiosCmdStr = "[" + timestamp + "] ACKNOWLEDGE_HOST_PROBLEM;" + msg.additionalTokens.host + ";2;1;1;" + msg.recipient + ";" + comment + " \\n";

 

What is ";2;1;1;"  in reference to?

 

 

 

 

0

Comments

2 comments
Date Votes

Please sign in to leave a comment.

  • Hey William!

       Yea, I could see that being rather annoying. It looks like that is in order:

    1. sticky - If the "sticky" option is set to two (2), the acknowledgement will remain until the host returns to an UP state. Otherwise the acknowledgement will automatically be removed when the host changes state.

    2. notify - If the "notify" option is set to one (1), a notification will be sent out to contacts indicating that the current host problem has been acknowledged.

    3. persistent - If the "persistent" option is set to one (1), the comment associated with the acknowledgement will survive across restarts of the Nagios process. If not, the comment will be deleted the next time Nagios restarts.

    According to the Nagios docs for the ACKNOWLEDGE_HOST_PROBLEM. So I'm not sure those would be of help. 

    Maybe one of the disable notification commands listed here might help? Although I'm not sure when you would re-enable them. 

    0
  • Hey William, what about this SCHEDULE_SVC_DOWNTIME command?

    0

Didn't find what you were looking for?

New post