Select Supported Platforms

Select Supported Architectures

Select Tier

Github Name

sensu-plugins/sensu-plugins-http (31) Versions 5.1.1 Community Tier

This plugin provides native HTTP instrumentation for monitoring and metrics collection, including: response code, JSON response, HTTP last modified, SSL expiry, and metrics via `curl`.

Downloads in last month
Commits in last year
Release Notes


Build Status
Gem Version
Dependency Status
Sensu Bonsai Asset

Sensu Asset

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-http-json.rb
  • bin/check-http.rb
  • bin/check-https-cert.rb
  • bin/check-last-modified.rb
  • bin/metrics-curl.rb
  • bin/metrics-http-json.rb
  • bin/metrics-http-json-deep.rb
  • bin/check-head-redirect.rb
  • bin/check-http-cors.rb


check-head-redirect.rb and check-last-modified.rb can be used in conjunction with AWS to pull configuration from a specific bucket and file.

This is helpful if you do not want to configure connection information as an argument to the sensu checks. If a bucket and key are specified that the environment the sensu check executes in has access to, or you provide an AWS key and token, the checks will pull the specified JSON file from S3 and merge the JSON config in to the current check configuration.

check-https-cert.rb can be used to test for valid and successfully expired certs, amongst other things.


Installation and Setup


check-http.rb and check-https-cert.rb

This check is not really geared to check all of the complexities of ssl which is why there is a separate repo and set of checks for that: If you are trying to verify cert expiration you will notice that in some cases it does not do what you always expect it to do. For example it might appear that when using using -k option you see different expiration times. This is due to the fact that when using -k it does not check expiration of all of the certs in the chain. Rather than duplicate this behavior in this check use the other repo where we handle those more complicated ssl checks better. For more information see:

Are you sure you want to report this asset?

Please describe the reason for reporting this asset. Our moderators will be notified and will disable the asset if it is found to be inappropriate.


You must be signed in to report this asset.

Sign In with Github