Grafana Reviews

I use the solution to configure new, high performance servers that include application monitoring. 

The solution's application server is easy to use and its overall architecture is better for development. 

It is easy to change and move virtual servers. 

The solution should include online support. 

I have been using the solution for six months. 

The solution is stable. 

The solution is scalable. 

I have not needed technical support. 

The setup is easy. 

Five people on our internal team handle deployments and one person handles ongoing maintenance. 

Our internal team implemented the solution and it occurred quickly with no issues.

I rate the solution a ten 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 are using Grafana for observability dashboards.

Grafana has helped our organization with observability and operational excellence. Operational excellence is a key part of any organization from a data platform perspective and setting the alerts and monitoring policies on Grafana was easy.

The most valuable feature of Grafana is the ease to build dashboards from observability construction. Additionally, the page services and integration are good.

The look and feel of the charting and graph capabilities in Grafana could improve. If they provided a storyboard type of feature as they have in other solutions, such as PowerBI. The multi-tenanted and stitch metrics features could improve.

I have been using Grafana for a couple of years.

The stability of Grafana is good. I have not seen any issues.

Grafana has been scalable in the pipelines we have used it in. We have 10,000 web links for 10,000 Grafana dashboards.

I have not used the support from Grafana.

We had set up our own monitoring and metrics dashboards and custom dashboards prior to Grafana.

I have not set up Grafana but my team has found it easy to do. We have an automated setup of Grafana. Every new pipeline gets created, and it creates a deep link into a Grafana dashboard.

Grafana is good as a solution because it is easy to offset monitoring and alerting policies in Grafana.

I rate Grafana a nine out of ten.

I use Grafana's multiple dashboards for throughput for real-time analysis of monitoring, checking creds and authentication requests, and monitoring the time between direct services.

Grafana's best features are live monitoring and alerts.

In order to enable Grafana, you need another tool called Prometheus, which loads data to it. It would be helpful if Grafana provided more information and training on how to use Prometheus. In the next release, Grafana should include API monitoring.

I've been using Grafana for two years.

Grafana is stable.

Grafana is scalable and can be implemented in multiple environments.

The initial setup is fairly straightforward, and Grafana is easy to configure.

I would give Grafana a rating of seven out of ten.

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.

We use this solution for monitoring activity for e-commerce businesses. With Grafana, we can identify in detail where issues come from and solve the problem. We are customers of Grafana. 

The solution provides more of a graphical representation so we can see any incoming requests, each and every functionality, and quickly know where the issue is. It's very helpful in terms of monitoring with respect to the market from a request to a response.

Grafana has made some changes recently. Previously, we had different dashboards but they have now merged the three designs into one dashboard and now we have to monitor a single dashboard for multiple reasons. It may not seem challenging, but we have critical issues that arise, and we don't know where they're coming from. We have to check all three aspects which takes us longer than it used to and can also affect productivity.

I've been using this solution for one year. 

Grafana is a stable product.

The solution is scalable, we have over 40 users. 

We have good technical support. 

Positive

I recommend this solution but for someone who doesn't have experience with Grafana, it may take a while to understand because it presents everything with a graphical representation and you need to figure out why there are multiple dashboards.  

I rate this solution eight out of 10. 

It's for monitoring our infrastructure. They have some databases and some applications running Java. There are some Kubernetes and old Kubernetes deployments. The company wanted to visualize the logs and send some application sys logs. This is the main utilization.

It's a web application, Tomcat application, Java application, and database application. They are the main focus for collecting the application or system logs.

There is no agent to install. There are many dashboards also. 

There is an active community where you can gather a lot of information about how the solution works. I come from Splunk. If I compare it with Splunk, Splunk has its own SPL, for example. You can play with the dashboard. There is some advantages in common with SPL. Visualization and collecting logs it's similar. However, Grafana is trying to cover many types of open-source infrastructure. This is why I appreciate Grafana versus, for example, Splunk.

The initial setup is not difficult. 

It is a stable, reliable product. 

They are doing well in terms of improvements they're making. They progressed much in dashboarding. However, it's very, very complicated when you start to understand how you make dashboards. You need to figure out how you collect and source your logs, for example. In the area of documentation, they must do a better job. Splunk documentation is much more organized than Grafana. Since it's open-source, you have to test your infrastructure more. You need to really understand it before you install it. 

It would be helpful if they simplified the data source.

I've used the solution for about a year. 

It is a stable solution. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

You have to plan. You have a certain number or gigabit of logs that you can index. You also have a limited number of series. For users, I don't remember if we had any issues adding users. However, there is a cost per the size of the logs or the number of series. Scaling will drive costs up. Right now, our IT and development team is on the product. They are encouraging other departments to try it out. 

The department where we worked has used support. We had to collaborate with Grafana since sometimes we were applying some solution that was not working. The logs were not coming and there were some errors. We had to open tickets and deal with the supplier to resolve the issues.

From my experience, when dealing with Splunk, for example, it's a big company and sometimes I have to deal with people that have no knowledge. However, with Grafana, we don't have that issue. They are good.

In one company, they asked me to play with Grafana and Prometheus. I've used them both.

I've used Splunk as well. It's not an open-source product. 

It is very easy to set up the solution. It's not overly complex or difficult. 

It's a couple of months before you start. For example, for a company that doesn't have any experience, they need to take time to understand it, especially if they only have a sys admin and not a senior person. 

In our case, we did a lot of testing and installed it on a virtual machine. You do have a couple of months to play with it before you decide to go into production. 

We have a license. The pricing varies. It depends on the number of metrics that you want to ingest per day.

We are a customer and end-user.

If you use this product for the first time, I would encourage you to try some sort of live demo. Go to see the product in action and understand how it works, and test it. To install it in the cloud, you can have a free license at the start or a limited license for some events. You can try to play with the product and create some dashboarding to ingest some logs. 

You don't have to install the whole thing as it's complicated to install the whole product, and you need many machines, CPUs, and memory. It's a good idea to try it out in a small way to see if it fits your needs or if you like it.

I'd rate the solution eight out of ten. I had a good experience testing the solution.

This is a good solution for companies that are using, for example, open source or Linux options for all the tools or those coming from the world of open source.

We use this solution primarily for data monitoring, specifically payment transaction monitoring. For example, we use it to monitor payments passing through our systems, integrate with different parties, and track the metrics of payments. The support team can view all these items on a dashboard to gauge the threshold of payments.

The query patch is the most valuable feature. We can write queries in different languages, which is beneficial for visualization.

The product could be improved with a feature that provides detailed error messages when we encounter issues. For example, we had a case where there was an error message and we could not decipher what went wrong. Additionally, the product's configuration for saving files could be improved, and more plugins could be provided when using the dashboards.

We have been using this solution for approximately two years as customers. We deploy this solution on-premises.

The solution has been stable for us. We can integrate our single internal sign-on into the solution. 

The solution is scalable and we can add people on without any issues. Additionally, we can integrate our single internal sign-on into the solution. About 40% percent of the engineers in the company are using this solution.

We have not had any experience with customer service and support yet.

Unfortunately, I would not be able to comment on the initial setup as I wasn't involved in the setup process.

Unfortunately, I cannot comment on licensing and pricing costs as I am unaware of the pricing details.

We chose this solution because it met the requirements of visualizing and monitoring to make decisions. We found it had very good industrial usage from the reports we read when Space X launched.

I rate this solution a six out of ten. Nevertheless, we recommend using this solution and advise others to go through the tutorial videos before using it. The solution is good but it could be improved by including features that provide more detailed error messages as well as additional plugin options for the dashboard.