How to monitor server resources with checks

What are Sensu checks?

Sensu checks are commands (or scripts), executed by the Sensu agent, that output data and produce an exit code to indicate a state. Sensu checks use the same specification as Nagios, therefore, Nagios check plugins may be used with Sensu.

Why use a check?

Checks are commonly used to monitor server resources, services, and application health (e.g. is Nginx running?) as well as collect & analyze metrics (e.g. how much disk space do I have left?)

Using checks to monitor a service

The purpose of this guide is to help you monitor server resources, more specifically the CPU usage, by configuring a check named check-cpu with a subscription named linux, in order to target all entities subscribed to the linux subscription. This guide requires a Sensu backend and at least one Sensu agent running on Linux.

Installing a script

The script provided by the Sensu CPU Checks Plugin can reliably detect the percentage of CPU usage. The following command will provide the script and should be run on every Sensu agent that has an entity subscribed to the linux subscription.

sudo curl \
-o /usr/local/bin/ && \
sudo chmod +x /usr/local/bin/

While this command is appropriate when running a few agents, you should consider using a configuration management tool or use Sensu assets to provide runtime dependencies to checks on bigger environments.

NOTE: On RHEL/CentOS, the plugin requires bc. Run sudo yum install bc to install bc.

Creating the check

Now that our script is installed, the second step is to create a check named check-cpu, which runs the command -w 75 -c 90, at an interval of 60 seconds, for all entities subscribed to the linux subscription.

sensuctl check create check-cpu \
--command ' -w 75 -c 90' \
--interval 60 \
--subscriptions linux

NOTE: Sensu advises against requiring root privileges to execute check commands or scripts. The Sensu user is not permitted to kill timed out processes invoked by the root user, which could result in zombie processes. While Sensu discourages the use of sudo in check commands, you are free to configure your checks as you see fit, but please do so at your own risk.

Validating the check

You can verify the proper behavior of this check against a specific entity by using sensuctl. Replace example-entity-name in the following command with the name of a linux-subscribed entity. It might take a few moments, once the check is created, for the check to be scheduled on the entity and the result sent back to Sensu backend.

sensuctl event info example-entity-name check-cpu

NOTE: To create an entity to run the check-cpu check, install the Sensu agent, then add the linux subscription to /etc/sensu/agent.yml and restart the agent.

Next steps

You now know how to run a simple check to verify the CPU usage. From this point, here are some recommended resources: