Grafana 2.0 Alpha
grafana.org
grafana.org
We are currently using ELK for doing some lightweight analysis of user behavior (we are using Elasticsearch anyway, so this was the easiest way to get up and running), but as far as I can tell there are some limits to the Elasticsearch/Kibana combination. For example, there seems to be no way to correlate separate events, e.g. how many users that performed action A then performed action B within some time window (or even as the next action). Is this possible with Graphite?
Time series are usually more about being able to collect huge amount of metrics. Metrics that can then be combined, averaged, filtered, put through a processing pipeline (analytical functions), summarized by different intervals. All in order to visualize (usually through graphs) recent live trends or long term trends and statistics.
Grafana is all about maximizing the power and ease of use of the underlying time series store so the user can focus om on building informative and nice looking dashboards. It is also about letting users define generic dashboards through variables that can be used in metric queries, this allows users to reuse the same dashboard for different servers, apps or experiments as long as the metric naming follows a consistent pattern.
Grafana also uses Elasticsearch but not for log analytics, but for annotating graphs with event/log information.
At some point in in the coming 1-3 years log analytics and metric analytics & visualization is going to converge and be solved/addressed by the same piece of software. But that is tricky right now without sacrificing either domain.
That's the one thing holding me back from giving Grafana a whirl (my younger self promised me to never touch graphite again).
We have a tool/wizard that imports your dashboards from elasticsearch (removing that dependency for graphite users).
Keep in mind that grafana 2.0 will of course continue to work with graphite, influxdb and opentsdb for metric storage.
InfluxDB is not really suitable as a general purpose data source (storing dashboards as influxdb metric series was more a temporary solution so influxdb users did not need to install elasticsearch, and influxdb dashboard storage did not support tag filtering).
With Grafana 2.0 needs to store a lot more, users, accounts, user starred dashboards & preferences. So a more general purpose database was needed.
thanks for replying 馃憤
So if you have metrics in one of those time series stores then Grafana is a really awesome tool for visualizing those metrics.
Are you abondoned your "paid version" ideas?