I’m afraid that currently the keepalive configuration is indeed a client setting and not a check setting or server setting.
You could change the keepalive configuration when provisioning your host, like I do (e.g. tell Puppet to use specific values for keepalive when installing Sensu on the client) or change the default handler (not a great option, I agree).
I wonder if at least the handler should be a server setting. I have different opinions on the thresholds since they might be different for different hosts, but the handler should probably be on the server side.
On Friday, July 21, 2017 at 5:04:34 PM UTC+2, Kernel Panic wrote:
Hi guys, today I noticed that the keepalive notification was set to
default handler, which in my case is something different,. I’m using
something different for notification, so a server went down and I did
not get any notification at all, my question is, that keepalive
setting is a client side issue , or if there a way to configure a
default keepalive at the server level so I do not have to go client by
client adding the keepalive handler I use?