opentelemetry-java VS Zabbix

After doing some research it appears this class references internal packages and therefore "makes it unusable for modern Java apps" (https://github.com/prometheus/client_java/issues/533 , https://github.com/open-telemetry/opentelemetry-java/issues/4192)

For monitoring: If you want to go the open source route, the open telemetry ecosystem is booming. You could use the open telemetry java agent along with their collector, and then use Elastic APM, which could give you a good starting point. Here is a small example project I found on github that was fun to play around with and explore the capabilities of a setup like this: https://github.com/riferrei/otel-with-apache-pulsar

OpenTelemetry and Java Flight Recorder (JFR) cover most bases. Use the OpenTelemetry Java agent if you want auto-instrumentation or just the APIs if you want to do your own instrumentation.

opentelemetry-java - contains components for manual instrumentation as well as the API and SDK.

opentelemetry-java This repo is the main OpenTelemetry Java SDK and provides components for manual instrumentation. Top-level components include OpenTelemetry API, extensions, SDK, bridge layers for OpenTracing and OpenCensus.

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.

Look at setting up Zabbix (https://www.zabbix.com/) you can then do ping and latency tests to key hosts/endpoints and get packet loss and other variables in a graphical format. Also will allow you to setup monitoring to alert when there are known issues.

Check out Zabbix. Similar to something like PRTG (I see was already mentioned) but it is a free solution. Only cost is setup time and infrastructure.

now if its more metric data you are using and want to do APM, prometheus is your man https://prometheus.io/, want to make prometheus your full time job? deploy cortex https://cortexmetrics.io/, honorable mention in the metrics space, Zabbix, https://www.zabbix.com/ I've seen use cases of zabbix going way beyond its intended use its a fantastic tool

- NMS / NPM: NetXMS, Zabbix, LibreNMS, PRTG - NCM, updates, automation: Unimus - IaC / automation: Ansible - DCIM / IPAM: NetBox - IPAM / DDI: Infoblox