# Sensu-base-checks

**URL:** <https://discourse.sensu.io/t/sensu-base-checks/1524>\
**Category:** Sensu Plugins\
**Tags:** sensu-go\
**Created:** [December 14, 2019, 12:59pm UTC](https://discourse.sensu.io/t/sensu-base-checks/1524 "2019-12-14T12:59:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![julian7](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/julian7/32/238_2.png) [@julian7](https://discourse.sensu.io/u/julian7)\
**Post date:** [December 14, 2019, 12:59pm UTC](https://discourse.sensu.io/t/sensu-base-checks/1524/1 "2019-12-14T12:59:10Z")

</div>

I was about to replace my current sensu-core setup with sensu-go, when I realized I don’t (and I don’t want to) have a ruby environment anymore.

It’s not because I don’t like ruby. I like it very much. However, when I put on my ops hat, a ruby env is just another liability.

Then, I realized I was using two checks extensively: `check-disk-usage.rb`, and `check-http.rb`. There are others (like check-http-json.rb` for example), which I also use, but that’s not that critical.

Therefore, I’ve written [sensu-base-checks](https://github.com/julian7/sensu-base-checks), and published it in either [asset](https://github.com/julian7/sensu-base-checks/releases/download/v0.1.4/sensu-base-checks-v0.1.4-asset.yml) file, and in bonsai (sorry, no link because of limits).

I plan to bring my own agenda forward (adding items I used to use), but I’m also open for requests 🙂.

Do you have any issues, requests, or questions? Please ask here.