51–60 of 91 posts
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
Is anyone using a log management tool in conjunction with Grafana? I.e. if you see something anomalous or see an alert triggered, how do you investigate what's going on?
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…
- 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
- you won't be able to do some things immediately because there aren't enough licenses.
And these are just the problems that came to my mind right now. All of them are real problems that I'd found in commercial software.
Earlier quoted context omitted.
To have been on the maintainer sides of the OSS tools, your statement is untrue. The OSS tools costs a fortune in human to maintain them, and another fortune in hardware to run it.
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…
True story: Our monitoring stack now has three distinct components with alerting functionality.
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
Congrats on release! We've been using Grafana for a few years now, and personally built-in alerting is the only thing I would have added. Some may argue that this "violates" good concern separation practices, but honestly you are going to be alerting about the same data you feed to Grafana, so at the end of the day it makes a lot of sense. Call it a "two in one" if you will. Either way this will make monitoring with…
Collectd, telegraf. etc, can be configured to send the same metrics to your favorite TSDB and Alerting system (like riemann) in parallel.
Earlier quoted context omitted.
Was this an older build? We had serious issues at first, but our setup is pretty stable these days.
Last I tried was 1.0. I love everything about using Influx but it would die and never restart and every time it would some crash on semacquire. I'll have to try it again since I need to check out this Grafana update anyway.
The two game changers are using the UDP line protocol instead of HTTP, and making sure you are batch-processing inputs. Fixing these settings is the difference between an instances that crashes all the time, and a purring one.
I'm currently using Prometheus, Grafana, and Alertmanager. I'm a big fan of the linux terminal, versioned config files, and separation of concerns but the rest of my team prefers web interfaces so I'm basically the only one maintaining Alertmanager. Grafana Altering looks appealing. What have other people had success with?
I've had success with killing all the s * free open source tools (Grafana, graphite, prometheus, whisper, icinga, nagios, carbon, ganglia, influxdb, zabbix...) And using a single paid tool that does the job better AND doesn't kill me in maintenance work. See https://www.datadoghq.com/ as leader or https://signalfx.com/ as the second comer, or http://www.bmcsoftware.uk/it-solutions/truesight.html if you're enterprisey…
Grafana really looks interesting, and it is interesting that you can add all the different backends to it, for an example I didn't know you can use Elasticsearch as a timeseries backend. Is it correct that Grafana works best with Graphite? At least that seems to be my impression, and it is a bit sad, since I think Graphite is cool, but it really has a lot of moving parts.
We also use it against mysql. Annoyingly there is no driver for that so we had to build a nasty layer than translates from influx to mysql.