I have a use case for this plugin where I need each agent to check multiple unique vhosts depending on their configuration. For example, server A needs an http check for https://foo.org and https://bar.com, and server B for https://orange.fruit, https://banana.fruit and https://mango.fruit. In the output I want to see which vhosts pass and fail.
Currently I have the hosts templated as {{ .annotations.check_http_uris }} and wrapped the check in a parallel invocation, which is fairly straightfoward and generally works, but it tends to break with system updates because of the LD_LIBRARY_PATH Sensu passes for Ruby.
Of course it could be done with a custom script, but this has the disadvantage of either (a) having to cram much more in a single command than what's comfortable or (b) having to install a script file on all client systems, which is horrible if the systems can't be updated at the same time.
Could multiple URI support be a good feature for this plugin? Or is there a better way to approach this situation?
I have a use case for this plugin where I need each agent to check multiple unique vhosts depending on their configuration. For example, server A needs an http check for
https://foo.organdhttps://bar.com, and server B forhttps://orange.fruit,https://banana.fruitandhttps://mango.fruit. In the output I want to see which vhosts pass and fail.Currently I have the hosts templated as
{{ .annotations.check_http_uris }}and wrapped the check in aparallelinvocation, which is fairly straightfoward and generally works, but it tends to break with system updates because of theLD_LIBRARY_PATHSensu passes for Ruby.Of course it could be done with a custom script, but this has the disadvantage of either (a) having to cram much more in a single command than what's comfortable or (b) having to install a script file on all client systems, which is horrible if the systems can't be updated at the same time.
Could multiple URI support be a good feature for this plugin? Or is there a better way to approach this situation?