The Sensu assets packaged from this repository are built against the Sensu ruby runtime environment. When using these assets as part of a Sensu Go resource (check, mutator or handler), make sure you include the corresponding Sensu ruby runtime asset in the list of assets needed by the resource. The current ruby-runtime assets can be found here in the Bonsai Asset Index.
- /bin/check-es-circuit-breakers.rb
- /bin/check-es-cluster-health.rb
- /bin/check-es-cluster-status.rb
- /bin/check-es-file-descriptors.rb
- /bin/check-es-heap.rb
- /bin/check-es-indices-field-count.rb
- /bin/check-es-indexes.rb
- /bin/check-es-indicies-sizes.rb
- /bin/check-es-node-status.rb
- /bin/check-es-query-count.rb
- /bin/check-es-query-exists.rb
- /bin/check-es-query-ratio.rb
- /bin/check-es-shard-allocation-status.rb
- /bin/handler-es-delete-indices.rb
- /bin/metrics-es-cluster.rb
- /bin/metrics-es-node.rb
- /bin/metrics-es-node-graphite.rb
When using handler-es-delete-indices.rb with Sensu Go, you will need to use the event mapping commandline option, see handler-es-delete-indices.rb --help for details. And please read the sensu-plugin README for more information on the event mapping functionality.
This repository uses the Kitchen suite for it's tests.
Note: The test suite uses an elasticsearch instance in order to have passing tests. Execute the following command to create a mock elasticsearch 6 instance:
docker run -d --name sensu-elasticsearch-6 docker.elastic.co/elasticsearch/elasticsearch:6.2.2Running the tests:
bundle install --path vendor/bundle
bundle exec kitchen testYou can find sample output for all tests running successfully in this gist.