Live data from Hacker News

Grafana 4.0 with alerting is released

grafana.org

71–80 of 91 posts

Re: Grafana 4.0 with alerting is released

#71
post #53

Earlier quoted context omitted.

And you have include in the price the problems of a paid app: - customization will be very expensive, if not impossible - you must have people for the procurement process (x10 more costly if you are in a gov agency), - weird failures due to not finding the license, - your cheap personal that install software won't be able to do it, - you'll have problems creating testing environments because you don't have licenses -…

> - customization will be very expensive, if not impossible You've got a full API and integrations with a hundred different tools and services out of the box. Seriously, my coworker was skeptic at first too (so was I). Then we configured the full integrations with AWS/the-agent/statsd/postgre/mysql/cassandra/elasticsearch/riak/nginx/haproxy/redis/memcache/pagerduty/slack and some more. My co-worker concluded in front…

I think the reason why you're getting negative reactions is that you're talking very broadly as if your personal experience is representative for everyone in the field. Rather than asserting that the real problems which neves mentioned don't exist, try describing how the specific products you've used were designed to avoid them.

Re: Grafana 4.0 with alerting is released

#72
post #51
post #3

This release has been long in the making. We started on Alerting way back in March this year and it's finally released! Read more about all the highlights in the release here: http://grafana.org/blog/2016/11/09/grafana-4.0-beta-release/ Oh, and if your in New York tomorrow, signup for GrafanaCon: http://grafanacon.org

Great work! Including a way to set grace periods will be really useful to prevent flapping on the metrics. ex, 'Alert When CPU > 95% for 10m'

One way to solve that problem is to reduce the series with min(). Ex http://play.grafana.org/dashboard/db/alerting-flappy?panelId...

This means that the lowest value for the last 5min of the serie have to be above 80% before the alert triggers.

Re: Grafana 4.0 with alerting is released

#73
post #45

Earlier quoted context omitted.

Agree that the SaaS offerings are a lot more turnkey; the integrations and polish that make all the difference. What you call a 'clusterfuck' is really a wider ecosystem. It would be pretty crazy for a single organization to use all or even most of the tools that you list. Right now, people accept high degrees of cost (especially for at scale users) and lock-in, in exchange for the convenience of SaaS. Or, they go op…

No offense but Grafana is only as good as the weaker piece in the monitoring chain. Having nice graphs is nice... until they fall apart because the source is unavailable. And that doesn't help with alerts either. (I tested the alerts in the v4 beta, it's just not comparable to the better alerting tools out there).

what are you missing compared to other alerting tools?

Re: Grafana 4.0 with alerting is released

#74

Earlier quoted context omitted.

Datadog will cost you $165,600 a year for 600 hosts. That is objectively equal to a very well paid engineer. So no, the statement is not untrue. (I picked 600 because that was the approximate number of machines we had at my last job, where we used Graphite maintained by one guy, part time). You included a LOT of redundancy in your OSS list. Multiple timeseries databases. Multiple collection daemons. Multiple dashboar…

Indeed, I gave a list of all the tools, you only need to make a stack of about 4 to 8 of them to get the job done. Let's say statsd + collectd (metrics collection) + graphite (aggregation) + carbon/whisper (graphite storage) + icinga (alerting) + grafana (graphing). That doesn't exactly come easy. No offense but a single graphite is not a monitoring solution. It's just the tip of the iceberg. Monitoring does take a l…

Let's talk about how much Amazon will charge you for 600 instances a year...

Re: Grafana 4.0 with alerting is released

#75
post #45

Earlier quoted context omitted.

Agree that the SaaS offerings are a lot more turnkey; the integrations and polish that make all the difference. What you call a 'clusterfuck' is really a wider ecosystem. It would be pretty crazy for a single organization to use all or even most of the tools that you list. Right now, people accept high degrees of cost (especially for at scale users) and lock-in, in exchange for the convenience of SaaS. Or, they go op…

