You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the host running nagios ends up with the pagerduty_queue directory in a read-only state, the "enqueue" action just dies upon failure to open and write the alert details into the queue.
I would suggest that it should have a fallback routine of trying to directly send an alert to the pagerduty API that the queue is not writable before dying on line 247.
The text was updated successfully, but these errors were encountered:
If the host running nagios ends up with the pagerduty_queue directory in a read-only state, the "enqueue" action just dies upon failure to open and write the alert details into the queue.
I would suggest that it should have a fallback routine of trying to directly send an alert to the pagerduty API that the queue is not writable before dying on line 247.
The text was updated successfully, but these errors were encountered: