Den 2014-03-17 13:17, Jeremy Laidman skrev:
On 14 March 2014 21:42, Henrik Størner <henrik at hswn.dk [1]> wrote:
It has been reported before, and is usually caused by the client data containing a very long list of network connections.
Would it be possible to have xymond recognise a client data message that is compressed and auto-decompress it? Then we could insert a "| gzip" into xymonclient.sh, and many of these problems would go away.
In fact, having a generic pre-processor plug-in framework could be really useful beyond just compression. It could perform authentication to compare status/data message signatures against public keys (or certs) stored in a xymon-hostkeys.cfg file, and reject messages that don't match the signing key for a host. A plug-in for encryption would work the same way.
Much of this has already been put into version 5: Compression, TLS encryption and client authentication via client SSL certificates. So it is pretty much done.
Regards, Henrik
Links:
[1] mailto:henrik at hswn.dk