I’ve read the FAQ and understand how stashes are created as a result of silencing a node or check
How is the default handler supposed to interact with these stashes when they exist?
Also, how does dashboard interact with these stashes if they exist?
Thanks,
Adam
You need to do one of two things to take advantage of silence stashes. You can extend Sensu::Handler as part of sensu-plugin and you get the stash filtering by default. If not, you can implement your own stash filtering as part of your handler.
The dashboard does nothing but create or delete stashes. It uses the API endpoints to do this.
On Tue, Jul 9, 2013 at 9:36 AM, windowsrefund windowsrefund@gmail.com wrote:
I’ve read the FAQ and understand how stashes are created as a result of silencing a node or check
How is the default handler supposed to interact with these stashes when they exist?
Also, how does dashboard interact with these stashes if they exist?
Thanks,
Adam
I may be over-complicating things as I’m basically just looking for a way to simulate the old Nagios Host/Service dependencies bits. Maybe using a mutator to create a stash in order to silence events is not the cleanest way.
I just noticed the filter_dependencies method in sensu-handler.rb. Is anyone using it? Looks like the a ‘dependencies’ attribute can be added to a check with an array of check names. This seems like a possible solution for node-specific checks. For example, my super_duper_check can depend on ‘keepalive’ which would (hopefully) result in super_duper_check not generating an event when the node’s ‘keepalive’ check fails. If I’m correct, I’m probably going to see if I can extend this to work across nodes. This could probably be done by refactoring the method to use a hash rather than an array where the key would represent the node and the value represents checks related to that node.
Anxious to hear any thoughts…
Adam
I’m not using any of the dependent check stuff. I did submit a pull request to allow more filtering options based on subscription groups and silencing all.
On Tue, Jul 9, 2013 at 1:53 PM, windowsrefund windowsrefund@gmail.com wrote:
I may be over-complicating things as I’m basically just looking for a way to simulate the old Nagios Host/Service dependencies bits. Maybe using a mutator to create a stash in order to silence events is not the cleanest way.
I just noticed the filter_dependencies method in sensu-handler.rb. Is anyone using it? Looks like the a ‘dependencies’ attribute can be added to a check with an array of check names. This seems like a possible solution for node-specific checks. For example, my super_duper_check can depend on ‘keepalive’ which would (hopefully) result in super_duper_check not generating an event when the node’s ‘keepalive’ check fails. If I’m correct, I’m probably going to see if I can extend this to work across nodes. This could probably be done by refactoring the method to use a hash rather than an array where the key would represent the node and the value represents checks related to that node.
Anxious to hear any thoughts…
Adam