Recently I installed a Zabbix 7.0 proxy on a remote rental FreeBSD virtual server of mine. Why?
To give Zabbix 7.0 proxy some hard time
I do not envy my new proxy. If I would be a piece of software, I really would not want to be it. No, not because it would be challenging -- no, this one must be the most bored proxy of all time. It doesn't have too much to do, other than now it's testing this blog and few other websites instead of my home Raspberry Pi 4 doing that.
But that does not mean that the proxy will have any smooth sailing in its horizon. For now, I'll let it run in peace, just to see that the 7.0 proxy itself is stable on FreeBSD. So far so good, it's been running for many days already without any issues.
In phase 2, beginning next week, I'll start to cause surprise issues for it, including but not limited to:
- complete blackout between the proxy and my Zabbix server
- random slowness in the network connection between the proxy and the server
- random network delays in the network connectivity
- random packet loss
To try out the new proxy memory/hybrid modes
As the new Zabbix 7.0 proxy comes with pure memory mode where it does not touch the disk at all, and with the hybrid mode that only uses disk if the specified RAM limits are not enough, of course that needs to be tested. For now my proxy runs in hybrid mode.
Because I can
What would my home monitoring kingdom be without at least one proxy? Less of a kingdom. That's why I also do have another proxy, but that's running on my nearby Linux laptop for monitoring the weird network I have dedicated for its virtual machines... that will be a story for another time.
