Need advice about which tool to choose?Ask the StackShare community!
Kibana vs Loggly: What are the differences?
Introduction
Here, we will focus on the key differences between Kibana and Loggly as two popular log management and analytics tools.
Deployment and Hosting: Kibana is an open-source tool developed by Elastic and can be self-hosted or hosted on platforms like Elastic Cloud. On the other hand, Loggly is a cloud-based log management solution, where the entire infrastructure and hosting are handled by Loggly.
Search and Querying: Kibana provides a powerful search and querying interface with its Elasticsearch integration. It offers a wide range of advanced search capabilities, including full-text search, filtering, and aggregations. Loggly also offers searching and querying features, but it focuses more on speed and simplicity, providing pre-built search filters and the ability to construct queries using standard search syntax.
Visualization and Dashboards: Kibana is well-known for its rich visualization features. It offers an extensive collection of visualization options, including line charts, bar charts, maps, and more. With its drag-and-drop dashboard builder, users can create interactive and personalized dashboards. Loggly, however, has a more limited set of visualization capabilities. It offers basic charting and graphing options, but it doesn't have the same level of customization or variety as Kibana.
Alerting and Monitoring: Kibana lacks built-in alerting and monitoring features by default. It relies on external integrations or plugins, such as Elasticsearch Watcher or third-party tools, to enable alerting and monitoring. On the other hand, Loggly provides built-in alerting functionality, allowing users to set up alerts based on specific log events or patterns, and receive notifications via various channels like email or Slack.
Log Ingestion and Parsing: Kibana relies on Elasticsearch for log ingestion, and it supports different log file formats. By using Logstash, users can preprocess logs before indexing them into Elasticsearch. Loggly, on the other hand, offers various ingestion methods, including bulk upload, syslog, log shippers, and log routing. It also provides automatic parsing and extraction of log events, making it easier to analyze and search through log data without much configuration.
Ease of Use and Learning Curve: Kibana has a steeper learning curve compared to Loggly, primarily due to its advanced features and flexibility. It requires some knowledge of Elasticsearch and the query language. Loggly, on the other hand, has a more user-friendly interface and offers a simpler setup process, making it easier for non-technical users or those new to log management to get started quickly.
In Summary, Kibana and Loggly have notable differences in deployment, search capabilities, visualization, alerting, log ingestion, and ease of use. These variations make them suitable for different use cases and user preferences.
From a StackShare Community member: “We need better analytics & insights into our Elasticsearch cluster. Grafana, which ships with advanced support for Elasticsearch, looks great but isn’t officially supported/endorsed by Elastic. Kibana, on the other hand, is made and supported by Elastic. I’m wondering what people suggest in this situation."
For our Predictive Analytics platform, we have used both Grafana and Kibana
- Grafana based demo video: https://www.youtube.com/watch?v=tdTB2AcU4Sg
- Kibana based reporting screenshot: https://imgur.com/vuVvZKN
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)
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
After looking for a way to monitor or at least get a better overview of our infrastructure, we found out that Grafana (which I previously only used in ELK stacks) has a plugin available to fully integrate with Amazon CloudWatch . Which makes it way better for our use-case than the offer of the different competitors (most of them are even paid). There is also a CloudFlare plugin available, the platform we use to serve our DNS requests. Although we are a big fan of https://smashing.github.io/ (previously dashing), for now we are starting with 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.
Kibana should be sufficient in this architecture for decent analytics, if stronger metrics is needed then combine with Grafana. Datadog also offers nice overview but there's no need for it in this case unless you need more monitoring and alerting (and more technicalities).
@Kibana, of course, because @Grafana looks like amateur sort of solution, crammed with query builder grouping aggregates, but in essence, as recommended by CERN - KIbana is the corporate (startup vectored) decision.
Furthermore, @Kibana comes with complexity adhering ELK stack, whereas @InfluxDB + @Grafana & co. recently have become sophisticated development conglomerate instead of advancing towards a understandable installation step by step inheritance.
Pros of Kibana
- Easy to setup88
- Free65
- Can search text45
- Has pie chart21
- X-axis is not restricted to timestamp13
- Easy queries and is a good way to view logs9
- Supports Plugins6
- Dev Tools4
- More "user-friendly"3
- Can build dashboards3
- Out-of-Box Dashboards/Analytics for Metrics/Heartbeat2
- Easy to drill-down2
- Up and running1
Pros of Loggly
- Centralized log management37
- Easy to setup25
- Great filtering21
- Live logging16
- Json log support15
- Log Management10
- Alerting10
- Great Dashboards7
- Love the product7
- Heroku Add-on4
- Easy to setup and use2
- Easy setup2
- No alerts in free plan2
- Great UI2
- Good parsing2
- Powerful2
- Fast search2
- Backup to S32
Sign up to add or upvote prosMake informed product decisions
Cons of Kibana
- Unintuituve7
- Works on top of elastic only4
- Elasticsearch is huge4
- Hardweight UI3
Cons of Loggly
- Pricey after free plan3