From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: [PATCH v3 0/5] zabbix_agentd: Update to v5.0.20 (LTS) and more
Date: Thu, 10 Feb 2022 00:26:26 +0100 [thread overview]
Message-ID: <20220209232631.14673-1-robin.roevens@disroot.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2525 bytes --]
Hi all
A new take on updating current zabbix_agentd 4.2.6 to latest LTS
version. This set updates the agent version, fixes a few problems with
the original addon and adds a few ipfire-specific metrics for
the user to monitor out of the box (which I will document on the wiki
when the patch-set is accepted).
The differences with the previous patch submission are:
- patch 1: update to v5.0.20
- patch 2:
- In the previous version the correct modules dir was commented
out in the rootfile and was manually removed in the uninstall script if
it was not empty. But since it is also included in the backup I figured
it can be removed always by remove_files so I kept it in the rootfile
now.
- Checks before creating dirs are added in install script to see if
dir is not already existing (like most other addons seem to do)
- Function extract_backup_includes was not called in update.sh script
causing possible scenarios where those includes are not present when
backup needs to be taken or restored.
- patch 3: Made sure to remove all configfiles upon uninstall as
everything is in the backup. Also made sure that the ipfire supplied
userparameter_pakfire.conf file is not added in addon-backup hence
correctly updated on pak update.
- patch 4: Is a small new patch to default the zabbix agent to listen
only on GREEN as that is probably where the user's Zabbix server is
and is a safer default than listening on all interfaces.
- patch 5: was formerly patch4.
- Grouped all ipfire (non-pakfire) related metrics in a single config
file for simplicity.
- Replaced the previous problematic iptables related metric and sudo
rights with the renewed and safer getipstats binary.
- Removed the services related metrics and perl script for now as we
first need to have the new services metadata in the pak's and
related pakfire functions so that I don't need to copy the bad code
from services.cgi as I did before.
- Added 2 new metrics: number of active dhcp leases and number of
captive portal users. Those where contributed by StackKorora on
my Zabbix template for IPFire on github.
As it was almost a year ago, previous patch submission and discussion
can be found here:
https://lists.ipfire.org/pipermail/development/2021-April/009872.html
I hope I addressed all concerns there where on the previous submission.
Regards
Robin
--
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.
next reply other threads:[~2022-02-09 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 23:26 Robin Roevens [this message]
2022-02-09 23:26 ` [PATCH v3 1/5] zabbix_agentd: Update to v5.0.20 (LTS) Robin Roevens
2022-02-15 13:22 ` Michael Tremer
2022-02-16 23:35 ` Robin Roevens
2022-02-20 18:10 ` Michael Tremer
2022-02-20 22:18 ` Robin Roevens
2022-02-21 11:41 ` Michael Tremer
2022-02-21 23:48 ` Robin Roevens
2022-03-01 14:02 ` Michael Tremer
2022-02-09 23:26 ` [PATCH v3 2/5] zabbix_agentd: Fix agent modules dir and few minor bugs Robin Roevens
2022-02-09 23:26 ` [PATCH v3 3/5] zabbix_agentd: Better configfile handling during update Robin Roevens
2022-02-09 23:26 ` [PATCH v3 4/5] zabbix_agentd: By default only listen on GREEN ip Robin Roevens
2022-02-09 23:26 ` [PATCH v3 5/5] zabbix_agentd: Add IPFire specific userparameters Robin Roevens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220209232631.14673-1-robin.roevens@disroot.org \
--to=robin.roevens@disroot.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox