Find a file
2019-05-02 00:31:45 -04:00
src Provide option to set config file location by env 2019-05-02 00:02:53 -04:00
templates templates now generate relative to cwd 2019-05-01 23:47:05 -04:00
.dockerignore added dockerignore to reduce build context size 2019-05-02 00:31:45 -04:00
.gitignore added example 2019-05-01 19:37:22 -04:00
Cargo.lock refactor to use chrono 2019-05-01 16:01:27 -04:00
Cargo.toml refactor to use chrono 2019-05-01 16:01:27 -04:00
Dockerfile added dockerignore to reduce build context size 2019-05-02 00:31:45 -04:00
endstat_conf.example.ron templates now generate relative to cwd 2019-05-01 23:47:05 -04:00
LICENSE added license 2019-04-30 01:59:38 -04:00
README.md updated readme 2019-05-01 19:47:30 -04:00

endstat

endstat is an easy-to-use Endpoint Status checking tool, meant for checking the health of various web locations. It supports arbitrary domains and ports, status matching, and body matching using ron, a quick-to-understand config file notation, built in Rust using actix.

My motivation was that I wanted to make a dashboard that was easy-to-use to make sure my homelab services were running when I screwed around with config files.

Features

  • HTTP/HTTPS
  • Arbitrary ports
  • Expected body and/or status code responses
  • Optional no redirect following
  • API endpoint (/api)

Getting started

There's an example config file that you can simply rename to endstat_conf.ron. It should be a relatively comprehensive example of what sort of flexibility endstat offers.

If you're building from source, execute cargo run.

If you've gotten this binary from somewhere else, simply execute it.