Monitoraggio ZFS in Zabbix

Monitoraggio POOLs e Datasets

• Installare i files

wget "https://raw.githubusercontent.com/GabrieleV/zabbix-zfs-on-linux/master/etc/sudoers.d/zabbix-zfs-on-linux" -O /etc/sudoers.d/zabbix-zfs-on-linux

chmod 0440 /etc/sudoers.d/zabbix-zfs-on-linux

wget "https://raw.githubusercontent.com/GabrieleV/zabbix-zfs-on-linux/master/etc/zabbix/zabbix_agentd.d/zfs-on-linux.conf" -O /etc/zabbix/zabbix_agentd.d/zfs-on-linux.conf

chmod 0440 /etc/zabbix/zabbix_agentd.d/zfs-on-linux.conf

• Verificare se i comandi funzionano (DATA è il nome di un pool zfs presente):

sudo -u zabbix /usr/bin/sudo /sbin/zpool list -H -o health DATA

• Riavviare zabbix_agent

systemctl restart zabbix-agent.service

• Dal server o dal prozy zabbix, verificare che le keys siano supportate:

zabbix_get -s 192.168.1.10 -k zfs.zpool.health[DATA]

• Importare il template ZFSonLinux_template.xml sul server ed assegnare il template all'host

ZFSonLinux

• Definire la Regex in

Administration / General/ Regular Expression

Name: ZFS Fileset
Expressions
  Expression type: Character string included
  Expression: /

Monitoraggio degli snapshot

• Installare gli script

mkdir -p /etc/zabbix/scripts

wget "https://raw.githubusercontent.com/GabrieleV/zabbix-zfs-on-linux/master/etc/zabbix/scripts/zabbix-zfs-snapshot" -O /etc/zabbix/scripts/zabbix-zfs-snapshot

chmod +x /etc/zabbix/scripts/zabbix-zfs-snapshot

• Abilitarlo in cron:

wget "https://raw.githubusercontent.com/GabrieleV/zabbix-zfs-on-linux/master/etc/cron.d/zabbix-zfs-snapshot" -O /etc/cron.d/zabbix-zfs-snapshot

• Assicurarsi che ci sia la homedir di zabbix:

mkdir -p /var/lib/zabbix
chown zabbix:zabbix /var/lib/zabbix

• Riavviare zabbix agent

systemctl restart zabbix-agent.service

• Provare a lanciare manualmente lo script per il collecting dei timestamp:

 sudo -u zabbix /etc/zabbix/scripts/zabbix-zfs-snapshot -i

• Controllare se ci sono i timestamp, ad esempio:

cat /var/lib/zabbix/zfs-snapshot.dat 

BACKUP 1545069600 2018-12-17 19:00:00
BACKUP/backuppc
BACKUP/znapzend-emip-home 1545069600 2018-12-17 19:00:00
BACKUP/znapzend-emip-mysql 1545069600 2018-12-17 19:00:00
BACKUP/znapzend-kinsi-home 1542810600 2018-11-21 15:30:00
BACKUP/znapzend-xopta-dati 1545069600 2018-12-17 19:00:00
BACKUP/znapzend-xopta-files 1545069600 2018-12-17 19:00:00
BACKUP/znapzend-xopta-mysql 1545069600 2018-12-17 19:00:00
DATA 1545069600 2018-12-17 19:00:00
DATA/dati 1545069600 2018-12-17 19:00:00
DATA/files 1545069600 2018-12-17 19:00:00
DATA/mysql 1545069600 2018-12-17 19:00:00

• Dal server zabbix o proxy monitorante, verificare se si leggono i timestamp:

zabbix_get -s machinename -k zfs.snapshot.time['BACKUP/znapzend-xopta-mysql']

1545069600

• Disabilitare le item per i Dataset che non si vogliono verificare

• Di default la snapshot age è di 2 ore (7200 secondi). Per impostare age diverse, creare a macro nell'host:

{$ZFS_SNAPSHOT_AGE:"BACKUP/znapzend-xopta-mysql"}
-> Numero di secondi di età dello snapshot

Riferimenti

• GabrieleV/zabbix-zfs-on-linux
• Monitoring your ZFS pools in Zabbix – Marin Atanasov Nikolov – A place about Open Source Software, Operating Systems and some random thoughts
• Zabbix Share - ZFS on Linux
• linux - How to cat <<'EOF' arbitrary text data from clipboard - Super User