batteries-included uptime monitor for your infrastructure https://up.alemi.dev/
Find a file
2024-12-03 21:05:18 +01:00
src feat: increase api limit 2024-12-03 20:37:38 +01:00
web feat: center align cards 2024-12-03 21:05:18 +01:00
.editorconfig feat: initial commit with proof-of-concept 2024-12-01 03:37:05 +01:00
.gitignore feat: initial commit with proof-of-concept 2024-12-01 03:37:05 +01:00
.rustfmt.toml feat: initial commit with proof-of-concept 2024-12-01 03:37:05 +01:00
Cargo.lock feat: now with 100% more sqlite 2024-12-02 23:29:43 +01:00
Cargo.toml feat: now with 100% more sqlite 2024-12-02 23:29:43 +01:00
README.md docs: added barebones readme.md 2024-12-03 02:27:42 +01:00
uppe-rs.toml feat: initial commit with proof-of-concept 2024-12-01 03:37:05 +01:00

uppe.rs

batteries-included uptime monitor for your infrastructure

uppe.rs runs off a single binary, a configuration file (in toml) and an sqlite database (can be in memory or persisted on disk), and provides a daemon that tests configured routes while also serving a tiny API and web frontend.

it periodically makes requests to configured services, and tracks roundtrip time (or if no response was returned at all!). this data is then accessible using uppe.rs tiny builtin api, and can be viewed on the integrated webpage (served on service's /)

as an example, check out my instance on up.alemi.dev

goals

this aims to be super simple to use to glance at your stuff and help figuring out if there are issues. this doesn't aim to be an extensive monitoring solution for infrastructure, and while it can fit the role it isn't actively maintained against that use-case.

future features which would be nice to add are:

  • notifications on downtime
  • auto-cleanup of old samples
  • configurable frontend span
  • graph references on frontend
  • data exporters
  • full database engine to use mysql/psql
  • multi-protocol endpoint tester

name

honestly pretty bad, probably a mix of uptime + rust + monitors + stimulants. send me better ideas plz, contacts on my site