Because of lack of antiflapping capabilities in Zabbix many peoples will be very glad to see total trigger events logging in file, so that it will be possible to read this log string-by-string within the SEC-like special correlation engine, which will produce its own actions.
Now total/selective trigger logging may be done in context of Zabbix Actions's "Remote command" feature.
But there are 2 big problems which makes action-oriented method unusable in many (or maybe all) situations:
1) Period between 2 action calls must not be less than 60 seconds
2) User have to write its own script to properly format information from different triggers and place it to log
So... it will be very cool if in the future releases of Zabbix there will be possibility to log (all/some of) events in the log file. Maybe something like syslog in *nix systems but more structurized and with the support of "Zabbix internal" things?
Now total/selective trigger logging may be done in context of Zabbix Actions's "Remote command" feature.
But there are 2 big problems which makes action-oriented method unusable in many (or maybe all) situations:
1) Period between 2 action calls must not be less than 60 seconds
2) User have to write its own script to properly format information from different triggers and place it to log
So... it will be very cool if in the future releases of Zabbix there will be possibility to log (all/some of) events in the log file. Maybe something like syslog in *nix systems but more structurized and with the support of "Zabbix internal" things?