Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Built a self hosted clean status page and batteries

github.com

Post reply on HN
Print view View original

11–20 of 56 posts

Re: Show HN: Built a self hosted clean status page and batteries

#11

Post by Daviey »

ahmedfromtunis wrote: post #9

I might be mistaken, but I always thought that status pages are supposed to be hosted by a third party. Am I supposed to have this run on a separate (presumably) dedicated server? Otherwise what's the point of having this running if it becomes inaccessible the instant my server goes down?

It entirely depends on your reason and expectation of the service. Yes, it would be best to separately host it on entirely different infra. However, if you have 1 x server, and you want to check that the services it is running are functional (such as a web server, app and database are functional), then co-locating this on there would be ok, providing the server itself doesn't go AWOL.

However, running this on a dedicated virtual server or raspberry pi would likely be always better.

Re: Show HN: Built a self hosted clean status page and batteries

#12

Post by purple_wow »

ahmedfromtunis wrote: post #9

I might be mistaken, but I always thought that status pages are supposed to be hosted by a third party. Am I supposed to have this run on a separate (presumably) dedicated server? Otherwise what's the point of having this running if it becomes inaccessible the instant my server goes down?

In case of status page you would want to host it in a different server / zone.

Re: Show HN: Built a self hosted clean status page and batteries

#13

Post by purple_wow »

dewey wrote: post #10
ushakov wrote: post #8

[flagged]

It's a small project with a clear and limited scope which makes it a good "hello world" project for developers. Just like we have a good selection of static site generators and blog frameworks used by one person only, nothing wrong with that. In the end what makes a status page successful isn't the code of the status page itself, but the reliability, the integration with existing tools (PagerDuty etc.) and all the ch…

Absolutely agree. I would be adding webhook integration with custom data transformation for popular providers like Slack/PagerDuty/Discord etc Thanks for pointing this out

Re: Show HN: Built a self hosted clean status page and batteries

#14

Post by purple_wow »

wscourge wrote: post #5

There's a whole red bar when the website was down for 1 minute on a given day. I don't like it, and I wouldn't want to show that to my users. I'd suggest you make the bar 1/3600 red, if the downtime was 1min - not exactly this, but you know what I mean.

Interesting. May be I can add a gradient from red -> yellow -> green with effected minute count, normalized to gradient threshold percentage. Let me try doing that

Re: Show HN: Built a self hosted clean status page and batteries

#18

Post by 8organicbits »

purple_wow wrote: post #14
wscourge wrote: post #5

There's a whole red bar when the website was down for 1 minute on a given day. I don't like it, and I wouldn't want to show that to my users. I'd suggest you make the bar 1/3600 red, if the downtime was 1min - not exactly this, but you know what I mean.

Interesting. May be I can add a gradient from red -> yellow -> green with effected minute count, normalized to gradient threshold percentage. Let me try doing that

I think it's worth deciding what you want to communicate. If it's "we have good uptime, but we may lie", then it's a green bar always. If it's "we're honest about our downtime" then the colors should be distinct so users can notice and inspect the days that are <100%. A gradient runs the risk of looking "all green" even when some downtime minimal happened. If that's not the goal, then I'd recommend a step function (green, yellow, red, for example).
Post reply on HN