No offense but Grafana is only as good as the weaker piece in the monitoring chain. Having nice graphs is nice... until they fall apart because the source is unavailable. And that doesn't help with alerts either. (I tested the alerts in the v4 beta, it's just not comparable to the better alerting tools out there).

No offense taken ;) You're spot on about needing a solid and scalable backend; it’s more than 'nice graphs'. We think Grafana is a great piece in the chain to start with. We're trying to put as much momentum behind it as our burgeoning company will support.

The alerting in v4.0 is just the beginning. Torkel and the team have tried to optimize for the “relatively simple" 80% of alert use cases.

We are fans of other, more sophisticated open source alerting tools like Bosun, and you can be sure that we'll be both improving our alerting capabilities in 4.x

Re: Grafana 4.0 with alerting is released

#76

Quick note for the ones who are tired of the giant clusterfuck of open-source tools for monitoring + alerting + storage + other, which is no less than: - statsd - collectd - graphite - whisper - carbon - prometheus - grafana - seyren - riemann - nagios - icinga - zabbix There are multiple modern SaaS software that will do all of that in a single tool with better integrations, more polish, less work and no maintenance…

For installations of a few hundred instances or more, some of the SaaS offerings cost more than the engineering salaries it would take to maintain the OSS tools.

Shame that many of the OSS tools do not have any sort of corporate sponsorship, or if they do, that it doesn't cover all the work that goes into releasing OSS in this space.

Note: I am one of the maintainers of Diamond, a metrics collection tool written in python. https://github.com/python-diamond/Diamond

Re: Grafana 4.0 with alerting is released

#77
post #69

Quick note for the ones who are tired of the giant clusterfuck of open-source tools for monitoring + alerting + storage + other, which is no less than: - statsd - collectd - graphite - whisper - carbon - prometheus - grafana - seyren - riemann - nagios - icinga - zabbix There are multiple modern SaaS software that will do all of that in a single tool with better integrations, more polish, less work and no maintenance…

Is there any hosted monitoring solution that integrates with service discovery, so that it's actually useful for serious alerting in nowadays' dynamic environments? Otherwise you can't even tell if things that should be there are reporting in or missing.

https://sysdig.com/

Re: Grafana 4.0 with alerting is released

#78
post #16

Influx + Telegraf + Grafana is such a simple, sweet stack. No work to maintain, trivial to set up, I can ship just about anything I want into it, and reporting is fast. With alerting in place now, I'm even happier than ever. A huge thank you to the Grafana team for solving a huge pain point!

What kind of volume are you sending into Influx? It crashed on me probably 5 times a day with only 100 requests per second.

I use riemann in front if influx, which collects data and forwards it once a second. Works nicely, especially given that I aggregate some more high volume metrics before sending them to influx.

Re: Grafana 4.0 with alerting is released

#79
post #61

Earlier quoted context omitted.

Right now it looks like it's around 50/sec. A lot of data points get rolled up by Telegraf on individual machines, and then it's shipped in via the UDP line protocol. I've written much larger volumes, though, and never had an issue with stability.

If I may ask. How is UDP doing for you? I checked my graphite setup once. We had 27% of metrics lost over UDP. That was bad. pro-tip: "netstat -anus" and look at the error counters.

About 4% err-to-received ratio. That's probably due to untuned UDP buffer sizes though; despite dropped packets, we're getting enough information to provide the information we need.

Re: Grafana 4.0 with alerting is released

#80
post #24

It'd be nice if this meant being able to use Grafana as a frontend to alertmanager. (Writing those "ALERT ..." requires a steep learning curve.)

This is exactly what I was thinking! I'd love to know what the dev of Prometheus think about alerting in Grafana...

https://twitter.com/fabxc/status/803870900097523712

> I repeat: Your alerts and dashboards belong into your SCM, not a random SQL database!

(And I 100% agree, particularly for alerts)

Post reply on HN