Hi all, 

I created the https://github.com/xymon-monitoring/ repository, which is intended to serve as a potential Git repository home for Xymon. It contains a curated mirror of the SourceForge repository, as well as other related repositories.

This effort is currently incomplete and faces several challenges. The original goal was to produce a clean and understandable representation of the SourceForge history while preserving it accurately. However, I am not yet sure how to properly handle the 4.4 branching from SourceForge, which makes the repository difficult to follow and messy from that point onward. My inability to tackle this problem led me to stop work at that stage. As a result, no further work has been done to improve the repository’s structure or visibility beyond that point.

More fundamentally, I realize that several high-level questions need to be answered before any technical progress can reasonably continue:

1. What concrete problem does this initiative actually solve?
   What issue does this repository aim to address for the Xymon project or community (visibility, fragmentation, contribution workflow, long-term continuity, etc.)?

2. Does the Xymon community want this repository to become the new development home?
   In other words, is there interest in moving active development here, or should this repository remain a mirror or coordination space only?

3. Who is willing to help make this a reality?
   Who can contribute time and expertise to resolve the history and branching issues, help define a clear direction, and participate in maintaining the repository?

Until these questions are clarified, I currently lack a clear vision for how to turn this repository into something valuable for both present and future use.

I would appreciate any help, guidance, or feedback from the community.

Bruno

Add one of the people using Xymon on FreeBSD for quite a while now, I want to thank you for all your work!  In fact, I might have even been using it for over 15 years, now that I think about it.  It has benefited me, my current employer, and my previous employer.

Jaime Kikpole Director of Technology Ichabod Crane Central School District (518) 758-7575, x5425

On Mon, Jan 12, 2026, 8:58 PM Mark Felder via Xymon <xymon@xymon.com> wrote:

Hi all,

Is Henrik or JC Cleaver still working on Xymon? I am still the
maintainer of the packages on FreeBSD and have been crawling through the
mailing list archives, Debian packages, etc and have accumulated a lot
of patches that have never made it into a Xymon release. I'm aware
there's an Alpha of 4.4 with IPv6 support and a lot of changes too, but
it's very much unfinished last I saw (IPv6 for client-server but
Xymonnet not refactored to be able to execute IPv6 tests IIRC...)

I'd like to light the fire again. Xymon is something special and I keep
coming back to it. It's just the perfect amount of simplicity and power
to make monitoring things easy.

I have privately converted the Xymon source repo to Git much like has
been done at https://github.com/xymon-monitoring/ but I've preserved all
the tags and backdated them properly. My own list of changes is growing:

- Fixed buffer overflow in trends which causes it to stop showing graphs
if you have too many

- Fix FreeBSD graphing of vmstat/CPU utilization (has been broken for
many years)

- Custom graphs docs do not match reality -- you can't submit NCV or
trends data to be processed into RRD files and then display them on any
status page you want. I've fixed this; you can put custom graphs on any
status page now, not just ones that already have graphs

- added ALPN support to xymmonnet so you can create custom protocols to
do things like test IMAP through Nginx HTTPS/443 port

- WIP -- debugging DS rule processing in analysis.cfg which doesn't obey
"first match" like everything else, hope to have this nailed down soon


Please reach out...


Mark
_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com