From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: [PATCH 0/2] zabbix_agentd: Update to 6.0.19 + new ovpn metrics
Date: Wed, 19 Jul 2023 22:29:16 +0200 [thread overview]
Message-ID: <20230719204140.29157-1-robin.roevens@disroot.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Hi all
A new version of the zabbix_agentd LTS, containing a few bug fixes.
As an additional patch I have added 2 new metrics (items) to the agent
for the user to check if they want:
- ipfire.ovpn.clients.discovery
which returns a JSON string with all configured ovpn clients from
/var/ipfire/ovpn/ovpnconfig. This can be used by Zabbix to automatically
discover any configured openvpn clients and start monitoring them.
- ipfire.ovpn.statusreport.gget
which returns a JSON string with the parsed content of
/var/run/ovpnserver.log. This can be used by Zabbix to effectively
monitor discovered configured clients: bytes in/out, connection state,
last activity, remote IP, VPN IP.
This will of course be documented on the wiki when the patch is merged.
For reference, the download link for the zabbix_agentd source used in
this patch:
https://cdn.zabbix.com/zabbix/sources/stable/6.0/zabbix-6.0.19.tar.gz
Regards
Robin
--
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.
next reply other threads:[~2023-07-19 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 20:29 Robin Roevens [this message]
2023-07-19 20:29 ` [PATCH 1/2] zabbix_agentd: Update to 6.0.19 (LTS) Robin Roevens
2023-07-19 20:29 ` [PATCH 2/2] zabbix_agentd: Add ovpn monitoring items 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=20230719204140.29157-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