Project direction and next steps - feedback requested 🔗 link

Hi all,

Quick follow-up.

So far, there seems to be agreement that:

• 4.3 is the current production version.
• 4.4 is unfinished and experimental.
• The main blocker is the lack of a shared Git workflow.

To move forward, feedback is needed, and input from everyone is welcome.
Feedback from long-time maintainers and contributors would be especially appreciated (JC Cleaver in particular; Henrik Storner is already involved).

In short:

• Who is willing to help?
• Is https://github.com/xymon-monitoring/xymon-svn-mirror a good place to move forward?
• If not, is there a better proposal (for example under https://github.com/xymon-monitoring)?
• What should be the next concrete step?

Short replies are perfectly fine.

I have experience with Github actions for other reasons… I could probably figure out the tags.  It would be great if it could automatically build the RPMs, tarballs, debs, or whatever other packaging is necessary on each release so there’s a real pipeline.  I don’t have experience with building packages though. 

 

Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate 
(XXX) XXX-XXXX | X-XXX-XXX-XXXX | user-9678697f1438@xymon.invalid
One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com
facebook.com/lazboy  | instagram.com/lazboy | youtube.com/lazboy

From: Nicola <user-2c63804b6921@xymon.invalid>
Sent: Thursday, January 15, 2026 12:44 PM
To: Xymon mailinglist <xymon@xymon.com>
Cc: Bruno Manzoni <user-81df5df13c04@xymon.invalid>
Subject: [Xymon] Re: Project direction and next steps - feedback requested

 

You don't often get email from user-2c63804b6921@xymon.invalid. Learn why this is important

Hi, I am willing to help (unfortunately my C skills are at the "hello world" level, from university studies).

My votes:

* rename (or duplicate) `xymon-svn-mirror` to `xymon`

* link the Xymon website to the new repo, instead of SVN/SourceForge

* incorporate the pending patches and publish a 4.3.31 (or maybe 4.3.32, since there's already a branch for .31) version, so we can also measure the interest

* enable github actions if anyone has experience to publish releases when a new tag is submitted

* either backport the needful from 4.4alpha or start testing fixes in there

Nicola

Mastodon: @user-3ad00cf7a0c9@xymon.invalid

 

 

Il giorno gio 15 gen 2026 alle ore 06:47 Bruno Manzoni via Xymon <xymon@xymon.com> ha scritto:

Hi all,

Quick follow-up.

So far, there seems to be agreement that:

· 4.3 is the current production version.

· 4.4 is unfinished and experimental.

· The main blocker is the lack of a shared Git workflow.

To move forward, feedback is needed, and input from everyone is welcome.
Feedback from long-time maintainers and contributors would be especially appreciated (JC Cleaver in particular; Henrik Storner is already involved).

In short:

· Who is willing to help?

· Is https://github.com/xymon-monitoring/xymon-svn-mirror a good place to move forward?

· If not, is there a better proposal (for example under https://github.com/xymon-monitoring)?

· What should be the next concrete step?

Short replies are perfectly fine.

Thanks,
runo

 

On 1/15/26 10:31, Stef Coene wrote:
> Hi,
>
> I also want to help. I'm not a C programmer, but I can help with
> documentation and testing.
>
> I also have some small patches and enhancements that I want to contribute.
>
> Like wget and curl drop-in replacement scripts for the xymon binary for
> encrypted https communication between client and server.
>
> I also have a patch to allow for a filter in the graphs so you can easy
> filter the data you want to display.
> And a patch for a list of rrd files so you can create graphs with
> exactly the data you want. We are using this to display disks graphs
> with all the disks for an AIX volume group. The URL is generated with an
> external scripts to include the needed disks.
>
>

Stef, I think you posted about these on the mailing list a long time ago
and I found them when I was going through mailing list history since the
last release. Very very interested in these additions too. The trick to
submit the client data over HTTPS was very clever -- I was about to
build that myself.

I have not yet started using RHEL 10 but I did find the following earlier ...

https://extras.getpagespeed.com/redhat/10/x86_64/repoview/pcre.html

Thanks,
Matt

On Thu, Jan 15, 2026 at 4:04 PM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote:

Would it be practical to implement network encryption for IPv4, then circle back for IPv6 later?  I don't really know what's involved in that, but I have several thousand clients using my own curl script to report, because I'm required to use encrypted connections.

I tried compiling on RHEL10 last week.  There's a problem there to address - pcre has been deprecated and replaced with pcre2.  The old pcre is still present up to RHEL9, but it's missing in 10.  I;ll take a look and see what I can do with it, but I'm not a hot-shot programmer so it might take a while.

Ralph Mitchell

On Thu, Jan 15, 2026 at 2:54 PM Mark Felder via Xymon <xymon@xymon.com> wrote:

On 1/15/26 10:31, Stef Coene wrote:
> Hi,
>
> I also want to help. I'm not a C programmer, but I can help with
> documentation and testing.
>
> I also have some small patches and enhancements that I want to contribute.
>
> Like wget and curl drop-in replacement scripts for the xymon binary for
> encrypted https communication between client and server.
>
> I also have a patch to allow for a filter in the graphs so you can easy
> filter the data you want to display.
> And a patch for a list of rrd files so you can create graphs with
> exactly the data you want. We are using this to display disks graphs
> with all the disks for an AIX volume group. The URL is generated with an
> external scripts to include the needed disks.
>
>

Stef, I think you posted about these on the mailing list a long time ago
and I found them when I was going through mailing list history since the
last release. Very very interested in these additions too. The trick to
submit the client data over HTTPS was very clever -- I was about to
build that myself.
xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

--

On 1/15/26 13:04, Ralph M wrote:
> Would it be practical to implement network encryption for IPv4, then
> circle back for IPv6 later?  I don't really know what's involved in
> that, but I have several thousand clients using my own curl script to
> report, because I'm required to use encrypted connections.
>
> I tried compiling on RHEL10 last week.  There's a problem there to
> address - pcre has been deprecated and replaced with pcre2.  The old
> pcre is still present up to RHEL9, but it's missing in 10.  I;ll take a
> look and see what I can do with it, but I'm not a hot-shot programmer so
> it might take a while.
>

Don't worry, the Debian folks already have a patch that changes Xymon to
use PCRE2. We'll get that merged.

Mark