Fwd: Re. Is this thing on?
Hi. Seem that Ye-Fee is unable to email to the mailing list? *Can you check that if there is a problem ( I think Henrik) ?*
By to way, I remember that we have to migrate to another service.
*What about: https://mailman3.com/ which is free for opensource ?* (comment to do or not to do are welcome!) *Can someone take the job ? * Thing to do:
- Ask malman3 if possible to have a freemailing list
- The we can see how to do it! (That will need for sure to contact Henrik), but I can help also.
Bruno
-------- Forwarded Message -------- Subject: Re. [Xymon] Is this thing on? Date: Thu, 28 Sep 2023 16:22:00 +0000 From: Liang, Ye-Fee [PHSA] <yefee.liang at phsa.ca> To: bruno.manzoni at ubi-network.ch <bruno.manzoni at ubi-network.ch>
Hi Bruno,
?? I was able to email xymon at xymon.com long time ago, and now find myself unable to email
anymore.? I have used xymon at different organizations over the decades, and would love to
help the tool/platform to continue for decades more.? Simply there is no other product
that is more versatile, easy to manage, and light server+client requirement.? Many more people are
eager to contribute, but can only just read the xymon list email, from the side line.
?? Thanks for your summary of Xymon non-technical and technical needs. Just to keep the
enthusiasm going, I would suggest a section on "making the better use of Xymon as now"
I am only a sys admin, not a coder, so my focus is on management and usability areas.
enhanced cpu utilization graph (adds wait IO; better colors); see 1a.
menu script (see 2a) to clean up of accumulating rrd, hostdata and histlogs, eg. due to short-term
???ad-hoc metrics like nfs file systems, container nic devices.
- menu script (see 3a) to manage clients easier
Keep up the great work!
Ye-Fee
1a
2a
c) change Client:?????? yyy
ct) change days to trim: 30
- summary???? 1a) list pings?? 1b) list cpu clients
1bbb) list to scp file?????????? 1bb) list in one column
1c) list non-pings tests?????? ??1d) list non-green cpu tests
2)? duplicate report
3)? Info on client?????????????? 3a) formatted
4)? Search client in hosts.cfg+
6)? find clients with too many rrd's???? 6z) list -5
RRD's 6a) list top 10?? 6af) find top 10?? 6at) trim
hostdata's ?6b) list top 10?? 6bf) find top 10?? 6bt) trim
histlogs's 6c) list top 10?? 6cf) find top 10?? 6ct) trim
Select from top 10 to trim??? 6ta) RRD? 6tb) hostdata? 6tc) histlogs
7a) diff host_cfg files????????? 7u) update host_cfg files
3a
c) Change Client: vag7
c1) check ssh???????????????? c2) ps -ef | grep xym
c3) copy-id?????????????????? c4) check client os version
2a) info xymonclient/logs???? 3a) log: logs/xymonclient.log
2b) info xymonclient/tmp????? 3i) log info? 3t) log tail
2c) info xymonclient dir????? 3u) log util
3s) scan xymonclient.log
5a) start xymonclient???????? 5c) status
5b) stop
t1) curl nag1 (10.248.224.149) 1984 test???? t3) telnet
t2) curl nag2 (142.71.43.51)?? 1984 test???? t4) telnet
t8) rm known_hosts entry
dc) compare config file?????? dx) cp? + extract client file
d2) diff vmstat2.sh?????????? d3) cp vmstat2.sh to client
d6) client file: xymonclient_v4_3_28_RH7.gz
d7) config file: xymonclient.cfg
d9) copy config file to client
On Fri, September 29, 2023 00:46, Bruno Manzoni wrote:
Hi. Seem that Ye-Fee is unable to email to the mailing list? *Can you check that if there is a problem ( I think Henrik) ?*
By to way, I remember that we have to migrate to another service.
*What about: https://mailman3.com/ which is free for opensource ?* (comment to do or not to do are welcome!) *Can someone take the job ? * Thing to do:
- Ask malman3 if possible to have a freemailing list
- The we can see how to do it! (That will need for sure to contact Henrik), but I can help also.
I was considering this as well. Given that the existing list is run on mailman, keeping it with that will make migration easier I presume. The mail archives for this are a pretty important resource for self-help, IMO, so we'd want those to still be accessible -- ideally with the same URL.
I've seen a few ads out there for Mailman list hosting, but I'm not sure if there's a clear favorite or open source standard out of the bunch. Of course, it's still just a mail app, so self-hosting on a VM is a reasonable solution going forward.
I suppose this is really up to Henrik :) as to what he wants to do with the lists.xymon.com subdomain, and shuttling mail archives around. I'd be willing to host it, but more administrative diversity is also important to the future health of any project.
-jc
Hi every one
*I did a POC on GitHub! *- https://github.com/xymon-monitoring To include/manage the summary of problem (I did previously on this mailing list). The mailing list is not really good to follow problems that take a long time to be resolved (my point of view) This summary also evolve with some more details (but mainly from me) and take a also new form for a better follow up (I hope so) : https://github.com/xymon-monitoring/problem-solving
This is only a POC so not official at all, but just for you to see what I did/what could be done (currently limited by my poor skills)
You are invited to help me to improve this POC, so to be a member of this GitHub organization: *let me know your GitHub name*
Remark:
- *Let me know what you think!*
- *Focus on the general ideas*: *the support (GitHub)* and *the form* I choose and not to much in the content (I try to make also a good content, but for sure this will need many more work, I would like first to add latest feedback: WIP)
- Constructive comment about anything is always welcome!
- And as English is not my language: do not hesitate also to correct it.
- Positive feedback also motivate...
*We still have an urgent problem: the mailing list *(see detail on the POC or in this mailing list)
Bruno
On Sun, October 1, 2023 23:19, Bruno Manzoni wrote:
Hi every one
*I did a POC on GitHub! *- https://github.com/xymon-monitoring To include/manage the summary of problem (I did previously on this mailing list). The mailing list is not really good to follow problems that take a long time to be resolved (my point of view) This summary also evolve with some more details (but mainly from me) and take a also new form for a better follow up (I hope so) : https://github.com/xymon-monitoring/problem-solving
This is only a POC so not official at all, but just for you to see what I did/what could be done (currently limited by my poor skills)
You are invited to help me to improve this POC, so to be a member of this GitHub organization: *let me know your GitHub name*
Remark:
- *Let me know what you think!*
- *Focus on the general ideas*: *the support (GitHub)* and *the form* I choose and not to much in the content (I try to make also a good content, but for sure this will need many more work, I would like first to add latest feedback: WIP)
- Constructive comment about anything is always welcome!
- And as English is not my language: do not hesitate also to correct it.
- Positive feedback also motivate...
*We still have an urgent problem: the mailing list *(see detail on the POC or in this mailing list)
Thank you for this! While moving development as a whole to GH is still an open question, it definitely helps to have a presence there, and an editable tracking method for various goals is helpful.
There is a lot of previous development tracking work at https://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Developer_Guide , but I'm not certain wikibooks itself is the best platform for hosting of it. Of course, much does need to be updated there, but an intro going forward would be helpful.
There's a LOT to chew through here; if we have any Library Science folks on the list, your input would be appreciated ;)
I've also been compiling a list of various Xymon/Hobbit presentations and intro materials that have been posted out there. In the interim (before any major re-structuring of a home page), simply making more details available for folks and leveraging the explainers people have already done (including the xymon 7 man page) would probably be helpful.
Agreed that the most pending immediate issue would be the mailing list, especially if there's a transfer/hosting contract deadline coming up.
Henrik: Would you like me to start working on a mailman hosting build?
Regards, -jc
JC, is there any new info regarding Xymon Server or XymonPSClient being updated any time soon?? I know there's been a conversation about it in the past few months, but the server's last version release was in 2019 and the Windows client was last updated then also.? There's been significant OS changes both on servers and clients in the past 5 years.? Can you please comment on the planned time frame of a release?? I love Xymon and I very much want to stick with it, but it's limitations have been manifesting a lot in my realm lately and I'm wondering if I should look for a new tool.
Kris Springer
On 10/3/23 21:40, J.C. Cleaver wrote:
On Sun, October 1, 2023 23:19, Bruno Manzoni wrote:
Hi every one
*I did a POC on GitHub! *- https://github.com/xymon-monitoring To include/manage the summary of problem (I did previously on this mailing list). The mailing list is not really good to follow problems that take a long time to be resolved (my point of view) This summary also evolve with some more details (but mainly from me) and take a also new form for a better follow up (I hope so) : https://github.com/xymon-monitoring/problem-solving
This is only a POC so not official at all, but just for you to see what I did/what could be done (currently limited by my poor skills)
You are invited to help me to improve this POC, so to be a member of this GitHub organization: *let me know your GitHub name*
Remark:
- *Let me know what you think!*
- *Focus on the general ideas*: *the support (GitHub)* and *the form* I choose and not to much in the content (I try to make also a good content, but for sure this will need many more work, I would like first to add latest feedback: WIP)
- Constructive comment about anything is always welcome!
- And as English is not my language: do not hesitate also to correct it.
- Positive feedback also motivate...
*We still have an urgent problem: the mailing list *(see detail on the POC or in this mailing list) Thank you for this! While moving development as a whole to GH is still an open question, it definitely helps to have a presence there, and an editable tracking method for various goals is helpful.
There is a lot of previous development tracking work at https://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Developer_Guide , but I'm not certain wikibooks itself is the best platform for hosting of it. Of course, much does need to be updated there, but an intro going forward would be helpful.
There's a LOT to chew through here; if we have any Library Science folks on the list, your input would be appreciated ;)
I've also been compiling a list of various Xymon/Hobbit presentations and intro materials that have been posted out there. In the interim (before any major re-structuring of a home page), simply making more details available for folks and leveraging the explainers people have already done (including the xymon 7 man page) would probably be helpful.
Agreed that the most pending immediate issue would be the mailing list, especially if there's a transfer/hosting contract deadline coming up.
Henrik: Would you like me to start working on a mailman hosting build?
Regards, -jc
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
As an update:
The 4.4 release is still pending pcre2 work, unfortunately, which is going to be a requirement for getting things re-added into distributions. That one is still without ETA.
There's also a crashing bug that's been reported in F38 and F39 (and rawhide) which prevents xymond_client processing that I've been trying to track down. The latter, and the several other submitted patches, will be the 4.3.31 release. I've been waiting for the GCC 14 drop in Rawhide to test against as well to ensure we don't have new issues introduced there at the same time. I don't *think* they're related, but after so long since the last release on the stable branch, I don't want that to be a source of more instability.
Finally, although using system libraries is strongly preferred, c-ares is still an included build, and it's been going through a rapid 1.20->1.26 release cycle since the start of October while they fix various reported issues.
WRT the mailing list, mailman3 is (finally!) fully available on EL9 -- including the web interface needed for signups -- so hoping to complete the transition to the new server shortly. Just has been a very busy last two weeks.
Regards, -jc
On Fri, January 26, 2024 13:44, Kris Springer wrote:
JC, is there any new info regarding Xymon Server or XymonPSClient being updated any time soon??? I know there's been a conversation about it in the past few months, but the server's last version release was in 2019 and the Windows client was last updated then also.?? There's been significant OS changes both on servers and clients in the past 5 years.?? Can you please comment on the planned time frame of a release??? I love Xymon and I very much want to stick with it, but it's limitations have been manifesting a lot in my realm lately and I'm wondering if I should look for a new tool.
Kris Springer
On 10/3/23 21:40, J.C. Cleaver wrote:
On Sun, October 1, 2023 23:19, Bruno Manzoni wrote:
Hi every one
*I did a POC on GitHub! *- https://github.com/xymon-monitoring To include/manage the summary of problem (I did previously on this mailing list). The mailing list is not really good to follow problems that take a long time to be resolved (my point of view) This summary also evolve with some more details (but mainly from me) and take a also new form for a better follow up (I hope so) : https://github.com/xymon-monitoring/problem-solving
This is only a POC so not official at all, but just for you to see what I did/what could be done (currently limited by my poor skills)
You are invited to help me to improve this POC, so to be a member of this GitHub organization: *let me know your GitHub name*
Remark:
- *Let me know what you think!*
- *Focus on the general ideas*: *the support (GitHub)* and *the form* I choose and not to much in the content (I try to make also a good content, but for sure this will need many more work, I would like first to add latest feedback: WIP)
- Constructive comment about anything is always welcome!
- And as English is not my language: do not hesitate also to correct it.
- Positive feedback also motivate...
*We still have an urgent problem: the mailing list *(see detail on the POC or in this mailing list) Thank you for this! While moving development as a whole to GH is still an open question, it definitely helps to have a presence there, and an editable tracking method for various goals is helpful.
There is a lot of previous development tracking work at https://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Developer_Guide , but I'm not certain wikibooks itself is the best platform for hosting of it. Of course, much does need to be updated there, but an intro going forward would be helpful.
There's a LOT to chew through here; if we have any Library Science folks on the list, your input would be appreciated ;)
I've also been compiling a list of various Xymon/Hobbit presentations and intro materials that have been posted out there. In the interim (before any major re-structuring of a home page), simply making more details available for folks and leveraging the explainers people have already done (including the xymon 7 man page) would probably be helpful.
Agreed that the most pending immediate issue would be the mailing list, especially if there's a transfer/hosting contract deadline coming up.
Henrik: Would you like me to start working on a mailman hosting build?
Regards, -jc
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
As an update:
The 4.4 release is still pending pcre2 work, unfortunately, which is going to be a requirement for getting things re-added into distributions. That one is still without ETA.
There's also a crashing bug that's been reported in F38 and F39 (and rawhide) which prevents xymond_client processing that I've been trying to track down. The latter, and the several other submitted patches, will be the 4.3.31 release. I've been waiting for the GCC 14 drop in Rawhide to test against as well to ensure we don't have new issues introduced there at the same time. I don't *think* they're related, but after so long since the last release on the stable branch, I don't want that to be a source of more instability.
Finally, although using system libraries is strongly preferred, c-ares is still an included build, and it's been going through a rapid 1.20->1.26 release cycle since the start of October while they fix various reported issues.
WRT the mailing list, mailman3 is (finally!) fully available on EL9 -- including the web interface needed for signups -- so hoping to complete the transition to the new server shortly. Just has been a very busy last two weeks.
Regards, -jc
On Fri, January 26, 2024 13:44, Kris Springer wrote:
JC, is there any new info regarding Xymon Server or XymonPSClient being updated any time soon??? I know there's been a conversation about it in the past few months, but the server's last version release was in 2019 and the Windows client was last updated then also.?? There's been significant OS changes both on servers and clients in the past 5 years.?? Can you please comment on the planned time frame of a release??? I love Xymon and I very much want to stick with it, but it's limitations have been manifesting a lot in my realm lately and I'm wondering if I should look for a new tool.
Kris Springer
On 10/3/23 21:40, J.C. Cleaver wrote:
On Sun, October 1, 2023 23:19, Bruno Manzoni wrote:
Hi every one
*I did a POC on GitHub! *- https://github.com/xymon-monitoring To include/manage the summary of problem (I did previously on this mailing list). The mailing list is not really good to follow problems that take a long time to be resolved (my point of view) This summary also evolve with some more details (but mainly from me) and take a also new form for a better follow up (I hope so) : https://github.com/xymon-monitoring/problem-solving
This is only a POC so not official at all, but just for you to see what I did/what could be done (currently limited by my poor skills)
You are invited to help me to improve this POC, so to be a member of this GitHub organization: *let me know your GitHub name*
Remark:
- *Let me know what you think!*
- *Focus on the general ideas*: *the support (GitHub)* and *the form* I choose and not to much in the content (I try to make also a good content, but for sure this will need many more work, I would like first to add latest feedback: WIP)
- Constructive comment about anything is always welcome!
- And as English is not my language: do not hesitate also to correct it.
- Positive feedback also motivate...
*We still have an urgent problem: the mailing list *(see detail on the POC or in this mailing list) Thank you for this! While moving development as a whole to GH is still an open question, it definitely helps to have a presence there, and an editable tracking method for various goals is helpful.
There is a lot of previous development tracking work at https://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Developer_Guide , but I'm not certain wikibooks itself is the best platform for hosting of it. Of course, much does need to be updated there, but an intro going forward would be helpful.
There's a LOT to chew through here; if we have any Library Science folks on the list, your input would be appreciated ;)
I've also been compiling a list of various Xymon/Hobbit presentations and intro materials that have been posted out there. In the interim (before any major re-structuring of a home page), simply making more details available for folks and leveraging the explainers people have already done (including the xymon 7 man page) would probably be helpful.
Agreed that the most pending immediate issue would be the mailing list, especially if there's a transfer/hosting contract deadline coming up.
Henrik: Would you like me to start working on a mailman hosting build?
Regards, -jc
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Hi,
Regarding the Windows Powershell client, the core functionality works in all recent windows versions. Under the hood, the windows of today is stil the Windows of 15 years ago. I have some updates for the Powershell clients, but they are more related to config changes and some extra functionality.
We run the client on 1.000 servers with 0 issues or missing functionality.
Stef
Thanks Stef, do you have the XymonPSClient sending it's stats back to the Xymon Server over https in all of those 1,000 servers?? Could you provide a redacted sample of the xymonclient_config.xml you're using on those functioning clients?? Perhaps there's an option that I need to enable.? I too use it many places, but only the hosts that are sending via https are having issues.
Kris Springer
On 1/29/24 8:48 AM, Stef Coene wrote:
Hi,
Regarding the Windows Powershell client, the core functionality works in all recent windows versions. Under the hood, the windows of today is stil the Windows of 15 years ago. I have some updates for the Powershell clients, but they are more related to config changes and some extra functionality.
We run the client on 1.000 servers with 0 issues or missing functionality.
Stef
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Hi,
Not all the clients use https because some of them are too old. Or the firewall is not open (and it's too troublesome to get the network team too open an extra port).
The xml file is really basic, no strange settings.
I attached my version to this mail. Can you test with that version? I changed how the message is encoded and also some small changes that screwed up the procs check.
With my version you can also set xymonlogarchive so the logfile and data files are saved in a directory. That can help in debugging. Example: xymonlogarchive:logs:7
Stef
On 29/01/2024 16:54, Kris Springer wrote:
Thanks Stef, do you have the XymonPSClient sending it's stats back to the Xymon Server over https in all of those 1,000 servers?? Could you provide a redacted sample of the xymonclient_config.xml you're using on those functioning clients?? Perhaps there's an option that I need to enable.? I too use it many places, but only the hosts that are sending via https are having issues.
Kris Springer
On 1/29/24 8:48 AM, Stef Coene wrote:
Hi,
Regarding the Windows Powershell client, the core functionality works in all recent windows versions. Under the hood, the windows of today is stil the Windows of 15 years ago. I have some updates for the Powershell clients, but they are more related to config changes and some extra functionality.
We run the client on 1.000 servers with 0 issues or missing functionality.
Stef
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Hi everyone,
I just reached a milestone? (mainly I have finish for now to clean the idea, the shape and the content) of the PoC https://github.com/xymon-monitoring/problem-solving that try to take help Xymon moving forward by following "current problems" and "wishes" that you have !
Let me know if you like it (feedback very very very very very appreciate: none received really so far: so very very very difficult to improve something without any feedback: No problem also if you just don't like it, but let me know!)
Thank you very very much for your help!
Bruno
On 02.10.2023 08:19, Bruno Manzoni wrote:
Hi every one
*I did a POC on GitHub! *- https://github.com/xymon-monitoring To include/manage the summary of problem (I did previously on this mailing list). The mailing list is not really good to follow problems that take a long time to be resolved (my point of view) This summary also evolve with some more details (but mainly from me) and take a also new form for a better follow up (I hope so) : https://github.com/xymon-monitoring/problem-solving
This is only a POC so not official at all, but just for you to see what I did/what could be done (currently limited by my poor skills)
You are invited to help me to improve this POC, so to be a member of this GitHub organization: *let me know your GitHub name*
Remark:
- *Let me know what you think!*
- *Focus on the general ideas*: *the support (GitHub)* and *the form* I choose and not to much in the content (I try to make also a good content, but for sure this will need many more work, I would like first to add latest feedback: WIP)
- Constructive comment about anything is always welcome!
- And as English is not my language: do not hesitate also to correct it.
- Positive feedback also motivate...
*We still have an urgent problem: the mailing list *(see detail on the POC or in this mailing list)
Bruno
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Just receive this info from Jezzaaa (in the PoC "problem solving" repo). (remark for anyone: If you can send mail to the mailing list: prefer it, if you cannot: no problem,? do what you can!)
Hi Bruno. Firstly, thanks for trying to find ways to progress Xymon, and Devmon too.
I think this is a good option for tracking problems and feature requests. I'm a bit old-school and while I've been using Github for a few years, I'm not familiar with all of its features and quirks. I agree that we need a single "collection point" for bugs/requests, and other forums can channel queries to here.
I'm a bit surprised you said "dev" info should not be here. Although perhaps I don't understand quite what you mean.
I would really like to see the Xymon source code imported into Github. I think this would be a great way to allow other developers to fork, test, and submit "pull requests" for merging. I think this would help the primary developers/maintainers to be able to manage patches.
Previously, patches were submitted in a number of ways. There's a "xymon-dev" mailing list, for instance, that some people used to submit patches. Others emailed the main mailing list with patches. I believe working with Git and Github can streamline this process.
My comments on some of these:
- skinning - nice to have, and can "freshen" xymon's look (personally, I like the current look)
- alternative dashboards - I suspect new dashboards can be added on without changing the existing code, by using the xymon client to query status from the xymond process via localhost:TCP/1984 (also see "Xymondash" - not sure how this works, but it's a new look that doesn't need the old look to go away)
- repo is probably very important, but that's an uninformed opinion and JC/Henrik would need to be comfortable
- make xymon up to date: this needs a fair bit of work client-side and server-side, but perhaps the server side can be extend to support per-OS plug-ins, and reduce the need to continually track OS changes
- Moving away from C: I don't really see this as being all that useful. Other languages have useful features, but they all come and go, and C is the language that seems to have endless longevity
- API: Xymon already has an API of sorts; but there might be some limited benefit in providing one or more other APIs such as JSON. However I suspect the popularity of JSON/REST and their ilk is going to wane over time, as other universal APIs come along. I think a CGI shim is probably the way to achieve this, and probably doesn't need any changes to the core code.
Other things high on my "requested features" list:
- IPv6
- SNMP that's robust, and has enough features to replace devmon
Info from Jeezzaa incorporated to the PoC "problem solving", Jezzaaa invited as a member of the PoC. Jeezzaa put some comments on some problems: I did not think about that: I like it: so feel free also to add yours: 1 comment per person would be perfect! Remark: I did try to summary also each problems: to have a quick view of any problems: This is quite challenging to be non oriented: So expect some mistakes and clumsiness. Best would be that some of you help me doing that.
Thank you very very very much Jeezzaaa for the feedback ! Bruno
On 09.10.2023 05:58, Bruno Manzoni wrote:
Just receive this info from Jezzaaa (in the PoC "problem solving" repo). (remark for anyone: If you can send mail to the mailing list: prefer it, if you cannot: no problem,? do what you can!)
Hi Bruno. Firstly, thanks for trying to find ways to progress Xymon, and Devmon too.
I think this is a good option for tracking problems and feature requests. I'm a bit old-school and while I've been using Github for a few years, I'm not familiar with all of its features and quirks. I agree that we need a single "collection point" for bugs/requests, and other forums can channel queries to here.
I'm a bit surprised you said "dev" info should not be here. Although perhaps I don't understand quite what you mean.
I would really like to see the Xymon source code imported into Github. I think this would be a great way to allow other developers to fork, test, and submit "pull requests" for merging. I think this would help the primary developers/maintainers to be able to manage patches.
Previously, patches were submitted in a number of ways. There's a "xymon-dev" mailing list, for instance, that some people used to submit patches. Others emailed the main mailing list with patches. I believe working with Git and Github can streamline this process.
My comments on some of these:
- skinning - nice to have, and can "freshen" xymon's look (personally, I like the current look)
- alternative dashboards - I suspect new dashboards can be added on without changing the existing code, by using the xymon client to query status from the xymond process via localhost:TCP/1984 (also see "Xymondash" - not sure how this works, but it's a new look that doesn't need the old look to go away)
- repo is probably very important, but that's an uninformed opinion and JC/Henrik would need to be comfortable
- make xymon up to date: this needs a fair bit of work client-side and server-side, but perhaps the server side can be extend to support per-OS plug-ins, and reduce the need to continually track OS changes
- Moving away from C: I don't really see this as being all that useful. Other languages have useful features, but they all come and go, and C is the language that seems to have endless longevity
- API: Xymon already has an API of sorts; but there might be some limited benefit in providing one or more other APIs such as JSON. However I suspect the popularity of JSON/REST and their ilk is going to wane over time, as other universal APIs come along. I think a CGI shim is probably the way to achieve this, and probably doesn't need any changes to the core code.
Other things high on my "requested features" list:
- IPv6
- SNMP that's robust, and has enough features to replace devmon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
participants (4)
-
bruno.manzoni＠ubi-network.ch
-
cleaver＠terabithia.org
-
kspringer＠innovateteam.com
-
stef.coene＠docum.org