Grafana Reviews

We use it internally to monitor both hardware and virtual machines running on our servers and then generate reports based on the monitoring data.

One standout feature is its open-source nature. It excels in providing comprehensive details when there are downtimes or fluctuations, offering thorough reports. From a cost perspective, it stands out positively, especially when compared to other tools, given its robust functionality as an open-source solution.

There is a need for improvement in automating daily monitoring reports, especially when alerts are triggered due to system downtimes or fluctuations. This enhancement would make the monitoring tool more efficient and streamlined. While it does produce reports, the quality might not be optimal.

I have approximately two years of experience working with it.

I haven't encountered any issues or bugs while using it, and it has been stable throughout.

Numerous users, ranging from five hundred to a maximum of three hundred, frequently engage in upscaling and downscaling activities. The system handles this well, and the performance remains stable, even when multiple users log in and out simultaneously.

The initial setup is not overly complicated nor excessively straightforward. It's a manageable process that involves following a step-by-step approach.

It's free of cost; it operates as an open-source tool.

It is recommended for use, and in parallel, WebEx is another open-source tool. Both are straightforward to deploy on a Linux server. The process is simple and similar to each other, and there's no need for any complex procedures. Deploying these monitoring tools on a Linux server is hassle-free. Overall, I would rate it eight out of ten.

Our team used a Grafana for training.

The comparison feature is very good. 

The service dashboard is very hard and needs improvement. 

I have been using Grafana for six to seven years. 

It is a stable solution. 

The solution was deployed with Kubernetes. The deployment took an hour to complete. It is not difficult to maintain as Kubernetes gives easy updates. 

I am using the open source version. 

I rate the overall solution an eight out of ten. 

We primarily use the solution for site visibility.

It helps us monitor our applications and their performance, including CPU.

The heat maps are great.

We like the dashboards on offer. 

It's a stable product.

The solution can scale well.

Pricing isn't overly expensive.

Technical support is good. 

I cannot think of any specific issues we've had.

We'd like an enhancement of legends and labels in the UI. The formatting could be better. 

I've been using the solution for two years. I haven't used it for too long just yet. 

I'd rate the stability eight out of ten. There aren't bugs or glitches that I have noticed. It doesn't crash or freeze. I find it to be reliable. 

I'd rate the scalability eight out of ten. It can extend well. 

We had 50 or more people using it in my previous organization. 

Technical support is fine. They have been helpful and responsive. 

Positive

I'm not sure if it is easy to set up the solution. I did not handle the deployment. 

I have not looked into the ROI.

The pricing is moderate. It is neither too expensive nor overly cheap. 

I am using the latest version of the solution. 

As a cloud solution, it is very good. Many organizations are going to the cloud, and Grafana is the best way to monitor those cloud environments.

I'd rate the solution eight out of ten. It is a good solution. 

We primarily use the solution as a dashboard and visualization tool for our business units.

Grafana is able to connect with multiple data sources, unlike Elasticsearch.

There is room for improvement when using multiple dashboards because they can become complicated to keep track of and use.

I would like to have alerting functions added to the solution.

I have been using the solution for seven years.

The solution is stable.

We previously used Pearl and PHP but they were outdated.

The initial setup is straightforward.

The implementation was completed in-house.

We are using the open-source license.

I give the solution a seven out of ten.

The solution requires one day a week for maintenance.

We have 200 people using the solution in our organization.

We built a web service around Prometheus and Grafana and control them through the web API, which is very helpful with deployment.

Our primary use case is for insight on CPU, what's happening in namespaces and nodes.

We like the features, it's a basic dashboard.

I'd like to see more in-depth graphs and more AI, alerting and log aggregation.

We've used this solution for two years. 

The solution is stable if you use it separate to Rancher. 

Scalability could be improved. 

Deployment is straightforward and takes a few minutes. It comes with Rancher so you can spin it up quickly. 

We're using the open-source version. 

Our company uses the solution as a monitoring tool that provides alerts and behavior information. We have many Spring Boot applications and the solution works well with them. 

The solution is adaptable, easy to use, and works well for microservices development. 

Compatibility with Prometheus databases and the Spring Boot application make it the first choice when moving toward an SRE model.

It is difficult to manage defects because the solution does not provide granular details about the internal system for tracing. 

Writing queries can be a bit difficult because the syntax must be maintained. The dependency on syntax should be removed so that it does not matter for queries. 

I have been using the solution for two years. 

The solution has some stability issues because I don't always see proper results. In comparison to other tools, it is not the most stable when using extensive SRE techniques. 

Dynatrace and ELK are more stable but are more costly. An organization that needs strong stability and has a bigger budget could consider these tools.  

Stability, features, or quality should not be based on cost. It is important to compare SRE models to find the best for your environment. 

I have never needed technical support. 

The initial setup is easy for on-premises. You install, integrate, and immediately see the visualization. 

I am not sure about the ease of cloud or enterprise-level setups. 

We implemented the solution in-house. 

I use the open source model so it is free. 

In the SRE model, there are many tools evolving but the solution is a good starting point for SRE with Spring Boot. Once you become familiar with SRE and are clear about the terminology, you can explore other products. Other users will say ELK or Dynatrace are good, but the best solution depends on your requirements. 

SRE is a journey that is uncovered as you progress. The solution is adaptable, easy to configure, works for microservices development, and integrates with Spring Boot so it is the best product for starting points. 

The solution is a visualization tool that is pretty easy to use. Writing queries can be difficult so it is important to learn how to integrate with data sources before you write queries to visualize those metrics. 

I rate the solution a six out of ten. 

The primary use case of the solution is to create business and technical dashboards in the metrics provided by the services through Prometheus.

The solution has improved our organization by providing a centralized way to instantly see our business, technical, and service metrics.

The most valuable features are the user-friendly interface and the ability to connect with many data sets.

The solution has room for improvement with a better API to help automate the construction of the dashboards easier.

I have been using the solution for three years.

The solution is stable.

The solution is scalable.

Previously we used New Relic before switching to the solution.

The initial setup is straightforward with just a few clicks on the solution's cloud.

The solution was implemented in-house with a few clicks.

I have seen a return on investment.

I give the solution an eight out of ten.

There are 40 people using the solution in our organization and it requires three people to maintain it.

I would recommend you try to use as many tools as you can. You can have an ecosystem that is quiet and works like using Temple, Prometheus, and so on.

We used Grafana to monitor our traffic.

The best feature was the creation of graphs and trends to know if the traffic was low or okay. We could create week-over-week traffic and trend analysis as well. All these features were good and were the only features I used.

If there was an issue on one node, we couldn't drill down and see all the issues on other nodes or see if there were interlinked issues. However, Datadog allowed us to do this. In Datadog, we could take our complete environment and see what nodes went down simultaneously and the cause. For example, Datadog allows you to see in the graphs whether the database is locked or if there was a firewall issue. However, in Grafana, we had to add everything into a single dashboard manually.

In the next release, there should be more of a colour palette. The colour palette in Grafana is limited, and it chooses its own. We used hundreds of services to monitor into a single graph, so in the stacked chart, it chose the colour needs, and when we wanted to change it, there were only four or five options.

I used this solution when I worked for Expedia. We used the solution for about three years.

There were no breakdowns or hiccups.

I am unaware of the scalability. There were around 500 users when I worked there. The network team was using it on a large scale.

I don't believe that Grafana fulfilled the requirements completely. That's why we moved to Datadog.

I was not involved in the initial setup. We had a password issue at a point, but I am unsure if that was an issue with the solution or just within the organization.

Grafana was not an open source, and we had to pay for a license to use it. The same was the case with CashPoint. There was a license, but I'm unaware of how much we were paying.

I believe my old company chose Grafana because they initially wanted to monitor the traffic and know the firewall and scaling.

I rate Grafana a six out of ten because Grafana has limited options compared to Datadog. Regarding advice, it was pretty simple to use Grafana. The trickiest part was creating a new dashboard, working on the query and adding the requirement. So you have to have the source and path handy to put that in the query. Any user can use Grafana once they understand what the dashboards are doing and what data is being searched from those dashboards.