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 #11452] Working with notifications #162
Comments
Updated by tgelf on 2016-03-27 17:08:41 +00:00
Honestly, wasn't my decision. But thank you anyway!
I guess you're perfectly aware of the fact that they're not :p Neither the explicit ones nor those between the lines ;) Cheers, |
Updated by Cactus on 2016-04-16 08:10:50 +00:00 Checked on my fresh install, table is already there and database schema is already at 92 rather than 91. However no files are being written for any of the notifications and there seems to be no form for icinga_notification_assignment. I must be missing something Pulled latest config this morning 16/04. Stacktrace error gone but don't understand how notifications can be linked to hosts / services |
Updated by tgelf on 2016-05-10 17:03:01 +00:00
|
Updated by VeXed on 2016-05-17 13:07:10 +00:00 Any way we could get a hotfix on this? I've had great success using director but not being able to setup notifications is kind of killer. |
Updated by tgelf on 2016-05-25 21:43:48 +00:00
Should be fixed in current master, otherwise please let me know. Cheers, |
Updated by VeXed on 2016-05-31 14:30:26 +00:00 Getting this error when I go to the assign tab in the notification apply rule: Fatal error: Class 'Icinga\Module\Director\Objects\IcingaNotificationAssignment' not found in /usr/share/icingaweb2/modules/director/library/Director/Web/Form/DirectorObjectForm.php on line 38 Just checked that directory and it is missing that file "IcingaNotificationAssignment" Also, it doesn't appear to be applying the notifications to the host (I assume it's due to this missing file..) |
Updated by tgelf on 2016-06-15 06:55:02 +00:00 VeXed wrote:
Please try the latest master, this tab should no longer exist. |
Updated by spillerm on 2016-06-16 07:40:49 +00:00 With today's git clone, I'm now able to save and deploy time periods, users, user groups, notifications and notification apply rules (it seems this "apply to services/ hosts"- thing did the trick). However - notifications still don't work since I'm not able to get a reasonable notification command - how to get mail-host-notification.sh into director? Will continue... :-) |
Updated by tgelf on 2016-06-16 08:58:31 +00:00 spillerm wrote:
Great to hear that, thank you!
Wait for #11849 or adjust the script to accept command line parameters. There is no ENV support in Director right now. mail-*-notification.sh is one of the shittiest notification scripts anyway. This should IMHO be seen as an example and not as the "default" script used by everyone and his dog. But I know, reality is different. Most people treat it as the god-given solely way of sending mails with Icinga :D Cheers, |
Updated by spillerm on 2016-06-17 12:35:54 +00:00 "I replaced it with a small shell script" (https://www.spiller.me/icinga2-director-notifications/) |
Updated by tgelf on 2016-06-17 14:09:08 +00:00 spillerm wrote:
Nice :-) |
Updated by VeXed on 2016-06-17 15:14:26 +00:00 spillerm wrote:
Thank you for posting this!! :) |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11452
Created by spillerm on 2016-03-25 17:59:38 +00:00
Assignee: tgelf
Status: Resolved (closed on 2016-05-25 21:43:48 +00:00)
Target Version: 1.1.0
Last Update: 2016-06-17 15:14:26 +00:00 (in Redmine)
Hi!
Congratulations - first release, very cool :D
Here's what I noticed using "notifications" in director:
Added it this way: ALTER TABLE icinga_notification_assignment ADD assign_type ENUM ('assign', 'ignore') NOT NULL DEFAULT 'assign';
Is there documentation available for notifications, creating NotificationCommands (with env= ...)?
Sorry if my questions are too stupid :)
Regards,
Marianne
Changesets
2016-03-27 17:11:28 +00:00 by tgelf 19d56fc
The text was updated successfully, but these errors were encountered: