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

Upptime – GitHub-powered open-source uptime monitor and status page

upptime.js.org

Post reply on HN
Print view View original

11–20 of 86 posts

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#11

Post by lipanski »

Karliss wrote: post #4

Abusing version control and CI service as database sounds like a way for ruining it for open source projects that actually need it. The recent Travis thing didn't happen without reason.

I second this - it sounds like a massive waste to spin up a Github Actions job in order to trigger a basic request every 5 minutes, 300 times a day.

Why not just use a dedicated uptime service with a free tier? I've been using UptimeRobot [1] in the past - they give you 50 free checks at the same refresh rate of 5 minutes.

[1] https://uptimerobot.com/

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#12

Post by jjeaff »

lipanski wrote: post #11
Karliss wrote: post #4

Abusing version control and CI service as database sounds like a way for ruining it for open source projects that actually need it. The recent Travis thing didn't happen without reason.

I second this - it sounds like a massive waste to spin up a Github Actions job in order to trigger a basic request every 5 minutes, 300 times a day. Why not just use a dedicated uptime service with a free tier? I've been using UptimeRobot [1] in the past - they give you 50 free checks at the same refresh rate of 5 minutes. [1] https://uptimerobot.com/

You say "spin up" which in my mind implies a whole VM. I think surely actions are just run in sort of a container of some sort like a lambda.

I would think it should be rather efficient to run a github action.

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#13

Post by xahrepap »

jjeaff wrote: post #12
lipanski wrote: post #11

Earlier quoted context omitted.

I second this - it sounds like a massive waste to spin up a Github Actions job in order to trigger a basic request every 5 minutes, 300 times a day. Why not just use a dedicated uptime service with a free tier? I've been using UptimeRobot [1] in the past - they give you 50 free checks at the same refresh rate of 5 minutes. [1] https://uptimerobot.com/

You say "spin up" which in my mind implies a whole VM. I think surely actions are just run in sort of a container of some sort like a lambda. I would think it should be rather efficient to run a github action.

Yes and no. Depends on tenancy requirements. I know with docker and other common Linux container strategies you would want to keep each tenant on their own VM. A container isn’t safe enough.

So if this is your org’s only action. Then you’re probably spinning up a VM. If you have other options. You’re probably not adding any overhead.

(Edit: grammar)

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#14

Post by nickjj »

lipanski wrote: post #11
Karliss wrote: post #4

Abusing version control and CI service as database sounds like a way for ruining it for open source projects that actually need it. The recent Travis thing didn't happen without reason.

I second this - it sounds like a massive waste to spin up a Github Actions job in order to trigger a basic request every 5 minutes, 300 times a day. Why not just use a dedicated uptime service with a free tier? I've been using UptimeRobot [1] in the past - they give you 50 free checks at the same refresh rate of 5 minutes. [1] https://uptimerobot.com/

I use Uptime Robot too. Been using them for years on the free plan. It's dependable.

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#15

Post by sneak »

Karliss wrote: post #4

Abusing version control and CI service as database sounds like a way for ruining it for open source projects that actually need it. The recent Travis thing didn't happen without reason.

I doubt Microsoft (GitHub's owner) cares that much about such tiny usage. They run all of Azure, after all.

A small price to pay, it seems, to lock more people into GitHub/GitHub Actions. We're talking pennies, here.

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#17

Post by the_arun »

lipanski wrote: post #11
Karliss wrote: post #4

Abusing version control and CI service as database sounds like a way for ruining it for open source projects that actually need it. The recent Travis thing didn't happen without reason.

I second this - it sounds like a massive waste to spin up a Github Actions job in order to trigger a basic request every 5 minutes, 300 times a day. Why not just use a dedicated uptime service with a free tier? I've been using UptimeRobot [1] in the past - they give you 50 free checks at the same refresh rate of 5 minutes. [1] https://uptimerobot.com/

How about self hosted enterprise GitHub?

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#18

Post by maxandersen »

From GitHub usage policy:

“ (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or”

I think this would qualify as serverless application...

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#19

Post by victorhooi »

One limitation of their approach seems to be that it must be published in a public Github repo - it can't be a private repo.

This means it might not be so suitable for internal, or local apps - only public facing websites.

I wonder how difficult it'd be to make a mode for Upptime, that used say, local agents, and posted the results to a local webserver, rather than to public Github Pages.

Re: Upptime – GitHub-powered open-source uptime monitor and status page

#20

Post by dinkleberg »

I like using GitHub Actions for small automation tasks like this as well, but I'm curious what the execution time is for each of these runs. GH Actions has been reliable for me, but it tends to be rather slow due to the architecture. Also I feel like this would chew up all my build mins pretty quick (this is 8000+ runs/month).

Side note, I find it hilarious how many sites use those generic "modern" illustrations which have absolutely nothing to do with the service or page context. I know it's tempting to keep up with the modern design trends, but picking from one of those illustration packs almost always leads to questionable choices.

Post reply on HN