A bit disappointed by the architecture -- it's a Django stack with MySQL, Redis, RabbitMQ, and Celery -- for what is effectively AlertManager (a single golang binary) with a nicer web frontend + Grafana integration + etc. I'm curious why/if this architecture was chosen. I get that it started as a standalone product (Amixr), but in the current state it is hard to rationalize deploying this next to Grafana in my curren…
Grafana releases OnCall open source project
31–40 of 134 posts
Re: Grafana releases OnCall open source project
#32Earlier 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.
Re: Grafana releases OnCall open source project
#33A bit disappointed by the architecture -- it's a Django stack with MySQL, Redis, RabbitMQ, and Celery -- for what is effectively AlertManager (a single golang binary) with a nicer web frontend + Grafana integration + etc. I'm curious why/if this architecture was chosen. I get that it started as a standalone product (Amixr), but in the current state it is hard to rationalize deploying this next to Grafana in my curren…
https://prometheus.io/docs/introduction/overview/#architectu...
Re: Grafana releases OnCall open source project
#34A bit disappointed by the architecture -- it's a Django stack with MySQL, Redis, RabbitMQ, and Celery -- for what is effectively AlertManager (a single golang binary) with a nicer web frontend + Grafana integration + etc. I'm curious why/if this architecture was chosen. I get that it started as a standalone product (Amixr), but in the current state it is hard to rationalize deploying this next to Grafana in my curren…
Curious as to what architecture you would have preferred or why this pretty standard stack (that can be deployed to k8s) is not giving you.
IMHO, OP just stated that one could solve this with less dependencies and have the same (if not a better) result.
Re: Grafana releases OnCall open source project
#35A bit disappointed by the architecture -- it's a Django stack with MySQL, Redis, RabbitMQ, and Celery -- for what is effectively AlertManager (a single golang binary) with a nicer web frontend + Grafana integration + etc. I'm curious why/if this architecture was chosen. I get that it started as a standalone product (Amixr), but in the current state it is hard to rationalize deploying this next to Grafana in my curren…
Re: Grafana releases OnCall open source project
#36A bit disappointed by the architecture -- it's a Django stack with MySQL, Redis, RabbitMQ, and Celery -- for what is effectively AlertManager (a single golang binary) with a nicer web frontend + Grafana integration + etc. I'm curious why/if this architecture was chosen. I get that it started as a standalone product (Amixr), but in the current state it is hard to rationalize deploying this next to Grafana in my curren…
Curious as to what architecture you would have preferred or why this pretty standard stack (that can be deployed to k8s) is not giving you.
Far less scalable, but it is dramatically simpler to deploy. Often gets you surprisingly far though. Would be interesting to know how many monitored integrations could be supported by that flow.
Re: Grafana releases OnCall open source project
#37Re: Grafana releases OnCall open source project
#38Re: Grafana releases OnCall open source project
#39Hello HN! Matvey Kukuy, ex-CEO of Amixr and a head of the OnCall project here. We've been working hard for a few months to make this OSS release happen. I believe it should make incident response features (on-call rotations, escalations, multi-channel notifications) and best practices more accessible to the wider audience of SRE and DevOps engineers. Hope someone will be able to finally sleep well at night being sure…
Being on-call has never made me sleep better at night!
Re: Grafana releases OnCall open source project
#40Earlier quoted context omitted.
Is Linux verboten at work?
Probably not. Linux usually gets a pass, because most times you're just deploying it and not mucking with source code. But a lot of places (I've worked at more that do than don't) will have rules about GPL/AGPL for libraries/infra as a whole though. Often evaluated case-by-case, but it's rare I've seen a AGPL stuff get approved for usage. I think some of it is not wanting to deal with the cost of vigilance; i.e. you…
That would apply for most uses of software, wouldn't it?
> This results in refusals ranging from "This is internal for now but we will open it up later" (a fair concern) to "Somebody is worried that exposing it over the VPN to contractors would count as making it public" (IDK, I'm not a lawyer.)
I've encountered variations of this problem at places I have worked in. Education goes a long way to solving this, and this example of simple usage of (A)GPL software is easy enough to explain with examples.