JaCoCo VS Zabbix

I will use here JaCoCo, where also the JaCoCo-Maven-lugin exists for the usage in your Maven builds. This article will show how to configure the code coverage to finally get the results for unit- and integration-tests.

In protection rules, I added build workflow in Require status checks to pass before merging. This is to ensure that before merging code in master branch, build should run successfully. I also added Jacoco Code Coverage to make sure that enough unit tests are available in project and Detekt to make sure that code in project is readable. I added them in build configuration. Even if one of them gives error, build will fail. Whenever, someone push code in pull request, build action will run and check if build is running successfully or not.

Code coverage analysis tools quantify the amount of tested code, serving as a valuable tool to inform on code structure and testing related decisions. We will make use of JaCoCo, JaCoCo produces reports on multiple kinds of code coverage metrics including instructions, line and branch coverage.

One specific example where I regularly use a profile in this way is for configuring code coverage. In all of my Java projects, I use JaCoCo for generating code coverage reports. I use JaCoCo during the Maven test phase. However, while developing I find it useful at times to exclude coverage reporting to reduce the build time. But in my CI/CD workflows in GitHub Actions, I activate the code coverage profile during pull-requests and pushes to the default branch. For pull-requests, my GitHub Actions workflow comments the code coverage on the PR and uploads the coverage report as a workflow artifact, where I can inspect it as necessary. And during a push to the default branch, my workflow updates coverage badges to keep them up to date with the current state of the default branch. I can also activate the code coverage profile locally while developing, such as prior to submitting a pull-request, to ensure that I didn't miss testing something.

In Unit tests, individual software code components are checked if it is working as expected or not. Unit tests isolate a function or module of code and verify its correctness. We can use tools like JaCoCo for Java and Mocha, and Jasmine for NodeJS to generate unit test reports. We can also send these reports to SonarQube which shows us code coverage and the percentage of your code covered by your test cases.

And there is the original jacoco/jacoco: (0.8.7: released this on May 5, 2021), but it's for Java. I'm not sure if we can use it with multiple flavors on Android.

Make sure to also update to Jacoco 0.8.7 to avoid test issues: https://github.com/jacoco/jacoco/releases/tag/v0.8.7

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