Thruk VS Zabbix

There are also a bunch of web interfaces available such as Thruk

I switched from Nagios to Naemon (a fork of Nagios), the migration is super easy, you don't even have to be nonweldable at all in linux to achieve it, and almost all the config files are compatible. It's also compatible with all the Nagios plugins, but the GUI is way better than the one on Nagios (is called Thruk https://www.thruk.org)

Fast forward 12 years and I have Icinga2 collectors in each datacenter using check_by_ssh to run check_systemd, all front-ended by Thruk. The TIG stack is something on my list of things to look into at some point, but with Dynatrace available to do all the fancy application monitoring, there's no rush.

For alerting for Linux systems, I use Icinga with check_ssh and check_systemd (caveat: distributed primarily on PyPI) with Thruk as the single pane of glass front-end to per-datacenter installations of Icinga.

But there are also other solutions out there that can manage the configs for you such as Thruk or Adagios.

A powerful open source SolarWinds alternative that combines modern features with enterprise-grade scalability. Zabbix provides comprehensive monitoring capabilities while maintaining the flexibility of an open-source solution.

Zabbix is an open-source enterprise-level monitoring solution that can be considered a robust prometheus alternative.

Zabbix is an open source software that monitors numerous parameters of a network and the health and integrity of servers, virtual machines, applications, services, databases, websites, the cloud and more. Zabbix uses a flexible notification mechanism that allows users to configure email-based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualization features based on the stored data. This makes Zabbix ideal for capacity planning.

GitHub: Zabbix GitHub Repository

Zabbix

Zabbix is a comprehensive open-source monitoring solution designed for real-time monitoring and management of various network components, such as servers, networks, and applications. It excels in data collection and processing, enabling proactive monitoring for early issue detection and resolution.

The PHP core package is offered as pre-compiled binary via Ports packages system. In addition, important softwares such as extensions, Composer and PECL libraries are available. So are frameworks such as NextCloud and Zabbix.

Prometheus is a great way to go, however you need to invest time in writing all the alerts. This was a daunting task for us, because we have too many vendors and device types.. we instead went with zabbix, which is a free open source platform similar to Orion. Quite easy to setup. All the device templates for monitoring alerting are provided by the community. There is a grafana plugin which integrates with Zabbix, so you can build beautiful dashboards in grafana while using the polling and alerting logic in zabbix. You can also use grafana OnCall via a zabbix integration. Phase1: You could move to zabbix. Realize cost savings without investing time. Phase2: learn and work on moving things to Prometheus slowly. edit: added links and some rewording

Setup Zabbix (https://www.zabbix.com/) and use SNMP (search for a template for your switches, chances are someone has created one) to pull throughput data from the switchport your proxies are connected to. This will graph them for you on a continual basis, you can then setup some triggers (alerts) that will flag over-utilization (say >80Mbps) for you, can generate an email or SMS alert based on that or just see it in the dashboard.