On 3/2/26 2:42 AM, nor krie wrote:
This will not work in most of my environments as either there is no mail configured or the xymon user is not allowed to send them.
ACK
Yes, I know about this and use it heavily for my custom inventory and reporting scripts. But this works only at the Xymon server and is dependend from its binaries.
My first hand experience questions the veracity of that statement.
I've been able to collect the data from other Xymon clients in addition to just the Xymon server.
I also question if the Xymon client command is actually needed. Looking at tcpdump, it seems like it's basically just text that's sent via a TCP connection.
I strongly suspect you can retrieve data using the same method as you can send status updates without the Xymon commands; e.g. telnet / raw TCP connection. -- I don't have time to get to poke this at the moment.
The ability to get those infos by a standardized API from extern would be helpful to connect Xymon with other management tools (and would increase the acceptance of Xymon imo). But this is not of high prio from my side as I am fine with my current solutions.
I think you can get the information in a standard way. It's just not the standard that I think you're referring to.
Obligatory xkcd:
Link - xkcd: Standards
-- Grant. . . . unix || die