Is there a particular reason why the existing HTTP API exposed by Monit
only supports HTML-formatted responses? Would it be a conflict of interest
if someone offered an extension to the existing browser-oriented HTTP
interface that would support JSON-encoded requests and responses to benefit
remote management of a large deployment of Monit servers (dozens of Monit
instances)?

I suspect this may partly conflict with commercial nature of M/Monit. Would
such patch be rejected by the maintainers of the project?


Regards,
/Sergey
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Reply via email to