Zabbix Documentation 2.0 (current)| In development:5.2 (devel)| Unsupported:

User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

manual:config:notifications [2017/08/25 07:13]
manual:config:notifications [2014/09/26 11:32] (current)
sasha Links adapted because of a move operation
Line 1: Line 1:
 +===== - #7 Notifications upon events =====
 +=== Overview ===
 +Assuming that we have configured some items and triggers and now are getting some events happening as a result of triggers changing state, it is time to consider some actions.
 +To begin with, we would not want to stare at the triggers or events list all the time. It would be much better to receive notification if something significant (such as a problem) has happened. Also, when problems occur, we would like to see that all the people concerned are informed.
 +That is why sending notifications is one of the primary actions offered by Zabbix. Who and when should be notified upon a certain event can be defined.
 +To be able to send and receive notifications from Zabbix you have to:
 +  * [[manual:​config:​notifications:​media|define some media]]
 +  * [[manual:​config:​notifications:​action|configure an action]] that sends a message to one of the defined media 
 +Actions consist of //​conditions//​ and //​operations//​. Basically, when conditions are met, operations are carried out. The two principal operations are sending a message (notification) and executing a remote command.
 +For discovery and auto-registration created events, some additional operations are available. Those include adding or removing a host, linking a template etc.