As some howto’s and wiki’s disappear from the internet, and I don’t want to use the “way back machine”, here are the sql scripts which I have used to partition the Zabbix History and Trends tables. I have tested these within Mysql v5.7 and v8.0.Continue reading Zabbix Mysql Table Partitioning
Merging Ansible with Zabbix under Debian 10.
I recenty rediscovered Ansible and wondered if I could use Ansible to create trigger actions and scripts to maintain my home lab. It turns out you can with some adjustments to the Zabbix server.
As an example I use Zabbix to monitor the available updates on my Debian vm’s. When updates are detected, I fire up my dedicated Ansible vm and run my update playbook, which works fine. The only downside is that I must boot the dedicated Ansible server and run the playbooks against the “to be updated” hosts. This is a bit time consumming and wondered if I could update the vm using Zabbix.
What if I could run the playbooks directly from within the Zabbix instance? Mmmm!
I went on the net looking for examples of such howto’s, but wasn’t able to find any. Guess I had to make my own then.Continue reading Debian, Ansible & zabbix Part I
As there were a few nice “how to’s” found on the internet about setting up Zabbix running on Docker containers within the Synology nas, time will eventually catch up those articles, as it will catch up this article eventually.
First to know is that we are using three separate containers. One for the DB storage, one for the actual DB and one for Zabbix.
Create a new directory within the shared Docker directory (which is created when installing Docker). I called it Zabbix:)
Create a Docker container with the following command:
docker run -d -v /var/lib/mysql --name zabbix-db-storage busybox:latest
This will create a container which hasn’t a lot of use, but is needed so we can link to actual storage. Create a volume within this container and point it to the newly create directory:
As far as I can see, we just need to start up the container for one time, afterwards we can ignore the container.
Now for a big step, create the Zabbix database:
docker run -d --volumes-from zabbix-db-storage --name zabbix-db -p 63306:3306 --env="MARIADB_USER=zabbix" --env="MARIADB_PASS=STRONGPASS" --env="DB_innodb_buffer_pool_size=768M" monitoringartist/zabbix-db-mariadb:latest
,…and start the container.
Install the Zabbix container with the following command:
docker run -d --name zabbix -p 8080:80 -p 10051:10051 -v /etc/localtime:/etc/localtime:ro --link zabbix-db:zabbix.db --env="PHP_date_timezone=Europe/Amsterdam" --env="ZS_DBHost=zabbix.db" --env="ZS_DBUser=zabbix" --env="ZS_DBPassword=STRONGPASS" monitoringartist/zabbix-xxl:latest
Wait a few (+/- 10 minutes) minutes and the zabbix will be available to you, using Admin as user and zabbix as password.
I have noticed that browsing my Zabbix webpage, there was a google tracker active which can be disabled within the container environment parameter : XXL_analytics = false. It’s on by default. Just that you know.
A year ago I decided that my current Synology DS1815+ was ready to take on some extra ram. Factory delivered, the nas only has 2GB of ram, which is not much. Especially when you want to use the SSD cache feature, the minimal ram needed was 6GB. So I upgraded it;)
Now that I have discovered Docker, which can be memory intensive at times (using Zabbix containers) it was time to further upgrade the ram. And although Synology stated that only the maximum of 6GB ram is supported I wandered around the internetz and found out it is possible to upgrade the ram to 16GB.
Continue reading Synology DS1815+ 16GB ram upgrade
Yet Another Zabbix Dashboard 🙂
Build with Php, it gets the active triggers from certain groups. Tested in 2.2.x and 3.0.x. Php Api is included.
Your Company Trigger Web
Get it from Github here, fork and improve it. Happy dashing.