Go to file
Edward Shen 85f765b30d
rss feature implemented
2019-05-03 23:13:31 -04:00
config moved templates into own dir 2019-05-03 01:25:56 -04:00
src rss feature implemented 2019-05-03 23:13:31 -04:00
templates rss feature implemented 2019-05-03 23:13:31 -04: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 rss feature implemented 2019-05-03 23:13:31 -04:00
Cargo.toml rss feature implemented 2019-05-03 23:13:31 -04: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 updated readme 2019-05-01 19:47:30 -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 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.