Administrators • Re: Is there a way to create a trigger/alert that will notify me when something specific happens in Zimbra?

There is this program running already:

Code:

/usr/bin/perl /opt/zimbra/common/bin/swatchdog --config-file=/opt/zimbra/conf/swatchrc --use-cpan-file-tail --script-dir=/opt/zimbra/data/tmp --tail-file /var/log/zimbra.log

It is a perl program that has a config file that can do things like throttle, action, mail, etc, etc. You might be able to understand the syntax by viewing the config file and looking for watchfor statements.

Code:

% cat /opt/zimbra/conf/swatchrc

You could put in your own watchfor /regex/ and corresponding action statements. You could also run your own swatch on the server against any log file you want to become event driven vs time driven with cron because /opt/zimbra/common/bin/swatchdog is included with zimbra. It is doing a tail -f on the log file you give with an easier syntax to make getting stuff down fairly fast.. If you know the log file, the pattern in that log file, and the action you want to perform than you can have it working in about 3 lines of syntax. Do this for more information:

Code:

# su - zimbra% pod2text /opt/zimbra/common/bin/swatchdog NAME    swatchdog - simple watcherSYNOPSIS    swatchdog [ --awk-field-syntax ] [ --config-file|-c *file* ] [ --daemon    ] [ --extra-include-dir|-I *path* ] [ --extra-module|-M *module_name* ]    [ --help|-h ] [ --input-record-separator *regex* ] [    --old-style-config|-O ] [ --pid-file *file* ] [ --restart-time|-r *time*    ] [ --script-dir *path* ] [ --tail-args *arguments_for_tail_program* ] [    --tail-program-name *filename* ] [ --version|-V ] [ --use-cpan-file-tail    ] [ [ --examine|-f *file_to_examine* ] | [ --read-pipe|-p    *program_to_pipe_from* ] | [ --tail-file|-t *file_to_tail* ] ] [ --debug    [ *level* ] ] [ --dump-script *filename* ]DESCRIPTION    Swatchdog is designed to monitor system activity. In order for Swatchdog    to be useful, it requires a configuration file which contains    *pattern(s)* to look for and *action(s)* to perform when each pattern is    found.......

A couple of things to keep in mind. Make sure you handle syslog log rotation every night .. swatch handles this nicely with a signal. Make sure your script or swatch is throtting so that you don't do the same action over and over again. If you modify any zimbra config file, make sure you have a script to put your changes back in should it change from updates, upgrades, etc.

You could also modify your script to tail appropriate log file, read from stdin and just do the action if you want to be event driven or grep and parse if you want to be time driven with cron. Since I have not created a domain in about 15 years, I don't know what logfile it would be logged to but most things in zimbra are logged so it should be fairly straightforward to look for the pattern and then automatically do what you want to do. Bonus points for adding the corresponding TXT resource record by using your providers or BIND's DNS API to make this completely autonomous. Lots of examples how to do that in programs like acme.sh (letsencrypt, certbot) or others that do DNS verfication and sometimes the manuals/documentation.

HTH,

Jim

Statistics: Posted by cmartinez127 — Fri Jan 19, 2024 8:56 am