Chronograf聽vs聽Kibana

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Chronograf
Chronograf

14
7
+ 1
1
Kibana
Kibana

4.6K
3K
+ 1
227
Add tool

Chronograf vs Kibana: What are the differences?

What is Chronograf? *It is the user interface and administrative component *. The complete interface. allows you to quickly see the data that you have stored, so you can build robust queries and alerts.

What is Kibana? Explore & Visualize Your Data. Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.

Chronograf and Kibana belong to "Monitoring Tools" category of the tech stack.

Chronograf and Kibana are both open source tools. Chronograf with 17.1K GitHub stars and 2.43K forks on GitHub appears to be more popular than Kibana with 12.6K GitHub stars and 4.89K GitHub forks.

According to the StackShare community, Kibana has a broader approval, being mentioned in 1196 company stacks & 2753 developers stacks; compared to Chronograf, which is listed in 5 company stacks and 3 developer stacks.

What is Chronograf?

The complete interface. allows you to quickly see the data that you have stored, so you can build robust queries and alerts.

What is Kibana?

Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Chronograf?
Why do developers choose Kibana?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Chronograf?
    What companies use Kibana?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Chronograf?
    What tools integrate with Kibana?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Chronograf and Kibana?
      Grafana
      Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins.
      Telegraf
      It is an agent for collecting, processing, aggregating, and writing metrics. Design goals are to have a minimal memory footprint with a plugin system so that developers in the community can easily add support for collecting metrics.
      Prometheus
      Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.
      Nagios
      Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License.
      Graphite
      Graphite does two things: 1) Store numeric time-series data and 2) Render graphs of this data on demand
      See all alternatives
      Decisions about Chronograf and Kibana
      StackShare Editors
      StackShare Editors
      Kibana
      Kibana
      Grafana
      Grafana
      Elasticsearch
      Elasticsearch
      Logstash
      Logstash
      Graphite
      Graphite
      Icinga
      Icinga

      One size definitely doesn鈥檛 fit all when it comes to open source monitoring solutions, and executing generally understood best practices in the context of unique distributed systems presents all sorts of problems. Megan Anctil, a senior engineer on the Technical Operations team at Slack gave a talk at an O鈥橰eilly Velocity Conference sharing pain points and lessons learned at wrangling known technologies such as Icinga, Graphite, Grafana, and the Elastic Stack to best fit the company鈥檚 use cases.

      At the time, Slack used a few well-known monitoring tools since it鈥檚 Technical Operations team wasn鈥檛 large enough to build an in-house solution for all of these. Nor did the team think it鈥檚 sustainable to throw money at the problem, given the volume of information processed and the not-insignificant price and rigidity of many vendor solutions. With thousands of servers across multiple regions and millions of metrics and documents being processed and indexed per second, the team had to figure out how to scale these technologies to fit Slack鈥檚 needs.

      On the backend, they experimented with multiple clusters in both Graphite and ELK, distributed Icinga nodes, and more. At the same time, they鈥檝e tried to build usability into Grafana that reflects the team鈥檚 mental models of the system and have found ways to make alerts from Icinga more insightful and actionable.

      See more
      Kibana
      Kibana
      Splunk
      Splunk
      Grafana
      Grafana

      I use Kibana because it ships with the ELK stack. I don't find it as powerful as Splunk however it is light years above grepping through log files. We previously used Grafana but found it to be annoying to maintain a separate tool outside of the ELK stack. We were able to get everything we needed from Kibana.

      See more
      Kibana
      Kibana
      Grafana
      Grafana
      Elasticsearch
      Elasticsearch

      I use both Kibana and Grafana on my workplace: Kibana for logging and Grafana for monitoring. Since you already work with Elasticsearch, I think Kibana is the safest choice in terms of ease of use and variety of messages it can manage, while Grafana has still (in my opinion) a strong link to metrics

      See more
      Grafana
      Grafana
      Kibana
      Kibana

      For our Predictive Analytics platform, we have used both Grafana and Kibana

      Kibana has predictions and ML algorithms support, so if you need them, you may be better off with Kibana . The multi-variate analysis features it provide are very unique (not available in Grafana).

      For everything else, definitely Grafana . Especially the number of supported data sources, and plugins clearly makes Grafana a winner (in just visualization and reporting sense). Creating your own plugin is also very easy. The top pros of Grafana (which it does better than Kibana ) are:

      • Creating and organizing visualization panels
      • Templating the panels on dashboards for repetetive tasks
      • Realtime monitoring, filtering of charts based on conditions and variables
      • Export / Import in JSON format (that allows you to version and save your dashboard as part of git)
      See more
      Interest over time
      Reviews of Chronograf and Kibana
      No reviews found
      How developers use Chronograf and Kibana
      Avatar of Clarabridge Engage
      Clarabridge Engage uses KibanaKibana

      Used for graphing internal logging data; including metrics related to how fast we serve pages and execute MySQL/ElasticSearch queries.

      Avatar of Wirkn Inc.
      Wirkn Inc. uses KibanaKibana

      Our Kibana instances uses our ElasticSearch search data to help answer any complicated questions we have about our data.

      Avatar of Hevelop
      Hevelop uses KibanaKibana

      Kibana is our tools to query data in Elasticsearch clusters set up as catalog search engine.

      Avatar of Diogo Silva
      Diogo Silva uses KibanaKibana

      Perfect for exploring and visualizing the data available at ElasticSearch

      Avatar of Tongliang Liu
      Tongliang Liu uses KibanaKibana

      Log visualization. Wish it could add built-in alert functionality.

      How much does Chronograf cost?
      How much does Kibana cost?
      Pricing unavailable
      News about Chronograf
      More news