It's really nice to see the effort that's being made. It's unfortunate that I'm going to be turning off the Xymon server at work in the very near future. We got bought by another company and they use LogicMonitor so Xymon is going.
I am seriously thinking about deploying it on a VM at home though to monitor my proxmox cluster and be able to get graphs for drive temps and such.
If I move job and they don't have something decent I'll be trying to get Xymon in again because as a Linux admin I find it an incredibly useful tool.
Thanks for all the efforts going on to get it progressing again and I look forward to hopefully suing it again in a future role and at the least probably using it at home.
I'm not sure how many years it is now but I think it's well over 10 years I've been using it. We started on 4.3.4 so it could well be 15 years.
Neil
Neil Simmonds
Senior Platform & Middleware Engineer (Unix)
[cid:fgfs_e04c0205-c635-4f54-817e-d1a70ae03721.jpg]
PHONE
0344 245 9200
ADDRESS
Unit A Brook Park East, NG20 8RY
Credit is provided by Frasers Group Financial Services Limited (Registered Company no. 00718151), which is authorised and regulated by the Financial Conduct Authority (FRN 311908) for consumer credit and general insurance and a member of the Finance and Leasing Association. Frasers Group Financial Services Limited is registered in England and its registered office is: Express House, Petre Road, Clayton Business Park, Accrington, Lancashire, BB5 5JB. For regulated payment services, Frasers Group Financial Services Limited is a payment agent of Transact Payments Limited, a company authorised and regulated by the Gibraltar Financial Services Commission as an electronic money institution. Transact Payments Limited, a company incorporated in Gibraltar (No 108217). Registered address 6.20 World Trade Center, 6 Bayside Road, Gibraltar, GX11 1AA.
Disclaimer | Frasers Group<https://frasers.group/legal/disclaimer>
From: Bruno Manzoni via Xymon <xymon@xymon.com> Sent: Thursday, May 28, 2026 08:56 To: xymon@xymon.com <xymon@xymon.com> Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch> Subject: [Xymon] Thoughts on the new Xymon organization - feedback appreciated
Hi all,
First of all, many thanks to everyone involved in the new Xymon organization and the recent work around the project. A lot of effort has clearly gone into modernizing and stabilizing the codebase while still preserving the spirit and simplicity of Xymon.
- The new governance model is a very positive step for the project:
The fact that at least two people are now involved in validating and merging changes gives much more legitimacy and long-term stability to the project. It certainly slows things down a bit, but for infrastructure software this is probably the correct tradeoff. It reduces the risk of unilateral decisions and helps keep the technical direction coherent.
- The modernization effort is also going in the right direction.
One major goal of the new organization is bringing Xymon back to a stable and maintainable upstream state, while progressively reintegrating improvements that historically existed only in downstream FreeBSD and Debian repositories (and some in the 4.4 alpha branch).
The work achieved so far in this direction is very encouraging. Several important steps have already been achieved:
- GitHub Actions now automatically builds and validates Xymon across multiple platforms,
- many Linux, FreeBSD, NetBSD, and pkgsrc portability and build issues were fixed upstream,
- parser cleanup and hardening improved robustness,
- several memory leaks and stability issues were corrected.
As many changes have already been completed, the project is progressively moving toward a new “ready to release” phase, with a growing number of downstream fixes already consolidated upstream, even if the work is not fully completed yet. It may be better to iterate additional fixes in future releases instead of trying to consolidate everything at once.
This first release will also impact Roland and Mark as Debian and FreeBSD maintainers, so it should happen when they feel ready, as they will also need to prepare and publish updated versions on their side.
Keeping the current focus on reducing historical technical debt and reintegrating long-standing downstream work upstream still appears to be the correct priority for now.
- That said, there are still some weak points:
- documentation is still fragmented between SourceForge, mailing lists, distro patches, wiki pages, and GitHub discussions,
- the maintainer pool is still relatively small, which can slow reviews and create some continuity risk,
- and the project still lacks a clearly centralized long-term roadmap defining modernization priorities and release direction.
Overall though, the direction feels healthy, pragmatic, and technically credible.
- It would be very interesting to hear what you think as well:
- What could still be improved?
- What is currently missing?
- How could more people become involved?
- And what should the priorities be for the next phases of the project?
Bruno
