Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #9749] Add last_notification_result for Notification class #3187

Closed
icinga-migration opened this issue Jul 28, 2015 · 3 comments
Labels
enhancement New feature or request

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9749

Created by kruisdraad on 2015-07-28 07:03:58 +00:00

Assignee: (none)
Status: Rejected (closed on 2016-09-07 12:57:30 +00:00)
Target Version: (none)
Last Update: 2016-09-07 12:57:30 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

When notifications result in a error, for example because of a broken mail script, icinga does not 'notify' or change the state of the service. You'd never know until you notice missing mails or errors in the logs. It would be great if the service/host status of the affected service to to enter a 'unable to notify state' to show there is a problem.

Example log:

[2015-07-28 08:56:01 +0200] warning/PluginNotificationTask: Notification command for object 'HOST!SERVICE' (PID: 5527, arguments: '/etc/icinga2/scripts/mail-service-notification.sh') terminated with exit code 127, output: /etc/icinga2/scripts/mail-service-notification.sh: line 26: mail: command not found
/usr/bin/printf: write error: Broken pipe

Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-07-30 09:01:16 +00:00

  • Subject changed from Handle notification errors to Add last_notification_result for Notification class
  • Description updated
  • Category set to libicinga
  • Target Version set to Backlog

One idea we have come up with is to add a new field to the Notification class: last_notification_result.
This field would contain the exit status and output of the last notification attempt similar to last_check_result for hosts and services.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-07-31 13:34:01 +00:00

  • Relates set to 9773

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-09-07 12:57:30 +00:00

  • Status changed from New to Rejected
  • Target Version deleted Backlog

Unfortunately this can't be stored on the notification object itself but for every 1..n user notification. We'll consider a different debug option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant