TrustRadius: an HG Insights company

Kibana Reviews and Ratings

Rating: 7.4 out of 10
Score
7.4 out of 10

Reviews

5 Reviews

An amazing tool for Data Visualization

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

Our organization uses Kibana primarily to visualize and analyze large volumes of logs and performance data generated by our applications and infrastructure.

Kibana is integrated with AWS OpenSearch. We use AWS OpenSearch to store AWS WAF logs. Whenever we identify an issue, we go to the Kibana console and search for various parameters related to our infrastructure that help us in searching the logs quickly and enable us to identify the issues.

Pros

  • Real-time Dashboards:
  • We use Kibana to create live dashboards that track WAF performance in real-time. We have a dashboard that visualizes our whitelabel partners and the requests they received on various pages. Using these metrics, we identify the origin of the requests and also how many requests were allowed/blocked by our AWS WAF.
  • Quick Search functionality: We have used OpenSearch to index WAF logs and hence Kibana gives us a quick search feature over several indexes in real time. We are able to filter logs almost real time against our WAF logs.
  • Another feature which is great in Kibana is the alerting and monitoring. We use Kibana to send alerts to our Slack channels that helps us in quickly identifying the issues.

Cons

  • Kibana supports both KQL and Lucene Syntax. While this functionality is great, but it is sometimes very confusing for the users to switch between these two.
  • I have faced several performance issues with large data sets and dashboards. Kibana takes a lot of time to response when run against a large data set. Also, the visulization is delayed.
  • While Kibana is great in alerting in a Slack channel, it is limited to send alerts to a single channel. I have been using Datadog and it allows sending alerts in multiple channels. This is a limitation from Kibana.

Likelihood to Recommend

Kibana is indeed a powerful tool and has many use cases especially in environments that rely heavily on real-time log analysis and visualisation. Kibana’s ability to handle large volumes of log data and present it in an accessible, searchable format is invaluable. We use Kibana to monitor security related issues and it proactively alerts our Slack channels about any anomality or issues.

Vetted Review
Kibana
3 years of experience

Kibana operations manager

Rating: 7 out of 10
Incentivized

Use Cases and Deployment Scope

We use Kibana to visualize automated error reports on our website. We are able to find potential consumer issues and investigate.

Pros

  • Visualize automated reports
  • List problem areas in site
  • Show consumer journey.

Cons

  • Improved tutorial/ user guidance
  • Improved labeling for sources
  • Ease of login and sharing with coworkers

Likelihood to Recommend

We are able to set alerts whenever a certain number of errors are appearing. These automated alerts allow us to have constant monitoring. Kibana is not very useful for much more edge cases or slow burn cases. These things will often hide under the noise of all the other indicators. Also, we need to find a way to ignore alerts.

Vetted Review
Kibana
2 years of experience

The king of observability for many years running!

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

Kibana is a cornerstone of our observability strategy. We use it for all aspects of our operational workflows, from tailing log files in production to debug events in real-time, to creating beautiful and enlightening dashboards for surfacing key metrics for our leadership team. Kibana helps us both with tracking our "known knowns" and our "unknown unknowns" via its expressive and powerful filters and customizations.

Pros

  • Fast searches with powerful index.
  • Beautiful data visualizations.
  • Real-time observability.

Cons

  • Data ingestion can be slow if not properly architected.
  • Operational workload is heavy to keep it finely tuned.
  • Learning curve for initial install can be steep for a production environment.

Likelihood to Recommend

Great for teams big and small that want a single pane of glass for understanding their systems, from dev, to staging, to production. Well-suited for teams that need to preserve logs for long-term compliance reasons, and also mine their logs for useful operational insights. Highly recommended as both an open source project and a commercial offering with fantastic paid support.

Vetted Review
Kibana
5 years of experience

Excellent free log analysis and dashboards

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use Kibana both for monitoring our production environment and debugging. The log parsing and aggregation are extremely helpful when trying to both get an overview and drill down into specific issues.

Pros

  • Dashboards.
  • Log parsing.
  • Log research.

Cons

  • Some performance issues with large datasets.
  • Linking to dashboards makes extremely long urls.
  • Lack of reports.

Likelihood to Recommend

It's well suited to creating dashboards for getting an overview of what is going on with an application.

Kibana: How else can you understand what is happening in production?

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

Kibana is the front-end to Elasticsearch. Together they offer a "Google-like" interface for all logs produced by applications, allowing to quickly investigate potential issues and access audit logs. Search is happening in near-real time, which makes the information presented relevant. It offers various filters, as required to quickly churn through the vast amount of logs that a production application may produce. We generally use Kibana/Elasticsearch only for recent logs (e.g., retention period of 30 days) and distribute logs simultaneously to a longer-term storage solution, such as Azure Storage or AWS S3.

Pros

  • searching
  • near real-time

Cons

  • slow
  • difficult to operate

Likelihood to Recommend

Kibana (as a front-end to Elasticsearch) is particularly well suite for searching through recent logs, such as the last 30 days.

Elasticsearch is notoriously difficult to operate with large data volumes, which is why it does not serve well as cold / archival storage of logs.