Go to file
Edward Shen 54c53629db
update deps
2020-04-08 22:02:11 -04:00
config moved templates into own dir 2019-05-03 01:25:56 -04:00
src liniting fixes 2019-11-09 17:25:42 -05:00
templates minor style changes 2019-11-09 17:12:53 -05:00
.dockerignore endpoint names don't shrink when url is long 2019-05-02 02:26:05 -04:00
.gitignore move configurables to config 2019-05-02 01:51:27 -04:00
Cargo.lock update deps 2020-04-08 22:02:11 -04:00
Cargo.toml update cargo deps 2019-11-09 17:12:22 -05:00
Dockerfile moved templates into own dir 2019-05-03 01:25:56 -04:00
LICENSE added license 2019-04-30 01:59:38 -04:00
README.md bump to 0.2.0 2019-05-07 22:47:24 -04:00

README.md

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 endpoints (/api, /rss)
  • Webhooks

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.