-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for setting spawn limit via puppet #727
Comments
Thanks @cabecada for reporting this! @agoddard @cwjohnston I cannot find any documentation for this option on our site. Could you point me in the right direction? Which file should this go in? |
You're right there's no documentation for this setting presently. sensu/sensu-docs#451 is tracking that need. Because this modifies the concurrency of both sensu-server pipe handler execution and sensu-client check execution (when running on same system), I recommend using /etc/sensu/conf.d/spawn.json |
This is what i tried but i guess this has to go via providers and types?
|
Without this patch the Sensu spawn limit setting cannot easily be configured by this module. This patch addresses the problem by adding a sensu::spawn_limit class parameter. If unset, the parameter defaults to the behavior of Sensu which is to have a limit of 12 in version 0.29.0. Resolves sensu#727
Without this patch the Sensu spawn limit setting cannot easily be configured by this module. This patch addresses the problem by adding a sensu::spawn_limit class parameter. If unset, the module behavior defers to the default behavior of Sensu which uses an effective spawn limit of 12 in version 0.29.0. Resolves sensu#727
(#727) Add sensu::spawn_limit class parameter
Thanks everyone! @jeffmccune 's fix is in v2.24.0 |
we have hit the bottleneck of too many checks (JIT) from a single server leading to issues addressed by sensu/sensu#1265. i know there are other workarounds to deal with this, but since this is public(?) config, i guess it should be configurable via puppet.
but it seems this is not yet configurable via puppet.
any plans to include this configurable option ?
The text was updated successfully, but these errors were encountered: