Read more about each extension below:
http://blog.sepa.spb.ru/2015/08/zabbix-graphs-improvements-patch.html
Updates here:
https://github.com/sepich/zabbixGrapher
https://github.com/sepich/glld
http://blog.sepa.spb.ru/2014/11/zabbix-network-socket-state-statistics.html
http://blog.sepa.spb.ru/2014/11/rabbitmq-internals-monitoring-by-zabbix.html
Alternative version also provided, which uses rabbitmqctl
instead of REST API of management-plugin
.
This could be useful when management-plugin
leaks memory or timeouts requests. Also rabbitmqctl
provides atom tab
stats, but as it is ran by root - you also need to add to cron:
$ cat /etc/cron.d/rabbit-status
*/3 * * * * root /etc/zabbix/rabbitmqctl-status.sh
*/5 * * * * root /etc/zabbix/rabbitmqctl-status.sh queues
Unfortunately rabbitmqctl
lacks some info provided only by REST API, for example - rates. This could be send as traps by adding one more line to cron:
* * * * * root /etc/zabbix/rbrates.py
http://blog.sepa.spb.ru/2014/12/mysql-internals-monitoring-by-zabbix.html
http://blog.sepa.spb.ru/2014/12/elasticsearch-internals-monitoring-by.html
http://blog.sepa.spb.ru/2015/09/aws-elb-monitoring-by-zabbix-using.html
Migrated to boto3, creds now moved per docs to:
$ cat /var/lib/zabbix/.aws/credentials
[default]
aws_access_key_id = XXX
aws_secret_access_key = XXX
Collect stats provided by mod_status, your nginx.conf should have this somewhere for https://127.0.0.1:
location /nginx_status {
stub_status on;
access_log off;
allow 127.0.0.1;
deny all;
}
Discover NFS3 and NFS4 mounts and collects stats from /proc/net/rpc/nfs
Discover block devices and collects reads/writes/utilization for each from /proc/diskstats
Official template boiled down to important things