How to install Check Executables using Assets

What are assets?

Sensu assets are resources that checks can specify as dependencies. When an agent runs a check, it will ensure that all of the check’s required assets are available to the agent during check runtime. If they aren’t, the agent will install them by consulting each of the assets’ URLs.

Why use assets?

When configuration management is unavailable, assets can help manage runtime dependencies such as scripts (ex: and tar files (ex: sensu-ruby-runtime.tar.gz) entirely within Sensu.

How to create a check that depends on an asset

Creating an asset

In this example, we’ll create an asset from a tar archive, and show you how to create a new check with that asset as a dependency, as well as apply it to an existing check. To create an asset, we’ll need a name, a URL to the asset location, and a SHA-512 checksum.

$ sensuctl asset create check_website.tar.gz \
  -u \
  --sha512 "$(sha512sum check_website.tar.gz | cut -f1 -d ' ')"

If you’re using macOS, you’ll need to use $(shasum -a 512 check_website.tar.gz | cut -f1 -d ' ') to generate a checksum.

If you’re using Windows, you’ll need to use the CertFile utility to generate the checksum:

CertUtil -hashfile check_website.tar.gz SHA512

and extract the checksum from the output manually, before adding it to the sensuctl command.

Adding an asset to a check on creation

$ sensuctl check create check_website \
  --command "check_website -a -C 3000 -w 1500" \
  --subscriptions web \
  --interval 10 \
  --runtime-assets check_website.tar.gz 

Adding an asset to an existing check’s dependencies

sensuctl check set-runtime-assets check_website.tar.gz 

This command will set a check’s assets to check_website.tar.gz.

Validating the asset

Once the check is setup, it should only take a few moments for it to be scheduled and start emitting events. When the check has been scheduled, you should see a log entry for that check’s execution.

{"component":"agent","level":"info","msg":"scheduling check execution: check_website","time":"2018-04-06T20:46:32Z"}

You can verify that the asset is working by using sensuctl to list the most recent events:

$ sensuctl event list
    Entity           Check                     Output               Status   Silenced             Timestamp
 ───────────── ────────────────── ──────────────────────────────── ──────── ────────── ───────────────────────────────
  sensu-agent    check_website      CheckHttpResponseTime OK: 345      0       false    2018-04-06 20:38:34 +0000 UTC

Next steps

You now know how to create an asset and add it to a check as a dependency. For further reading, check out the assets reference.