# Kibana vs Grafana **URL:** \ **Category:** Kibana\ **Created:** [February 16, 2016, 10:04am UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865 "2016-02-16T10:04:42Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Croos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/croos/32/29489_2.png) [@Croos](https://discuss.elastic.co/u/Croos)\ **Post date:** [February 16, 2016, 10:04am UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865/1 "2016-02-16T10:04:42Z")
There is a question in front of me, Why we go to elasticseach+Kibana for visualization? There are some other techniques available for the same like Grafana+InfluxDB. Suppose my answer is "ES+Kibana is better way than others", How can I justify my answer? ---
**Author:** ![german23](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/german23/32/11052_2.png) [@german23](https://discuss.elastic.co/u/german23)\ **Post date:** [February 16, 2016, 10:35am UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865/2 "2016-02-16T10:35:28Z")
Have a look at this awesome thread: > [@ELK vs grafana+influxDB](https://discuss.elastic.co/t/elk-vs-grafana-influxdb/1686/36): > > If you want to chat about performance on your cluster then it might be better to start another thread and then link us to it. That way we can provide specific assistance while still retaining the flow (and feel) of this thread slight_smile ---
**Author:** ![isaacpm](https://avatars.discourse-cdn.com/v4/letter/i/b9e5f3/32.png) [@isaacpm](https://discuss.elastic.co/u/isaacpm)\ **Post date:** [February 16, 2016, 10:36am UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865/3 "2016-02-16T10:36:02Z")
Hi Croos, I have exactly the same situation as you are describing. Grafana+Influxdb or "ES+Kibana" I don't think there is an answer for what's a better option, it depends on your environment, in my case I ended up with ES+Kibana+Grafana for the following reasons: Influxdb is not stable, I couldn't get it to ingest data into a cluster for a few hours without some sort of problem. With ES I only had to tweak to not overload the system. ES can plug into Grafana AND Kibana, so I had the best of both worlds. As Grafana does not have as many plotting options as Kibana. I have no problems with storage capacity for the amount of data I need to handle nor ingestion rates that ES can't cope with (in the case that influxdb could ingest more metrics per second). ES is much more stable and mature, it may have not been designed as a timeseries DB, but it does the job well as far as I can tell and it's being used in many places for this. You also have timelion in case you don't want to use grafana and keep everything under kibana. hope that helps, Isaac ---
**Author:** ![Croos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/croos/32/29489_2.png) [@Croos](https://discuss.elastic.co/u/Croos)\ **Post date:** [February 16, 2016, 10:45am UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865/4 "2016-02-16T10:45:09Z")
Thank you very much Isaac. This is what I expect from this thread 🙂. ---
**Author:** ![isaacpm](https://avatars.discourse-cdn.com/v4/letter/i/b9e5f3/32.png) [@isaacpm](https://discuss.elastic.co/u/isaacpm)\ **Post date:** [February 16, 2016, 10:46am UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865/5 "2016-02-16T10:46:27Z")
Also check german23 link, it has a more in depth explanation of it. Even though it's a bit old and grafana wasn't available for ES, the storage point they make are valid ---
**Author:** ![azhukov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azhukov/32/15856_2.png) [@azhukov](https://discuss.elastic.co/u/azhukov)\ **Post date:** [February 25, 2017, 10:47am UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865/6 "2017-02-25T10:47:38Z")
I'm using ELK, InfluxDB and Grafana and there're just my two cents: Grafana as single centrilized dashboard in your company seems better option because of DataSource feature. With Grafana dashboard you can draw graphs from multiple DataSource: ElasticSearch, InfuxDB, Prometheus, etc. You can use different ElasticSearch clusters as DataSource on one graph whereas KIbana works with only one ElasticSearch cluster and cannot visualize data from another TSDB. So Grafana is much more universal as vusualizing tool. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:33pm UTC](https://discuss.elastic.co/t/kibana-vs-grafana/41865/7 "2017-07-06T13:33:00Z")