Awesome, thanks for the consideration!
Please don’t immediately start public facing however - I literally just bashed the thing together in an afternoon, so who knows what kind of exploitable information leaks it might bring!
I’m personally using it from within a tailnet, so not public facing.
Ah, well, then perhaps I will monitor it.
For internal use I just monitor everything with zabbix. What Ive been wanting is (as I said) a public “status screen” that my few users can hit just to verify if things are in fact down or if it’s just them.
Couldn’t stop worrying about this, so I added:
- --no-tooltips param: Don’t include check output for hover tooltips
- --no-timestamp param: Omit the “Generated at” timestamp to hide system clock and monitoring cadence.
If you’re using these, I feel much better about making the html publicly accessible, but when you set up a config please remember that links-tags can expose your internal topology and the tile/slot name might do the same! Don’t go naming your tiles something like “Database Primary”, “Payment Service Worker”, or “Internal Auth API”!
(unless you wanna place a honeypot)
themachine