From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: Interested in maintaining zabbix addon package
Date: Sat, 27 Mar 2021 00:13:54 +0100 [thread overview]
Message-ID: <1a94488fff57c194e9cb4aabb18559b8be82dfe9.camel@filekeeper.sicho.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 2240 bytes --]
Hi all
I'm Robin, living in Belgium and a daily administrator of Zabbix both
professionally and at home. I use linux on all my computers, mainly
openSUSE, and administer RHEL based linux servers as a profession. Used
Gentoo, Debian, Slackware, Redhat, Mandrake etc many many years ago..
I have been using IPFire also for many years now, coming from
Smoothwall and IPcop, first in a VM on my home server, currently on an
IPFire appliance from Lightning Wire, so evidently I like monitoring my
appliance using Zabbix.
Hence I wrote a Zabbix Template to monitor and alert on IPFire specific
metrics (https://github.com/RobinR1/zbx-template-ipfire) and had
recently added a suggestion in the IPFire wiki - zabbix addon page to
use my template.
In response to my edit, Alexander Koch added a notice to that page that
the current Zabbix IPFire addon was no longer maintained.
As an experienced user of both I may be interested in taking up the
role as package maintainer for the zabbix addon in IPFire.
I created packages before using Suse's OBS but never officially
maintained ones, so this would be my first, and with a currently
'unknown' technology for me (Pakfire).
I started by reading the info available on the IPFire wiki and found
https://wiki.ipfire.org/devel/ipfire-2-x/addon-howto as, I think, the
most current documentation on how to build packages on IPFire 2.x.
Other Pakfire-related info seems to be mainly for IPFire 3.
The required build environment is currently building on my PC, so I
hope to start working on it soon.
However at the end of that document, the instructions as of how to
actually submit the package for inclusion in IPFire seems to be
missing.
So I will try to update the zabbix agent using this build env as soon
as it is ready, and for as far as I currently understand it, I will
then probably end up with changes in lfs/zabbix_agentd and
config/zabbix_agentd/, which I then just have to submit here as a patch
following the instructions on ipfire wiki about submitting patches?
Anyway, this was my introduction, and I hope I will be of some help in
this great project.
Regards
Robin
--
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.
next reply other threads:[~2021-03-26 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 23:13 Robin Roevens [this message]
2021-03-27 7:30 ` Adolf Belka
2021-03-29 20:38 ` Michael Tremer
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=1a94488fff57c194e9cb4aabb18559b8be82dfe9.camel@filekeeper.sicho.home \
--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