3 ms·
Most notably, this isn't just health checks; it also ships with a purely static status page to which you can publish updates. I'm the author of Checkup; hope o
by mholt 10y ago
Most notably, this isn't just health checks; it also ships with a purely static status page to which you can publish updates.
I'm the author of Checkup; hope others find it useful!
- iofj 10y agoWe should really have something like this that can easily just be linked into an application and do health checking. A place where the last n lines of log, all sorts of stats like mem usage for the last few hours, open file descriptors, subprocesses, ... can be checked. Ideally something that could be read by a monitoring process as well.
- rakoo 10y agoIt's still a bit fuzzy for me, but according to the README at https://github.com/sourcegraph/checkup https://github.com/sourcegraph/checkup, this is how I understand how it works: * You launch the checkup command manually or every X minutes * Each run stores a report inside a file * The caddy server serves the same resource to the browser... * ... that fetches the last Y reports and computes a dashboard to be displayed The 2 last steps seem not static to me. Is it how checkup works, or is the dashboard display part a bit different ? Regardless of that, this is something that is going to be extremely useful to me. Thanks a lot for for it !
- mholt 10y agoThe status page is static, in that there is no server-side rendering/processing other than just serving static files. You need only host the resources for the status page, but the files with the check results are typically stored somewhere else like S3. The status page downloads those check files with JavaScript and renders the results client-side. Hope that answers your question!
- firewalkwithme 10y agoHey, how do I set this up with local storage ?