If the hosts are already in Sensu, you can create a check with a proxy request attribute which will find all clients which has certain attributes. As the example in the docs describe, you can then have the check go to a roundrobin subscription for some host to run the commands. So in theory, if you had 600 clients which have a client config looking something like this:
You could have a check defined on the server that looks like this:
“command”: “check-ssh.rb -h :::address:::”,
Internal to sensu, it finds all clients with those attributes (os == linux), and then adds the client name to the source, and replaces the :::address::: part of the command for you. The checks will happen on some subset of hosts which should be checking for ssh, but the results will be attributed to the individual client, not the host checking it.
Hope that makes sense and answers your question.
On Monday, April 3, 2017 at 3:56:33 PM UTC-4, Vahagn wrote:
I was wondering if initial question found another answer with better approach or no?
As I am running POC for Sensu , but we have more that 600 server and we have some application checks which are executed across multiple servers from some remote server.
So descried 2 approaches are not really correct way of doing things.
- 600 check definition will be paint in the …
- Triggering dead man switch with several checks will not tell me what is the real problem.
To sum up , is it possible to run check from remote server on subscription list from sensu ?
With best regards,