ruby-on-railsmonit

Monit stops responding when more that 512 configurations are added


Should be a fairly simple question but is anyone aware of any limitations regarding monit and having more than 512 configurations and if so any way to bypass?

It seems to stop being able to load items when it hits the 512 limit but we are unable to find any mentions of this in documentations or elsewhere.

The version of monit we are using is not the latest so if upgrading will solve it thats also fine but would just need to know if thats the issue or not before doing the upgrade?

If i have missed anything just let me know and ill speak to the gent that handles this stuff our end (thats not me if you couldnt tell by my vagueness).

Cheers in advance for any help guys, much appreciated

Regards

Scott.


Solution

  • This is a hard coded limit today.

    Should be a fairly simple question but is anyone aware of any limitations regarding monit and having more than 512 configurations and if so any way to bypass?

    You are right, the limit is not documented.

    With regards, Lutz