Is this thing on?
list Galen Johnson
Nothing since May seems a bit suss. =G=
list Ryan Novosielski
Just a quiet mature product, I suppose. Sent from my iPhone On Aug 12, 2023, at 22:01, Galen Johnson <user-fc632e705d24@xymon.invalid> wrote: ? Nothing since May seems a bit suss. =G=
list Kris Springer
Yes, we're still out here. Thank You, Systems Admin I/O Network Administration user-a65af99e49c9@xymon.invalid https://www.ionetworkadmin.com On 8/12/23 20:00, Galen Johnson wrote:
Nothing since May seems a bit suss. =G=
list Ralph Mitchell
I wish encryption for sending reports had come along before it all went quiet. Ralph Mitchell On Sat, Aug 12, 2023 at 10:55?PM Ryan Novosielski via Xymon <xymon at xymon.com> wrote:
---------- Forwarded message ---------- From: Ryan Novosielski <user-46c89e614701@xymon.invalid> To: Galen Johnson <user-fc632e705d24@xymon.invalid> Cc: "xymon >> xymon at xymon.com" <xymon at xymon.com> Bcc: Date: Sun, 13 Aug 2023 02:55:33 +0000 Subject: Re: [Xymon] Is this thing on?
▸
Just a quiet mature product, I suppose.
Sent from my iPhone
On Aug 12, 2023, at 22:01, Galen Johnson <user-fc632e705d24@xymon.invalid> wrote:
?
Nothing since May seems a bit suss.
=G=
---------- Forwarded message ----------
From: Ryan Novosielski via Xymon <xymon at xymon.com>
To: Galen Johnson <user-fc632e705d24@xymon.invalid>
Cc: "xymon >> xymon at xymon.com" <xymon at xymon.com>
Bcc:
Date: Sun, 13 Aug 2023 02:55:33 +0000
Subject: Re: [Xymon] Is this thing on?
list Christoph Zechner
▸
On 13/08/2023 05:13, Ralph M wrote:
I wish encryption for sending reports had come along before it all went quiet.
You could always use stunnel if your OS(es) support it. Not the perfect solution, but a good workaround. Cheers Christoph
Ralph Mitchell
On Sat, Aug 12, 2023 at 10:55?PM Ryan Novosielski via Xymon <xymon at xymon.com <mailto:xymon at xymon.com>> wrote:
---------- Forwarded message ----------
From:?Ryan Novosielski <user-46c89e614701@xymon.invalid
To:?Galen Johnson <user-fc632e705d24@xymon.invalid <mailto:user-fc632e705d24@xymon.invalid>>
Cc:?"xymon >> xymon at xymon.com <mailto:xymon at xymon.com>"
<xymon at xymon.com <mailto:xymon at xymon.com>>
Bcc:
Date:?Sun, 13 Aug 2023 02:55:33 +0000
Subject:?Re: [Xymon] Is this thing on?
▸
Just a quiet mature product, I suppose. Sent from my iPhoneOn Aug 12, 2023, at 22:01, Galen Johnson <user-fc632e705d24@xymon.invalid <mailto:user-fc632e705d24@xymon.invalid>> wrote: ? Nothing since May seems a bit suss. =G= <---------- Forwarded message ----------
From:?Ryan Novosielski via Xymon <xymon at xymon.com
<mailto:xymon at xymon.com>>
To:?Galen Johnson <user-fc632e705d24@xymon.invalid <mailto:user-fc632e705d24@xymon.invalid>>
Cc:?"xymon >> xymon at xymon.com <mailto:xymon at xymon.com>"
<xymon at xymon.com <mailto:xymon at xymon.com>>
Bcc:
Date:?Sun, 13 Aug 2023 02:55:33 +0000
Subject:?Re: [Xymon] Is this thing on?
<
list Neil Simmonds
Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. From: Xymon <xymon-bounces at xymon.com> On Behalf Of Galen Johnson Sent: Sunday, August 13, 2023 3:01 AM To: xymon >> xymon at xymon.com <xymon at xymon.com> Subject: [Xymon] Is this thing on? [CAUTION] This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk and clicking ?Contact Us?.
list Scot Kreienkamp
No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | ? (XXX) XXX-XXXX | | ? X-XXX-XXX-XXXX | ? user-9678697f1438@xymon.invalid www.la-z-boy.com<http://www.la-z-boy.com>; | facebook.com/lazboy<http://facebook.com/lazboy>; | twitter.com/lazboy<http://twitter.com/lazboy>; | youtube.com/lazboy<http://youtube.com/lazboy>; [cid:smallerlzbonlylogoforsign_b8ca06bf-75b5-4619-8093-c9418c455597.png]
▸
From: Xymon <xymon-bounces at xymon.com> On Behalf Of Neil Simmonds
Sent: Monday, August 14, 2023 5:29 AM
To: xymon >> xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] Is this thing on?
Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that.
It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool.
From: Xymon <xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>> On Behalf Of Galen Johnson
Sent: Sunday, August 13, 2023 3:01 AM
To: xymon >> xymon at xymon.com<mailto:xymon at xymon.com> <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: [Xymon] Is this thing on?
[CAUTION] This is an external email. Do not click links or open any attachments unless you are sure they are safe.
Nothing since May seems a bit suss.
=G=
Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE.
NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk and clicking ?Contact Us?.
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
list Ralph Mitchell
I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp <
▸
user-9678697f1438@xymon.invalid> wrote:
No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | * user-9678697f1438@xymon.invalid
www.la-z-boy.com | facebook.com/lazboy | twitter.com/lazboy |
youtube.com/lazboy
[image: Smaller LZB Only Logo for Sign.png]
▸
*From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds
*Sent:* Monday, August 14, 2023 5:29 AM
*To:* xymon >> xymon at xymon.com <xymon at xymon.com>
*Subject:* Re: [Xymon] Is this thing on?
Is Xymon dying? No new release since 2019, There was a roadmap in 2015
that mention Versions 4.4 up to 5 but nothing seems to have moved on that.
It feels like Xymon has become a static project that?s going to fade away.
That would be a shame as I for one think it?s a great tool.
*From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson
*Sent:* Sunday, August 13, 2023 3:01 AM
*To:* xymon >> xymon at xymon.com <xymon at xymon.com>
*Subject:* [Xymon] Is this thing on?
*[CAUTION]* This is an external email. Do not click links or open any
attachments unless you are sure they are safe.
Nothing since May seems a bit suss.
=G=
Studio is a trading name of Studio Retail Trading Limited (Company no.
03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are
registered in England and their registered office is: Church Bridge House
Henry Street Accrington BB5 4EE.
*NOTE: This email and any information contained within or attached in a
separate file is confidential and intended solely for the Individual to
whom it is addressed. The information or data included is solely for the
purpose indicated or previously agreed. Any information or data included
with this e-mail remains the property of Studio Retail Trading Ltd or
Frasers Group Financial Services Ltd. The recipient will refrain from
utilising the information for any purpose other than that indicated and
upon request will destroy the information and remove it from their records.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of Studio Retail Trading Ltd or Frasers Group
Financial Services Ltd. If you are not the intended recipient, be advised
that you have received this email in error and that any use, dissemination,
forwarding, printing, or copying of this email is strictly prohibited. No
warranties or assurances are made in relation to the safety and content of
this e-mail and any attachments. No liability is accepted for any
consequences arising from it. Studio Retail Trading Ltd and Frasers Group
Financial Services Ltd reserve the right to monitor all e-mail
communications through their internal and external networks. If you have
received this email in error please let us know. You can find our availablecontact details by going to help.studio.co.uk <http://help.studio.co.uk>;
▸
and clicking ?Contact Us?.*
This message is intended only for the individual or entity to which it is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the intended
recipient, you are strictly prohibited from disseminating or distributing
this information (other than to the intended recipient) or copying this
information. If you have received this communication in error, please
notify us immediately by e-mail or by telephone at the above number. Thank
you.
list Rod
I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time.
▸
On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote:
I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp < user-9678697f1438@xymon.invalid> wrote:No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | * user-9678697f1438@xymon.invalid www.la-z-boy.com | facebook.com/lazboy | twitter.com/lazboy | youtube.com/lazboy [image: Smaller LZB Only Logo for Sign.png] *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]* This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
list Scot Kreienkamp
I would be OK with contributing some as well?. But that?s not what Xymon needs. Xymon needs caretaker(s) to keep it relevant. That means code updates to fix bugs, adapt it to new OS versions, etc. Otherwise it will fade away to obscurity like many other open source projects. I?m not a coder either, or I would gladly give some time to it. Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | ? (XXX) XXX-XXXX | | ? X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid
▸
From: Rod <user-626df9d20e67@xymon.invalid>
Sent: Monday, August 14, 2023 10:56 AM
To: Ralph M <user-00a5e44c48c0@xymon.invalid>
Cc: Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] Is this thing on?
I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time.
On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid<mailto:user-00a5e44c48c0@xymon.invalid>> wrote:
I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents.
@Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense.
Ralph Mitchell
On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid<mailto:user-9678697f1438@xymon.invalid>> wrote:
No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more.
Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy CorporateOne La-Z-Boy Drive | Monroe, Michigan 48162 | ? (XXX) XXX-XXXX | | ? X-XXX-XXX-XXXX | ? user-9678697f1438@xymon.invalid<mailto:user-9678697f1438@xymon.invalid> www.la-z-boy.com<http://www.la-z-boy.com>; | facebook.com/lazboy<http://facebook.com/lazboy>; | twitter.com/lazboy<http://twitter.com/lazboy>; | youtube.com/lazboy<http://youtube.com/lazboy>; [cid:image001.png at 01D9CE9E.C5C077A0]
▸
From: Xymon <xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>> On Behalf Of Neil Simmonds
Sent: Monday, August 14, 2023 5:29 AM
To: xymon >> xymon at xymon.com<mailto:xymon at xymon.com> <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: Re: [Xymon] Is this thing on?
Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that.
It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool.
From: Xymon <xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>> On Behalf Of Galen Johnson
Sent: Sunday, August 13, 2023 3:01 AM
To: xymon >> xymon at xymon.com<mailto:xymon at xymon.com> <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: [Xymon] Is this thing on?
[CAUTION] This is an external email. Do not click links or open any attachments unless you are sure they are safe.
Nothing since May seems a bit suss.
=G=
Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE.
NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk<http://help.studio.co.uk>; and clicking ?Contact Us?.
▸
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
list James Louis
Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03?AM Scot Kreienkamp <
▸
user-9678697f1438@xymon.invalid> wrote:
I would be OK with contributing some as well?. But that?s not what Xymon needs. Xymon needs caretaker(s) to keep it relevant. That means code updates to fix bugs, adapt it to new OS versions, etc. Otherwise it will fade away to obscurity like many other open source projects. I?m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp < user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | * user-9678697f1438@xymon.invalid www.la-z-boy.com | facebook.com/lazboy | twitter.com/lazboy | youtube.com/lazboy [image: Smaller LZB Only Logo for Sign.png] *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]* This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
--
*Jim Louis \\\\||//// \ ~ ~ / | @ @ |*
*--oOo---(_)---oOo--*
*?The part of life we really live is small. All the rest is not life, but
merely time.?*
list Bruno Manzoni
Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno
▸
On 14.08.2023 18:36, James Louis wrote:Is the Terabithia RPM also dead?
Jim
On Mon, Aug 14, 2023 at 10:03?AM Scot Kreienkamp
<user-9678697f1438@xymon.invalid> wrote:
I would be OK with contributing some as well?. But that?s not what
Xymon needs.? Xymon needs caretaker(s) to keep it relevant.? That
means code updates to fix bugs, adapt it to new OS versions, etc.?
Otherwise it will fade away to obscurity like many other open
source projects.? I?m not a coder either, or I would gladly give
some time to it.
*Scot Kreienkamp?| Senior Linux Systems Engineer | La-Z-Boy Corporate*
One La-Z-Boy Drive | Monroe, Michigan 48162 |( (XXX) XXX-XXXX | |
) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid
*From:* Rod <user-626df9d20e67@xymon.invalid>
*Sent:* Monday, August 14, 2023 10:56 AM
*To:* Ralph M <user-00a5e44c48c0@xymon.invalid>
*Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >>
xymon at xymon.com <xymon at xymon.com>
*Subject:* Re: [Xymon] Is this thing on?
I would like to continue the legacy. I'm not a developer but I'm
willing to pay for hosting space and the domain name to keep it
going for as long as I'm alive. Its kept me employed for a long time.
On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid>
wrote:
I've been using Xymon at several different?employers since it
▸
was BigBrother owned by a couple of guys in Canada.? My
current Senior VP wants Xymon to go away.? He hasn't actually
told me that directly, but I've heard it via another channel.?
We have SolarWinds on some machines, but I've never even seen
the GUI for that.? We're also distributing Oracle Enterprise
Manager (OEM) to a bunch of machines.? I don't know for sure,
but I suspect a contracting company is whispering in my SVP's
ear to sell support for OEM.? In the meantime, my Xymon server
has 878 days uptime and they're still trying to figure out how
to install and configure the OEM agents.? It's going to be
tons of fun watching them try to replace all the little
scripts I've written with OEM equivalents.
@Cristoph - I don't know if I can use stunnel.? It's a
military-related company and there are all kinds of
restrictions that sometimes even make sense.
Ralph Mitchell
On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp
<user-9678697f1438@xymon.invalid> wrote:
No new release since 2019, no activity on the mailing
list, I think it?s safe to say it?s flatlined.? Sad to see
it fade, I?ve been using it for a decade or more.
*Scot Kreienkamp?| Senior Linux Systems Engineer |
La-Z-Boy Corporate*One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX| *user-9678697f1438@xymon.invalid www.la-z-boy.com <http://www.la-z-boy.com>?| facebook.com/lazboy <http://facebook.com/lazboy>??| twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>;
▸
Smaller LZB Only Logo for Sign.png
*From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of
*Neil Simmonds
*Sent:* Monday, August 14, 2023 5:29 AM
*To:* xymon >> xymon at xymon.com <xymon at xymon.com>
*Subject:* Re: [Xymon] Is this thing on?
Is Xymon dying? No new release since 2019, There was a
roadmap in 2015 that mention Versions 4.4 up to 5 but
nothing seems to have moved on that.
It feels like Xymon has become a static project that?s
going to fade away. That would be a shame as I for one
think it?s a great tool.
*From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of
*Galen Johnson
*Sent:* Sunday, August 13, 2023 3:01 AM
*To:* xymon >> xymon at xymon.com <xymon at xymon.com>
*Subject:* [Xymon] Is this thing on?
*[CAUTION]*This is an external email. Do not click links
▸
or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- *Jim Louis ? ? ? ? ? \\\\||//// ? ? ? ? ? \ ~ ~? / ? ? ? ? ? | @ @ | • *--oOo---(_)---oOo-- • /?The part of life we really live is small. All the rest is not life, but merely time.?/
list Kris Springer
I've been using this product since the late 90's when it was called BigBrother, got sold to Quest, was rewritten as Hobbit, had to change it's name, and finally became Xymon. On one hand it's core tools just work and easily do what I need them to do.? On the other hand there's additional features that it doesn't handle easily that we need in modern environments.? In my opinion the competing products have gone overboard with 'additional features' and have bloated products that are missing basic things for the core tools. I have noticed Xymon getting stale for years now and had the idea in the back of my mind for my company to start maintaining it, but that seems like a large undertaking for an Open Source product I didn't create, and currently don't have the staff to do it justice.? I love the product and the community, but if no one will take on this challenge, it will sadly die. https://sourceforge.net/projects/xymon/ What happened to JC and Henrik?? Life gets in the way I guess. Thank You, Kris Springer
▸
Systems Admin I/O Network Administration user-a65af99e49c9@xymon.invalid https://www.ionetworkadmin.com On 8/14/23 10:58, Bruno Manzoni wrote:
Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote:Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well?. But that?s not what Xymon needs. Xymon needs caretaker(s) to keep it relevant.? That means code updates to fix bugs, adapt it to new OS versions, etc.? Otherwise it will fade away to obscurity like many other open source projects.? I?m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp?| Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 |?( (XXX) XXX-XXXX | | ?) X-XXX-XXX-XXXX |? Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different?employers since it was BigBrother owned by a couple of guys in Canada.? My current Senior VP wants Xymon to go away.? He hasn't actually told me that directly, but I've heard it via another channel.? We have SolarWinds on some machines, but I've never even seen the GUI for that.? We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines.? I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM.? In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents.? It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel.? It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined.? Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp?| Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX| *user-9678697f1438@xymon.invalid www.la-z-boy.com <http://www.la-z-boy.com>?| facebook.com/lazboy <http://facebook.com/lazboy>??| twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>; Smaller LZB Only Logo for Sign.png *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]*This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- *Jim Louis ? ? ? ? ? \\\\||//// ? ? ? ? ? \ ~ ~? / ? ? ? ? ? | @ @ | • *--oOo---(_)---oOo-- • /?The part of life we really live is small. All the rest is not life, but merely time.?/
list Tom Schmidt
I have also used Xymon and Big Brother for decades. I contributed to it several times, including several add-on monitors. I am now retired, but I still use Xymon at home to monitor my home network, running it on a Rocky Linux 8.8 install on a small computer. For my home network, I have created some custom monitors for my ASUS mesh router, HP printers, Foscam security cameras, and SolarEdge solar panels. I am a coder so I am willing to help keep Xymon alive. I am willing to share my custom monitors as well to anyone that is interested. Tom Schmidt On Mon, Aug 14, 2023 at 11:07?AM Bruno Manzoni <user-81df5df13c04@xymon.invalid>
▸
wrote:
Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote: Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03?AM Scot Kreienkamp < user-9678697f1438@xymon.invalid> wrote:I would be OK with contributing some as well?. But that?s not what Xymon needs. Xymon needs caretaker(s) to keep it relevant. That means code updates to fix bugs, adapt it to new OS versions, etc. Otherwise it will fade away to obscurity like many other open source projects. I?m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp < user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | * user-9678697f1438@xymon.invalid www.la-z-boy.com | facebook.com/lazboy | twitter.com/lazboy | youtube.com/lazboy [image: Smaller LZB Only Logo for Sign.png] *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]* This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.-- *Jim Louis \\\\||//// \ ~ ~ / | @ @ | * *--oOo---(_)---oOo-- * *?The part of life we really live is small. All the rest is not life, but merely time.?*
Xymon mailing user-d459c9d661b6@xymon.invalid
list Damien Martins
Hi all, As an add-on writer, I'd like Xymon staying alive as long as possible. AFAIK there is one (Tom Schmidt) coder who could work on it, but no one else is proficient in C/C++ ? On my side I can host/admin a website, and a demo platform. I'd be happy to share my experience (18 years since using BigB for the first time), and share some thoughts on possible evolution. Le 14/08/2023 19:42, Tom Schmidt a ?crit?:
▸
I have also used Xymon and Big Brother for decades. I contributed to it several times, including several add-on monitors. I am now retired, but I still use Xymon at home to monitor my home network, running it on a Rocky Linux 8.8 install on a small computer. For my home network, I have created some custom monitors for my ASUS mesh router, HP printers, Foscam security cameras, and SolarEdge solar panels. I am a coder so I am willing to help keep Xymon alive. I am willing to share my custom monitors as well to anyone that is interested. Tom Schmidt On Mon, Aug 14, 2023 at 11:07?AM Bruno Manzoni <user-81df5df13c04@xymon.invalid> wrote:Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote: Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well?. But that?s not what Xymon needs. Xymon needs caretaker(s) to keep it relevant. That means code updates to fix bugs, adapt it to new OS versions, etc. Otherwise it will fade away to obscurity like many other open source projects. I?m not a coder either, or I would gladly give some time to it. Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid From: Rod <user-626df9d20e67@xymon.invalid> Sent: Monday, August 14, 2023 10:56 AM To: Ralph M <user-00a5e44c48c0@xymon.invalid> Cc: Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> Subject: Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | * user-9678697f1438@xymon.invalid
www.la-z-boy.com [1] | facebook.com/lazboy [2] | twitter.com/lazboy [3] | youtube.com/lazboy [4]
▸
From: Xymon <xymon-bounces at xymon.com> On Behalf Of Neil Simmonds Sent: Monday, August 14, 2023 5:29 AM To: xymon >> xymon at xymon.com <xymon at xymon.com> Subject: Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. From: Xymon <xymon-bounces at xymon.com> On Behalf Of Galen Johnson Sent: Sunday, August 13, 2023 3:01 AM To: xymon >> xymon at xymon.com <xymon at xymon.com> Subject: [Xymon] Is this thing on? [CAUTION] This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available
contact details by going to help.studio.co.uk [5] and clicking
▸
?Contact Us?. This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.-- Jim Louis \\\\||//// \ ~ ~ / | @ @ | --oOo---(_)---oOo-- _?The part of life we really live is small. All the rest is not life, but merely time.?_
Links: [1] http://www.la-z-boy.com [2] http://facebook.com/lazboy [3] http://twitter.com/lazboy [4] http://youtube.com/lazboy [5] http://help.studio.co.uk
list Zoltan Forray
I too have worked with Hobbit/BigBrother/Xymon for decades. We too have been looking at Xymon alternatives. We were looking at Zabbix but with Solarwinds embedded everywhere, we will probably go with it fully to replace Xymon.
▸
On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote:
I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp < user-9678697f1438@xymon.invalid> wrote:No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | * user-9678697f1438@xymon.invalid www.la-z-boy.com | facebook.com/lazboy | twitter.com/lazboy | youtube.com/lazboy [image: Smaller LZB Only Logo for Sign.png] *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]* This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
--
*Zoltan Forray* Enterprise Data Protection Administrator VMware Systems Administrator Enterprise Compute & Storage Platforms Team VCU Infrastructure Services user-755163d80bce@xymon.invalid - XXX-XXX-XXXX <https://www.credly.com/badges/131d9645-79f0-49ec-9f29-41f15900dca7/public_url>;
list Japheth Cleaver
Hello all,
Catching up with the thread from these past few days, this seems the
proper place for me to chime back in.
While it's possible to call xymon simply a quiet, stable project (which it
is, with many installs simply and quietly doing their jobs in the
background out there), it's also very fair to say that the project -- or
at least the plans I (and, I'll assume, Henrik) had for it has indeed
reached a stalling point.
That doesn't mean it can't come out of a stall! But it does mean it takes
effort to resume work on.
Following on with others' comments, the Xymon codebase is somewhat...
intense. When I was performing near-daily performance enhancement and
tweaks for Xymon for $dayjob, there was a solid ability to stay in the
zone and I could add features as needed at a rapid clip. Since then, as I
moved on to other positions and responsibilities, my day-to-day
involvement with the code base dried up, and getting back into it can be
difficult unless you're doing a lot of C elsewhere and not spending it
cursing at kubernetes.
In short, there's a significant ramp-up and re-ramp-up involved, as one
might expect from any mature codebase. While the underlying documentation
for use and administration is extremely thorough IMHO, an Intro for Devs
document was something we never followed through well on.
Development plans had at one point been something like:
- direct SSL support and/or message signing (probably the most frequently
requested things, for those for whom stunnel-wrapping was not an option)
- IPv6 (some of which is working in the 4.4 alpha branch)
- abstraction of remaining formatting to simple CSS to allow for skinning
and dashboarding
I'd also had in mind things like a JSON endpoint version of
xymondx{log|board}, and a REST-based C shim .cgi, both of which could help
folks integrating Xymon with other monitoring systems out there.
Of course, the initial target was simply the forklifting of the many
performance enhancements and tweaks from the Terabithia RPMs into the
source tarball. This got pretty far there in the 4.4 branch, with only a
few major components not integrated. However debugging those components
and patches stalled out, especially with the need to maintain robust
pan-*nix compatibility.
That, ultimately, is where we are now.
To kick things off: In the past, there had been requests to move the
source to Github in the hopes of creating an easier onramp for patch
submissions via PRs, bug reports, and the like. While I personally feel
like SF and svn would still work, I think this probably deserves to be
back on the table.
In addition, Henrik had mentioned that we'll need a mailing list migration
at some point coming up soon.
Beyond that, to be honest I'm not sure what the next, best step is to
take. Life had indeed gotten in the way, to follow from the comment below,
as $dayjob+=4 and other responsibilities cropped up.
I really welcome the entire community's input here going forward.
Regards,
J.C. Cleaver
▸
On Mon, August 14, 2023 09:58, Bruno Manzoni wrote:Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote:Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well???. But that???s not what Xymon needs.?? Xymon needs caretaker(s) to keep it relevant.?? That means code updates to fix bugs, adapt it to new OS versions, etc.?? Otherwise it will fade away to obscurity like many other open source projects.?? I???m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp??| Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 |( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32???AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different??employers since it was BigBrother owned by a couple of guys in Canada.?? My current Senior VP wants Xymon to go away.?? He hasn't actually told me that directly, but I've heard it via another channel.?? We have SolarWinds on some machines, but I've never even seen the GUI for that.?? We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines.?? I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM.?? In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents.?? It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel.?? It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it???s safe to say it???s flatlined.?? Sad to see it fade, I???ve been using it for a decade or more. *Scot Kreienkamp??| Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX| *user-9678697f1438@xymon.invalid www.la-z-boy.com <http://www.la-z-boy.com>??| facebook.com/lazboy <http://facebook.com/lazboy>????| twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>; Smaller LZB Only Logo for Sign.png *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that???s going to fade away. That would be a shame as I for one think it???s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]*This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ???Contact Us???.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- *Jim Louis ?? ?? ?? ?? ?? \\\\||//// ?? ?? ?? ?? ?? \ ~ ~?? / ?? ?? ?? ?? ?? | @ @ | • *--oOo---(_)---oOo-- • /???The part of life we really live is small. All the rest is not life, but merely time.???/
list Norbert Kriegenburg
I'm also into Bigbrother/Hobbit/Xymon business since decades, and from time to time I was forced to use other monitoring tools but never found something similar in being as flexible and powerful like Xymon, and on the other hand so simple to maintain and extend if needed. My biggest installation monitored 10k hosts and 400k rrd files on an 8 core RedHat server and 64GB memory easily. I have a lot of extension scripts to share but was kind of skeptical if Xymonton is still the place to do this. Also I changed the gifs a lot to create a more modern style (and increase the management acceptance). But I have to admit I'm kind of tired about the discussions with security team and management team about the future of Xymon, and that they don't want to opt for a monitoring solution which didn't got updates since years. I think Xymon is so mature and stable that it did not need regular new versions (if installed and run at non root environments, what is easily possible, it is more save and stable as all these tools with privileged access needs), but it is a always the first and basic question. Even if there is a very helpful community, if there is no update it is not acceptable from a managements standpoint. I can live with the current Xymon framework (that's how I use it for my customers), and do not need a configuration GUI or database as backend. I also do not need rpm packages as I'm always compile the servers for my needs (non root, no standard path,...). What I really would like to see is encrypted communication (the first question of every customer, as this they have heard is absolutely necessary these days. I know that there are workarounds possible, but they are, hm, workarounds...). And a well known and accepted place for extensions (remember deadcat? strange name, but i learned a lot there). I think I will give Xymonton another try, it is still online and available. Btw: It is not possible to sign up for the Xymon user group anymore (we are long time users and can comment, but no new users are allowed). If someone can take over this mail service this would be more important then code updates imho, to show that the project is still alive. I like to see a lot of well known names taking part in this discussion, and hope this will initiate some activity again for all of us Xymonters. And: I'm still grateful to Henrik for such an incredible work and product. I never had any issue caused by Xymon monitoring with dozens of installations for years, but a lot (and you can take this literally) by all other systems I had the "joy" to work with. Norbert Am Mo., 14. Aug. 2023 um 21:25 Uhr schrieb Zoltan Forray <user-755163d80bce@xymon.invalid>:
▸
I too have worked with Hobbit/BigBrother/Xymon for decades. We too have been looking at Xymon alternatives. We were looking at Zabbix but with Solarwinds embedded everywhere, we will probably go with it fully to replace Xymon. On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote:I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp < user-9678697f1438@xymon.invalid> wrote:No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | ( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | * user-9678697f1438@xymon.invalid www.la-z-boy.com | facebook.com/lazboy | twitter.com/lazboy | youtube.com/lazboy [image: Smaller LZB Only Logo for Sign.png] *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]* This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.-- *Zoltan Forray* Enterprise Data Protection Administrator VMware Systems Administrator Enterprise Compute & Storage Platforms Team VCU Infrastructure Services user-755163d80bce@xymon.invalid - XXX-XXX-XXXX <https://www.credly.com/badges/131d9645-79f0-49ec-9f29-41f15900dca7/public_url>;
list Damien Martins
If i had to vote for something: bring the code to a git(hub?) repo so people with required skills and time could contribute. ?Regards, Damien Martins? Le 14 ao?t 2023, 22:57, ? 22:57, "J.C. Cleaver" <user-87556346d4af@xymon.invalid> a ?crit:
▸
Hello all, Catching up with the thread from these past few days, this seems the proper place for me to chime back in. While it's possible to call xymon simply a quiet, stable project (which it is, with many installs simply and quietly doing their jobs in the background out there), it's also very fair to say that the project -- or at least the plans I (and, I'll assume, Henrik) had for it has indeed reached a stalling point. That doesn't mean it can't come out of a stall! But it does mean it takes effort to resume work on. Following on with others' comments, the Xymon codebase is somewhat... intense. When I was performing near-daily performance enhancement and tweaks for Xymon for $dayjob, there was a solid ability to stay in the zone and I could add features as needed at a rapid clip. Since then, as I moved on to other positions and responsibilities, my day-to-day involvement with the code base dried up, and getting back into it can be difficult unless you're doing a lot of C elsewhere and not spending it cursing at kubernetes. In short, there's a significant ramp-up and re-ramp-up involved, as one might expect from any mature codebase. While the underlying documentation for use and administration is extremely thorough IMHO, an Intro for Devs document was something we never followed through well on. Development plans had at one point been something like: - direct SSL support and/or message signing (probably the most frequently requested things, for those for whom stunnel-wrapping was not an option) - IPv6 (some of which is working in the 4.4 alpha branch) - abstraction of remaining formatting to simple CSS to allow for skinning and dashboarding I'd also had in mind things like a JSON endpoint version of xymondx{log|board}, and a REST-based C shim .cgi, both of which could help folks integrating Xymon with other monitoring systems out there. Of course, the initial target was simply the forklifting of the many performance enhancements and tweaks from the Terabithia RPMs into the source tarball. This got pretty far there in the 4.4 branch, with only a few major components not integrated. However debugging those components and patches stalled out, especially with the need to maintain robust pan-*nix compatibility. That, ultimately, is where we are now. To kick things off: In the past, there had been requests to move the source to Github in the hopes of creating an easier onramp for patch submissions via PRs, bug reports, and the like. While I personally feel like SF and svn would still work, I think this probably deserves to be back on the table. In addition, Henrik had mentioned that we'll need a mailing list migration at some point coming up soon. Beyond that, to be honest I'm not sure what the next, best step is to take. Life had indeed gotten in the way, to follow from the comment below, as $dayjob+=4 and other responsibilities cropped up. I really welcome the entire community's input here going forward. Regards, J.C. Cleaver On Mon, August 14, 2023 09:58, Bruno Manzoni wrote:Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote:Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well???. But that???s not what Xymon needs.?? Xymon needs caretaker(s) to keep it relevant.??Thatmeans code updates to fix bugs, adapt it to new OS versions, etc.?? Otherwise it will fade away to obscurity like many other open source projects.?? I???m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp??| Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 |( (XXX) XXX-XXXX ||) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32???AM Ralph M<user-00a5e44c48c0@xymon.invalid>wrote: I've been using Xymon at several different??employers since it was BigBrother owned by a couple of guys in Canada.?? My current Senior VP wants Xymon to go away.?? He hasn't actually told me that directly, but I've heard it via another channel.?? We have SolarWinds on some machines, but I've never even seen the GUI for that.?? We're also distributing OracleEnterpriseManager (OEM) to a bunch of machines.?? I don't know for sure, but I suspect a contracting company is whispering in mySVP'sear to sell support for OEM.?? In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents.?? It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel.?? It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it???s safe to say it???s flatlined.?? Sad to see it fade, I???ve been using it for a decade or more. *Scot Kreienkamp??| Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX|*user-9678697f1438@xymon.invalidwww.la-z-boy.com <http://www.la-z-boy.com>??| facebook.com/lazboy <http://facebook.com/lazboy>????| twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>; Smaller LZB Only Logo for Sign.png *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that???s going to fade away. That would be a shame as I for one think it???s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]*This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail TradingLimited(Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments.Noliability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers GroupFinancialServices Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ???Contact Us???.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- *Jim Louis ?? ?? ?? ?? ?? \\\\||//// ?? ?? ?? ?? ?? \ ~ ~?? / ?? ?? ?? ?? ?? | @ @ | • *--oOo---(_)---oOo-- • /???The part of life we really live is small. All the rest is not life, but merely time.???/
list Josh Luthman
What is there works beautifully for me. To say I appreciate the work that everyone has done just doesn't begin to describe how it helped us grow. In the near future I'd love to see a Rocky package. SSL would be kinda neat I guess, but I subscribe to the notion that if you've got a mitm on your system's network you have other problems to worry about anyway. On Mon, Aug 14, 2023 at 6:39?PM Damien Martins via Xymon <xymon at xymon.com> wrote:
---------- Forwarded message ---------- From: Damien Martins <user-c12727b399f0@xymon.invalid> To: "J.C. Cleaver" <user-87556346d4af@xymon.invalid> Cc: Damien via Xymon <xymon at xymon.com> Bcc: Date: Tue, 15 Aug 2023 00:38:28 +0200 Subject: Re: [Xymon] Xymon, community, updates, and directions (was Re: Is this thing on?)
▸
If i had to vote for something: bring the code to a git(hub?) repo so people with required skills and time could contribute. Regards, Damien Martins Le 14 ao?t 2023, ? 22:57, "J.C. Cleaver" <user-87556346d4af@xymon.invalid> a ?crit:Hello all, Catching up with the thread from these past few days, this seems the proper place for me to chime back in. While it's possible to call xymon simply a quiet, stable project (which it is, with many installs simply and quietly doing their jobs in the background out there), it's also very fair to say that the project -- or at least the plans I (and, I'll assume, Henrik) had for it has indeed reached a stalling point. That doesn't mean it can't come out of a stall! But it does mean it takes effort to resume work on. Following on with others' comments, the Xymon codebase is somewhat... intense. When I was performing near-daily performance enhancement and tweaks for Xymon for $dayjob, there was a solid ability to stay in the zone and I could add features as needed at a rapid clip. Since then, as I moved on to other positions and responsibilities, my day-to-day involvement with the code base dried up, and getting back into it can be difficult unless you're doing a lot of C elsewhere and not spending it cursing at kubernetes. In short, there's a significant ramp-up and re-ramp-up involved, as one might expect from any mature codebase. While the underlying documentation for use and administration is extremely thorough IMHO, an Intro for Devs document was something we never followed through well on. Development plans had at one point been something like: - direct SSL support and/or message signing (probably the most frequently requested things, for those for whom stunnel-wrapping was not an option) - IPv6 (some of which is working in the 4.4 alpha branch) - abstraction of remaining formatting to simple CSS to allow for skinning and dashboarding I'd also had in mind things like a JSON endpoint version of xymondx{log|board}, and a REST-based C shim .cgi, both of which could help folks integrating Xymon with other monitoring systems out there. Of course, the initial target was simply the forklifting of the many performance enhancements and tweaks from the Terabithia RPMs into the source tarball. This got pretty far there in the 4.4 branch, with only a few major components not integrated. However debugging those components and patches stalled out, especially with the need to maintain robust pan-*nix compatibility. That, ultimately, is where we are now. To kick things off: In the past, there had been requests to move the source to Github in the hopes of creating an easier onramp for patch submissions via PRs, bug reports, and the like. While I personally feel like SF and svn would still work, I think this probably deserves to be back on the table. In addition, Henrik had mentioned that we'll need a mailing list migration at some point coming up soon. Beyond that, to be honest I'm not sure what the next, best step is to take. Life had indeed gotten in the way, to follow from the comment below, as $dayjob+=4 and other responsibilities cropped up. I really welcome the entire community's input here going forward. Regards, J.C. Cleaver On Mon, August 14, 2023 09:58, Bruno Manzoni wrote:Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote:Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well???. But that???s not what Xymon needs.? Xymon needs caretaker(s) to keep it relevant.? That means code updates to fix bugs, adapt it to new OS versions, etc.? Otherwise it will fade away to obscurity like many other open source projects.? I???m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp? | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 |( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32???AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different? employers since it was BigBrother owned by a couple of guys in Canada.? My current Senior VP wants Xymon to go away.? He hasn't actually told me that directly, but I've heard it via another channel.? We have SolarWinds on some machines, but I've never even seen the GUI for that.? We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines.? I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM.? In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents.? It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel.? It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it???s safe to say it???s flatlined.? Sad to see it fade, I???ve been using it for a decade or more. *Scot Kreienkamp? | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX| *user-9678697f1438@xymon.invalid www.la-z-boy.com <http://www.la-z-boy.com>? | facebook.com/lazboy <http://facebook.com/lazboy>? ? | twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>; Smaller LZB Only Logo for Sign.png *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that???s going to fade away. That would be a shame as I for one think it???s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]*This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ???Contact Us???.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- *Jim Louis ? ? ? ? ? \\\\||//// ? ? ? ? ? \ ~ ~? / ? ? ? ? ? | @ @ | • *--oOo---(_)---oOo-- • /???The part of life we really live is small. All the rest is not life, but merely time.?? /
---------- Forwarded message ---------- From: Damien Martins via Xymon <xymon at xymon.com> To: "J.C. Cleaver" <user-87556346d4af@xymon.invalid> Cc: Damien via Xymon <xymon at xymon.com> Bcc: Date: Tue, 15 Aug 2023 00:38:28 +0200 Subject: Re: [Xymon] Xymon, community, updates, and directions (was Re: Is this thing on?)
list Jeremy Laidman
Thanks JC for taking the time to chime in. Your efforts in recent years breathed new life into the project, and so many of us have benefited greatly. It would've been nice to have a way to have my employer contribute financially to a fund that made it more viable for you/Henrik to spend time on maintenance. I agree with others on the need for SSL/TLS these days, or at least some form of encryption. Many organisations now require comms to be encrypted, or at least authenticated, using robust, modern cryptography. In my case, we're periodically asked about our comms, and receive raised eyebrows when we respond. I am also sympathetic to the notion that if we have to rely on encryption on our network, then we have bigger problems. But there are still reasons why encryption is desirable. For example, when monitoring a device connected via someone else's network. Or even just to slow down an attacker that has made her way onto our network, and perhaps even set off alarm bells when she tries to talk BB in cleartext and without authenticating, with the attempts generating log messages. Another way to view it is, "perfect is the enemy of good". I'd prefer to have encryption and authentication on a network that has an APT ferreting around, than not. The work-arounds are not ideal for a few reasons. But I suspect the main one is that there is no consistent and standardised workaround, that every deployment that requires it tends to use. If everyone simply used the stunnel solution, then it would end up being well supported by the community, with lots of help, documented experiences, how-tos and best practice guides. But I find myself not wanting to make a poor choice, so I haven't made any choice. I suspect the stunnel option is probably the best option, but I have a feeling there will be a performance impact. Not wanting to de-rail the conversation, the main point is that encryption/authentication is an important factor for me, and the missing feature is present in alternatives to Xymon. Some of the proposed alternatives are inadequate, but are still given credence due to the ticking the "security" boxes. If Xymon had this one feature built-in (or standardised), and had the occasional bug fix, then it would be treated with much less scepticism. J On Tue, 15 Aug 2023 at 11:48, Josh Luthman <user-4c45a83f15cb@xymon.invalid>
▸
wrote:
What is there works beautifully for me. To say I appreciate the work that everyone has done just doesn't begin to describe how it helped us grow. In the near future I'd love to see a Rocky package. SSL would be kinda neat I guess, but I subscribe to the notion that if you've got a mitm on your system's network you have other problems to worry about anyway. On Mon, Aug 14, 2023 at 6:39?PM Damien Martins via Xymon <xymon at xymon.com> wrote:---------- Forwarded message ---------- From: Damien Martins <user-c12727b399f0@xymon.invalid> To: "J.C. Cleaver" <user-87556346d4af@xymon.invalid> Cc: Damien via Xymon <xymon at xymon.com> Bcc: Date: Tue, 15 Aug 2023 00:38:28 +0200 Subject: Re: [Xymon] Xymon, community, updates, and directions (was Re: Is this thing on?) If i had to vote for something: bring the code to a git(hub?) repo so people with required skills and time could contribute. Regards, Damien Martins Le 14 ao?t 2023, ? 22:57, "J.C. Cleaver" <user-87556346d4af@xymon.invalid> a ?crit:Hello all, Catching up with the thread from these past few days, this seems the proper place for me to chime back in. While it's possible to call xymon simply a quiet, stable project (which it is, with many installs simply and quietly doing their jobs in the background out there), it's also very fair to say that the project -- or at least the plans I (and, I'll assume, Henrik) had for it has indeed reached a stalling point. That doesn't mean it can't come out of a stall! But it does mean it takes effort to resume work on. Following on with others' comments, the Xymon codebase is somewhat... intense. When I was performing near-daily performance enhancement and tweaks for Xymon for $dayjob, there was a solid ability to stay in the zone and I could add features as needed at a rapid clip. Since then, as I moved on to other positions and responsibilities, my day-to-day involvement with the code base dried up, and getting back into it can be difficult unless you're doing a lot of C elsewhere and not spending it cursing at kubernetes. In short, there's a significant ramp-up and re-ramp-up involved, as one might expect from any mature codebase. While the underlying documentation for use and administration is extremely thorough IMHO, an Intro for Devs document was something we never followed through well on. Development plans had at one point been something like: - direct SSL support and/or message signing (probably the most frequently requested things, for those for whom stunnel-wrapping was not an option) - IPv6 (some of which is working in the 4.4 alpha branch) - abstraction of remaining formatting to simple CSS to allow for skinning and dashboarding I'd also had in mind things like a JSON endpoint version of xymondx{log|board}, and a REST-based C shim .cgi, both of which could help folks integrating Xymon with other monitoring systems out there. Of course, the initial target was simply the forklifting of the many performance enhancements and tweaks from the Terabithia RPMs into the source tarball. This got pretty far there in the 4.4 branch, with only a few major components not integrated. However debugging those components and patches stalled out, especially with the need to maintain robust pan-*nix compatibility. That, ultimately, is where we are now. To kick things off: In the past, there had been requests to move the source to Github in the hopes of creating an easier onramp for patch submissions via PRs, bug reports, and the like. While I personally feel like SF and svn would still work, I think this probably deserves to be back on the table. In addition, Henrik had mentioned that we'll need a mailing list migration at some point coming up soon. Beyond that, to be honest I'm not sure what the next, best step is to take. Life had indeed gotten in the way, to follow from the comment below, as $dayjob+=4 and other responsibilities cropped up. I really welcome the entire community's input here going forward. Regards, J.C. Cleaver On Mon, August 14, 2023 09:58, Bruno Manzoni wrote:Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote:Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well???. But that???s not what Xymon needs.? Xymon needs caretaker(s) to keep it relevant.? That means code updates to fix bugs, adapt it to new OS versions, etc.? Otherwise it will fade away to obscurity like many other open source projects.? I???m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp? | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 |( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32???AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different? employers since it was BigBrother owned by a couple of guys in Canada.? My current Senior VP wants Xymon to go away.? He hasn't actually told me that directly, but I've heard it via another channel.? We have SolarWinds on some machines, but I've never even seen the GUI for that.? We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines.? I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM.? In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents.? It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel.? It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41???AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it???s safe to say it???s flatlined.? Sad to see it fade, I???ve been using it for a decade or more. *Scot Kreienkamp? | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX| *user-9678697f1438@xymon.invalid www.la-z-boy.com <http://www.la-z-boy.com>? | facebook.com/lazboy <http://facebook.com/lazboy>? ? | twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>; Smaller LZB Only Logo for Sign.png *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that???s going to fade away. That would be a shame as I for one think it???s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]*This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ???Contact Us???.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- *Jim Louis ? ? ? ? ? \\\\||//// ? ? ? ? ? \ ~ ~? / ? ? ? ? ? | @ @ | • *--oOo---(_)---oOo-- • /???The part of life we really live is small. All the rest is not life, but merely time.?? /---------- Forwarded message ---------- From: Damien Martins via Xymon <xymon at xymon.com> To: "J.C. Cleaver" <user-87556346d4af@xymon.invalid> Cc: Damien via Xymon <xymon at xymon.com> Bcc: Date: Tue, 15 Aug 2023 00:38:28 +0200 Subject: Re: [Xymon] Xymon, community, updates, and directions (was Re: Is this thing on?)
list Berry van Sleeuwen
We recently migrated our server to SLES15 SP4 and found there are a few network tools missing in the base, arp, netstat, ifconfig and route are supposed to be replaced by "ip" and "ss" command. While similar the output of these commands differs from the traditional tools so I guess that would interfere with the processing of the command output. For now it's solved by installing net-tools-deprecated but this might not be available in future versions so we might need support for these commands. I don't now if that is also the direction for other distributions, but it's at least the case for Suse and OpenSuse. Met vriendelijke groet/With kind regards/Mit freundlichen Gr??en, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven -----Original Message----- From: Xymon <xymon-bounces at xymon.com> On Behalf Of J.C. Cleaver Sent: Monday, 14 August 2023 22:51 To: xymon at xymon.com Subject: [Xymon] Xymon, community, updates, and directions (was Re: Is this thing on?) Caution: External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe.
▸
Hello all,
Catching up with the thread from these past few days, this seems the proper place for me to chime back in.
While it's possible to call xymon simply a quiet, stable project (which it is, with many installs simply and quietly doing their jobs in the background out there), it's also very fair to say that the project -- or at least the plans I (and, I'll assume, Henrik) had for it has indeed reached a stalling point.
That doesn't mean it can't come out of a stall! But it does mean it takes effort to resume work on.
Following on with others' comments, the Xymon codebase is somewhat...
intense. When I was performing near-daily performance enhancement and tweaks for Xymon for $dayjob, there was a solid ability to stay in the zone and I could add features as needed at a rapid clip. Since then, as I moved on to other positions and responsibilities, my day-to-day involvement with the code base dried up, and getting back into it can be difficult unless you're doing a lot of C elsewhere and not spending it cursing at kubernetes.
In short, there's a significant ramp-up and re-ramp-up involved, as one might expect from any mature codebase. While the underlying documentation for use and administration is extremely thorough IMHO, an Intro for Devs document was something we never followed through well on.
Development plans had at one point been something like:
- direct SSL support and/or message signing (probably the most frequently requested things, for those for whom stunnel-wrapping was not an option)
- IPv6 (some of which is working in the 4.4 alpha branch)
- abstraction of remaining formatting to simple CSS to allow for skinning and dashboarding
I'd also had in mind things like a JSON endpoint version of xymondx{log|board}, and a REST-based C shim .cgi, both of which could help folks integrating Xymon with other monitoring systems out there.
Of course, the initial target was simply the forklifting of the many performance enhancements and tweaks from the Terabithia RPMs into the source tarball. This got pretty far there in the 4.4 branch, with only a few major components not integrated. However debugging those components and patches stalled out, especially with the need to maintain robust pan-*nix compatibility.
That, ultimately, is where we are now.
To kick things off: In the past, there had been requests to move the source to Github in the hopes of creating an easier onramp for patch submissions via PRs, bug reports, and the like. While I personally feel like SF and svn would still work, I think this probably deserves to be back on the table.
In addition, Henrik had mentioned that we'll need a mailing list migration at some point coming up soon.
Beyond that, to be honest I'm not sure what the next, best step is to take. Life had indeed gotten in the way, to follow from the comment below, as $dayjob+=4 and other responsibilities cropped up.
I really welcome the entire community's input here going forward.
Regards,
J.C. Cleaver
On Mon, August 14, 2023 09:58, Bruno Manzoni wrote:Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) Bruno On 14.08.2023 18:36, James Louis wrote:Is the Terabithia RPM also dead? Jim
On Mon, Aug 14, 2023 at 10:03?EUR?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well?EUR?. But that?EUR(tm)s not what
▸
Xymon needs.? Xymon needs caretaker(s) to keep it relevant.? That means code updates to fix bugs, adapt it to new OS versions, etc.? Otherwise it will fade away to obscurity like many other open
source projects.? I?EUR(tm)m not a coder either, or I would gladly give
▸
some time to it. *Scot Kreienkamp? | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 |( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time.
On Mon, Aug 14, 2023 at 10:32?EUR?AM Ralph M <user-00a5e44c48c0@xymon.invalid>
▸
wrote: I've been using Xymon at several different? employers since it was BigBrother owned by a couple of guys in Canada.? My current Senior VP wants Xymon to go away.? He hasn't actually told me that directly, but I've heard it via another channel.? We have SolarWinds on some machines, but I've never even seen the GUI for that.? We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines.? I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM.? In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents.? It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel.? It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell
On Mon, Aug 14, 2023 at 9:41?EUR?AM Scot Kreienkamp
▸
<user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing
list, I think it?EUR(tm)s safe to say it?EUR(tm)s flatlined.? Sad to see it fade, I?EUR(tm)ve been using it for a decade or more.
▸
*Scot Kreienkamp? | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX| *user-9678697f1438@xymon.invalid
http://www.la-z-boy.com/ <http://www.la-z-boy.com/>? |
▸
facebook.com/lazboy <http://facebook.com/lazboy>? ? | twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>; Smaller LZB Only Logo for Sign.png *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that.
It feels like Xymon has become a static project that?EUR(tm)s going to fade away. That would be a shame as I for one think it?EUR(tm)s a great tool.
▸
*From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]*This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk/>; and
clicking ?EUR~Contact Us?EUR(tm).*
▸
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
http://list/ s.xymon.com%2Fmailman%2Flistinfo%2Fxymon&data=05%7C01%7Cberry.vanslee user-2200768c554f@xymon.invalid%7C912510ba8fc54a5be53308db9d0913c0%7C33440fc6b7c7412c bb730e70b0198d5a%7C0%7C0%7C638276434536654659%7CUnknown%7CTWFpbGZsb3d 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7 C3000%7C%7C%7C&sdata=jahiEFHlsISPJzGQsy7djiQI%2BF1Ui%2Bbzc36MIp4%2BL2 E%3D&reserved=0 http://list/ s.xymon.com%2Fmailman%2Flistinfo%2Fxymon&data=05%7C01%7Cberry.vanslee user-2200768c554f@xymon.invalid%7C912510ba8fc54a5be53308db9d0913c0%7C33440fc6b7c7412c bb730e70b0198d5a%7C0%7C0%7C638276434536654659%7CUnknown%7CTWFpbGZsb3d 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7 C3000%7C%7C%7C&sdata=jahiEFHlsISPJzGQsy7djiQI%2BF1Ui%2Bbzc36MIp4%2BL2 E%3D&reserved=0 http://list/ s.xymon.com%2Fmailman%2Flistinfo%2Fxymon&data=05%7C01%7Cberry.vanslee user-2200768c554f@xymon.invalid%7C912510ba8fc54a5be53308db9d0913c0%7C33440fc6b7c7412c bb730e70b0198d5a%7C0%7C0%7C638276434536654659%7CUnknown%7CTWFpbGZsb3d 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7 C3000%7C%7C%7C&sdata=jahiEFHlsISPJzGQsy7djiQI%2BF1Ui%2Bbzc36MIp4%2BL2 E%3D&reserved=0 -- *Jim Louis ? ? ? ? ? \\\\||//// ? ? ? ? ? \ ~ ~? / ? ? ? ? ? | @ @ | • *--oOo---(_)---oOo-- • /?EURoeThe part of life we really live is small. All the rest is not life, but merely time.?EUR?/ http://list/ s.xymon.com%2Fmailman%2Flistinfo%2Fxymon_____________________________ __________________&data=user-20c40b3245c1@xymon.invalid%7C9125 10ba8fc54a5be53308db9d0913c0%7C33440fc6b7c7412cbb730e70b0198d5a%7C0%7 C0%7C638276434536654659%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=G pthTaSyrc0Kb%2FbUDa92GamfFmsBNKYbbTWJUzDNNP4%3D&reserved=0http://lists/ .xymon.com%2Fmailman%2Flistinfo%2Fxymon&data=05%7C01%7Cberry.vansleeuw user-a070f99a3af9@xymon.invalid%7C912510ba8fc54a5be53308db9d0913c0%7C33440fc6b7c7412cbb7 30e70b0198d5a%7C0%7C0%7C638276434536654659%7CUnknown%7CTWFpbGZsb3d8eyJ WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000 %7C%7C%7C&sdata=jahiEFHlsISPJzGQsy7djiQI%2BF1Ui%2Bbzc36MIp4%2BL2E%3D&r eserved=0
list Henrik Størner
Hi, it seems this ?Is Xymon dead?? thread pops up from time to time. Which is understandable, given the lack of new releases and development work. If someone would like to pick it up and dust it off in a major way, then I would suggest moving away from C as the primary language. Python would probably have a lot more potential developers. Also consider replacing the proprietary Xymon protocol with a REST API instead - then you could use standard http modules to talk to Xymon. Look at what each tool does, and reimplement it in a more modern way. But that requires more than one enthusiastic developer. Although I do lurk on the mailing list occasionally, like JC I no longer have all of the codebase engrained in my brain. And my use of Xymon is strictly personal. So I won?t be able to contribute much. And yes, the mailing list needs a new home soon. Regards, Henrik
Den 14. aug. 2023 kl. 21.57 skrev J.C. Cleaver <user-87556346d4af@xymon.invalid>:
▸
? Hello all, Catching up with the thread from these past few days, this seems the proper place for me to chime back in. While it's possible to call xymon simply a quiet, stable project (which it is, with many installs simply and quietly doing their jobs in the background out there), it's also very fair to say that the project -- or at least the plans I (and, I'll assume, Henrik) had for it has indeed reached a stalling point. That doesn't mean it can't come out of a stall! But it does mean it takes effort to resume work on. Following on with others' comments, the Xymon codebase is somewhat... intense. When I was performing near-daily performance enhancement and tweaks for Xymon for $dayjob, there was a solid ability to stay in the zone and I could add features as needed at a rapid clip. Since then, as I moved on to other positions and responsibilities, my day-to-day involvement with the code base dried up, and getting back into it can be difficult unless you're doing a lot of C elsewhere and not spending it cursing at kubernetes. In short, there's a significant ramp-up and re-ramp-up involved, as one might expect from any mature codebase. While the underlying documentation for use and administration is extremely thorough IMHO, an Intro for Devs document was something we never followed through well on. Development plans had at one point been something like: - direct SSL support and/or message signing (probably the most frequently requested things, for those for whom stunnel-wrapping was not an option) - IPv6 (some of which is working in the 4.4 alpha branch) - abstraction of remaining formatting to simple CSS to allow for skinning and dashboarding I'd also had in mind things like a JSON endpoint version of xymondx{log|board}, and a REST-based C shim .cgi, both of which could help folks integrating Xymon with other monitoring systems out there. Of course, the initial target was simply the forklifting of the many performance enhancements and tweaks from the Terabithia RPMs into the source tarball. This got pretty far there in the 4.4 branch, with only a few major components not integrated. However debugging those components and patches stalled out, especially with the need to maintain robust pan-*nix compatibility. That, ultimately, is where we are now. To kick things off: In the past, there had been requests to move the source to Github in the hopes of creating an easier onramp for patch submissions via PRs, bug reports, and the like. While I personally feel like SF and svn would still work, I think this probably deserves to be back on the table. In addition, Henrik had mentioned that we'll need a mailing list migration at some point coming up soon. Beyond that, to be honest I'm not sure what the next, best step is to take. Life had indeed gotten in the way, to follow from the comment below, as $dayjob+=4 and other responsibilities cropped up. I really welcome the entire community's input here going forward. Regards, J.C. CleaverOn Mon, August 14, 2023 09:58, Bruno Manzoni wrote: Hellor Xymon Lovers I'm not a coder either, but I see there's quite a bit of brains out there (and I think if there are enough of us we can try to maintain and improve it). Perhaps the current officials could first tell us what their plans are and how we could help them. On our side, we can perhaps encourage them: it would be good to list what we can bring to the project, as some have done! - I try to maintain "devmon" (on the github repo) and some other xymon tool (I did try to understand how devmon is integrate to xymon, but I am not an expert in Xymon code) - I am a telecom engineer - I can give some some time - I am an independent and I have some infra to play with - Usually I speak swiss-french (so sorry for all my mistakes) BrunoOn 14.08.2023 18:36, James Louis wrote: Is the Terabithia RPM also dead? Jim On Mon, Aug 14, 2023 at 10:03?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: I would be OK with contributing some as well?. But that?s not what Xymon needs. Xymon needs caretaker(s) to keep it relevant. That means code updates to fix bugs, adapt it to new OS versions, etc. Otherwise it will fade away to obscurity like many other open source projects. I?m not a coder either, or I would gladly give some time to it. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 |( (XXX) XXX-XXXX | | ) X-XXX-XXX-XXXX | Email: user-9678697f1438@xymon.invalid *From:* Rod <user-626df9d20e67@xymon.invalid> *Sent:* Monday, August 14, 2023 10:56 AM *To:* Ralph M <user-00a5e44c48c0@xymon.invalid> *Cc:* Scot Kreienkamp <user-9678697f1438@xymon.invalid>; xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? I would like to continue the legacy. I'm not a developer but I'm willing to pay for hosting space and the domain name to keep it going for as long as I'm alive. Its kept me employed for a long time. On Mon, Aug 14, 2023 at 10:32?AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote: I've been using Xymon at several different employers since it was BigBrother owned by a couple of guys in Canada. My current Senior VP wants Xymon to go away. He hasn't actually told me that directly, but I've heard it via another channel. We have SolarWinds on some machines, but I've never even seen the GUI for that. We're also distributing Oracle Enterprise Manager (OEM) to a bunch of machines. I don't know for sure, but I suspect a contracting company is whispering in my SVP's ear to sell support for OEM. In the meantime, my Xymon server has 878 days uptime and they're still trying to figure out how to install and configure the OEM agents. It's going to be tons of fun watching them try to replace all the little scripts I've written with OEM equivalents. @Cristoph - I don't know if I can use stunnel. It's a military-related company and there are all kinds of restrictions that sometimes even make sense. Ralph Mitchell On Mon, Aug 14, 2023 at 9:41?AM Scot Kreienkamp <user-9678697f1438@xymon.invalid> wrote: No new release since 2019, no activity on the mailing list, I think it?s safe to say it?s flatlined. Sad to see it fade, I?ve been using it for a decade or more. *Scot Kreienkamp | Senior Linux Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162|((734) 384-6403 | | )X-XXX-XXX-XXXX| *user-9678697f1438@xymon.invalid www.la-z-boy.com <http://www.la-z-boy.com>; | facebook.com/lazboy <http://facebook.com/lazboy>; | twitter.com/lazboy <http://twitter.com/lazboy>| youtube.com/lazboy <http://youtube.com/lazboy>; Smaller LZB Only Logo for Sign.png *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Neil Simmonds *Sent:* Monday, August 14, 2023 5:29 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* Re: [Xymon] Is this thing on? Is Xymon dying? No new release since 2019, There was a roadmap in 2015 that mention Versions 4.4 up to 5 but nothing seems to have moved on that. It feels like Xymon has become a static project that?s going to fade away. That would be a shame as I for one think it?s a great tool. *From:* Xymon <xymon-bounces at xymon.com> *On Behalf Of *Galen Johnson *Sent:* Sunday, August 13, 2023 3:01 AM *To:* xymon >> xymon at xymon.com <xymon at xymon.com> *Subject:* [Xymon] Is this thing on? *[CAUTION]*This is an external email. Do not click links or open any attachments unless you are sure they are safe. Nothing since May seems a bit suss. =G= Studio is a trading name of Studio Retail Trading Limited (Company no. 03994833), which is an introducer of credit not a lender. Studio Pay 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. Both companies are registered in England and their registered office is: Church Bridge House Henry Street Accrington BB5 4EE. *NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. The recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Trading Ltd or Frasers Group Financial Services Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Trading Ltd and Frasers Group Financial Services Ltd reserve the right to monitor all e-mail communications through their internal and external networks. If you have received this email in error please let us know. You can find our available contact details by going to help.studio.co.uk <http://help.studio.co.uk>; and clicking ?Contact Us?.* This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- *Jim Louis \\\\||//// \ ~ ~ / | @ @ | • *--oOo---(_)---oOo-- • /?The part of life we really live is small. All the rest is not life, but merely time.?/
list Bruno Manzoni
Hi Xymon Lovers, Glad to see everyone still loves Xymon and ready to give more! *I've summarized this discussion *"Is this thing on" *To move forward:** **Non-technical needs:* *? Mailing list migration*, not possible to sign up for the Xymon user group anymore (*URGENT PROBLEM*) ??? Share community developed plugins/monitors (it seems some people may have a lot to share) ??? Several resources available if needed (developer, server web, demo platform, infra, maybe also money) ??? More than one enthusiastic developer (probably not only devs...) ??? Need a caretaker: updates to fix bugs, adapt to new OS versions, Terabithia RPM ??? Henrik won't be able to contribute much (but a little might also be good!) ??? A clearer organization ??? Wikibook information udpate *Technical needs* *New features that we would like to have or that were planned* ??? Reports, communication encrypted, or at least authenticated, Direct SSL support and/or message signing (*MOST REQUESTED*) ??? Introductory document for developers
▸
??? IPv6 (some of which is working in the 4.4 alpha branch)
??? Abstraction of remaining formatting to simple CSS to allow for skinning and dashboarding
??? JSON endpoint version of xymondx{log|board}
▸
??? REST-based C shim .cgi, both of which could help folks integrating Xymon with other monitoring systems out there
??? Forklifting of the many performance enhancements and tweaks from the Terabithia RPMs into the source tarball.
??? Move the source to Github in the hopes of creating an easier onramp for patch submissions via PRs, bug reports
??? Rocky package.
??? Missing in the base, arp, netstat, ifconfig and route are supposed to be replaced by "ip" and "ss" commands.
??? Moving away from C as the primary language. Python would probably have a lot more potential developers (*MAIN SUGGESTION FROM HENRIK*)
??? Consider replacing the proprietary Xymon protocol with a REST API instead - then you could use standard http modules to talk to Xymon. Look at what each tool does, and reimplement it in a more modern way.
??? Fix all string management warnings reported by gcc.
*1. Please, let us know if all your info is in these lists *or *if you have other ideas *and *what do you think of all this now that you have an summary ?*
Also, I understood that Henrik and Japhet couldn't be much more involved, but they are invaluable people for this project.
*@Henrik and Japhet: *
- Do we need a new Prophet ?
- So if yes, if someone/people would like to continue the project, what would you like to see from him/them: It would be great to have someone who would have your blessing
Bruno
list Corentin Labbe
Le Tue, Aug 15, 2023 at 07:42:47AM +0100, Henrik St?rner via Xymon a ?crit :
Return-Path: <user-ce4a2c883f75@xymon.invalid> X-Virus-Scanned: Debian user-18054d8e9b55@xymon.invalid DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hswn.dk; s=mail; t=1692081779; bh=6F8mAvlRTRvCdysuFXnx0ce1H/hOkoTfydrY+Jc40Pg=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=WwOVVcRxDvtUyEtqlB8j5yb4A+xBV3PmjPx6FFgmvAmDjArK2QtUEUlRhBUjjZRoW 1Miz8QewOvFvsDCK2+/IxUrH9SGuFyK12p8Otdp32w3LgNWnJKzAmxfox96SL4jT0S A2qPmlOUhqrVdpRNbXSnycKQIqaSXZ4HgLmkiS2s= Received: from smtpclient.apple (unknown [213.141.9.206]) by vmail.hswn.dk (Postfix) with ESMTPSA id 058E54413E; Tue, 15 Aug 2023 08:42:58 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Henrik St?rner <user-ce4a2c883f75@xymon.invalid> Mime-Version: 1.0 (1.0)
▸
Subject: Re: [Xymon] Xymon, community, updates, and directions (was Re: Is
this thing on?)
Date: Tue, 15 Aug 2023 07:42:47 +0100
Message-Id: <user-fe3dd6b83dab@xymon.invalid>
References: <user-e074871a01b3@xymon.invalid>
Cc: Xymon at xymon.com
In-Reply-To: <user-e074871a01b3@xymon.invalid>
To: "J.C. Cleaver" <user-87556346d4af@xymon.invalid>
X-Mailer: iPad Mail (20G75)
▸
Hi,
it seems this ?Is Xymon dead?? thread pops up from time to time. Which is understandable, given the lack of new releases and development work.
If someone would like to pick it up and dust it off in a major way, then I would suggest moving away from C as the primary language. Python would probably have a lot more potential developers. Also consider replacing the proprietary Xymon protocol with a REST API instead - then you could use standard http modules to talk to Xymon. Look at what each tool does, and reimplement it in a more modern way.Hello I agree on using a different language, xymon is basicly just string handling and C is dangerous with that. I am happy you thinked about python, because my try to redo xymon was in python and I think no other language could have permitted to reimplement so many part so fast and easily. But for me, the xymon protocol should be kept, it is easy parsable and do not need extra dependencies to be parsable. At least for the client protocol, having a client so easy to implement is a great advantage. For example, I could put a fake xymon client on some embedded boards (like ESP8266 and co)
▸
But that requires more than one enthusiastic developer. Although I do lurk on the mailing list occasionally, like JC I no longer have all of the codebase engrained in my brain. And my use of Xymon is strictly personal. So I won?t be able to contribute much. And yes, the mailing list needs a new home soon.
If nobody want to do it, I could try to install a mailman on my personnal server. The list is so low traffic that should not be a problem. Thanks for you work Regards
list Japheth Cleaver
▸
On Tue, August 15, 2023 13:18, Corentin Labbe wrote:
Le Tue, Aug 15, 2023 at 07:42:47AM +0100, Henrik St??rner via Xymon a ??crit :Return-Path: <user-ce4a2c883f75@xymon.invalid> X-Virus-Scanned: Debian user-18054d8e9b55@xymon.invalid DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hswn.dk; s=mail; t=1692081779; bh=6F8mAvlRTRvCdysuFXnx0ce1H/hOkoTfydrY+Jc40Pg=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=WwOVVcRxDvtUyEtqlB8j5yb4A+xBV3PmjPx6FFgmvAmDjArK2QtUEUlRhBUjjZRoW 1Miz8QewOvFvsDCK2+/IxUrH9SGuFyK12p8Otdp32w3LgNWnJKzAmxfox96SL4jT0S A2qPmlOUhqrVdpRNbXSnycKQIqaSXZ4HgLmkiS2s= Received: from smtpclient.apple (unknown [213.141.9.206]) by vmail.hswn.dk (Postfix) with ESMTPSA id 058E54413E; Tue, 15 Aug 2023 08:42:58 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Henrik St??rner <user-ce4a2c883f75@xymon.invalid> Mime-Version: 1.0 (1.0) Subject: Re: [Xymon] Xymon, community, updates, and directions (was Re: Is this thing on?) Date: Tue, 15 Aug 2023 07:42:47 +0100 Message-Id: <user-fe3dd6b83dab@xymon.invalid> References: <user-e074871a01b3@xymon.invalid> Cc: Xymon at xymon.com In-Reply-To: <user-e074871a01b3@xymon.invalid> To: "J.C. Cleaver" <user-87556346d4af@xymon.invalid> X-Mailer: iPad Mail (20G75) Hi, it seems this ???Is Xymon dead???? thread pops up from time to time. Which is understandable, given the lack of new releases and development work. If someone would like to pick it up and dust it off in a major way, then I would suggest moving away from C as the primary language. Python would probably have a lot more potential developers. Also consider replacing the proprietary Xymon protocol with a REST API instead - then you could use standard http modules to talk to Xymon. Look at what each tool does, and reimplement it in a more modern way.Hello I agree on using a different language, xymon is basicly just string handling and C is dangerous with that. I am happy you thinked about python, because my try to redo xymon was in python and I think no other language could have permitted to reimplement so many part so fast and easily. But for me, the xymon protocol should be kept, it is easy parsable and do not need extra dependencies to be parsable. At least for the client protocol, having a client so easy to implement is a great advantage. For example, I could put a fake xymon client on some embedded boards (like ESP8266 and co)
I agree that with it mostly being string handling, which does raise plenty of options for other interpretations. And the text-based nature of the protocol allows for interoperability to be maintained. One of the beauties of xymon as currently architected is that there are essentially no performance-sensitive areas that require a fork in the central server, which puts a lot of the objection to interpreted languages to the side, if it only need to be launched once. (I'd considered a perl version of the server at one point, but python would be a solid case now.) Along with string manipulation, memory management is pretty key as well, especially at scale. It's both a strength and a weakness here, but it suggests that "safer C" (a/k/a Rust) might also be an option. I don't think either of these would be happening any time soon, however, and I agree that the TCP protocol as used is pretty easy to implement, minus the one-sided closure to signal a complete message that you're expecting a response back from. Regards, -jc
list Japheth Cleaver
▸
On Mon, August 14, 2023 19:55, Jeremy Laidman wrote:
I agree with others on the need for SSL/TLS these days, or at least some form of encryption. Many organisations now require comms to be encrypted, or at least authenticated, using robust, modern cryptography. In my case, we're periodically asked about our comms, and receive raised eyebrows when we respond. I am also sympathetic to the notion that if we have to rely on encryption on our network, then we have bigger problems. But there are still reasons why encryption is desirable. For example, when monitoring a device connected via someone else's network. Or even just to slow down an attacker that has made her way onto our network, and perhaps even set off alarm bells when she tries to talk BB in cleartext and without authenticating, with the attempts generating log messages. Another way to view it is, "perfect is the enemy of good". I'd prefer to have encryption and authentication on a network that has an APT ferreting around, than not.
I tend to agree with this as well. Although the interaction is what it is, having anything unencrypted on networks can be a red flag and a barrier to implementation.
▸
The work-arounds are not ideal for a few reasons. But I suspect the main one is that there is no consistent and standardised workaround, that every deployment that requires it tends to use. If everyone simply used the stunnel solution, then it would end up being well supported by the community, with lots of help, documented experiences, how-tos and best practice guides. But I find myself not wanting to make a poor choice, so I haven't made any choice. I suspect the stunnel option is probably the best option, but I have a feeling there will be a performance impact.
Indeed. Performance comes into play with all the options here. - Setup and teardown for small TCP connections hitting xymond directly - Signing and authenticating messages received asynchronously (combo messages, xymonproxy, or messages read in from the BFQ), which should be tossed if invalid As it currently stands, xymon is already very efficient, so it's worth pointing out that the complexity really doesn't have to come in until you start hitting things at scale. If you're on a modern core and handling 90 msg/s, xymond is going to be just fine. If you're trying to push 9000 msg/s, more needs to be taken into consideration. Furthermore, ensuring that one-way messages are submitted asynchronously to the daemon means that SSL termination and/or authentication can still pretty easily be off-loaded architecturally, even while SSL features are still in development. (HTTPS message submission in particular, with apache handling the ugly part.) I think a community solution and best practices can be drawn up, but it probably calls for something of a working group among those who are pushing the limits now (or still) and have already worked through some of the kinks in their SSL implementation. (Memories of stunnel-wrapping qmail-smtpd coming into play here...)
▸
Not wanting to de-rail the conversation, the main point is that encryption/authentication is an important factor for me, and the missing feature is present in alternatives to Xymon. Some of the proposed alternatives are inadequate, but are still given credence due to the ticking the "security" boxes. If Xymon had this one feature built-in (or standardised), and had the occasional bug fix, then it would be treated with much less scepticism.
Agreed. -jc
list Japheth Cleaver
▸
On Mon, August 14, 2023 21:10, Berry van Sleeuwen wrote:
We recently migrated our server to SLES15 SP4 and found there are a few network tools missing in the base, arp, netstat, ifconfig and route are supposed to be replaced by "ip" and "ss" command. While similar the output of these commands differs from the traditional tools so I guess that would interfere with the processing of the command output. For now it's solved by installing net-tools-deprecated but this might not be available in future versions so we might need support for these commands. I don't now if that is also the direction for other distributions, but it's at least the case for Suse and OpenSuse.
Agreed; it's similar in the RHEL side. xymond_client updates that can interpret the output of ip and ss are probably called for now. While deprecated net-tools will stick around for sure for current systems, it's only a matter of time until they're removed, and in the meantime it's one less package to have to pull in for compatibility (and to explain). This probably goes higher on the list. -jc
list Ryan Novosielski
▸
On Aug 17, 2023, at 14:27, J.C. Cleaver <user-87556346d4af@xymon.invalid> wrote: On Mon, August 14, 2023 21:10, Berry van Sleeuwen wrote:We recently migrated our server to SLES15 SP4 and found there are a few network tools missing in the base, arp, netstat, ifconfig and route are supposed to be replaced by "ip" and "ss" command. While similar the output of these commands differs from the traditional tools so I guess that would interfere with the processing of the command output. For now it's solved by installing net-tools-deprecated but this might not be available in future versions so we might need support for these commands. I don't now if that is also the direction for other distributions, but it's at least the case for Suse and OpenSuse.Agreed; it's similar in the RHEL side. xymond_client updates that can interpret the output of ip and ss are probably called for now. While deprecated net-tools will stick around for sure for current systems, it's only a matter of time until they're removed, and in the meantime it's one less package to have to pull in for compatibility (and to explain).
Slash harass people to stop writing new code for/create dependencies on in 2022/2023. :-P
This probably goes higher on the list.
100% agreed.
--
#BlackLivesMatter
____
|| \\UTGERS, |---------------------------*O*---------------------------
||_// the State | Ryan Novosielski - user-46c89e614701@xymon.invalid
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
|| \\ of NJ | Office of Advanced Research Computing - MSB A555B, Newark
`'
list Japheth Cleaver
▸
On Tue, August 15, 2023 09:34, Bruno Manzoni wrote:
Hi Xymon Lovers,
Glad to see everyone still loves Xymon and ready to give more!
*I've summarized this discussion *"Is this thing on"
*To move forward:**
**Non-technical needs:*
*?? Mailing list migration*, not possible to sign up for the Xymon user
group anymore (*URGENT PROBLEM*)
?????? Share community developed plugins/monitors (it seems some people
may have a lot to share)
?????? Several resources available if needed (developer, server web, demo
platform, infra, maybe also money)
?????? More than one enthusiastic developer (probably not only devs...)
?????? Need a caretaker: updates to fix bugs, adapt to new OS versions,
Terabithia RPM
?????? Henrik won't be able to contribute much (but a little might also
be
good!)
?????? A clearer organization
?????? Wikibook information udpate
*Technical needs*
*New features that we would like to have or that were planned*
?????? Reports, communication encrypted, or at least authenticated,
Direct
SSL support and/or message signing (*MOST REQUESTED*)
?????? Introductory document for developers
?????? IPv6 (some of which is working in the 4.4 alpha branch)
?????? Abstraction of remaining formatting to simple CSS to allow for
skinning and dashboarding
?????? JSON endpoint version of xymondx{log|board}
?????? REST-based C shim .cgi, both of which could help folks integrating
Xymon with other monitoring systems out there
?????? Forklifting of the many performance enhancements and tweaks from
the Terabithia RPMs into the source tarball.
?????? Move the source to Github in the hopes of creating an easier
onramp
for patch submissions via PRs, bug reports
?????? Rocky package.
?????? Missing in the base, arp, netstat, ifconfig and route are supposed
to be replaced by "ip" and "ss" commands.
?????? Moving away from C as the primary language. Python would probably
have a lot more potential developers (*MAIN SUGGESTION FROM HENRIK*)
?????? Consider replacing the proprietary Xymon protocol with a REST API
instead - then you could use standard http modules to talk to Xymon.
Look at what each tool does, and reimplement it in a more modern way.
?????? Fix all string management warnings reported by gcc.
*1. Please, let us know if all your info is in these lists *or *if you
have other ideas *and *what do you think of all this now that you have
an summary ?*
Thank you for this write-up! I think this aptly summarizes where things are.
I suspect with the number of sysadmins on the list, we should be able to
solve any questions of domains, hosting, and email fairly quickly. I use
my own builders for the Terabithia RPMs, but as development picks back up
it will be helpful to set some formal targets for the main release to
ensure that we maintain compatibility with the various systems we're
intending to. (GCC warnings in particular may cause more strife.)
The rest broadly does seem like it comes down to technical vs
non-technical issues. While *I'm* personally OK with the man2html look,
I'm pretty sure that's not what The Kids like today :) I had looked at
things like ReadTheDocs and other .io projects, which could provide a
useful re-structuring of the existing introductory material, and then form
the basis for renewed walkthroughs, FAQs, and the like in a more
approachable manner. (While still keeping the comprehensive man pages
available.)
While I'm a competent enough technical writer, as these emails make clear
I'd sorely need an editor :) But if someone with an eye for documentation
and more aligned with modern tech sensibilities could take the lead on
site design and structure I think that would be something very helpful for
the project.
I would also second that unifying the wiki materials is probably a good
thing, including making sure links to xymonton and any other BB resources
are prominently available.
The technical directions are a big chunk to chew, but I think the
documentation and front-door experience is probably more directly relevant
to revitalizing interest (barring the SSL issues brought up elsewhere).
Regards,
-jc
list Bruce Ferrell
▸
On 8/17/23 1:27 PM, J.C. Cleaver wrote:
On Tue, August 15, 2023 09:34, Bruno Manzoni wrote:Hi Xymon Lovers, Glad to see everyone still loves Xymon and ready to give more! *I've summarized this discussion *"Is this thing on" *To move forward:** **Non-technical needs:* *? Mailing list migration*, not possible to sign up for the Xymon user group anymore (*URGENT PROBLEM*) ??? Share community developed plugins/monitors (it seems some people may have a lot to share) ??? Several resources available if needed (developer, server web, demo platform, infra, maybe also money) ??? More than one enthusiastic developer (probably not only devs...) ??? Need a caretaker: updates to fix bugs, adapt to new OS versions, Terabithia RPM ??? Henrik won't be able to contribute much (but a little might also be good!) ??? A clearer organization ??? Wikibook information udpate *Technical needs* *New features that we would like to have or that were planned* ??? Reports, communication encrypted, or at least authenticated, Direct SSL support and/or message signing (*MOST REQUESTED*) ??? Introductory document for developers ??? IPv6 (some of which is working in the 4.4 alpha branch) ??? Abstraction of remaining formatting to simple CSS to allow for skinning and dashboarding ??? JSON endpoint version of xymondx{log|board} ??? REST-based C shim .cgi, both of which could help folks integrating Xymon with other monitoring systems out there ??? Forklifting of the many performance enhancements and tweaks from the Terabithia RPMs into the source tarball. ??? Move the source to Github in the hopes of creating an easier onramp for patch submissions via PRs, bug reports ??? Rocky package. ??? Missing in the base, arp, netstat, ifconfig and route are supposed to be replaced by "ip" and "ss" commands. ??? Moving away from C as the primary language. Python would probably have a lot more potential developers (*MAIN SUGGESTION FROM HENRIK*) ??? Consider replacing the proprietary Xymon protocol with a REST API instead - then you could use standard http modules to talk to Xymon. Look at what each tool does, and reimplement it in a more modern way. ??? Fix all string management warnings reported by gcc. *1. Please, let us know if all your info is in these lists *or *if you have other ideas *and *what do you think of all this now that you have an summary ?*Thank you for this write-up! I think this aptly summarizes where things are. I suspect with the number of sysadmins on the list, we should be able to solve any questions of domains, hosting, and email fairly quickly. I use my own builders for the Terabithia RPMs, but as development picks back up it will be helpful to set some formal targets for the main release to ensure that we maintain compatibility with the various systems we're intending to. (GCC warnings in particular may cause more strife.) The rest broadly does seem like it comes down to technical vs non-technical issues. While *I'm* personally OK with the man2html look, I'm pretty sure that's not what The Kids like today :) I had looked at things like ReadTheDocs and other .io projects, which could provide a useful re-structuring of the existing introductory material, and then form the basis for renewed walkthroughs, FAQs, and the like in a more approachable manner. (While still keeping the comprehensive man pages available.) While I'm a competent enough technical writer, as these emails make clear I'd sorely need an editor :) But if someone with an eye for documentation and more aligned with modern tech sensibilities could take the lead on site design and structure I think that would be something very helpful for the project. I would also second that unifying the wiki materials is probably a good thing, including making sure links to xymonton and any other BB resources are prominently available. The technical directions are a big chunk to chew, but I think the documentation and front-door experience is probably more directly relevant to revitalizing interest (barring the SSL issues brought up elsewhere). Regards, -jc
In the beginning there was port 1984 and shell scripts... And it was good; So good that Dell devoured it whole without a burp and it was never seen again. C was an improvement, but also introduced all sorts of odd little bugs that shell never was vulnerable to (some called them hobbits until people lacking a sense of humor told them to knock it off) and those had to be solved and gave us some interesting new capabilities at the same time like SNMP monitoring built in (IF you could gather all the bits and pieces and get it to work;? I did it once and the next upgrade broke it and I had no to time to sort it out again). Now someone is suggesting python or rust.? Which python?? Which rust?? As someone who fights with questions like this for both a living and a hobby, I shudder and pale at the suggestion and begin considering what other tools I should start thinking about. Starting adding funky dependencies and admins start walking away. The iproute2 family of tools (the "ip" and "ss" commands) have introduced a similar set of issues.? These aren't terrible, but they ARE irritating. Adding secure communications (ssl/tls and certificates/signing) is possibly the simplest enhancement to make... And most likely to break everything for someone if done wrong in either the code or config. Replacing the "the proprietary Xymon protocol with a REST API"? ?Is it really a proprietary protocol? Let's look at that;? I want a new test -- I knock together something that collects/senses what I need to know about and tells $XYMONHOME/bin/xymon to transmit it. I don't need to know ANYTHING about how to get it to the display and I don't care.? I do have to know how to tell the display what to do when the data get's there and how to chart it.? I've spent a number of hours digging through rrdtool docs, but those are pretty clear. How much of the existing ecosystem might a REST API destroy? Is that destruction worth it?? What is the actual gain? The friendliest and most useful enhancement, I believe, is documentation. As an example, I just installed snap package management on a VM that sets up some mounts that are 100 percent all the time. Solution: Ignore them... Yeah, right!? I cannot make them be silent. When I have a BIT more time, I know I'll solve the issue, but for now, I've simply suppressed them.? There a LOT of this type of issue and lack of documentation has led to a lot more re-invention of the wheel. SSL/TLS used to be handled by freely available stunnel... But the method was never documented well (it was obvious!? Was it?) and is now lost in the mists of time. I already mentioned the SNMP monitor configuration.? Trust me, devmon sucks, but it's what is consistently/readily workable... As long as I restart it regularly otherwise it swells like a poisoned animal. Documentation is the least "sexy" thing to do, so I suspect the kewl sexy things will happen... Python/rust/REST, and the documentation will be ignored Just my old neck beard view of this, worth every penny that you paid for it.
list Jeremy Laidman
▸
On Fri, 18 Aug 2023 at 04:27, J.C. Cleaver <user-87556346d4af@xymon.invalid> wrote:
On Mon, August 14, 2023 21:10, Berry van Sleeuwen wrote:We recently migrated our server to SLES15 SP4 and found there are a few network tools missing in the base, arp, netstat, ifconfig and route are supposed to be replaced by "ip" and "ss" command. While similar the output of these commands differs from the traditional tools so I guess that would interfere with the processing of the command output. For now it's solved by installing net-tools-deprecated but this might not be available in future versions so we might need support for these commands. I don't now if that is also the direction for other distributions, but it's at least the case for Suse and OpenSuse.Agreed; it's similar in the RHEL side. xymond_client updates that can interpret the output of ip and ss are probably called for now. While deprecated net-tools will stick around for sure for current systems, it's only a matter of time until they're removed, and in the meantime it's one less package to have to pull in for compatibility (and to explain). This probably goes higher on the list.
Two brief comments about this. To me, xymond_client always seemed to be a good candidate for making it a bit more modular. The code is written in a modular way, to make it fairly easy to add new ways of collecting the same metrics from different OSes and OS versions (which would presumably make it possible for even me to add support for "ip" and "ss", albeit with bloated code and buffer overruns). But I thought it would be neat to be able to plug in some kind of run-time process to handle new scenarios - bit it a dynamic library, or a shared memory protocol or a worker module launched by xymond_channel or similar and written in whatever language was available and familiar to the sysadmin at the time. The emergence of "sar" as a universally available system metric reporting tool seems to solve this problem in a different way. If xymond_client had a "sar" module, it could pretty much support any popular modern OS apart from Windows (so Linux, Solaris, MacOS/*BSD, HPUX, even IRIX). While sar provides only a subset of the info obtained from the client script (so it couldn't replace ss/netstat or ip/ifconfig) it would reduce the overhead of having to support a range of different tools for plenty of metrics. It would probably standardise the output of metrics so that the parsing cond in xymond_client can be much simpler, easier to write and maintain, and less likely to have bugs. Generally speaking, parsing is something that can be difficult to do safely; programs that parse files and data streams are notoriously common targets for hackers. Any further work on Xymon needs to ensure that it works with up-to-date OSes, and anything that can be done to make that easier is likely to help the cause. J
list Adam Thorn
▸
On 17/08/2023 19:21, J.C. Cleaver wrote:
As it currently stands, xymon is already very efficient, so it's worth pointing out that the complexity really doesn't have to come in until you start hitting things at scale. If you're on a modern core and handling 90 msg/s, xymond is going to be just fine. If you're trying to push 9000 msg/s, more needs to be taken into consideration.
We see about ~100 msgs / second and CPU load on xymond has never even crossed our radar (we run xymond on a relatively low-spec VM with a single virtual CPU) The place where we have historically encountered performance-related issues was writing data to rrd files. We have a lot of custom tests and like being able to store and graph numerical data. My colleague thus implemented a custom xymond_channel listener which lets us take all our custom messages that come in a whole range of different formats, parse the messages to extract the numerical fields we're interested in, and then store them in a postgresql backend database rather than rrd files. This did also mean a moderate amount of custom development work for the web frontend (including some external js libs to draw graphs) to extract the data from the backend. That wouldn't have been possible without the xymond_channel architecture along with the simple and well-defined format of the xymon messages themselves. Adam
list Japheth Cleaver
▸
On Fri, August 18, 2023 01:31, Adam Thorn wrote:
On 17/08/2023 19:21, J.C. Cleaver wrote:As it currently stands, xymon is already very efficient, so it's worth pointing out that the complexity really doesn't have to come in until you start hitting things at scale. If you're on a modern core and handling 90 msg/s, xymond is going to be just fine. If you're trying to push 9000 msg/s, more needs to be taken into consideration.We see about ~100 msgs / second and CPU load on xymond has never even crossed our radar (we run xymond on a relatively low-spec VM with a single virtual CPU) The place where we have historically encountered performance-related issues was writing data to rrd files. We have a lot of custom tests and like being able to store and graph numerical data. My colleague thus implemented a custom xymond_channel listener which lets us take all our custom messages that come in a whole range of different formats, parse the messages to extract the numerical fields we're interested in, and then store them in a postgresql backend database rather than rrd files. This did also mean a moderate amount of custom development work for the web frontend (including some external js libs to draw graphs) to extract the data from the backend. That wouldn't have been possible without the xymond_channel architecture along with the simple and well-defined format of the xymon messages themselves.
Agreed. The simplicity of a streaming pipe of well-defined ASCII messages combined with a bus architecture makes it incredibly easy to extend or (in larger orgs) spew data out to another team to process in whatever manner they see fit. We had a bigdata team that wanted to do multi-dimensional analysis on "metrics" and a data/DS feed into their cluster via xymond_channel solved the problem completely. Often the only sticking point is that xymond_channel's recipient needs to be able to handle the quantity of data that's coming at it efficiently. The SysV IPC for registered channel listeners flagging their message as taken is one of the very few pinch points in the system. -jc
list Japheth Cleaver
▸
On Thu, August 17, 2023 16:44, Jeremy Laidman wrote:
On Fri, 18 Aug 2023 at 04:27, J.C. Cleaver <user-87556346d4af@xymon.invalid> wrote:On Mon, August 14, 2023 21:10, Berry van Sleeuwen wrote:We recently migrated our server to SLES15 SP4 and found there are a few network tools missing in the base, arp, netstat, ifconfig and route are supposed to be replaced by "ip" and "ss" command. While similar the output of these commands differs from the traditional tools so I guess that would interfere with the processing of the command output. For now it's solved by installing net-tools-deprecated but this might not be available in future versions so we might need support for these commands. I don't now if that is also the direction for other distributions, but it's at least the case for Suse and OpenSuse.Agreed; it's similar in the RHEL side. xymond_client updates that can interpret the output of ip and ss are probably called for now. While deprecated net-tools will stick around for sure for current systems, it's only a matter of time until they're removed, and in the meantime it's one less package to have to pull in for compatibility (and to explain). This probably goes higher on the list.Two brief comments about this. To me, xymond_client always seemed to be a good candidate for making it a bit more modular. The code is written in a modular way, to make it fairly easy to add new ways of collecting the same metrics from different OSes and OS versions (which would presumably make it possible for even me to add support for "ip" and "ss", albeit with bloated code and buffer overruns). But I thought it would be neat to be able to plug in some kind of run-time process to handle new scenarios - bit it a dynamic library, or a shared memory protocol or a worker module launched by xymond_channel or similar and written in whatever language was available and familiar to the sysadmin at the time.
This would definitely be a useful feature, with the most performant option I assume being a dynamic library module framework of some sort for common cases. I'm afraid designing this type of module system is a bit out of my baliwick. Then again, many (I suspect most) xymon users don't have the intense performance needs at the 1000s/msgs/s range. I'd prefer not to encourage *adding* forking on a per message basis, so a socket method would be on the table. Then again, xymond_channel basically *is* a socket and I suspect the impact of multiple 'client' channel listeners again is only going to become apparent at massive scale as well. This was the impetus for the --meta(ex)filter patches (https://sourceforge.net/p/xymon/code/7868/), as well as --multilocal (https://sourceforge.net/p/xymon/code/7811/) and a lot of other tuning (https://sourceforge.net/p/xymon/code/7813/). We had a *lot* of non-*nix "client"data coming through and we wanted to make sure we were processing as little unnecessary data as possible so we could quickly move onto the next one. One can also fork off to (the rather unfortunately named) "pee" utility from moreutils (https://www.putorius.net/linux-pee-command-tee-standard-input-into-pipes.html) and let multiple pipes read from STDIN, as long as they all can perform efficiently themselves; ultimately this is what we did. We combined all of our "extra" *nix tests (such as interpreting the output of /proc/mounts looking for disks that had flipped into ro-mode and generating a status msg for it) into a single large perl script that simply ran off the same linux client channel listener that xymond_client did. Given that most users won't have the kind of performance scale considerations we did, I wonder if what's needed more here isn't just *standardization* of add-ons (as mentioned elsewhere in the thread). Example: A drop-in (.d) location that provides a tasks.cfg snippet specifying what messages it cares about (or enough info for a plugin-generator to craft one) and a channel listener script directory with an executable that only gets the filtered messages it cares about, and is responsible for reinjecting status messages at its desire. There would also need to be a facility for easily adding graph definitions, etc. Perhaps what would be most helpful would simply be packagization templates that provide the file drops in the necessary locations directly, and/or a "plugins" directory that is scanned for relevant snippets a level down when found (e.g., "plugins/foobar/tasks.d/* ; plugins/foobar/graphs.d/*") to allow these to be distributed as simple tarballs.
▸
The emergence of "sar" as a universally available system metric reporting tool seems to solve this problem in a different way. If xymond_client had a "sar" module, it could pretty much support any popular modern OS apart from Windows (so Linux, Solaris, MacOS/*BSD, HPUX, even IRIX). While sar provides only a subset of the info obtained from the client script (so it couldn't replace ss/netstat or ip/ifconfig) it would reduce the overhead of having to support a range of different tools for plenty of metrics. It would probably standardise the output of metrics so that the parsing cond in xymond_client can be much simpler, easier to write and maintain, and less likely to have bugs. Generally speaking, parsing is something that can be difficult to do safely; programs that parse files and data streams are notoriously common targets for hackers.
I had to check this as well, as I was sure some [sar] reading had been added in, but t'was not the case. One experiment I had was running rotating 30s for 5m sadc collectors in a similar manner to how vmstat is executed in the client. This is at the very least helpful for hostdata client snapshots, but needed a processor on the server side, like you say, to make better use of it.
▸
Any further work on Xymon needs to ensure that it works with up-to-date OSes, and anything that can be done to make that easier is likely to help the cause.
Agreed 100%. Touching on the collector/processor distinction though: Xymon has had the client/local facility for quite a while now, dating back to 4.3.7 (https://sourceforge.net/p/xymon/code/6800/) but I'm not sure how well-known it is. In the Terabithia packages (and 4.4: https://sourceforge.net/p/xymon/code/7755/) there's a parallel "/sections" directory that works the same way but doesn't pre-pend "local:" to the section name (intended for site packages vs custom per-box scripting). -jc