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

Grafana releases OnCall open source project

grafana.com

Post reply on HN
Print view View original

81–90 of 134 posts

Re: Grafana releases OnCall open source project

#81

Post by pphysch »

throwaway892238 wrote: post #77
slotrans wrote: post #76

Earlier quoted context omitted.

You don't need Rabbit, Celery, or Redis. You should be able to replace MySQL with SQLite. Then it would be radically easier to deploy.

A MySQL database cluster, and a local copy of a SQL database on a single file on a single filesystem, are not close to the same thing. Except they both have "SQL" in the name. One of them allows a thousand different nodes on different networks to share a single dataset with high availability. The other can't share data with any other application, doesn't have high availability, is constrained by the resources of the…

This discussion is in the context of a self-contained app called Grafana OnCall, which is built on Django, which does not particularly care which RDBMS you are using.

At the very least, SQLite should be the default database for this product, and users can swap it out with their MySQL database cluster if they really are Google-scale.

Re: Grafana releases OnCall open source project

#83

Post by gjulianm »

throwaway892238 wrote: post #77
slotrans wrote: post #76

Earlier quoted context omitted.

You don't need Rabbit, Celery, or Redis. You should be able to replace MySQL with SQLite. Then it would be radically easier to deploy.

A MySQL database cluster, and a local copy of a SQL database on a single file on a single filesystem, are not close to the same thing. Except they both have "SQL" in the name. One of them allows a thousand different nodes on different networks to share a single dataset with high availability. The other can't share data with any other application, doesn't have high availability, is constrained by the resources of the…

> The entire point is to alert when things are crashing, so you would want it to be highly available. As in, running on more than one node.

An important question to ask is how much availability are you actually gaining from the setup. It wouldn't be the first time I see a system moving from single-node to multinode and being less available than before due to the extra complexity and moving pieces.

Re: Grafana releases OnCall open source project

#84

Post by Spivak »

slotrans wrote: post #80
throwaway892238 wrote: post #77

Earlier quoted context omitted.

A MySQL database cluster, and a local copy of a SQL database on a single file on a single filesystem, are not close to the same thing. Except they both have "SQL" in the name. One of them allows a thousand different nodes on different networks to share a single dataset with high availability. The other can't share data with any other application, doesn't have high availability, is constrained by the resources of the…

I don't need any of that stuff, and nor does anyone who would use this. People who need clustered high-availability stuff are paying for PagerDuty or VictorOps . This is for tiny shops with 4 servers. And tiny shops with 4 servers don't have time to spin up a horrendous stack like this. I was excited to see this announcement until I saw all the moving pieces. No thanks!

And this is the on-prem version of those tools. Just because it isn't the tool you wanted doesn't mean it's not good.

Re: Grafana releases OnCall open source project

#85

Post by eeZah7Ux »

nojito wrote: post #15
ucosty wrote: post #9

Earlier quoted context omitted.

Why is that unfortunate? Unless you're looking to make proprietary changes to Grafana Oncall and host it as a SAAS, it's the same as running any other GPL software.

GPL and its variants are a no go where I work.

Then the problem is in the company and not in the license.

Re: Grafana releases OnCall open source project

#86

Post by sergiomattei »

slotrans wrote: post #76
motakuk wrote: post #53

Earlier quoted context omitted.

I agree that multi-component architecture is harder to deploy. We did our best and prepared tooling to make deployment an easy thing. Helm ( https://github.com/grafana/oncall/tree/dev/helm/oncall ), docker-composes for hobby and dev environments. Besides deployment, there are two main priorities for OnCall architecture: 1) It should be as "default" as possible. No fancy tech, no hacking around 2) It should deliver no…

You don't need Rabbit, Celery, or Redis. You should be able to replace MySQL with SQLite. Then it would be radically easier to deploy.

It’s curious to see people questioning the stack choices of apps they haven’t built yet and problems they haven’t faced either.

They chose this stack, it works for them. They’ve put it through its paces in production.

It’s as boring as it gets.

Re: Grafana releases OnCall open source project

#87

Post by warp »

dividedbyzero wrote: post #72
ketralnis wrote: post #29

Earlier quoted context omitted.

To distribute I understand, but even just to use? Almost any desktop OS you run has GPL code somewhere in it

Almost any desktop OS? I may be wrong but I don't think Windows and macOS contain any GPL code.

Doesn't Windows 10 ship with WSL2 now? (which includes a full Linux kernel).

Apple still ships bash under GPLv2 on current macOS versions. Apple hates GPLv3, which is why they're trying to switch away from bash to zsh, but for the time being they're still shipping bash.

Re: Grafana releases OnCall open source project

#88

Post by [deleted] »

gjulianm wrote: post #83
throwaway892238 wrote: post #77

Earlier quoted context omitted.

A MySQL database cluster, and a local copy of a SQL database on a single file on a single filesystem, are not close to the same thing. Except they both have "SQL" in the name. One of them allows a thousand different nodes on different networks to share a single dataset with high availability. The other can't share data with any other application, doesn't have high availability, is constrained by the resources of the…

> The entire point is to alert when things are crashing, so you would want it to be highly available. As in, running on more than one node. An important question to ask is how much availability are you actually gaining from the setup. It wouldn't be the first time I see a system moving from single-node to multinode and being less available than before due to the extra complexity and moving pieces.

[deleted]

Re: Grafana releases OnCall open source project

#90

Post by skullone »

contravariant wrote: post #41
skullone wrote: post #35

Earlier quoted context omitted.

That seems like a perfectly reasonable architecture. If only all of us could work on battle tested components like those during our job!

For something that is supposed to add some more features to the basic email/HTTP message alert like grafana generates, I do wonder what extra features require an additional 2 databases, a message queue and a separate task queue.

probably keeps history, state, escalation flow, etc?
Post reply on HN