Several event notification channels can be configured. An event notification target is configured by choosing a channel and a corresponding parameter. Valid parameters are mail recipients for emails and URLs for http requests.
Messages are not queued. In case an alert channel can not be reached, the message will get lost.
Valid event notification channels are:
- Mail
Events will be sent to the specified mail recipient. For mail events it is recommended to define meaningful mail aliases to distribute the event messages to the responsible persons.
The SMTP host has to be configured here: Section – SMTP Settings. - HTTP
Events will be sent to the specified URL. This could be used to connect to external alerting systems such as SMS-gateways, pagers, or centralized log management and monitoring systems.
The following placeholder can be used:
@@ALRT_ID@@ : Alert ID
in example message : EVENT_SY-Y-TTY-LOGIN-OK
@@ALRT_COMP@@ : Component, which triggered the alert
in example message : SY
@@ALRT_TIME@@ : Time when the alert was triggered.
in example message : Mar 13 15:17:21.394786
@@ALRT_TXT@@: Alert body (message).
in example message : login[80890]: [event.notice] successful console login (ROOT)
Example message : Mar 13 15:17:21.394786 airlock.example.com airlock-alert[81330]: m:EVENT_SY-Y-TTY-LOGIN-OK c:Y Successful console login (ROOT)
http channel example: "http://mysmsgate.com/cgi-bin/sendsms.pl?msg=@@ALRT_TXT@@&phone=12345"