1 Title: Notification scripts are now configurable via WATO
3 Component: notifications
8 Check_MK now has a new alternative API for notification scripts, which allows
9 them to be configured via WATO. The classical API provided the possibility
10 of a list of strings that was passed to the script in form of variables like
11 <tt>PARAMETER_1</tt>, <tt>PARAMETER_2</tt>, etc. The new API passes parameters
12 according to keys of a WATO-configured dictionary, like <tt>PARAMETER_FROM</tt>
13 and <tt>PARAMETER_REPLY_TO</tt>.
15 Two notification scripts have already been converted to use the new API: <tt>mail</tt>
16 (sending HTML emails) and <tt>mkeventd</tt> (forwarding to the Event Console).
18 The configuration of a notification script does only work with the new
19 <i>Rule Based Notifications</i> can be done at two places:
22 <li>In new rulesets below <i>Host & Service Parameters</i> → <i>Monitoring Configuration</i> → <i>Notifications</i></li>
23 <li>In a notification rule</li>
26 Both configurations are being merged on a per-key basis. That way you
27 can e.g. setup a <tt>From:</tt> header for your outgoing emails via
28 a global rule, but select various different <tt>Reply-To:</tt> addresses
29 in different notification rules.
30 If a configuration key appears both in <i>Host & Service Parameters</i> and
31 in a notification rule then the latter one has precedence.
33 Within that effort the HTML email script has been made far more configurable. You
37 <li>The From- and Reply-To Address</li>
38 <li>The subjects for host and service notifications</li>
39 <li>An URL-Prefix for your Multisite interface (this makes hosts and services
40 in the notifications clickable</li>
41 <li>A choice of optional information to be displayed in the emails</li>