[dev.icinga.com #1697] add easy-to-use config examples and scripts for notifications

[icinga-migration]

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

Created by mfriedrich on 2011-07-03 12:26:33 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2011-07-12 09:55:27 +00:00)
Target Version: 1.5
Last Update: 2011-07-12 09:55:27 +00:00 (in Redmine)

---

as stated on the feedback tracker, it's not that clear, how to use those macro logic and even more, when to use which macros and formatting with the default printf into mail.

even more, people tend to keep configs so deprecated macros are still kept within configs (like over here) and giving more telling examples or even shell scripts for easier including would be a great idea for a maintenance release.
this shouldn't be within the docs in the first place, but within the core package itsself, targetted 1.5 for a maintenance release.

http://feedback.icinga.org/forums/50329-general/suggestions/832369-email-content-configurable?ref=title

Changesets

2011-07-12 08:30:55 +00:00 by mfriedrich 546655f

config: add easy-to-use config examples and scripts for notifications #1697

fixes #1697

[icinga-migration]

Updated by mfriedrich on 2011-07-03 12:48:49 +00:00

also regarding this, showing more examples on a per-user-basis.

http://feedback.icinga.org/forums/50329-general/suggestions/1240007-user-customisable-notifications?ref=title

[icinga-migration]

Updated by mfriedrich on 2011-07-12 07:51:05 +00:00

• Done % changed from 0 to 60

since i have rewritten the mail notifications to an advanced format at our stage, and also jabber notifications too, i'll be adding notifications.cfg.in as opt-in config for advanced used.

furthermore, the notidy_via jabber will be provided in contrib/notifications/

[icinga-migration]

Updated by mfriedrich on 2011-07-12 09:55:27 +00:00

• Status changed from Assigned to Resolved
• Done % changed from 60 to 100

Applied in changeset 546655f.