The 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!
Why would you default to S3 storage? You create a stand-alone product for self-hosting, complain about cloud providers going down, but then use a cloud provider for your collection?
You can implement and plug in any storage provider, including local storage if you want. The point is you don't have to rely on a proprietary, locked down status page service.
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!
It's still a bit fuzzy for me, but according to the README at 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 !
The 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!
Hey, how do I set this up with local storage ?
Feature request: PagerDuty integration
Filed here! https://github.com/sourcegraph/checkup/issues/4
Pull requests also welcome :) The code is very well-documented and easy to navigate.
When I read the title, I was thinking of dashboard for (my) personal health instead.
Sorry. Yeah, the title is missing half of the story: status pages.
Why would you default to S3 storage? You create a stand-alone product for self-hosting, complain about cloud providers going down, but then use a cloud provider for your collection?
S3 differs considerably from most SaaS offerings in terms of:
You can implement and plug in any storage provider, including local storage if you want. The point is you don't have to rely on a proprietary, locked down status page service.
This is interesting. Can we use custom headers/auth when setting up the APIs for health checkups?
I put your request in here: https://github.com/sourcegraph/checkup/issues/8
Ah I didn't realize what S3 was for at first -- it hosts it to S3 for "off-network" reliability. Nice. Will definitely look into this soon.
Kind of unrelated, but this page doesn't scroll for me on iOS with Safari: https://sourcegraph.com/github.com/sourcegraph/checkup/-/blo...
Thanks for the report! We've fixed the bug now.
That definitely earns a sticker, check out https://sourcegraph.com/about if you want to redeem it :)