Grafana Reviews

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. 

We use the solution in a financial institution to monitor applications and infrastructure. 

We really only started. 

So far, the management is very good.

The dashboards are very easy to work with. 

It's a fantastic tool.

Support is helpful. There are many useful forums users can turn to as well.

It can scale.

The stability is good.

There are not a lot of plugins for financial market monitoring. Our old tool had more plugin capabilities. 

We need more AI features. We need more data analytics and monitoring done by AI.

We just started using the solution. We haven't used it for that long. 

The solution is very stable. There are no issues with reliability. There are no bugs or glitches and it doesn't crash or freeze. 

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

The team that is implementing the solution has relied quite a bit on the support and forums, and so far, it has been helpful. So far, we are satisfied with the level of support on offer. 

We used to use a different solution. It had very specific tools for fixed message monitoring, among other features, that were useful for finance companies. Grafana doesn't have much that tailors to our sector. 

I was not involved in the implementation. I work with the team that has implemented it. 

We're a customer and end-user. 

We are likely using the latest version of the solution. I'm not sure of the version number. 

I'd rate the solution six out of ten. So far, I can't say it's doing more than our older monitoring was doing. 

We use the solution for integrated logging, which works on our Kubernetes cluster and our separate VM. 

The solution allows our teams to search and conduct application troubleshooting.

The dashboards are the most valuable features.

I would like to have a better configuration in the next release.

The technical support has room for improvement.

I have been using the solution for five years.

I give the stability an eight out of ten.

I give the scalability an eight out of ten.

We have five users in our organization.

I give the initial setup an eight out of ten. There was a lack of support documents to help with the deployment. We just need to configure the file to plan the cluster.

I give the price an eight out of ten.

I give the solution an eight out of ten.

We use Grafana with a Kubernetes filter and it works well. I am not sure how the solution will work on its own.

I was using a restricted version of Grafana where I didn't have the option to create alerts and didn't have direct options to build dashboards. We used the already built-in dashboards there. Therefore, the most valuable thing was that it had a good visualization tool where we got better clarity on the issues to select the timeline and see the data or charts. So, the visualization tool is the most valuable feature I found.

It could be more user-friendly. For example, if I need to build a chart, I first need to sit and learn something on Grafana to write a query to create a chart, it is not user-friendly. 

Its UI features to create charts can also be improved. Some features could have a link to the documentation. 

Another thing I would like is the alerting feature because it was not there in the version I was using.

Grafana is a stable product because with whatever frequency I have used this tool, I have never faced any downtime. Grafana's dashboard is stable.

It is a scalable product because we used Grafana on-prem, with only one server. If we need to add more Grafana servers, it is possible.

I did not use Grafana that much as it was a built-in application of the company I worked at.

Grafana does not have straightforward documentation or direct answers on help pages. I would suggest Grafana users get support from another user or someone who already has used Grafana. While using Grafana, we need to understand how the queries are written to build a new chart. A new user would need to explore it, how it works, how to install it, etc. It would make it easier to use Grafana.

I give Grafana a rating of six out of ten because it is not very user-friendly. It also needs clear documentation and requires time to get started.

In order to understand trends, troubleshoot any issues, and gain observability of our hundred-server retail market cluster, we started using Grafana. This allows us to detect causes and better understand what is happening in the cluster.

Kubernetes could help us to better visualize the trend of our data by recording and displaying our history over a chosen duration, such as the last 30 days. This allows us to better understand our data and the trends associated with it.

It can take a considerable amount of time to learn the graphs if a long duration is selected. Additionally, other aspects such as networking may also come into play. Thus, the loading of graphs for long durations may require additional optimization to improve performance.

I have been using the solution for a couple of years.

I would rate the stability of the system a seven out of ten. There are some conditions that can affect this rating, however, we have already addressed a few issues that were causing problems in the backend.

I give the scalability of the solution an eight out of ten.

We previously used Zabbix and switched to Grafana because of its ease of use.

The initial setup is simple. Depending on our needs initially. To plot graphs, there are many plugins and open-source dashboards available for use. 

All of us in the company have been utilizing Grafana and appreciating its results. Grafana is cost-effective and has provided us with a clear, comprehensive view of our applications, infrastructure, and more.

We use the open-source version of Grafana.

I give the solution an eight out of ten.

The beginning is simple, so anyone interested can quickly deploy and begin using Grafana without any difficulty.

The solution is used for monitoring the live monitoring of our load test.

The most valuable feature of the solution is the UI dashboard because we need to create a dashboard on Grafana to monitor our data.

The solution's integration with other tools needs improvement.

I would like the ability to download my results into any format in order to share the information with my clients.

I have been using the solution for over three years.

We currently have over 50 people using the solution.

The initial setup is straightforward. The deployment usually takes one and a half hours.

I give the solution an eight out of ten.

We use Grafana for matrix and logging Kubernetes.

Many bottlenecks are sent to the base on the logs generated on Loki. We can create alerts based on that log, see the traces and find the bottlenecks easily.

The integration between Loki and Tempo is valuable.

We need different kinds of applications in our infrastructure to see information in Grafana. For example, some other companies use OneAgent, which takes control like Grafana but in one place and is better than Grafana.

We have been using this solution for three years and are using the below enterprise. It is deployed on-premises.

It is a stable solution.

It is scalable based on different metrics, and we have 40 users.

We have raised a lot of tickets, and they respond fast. I rate the technical support a ten out of ten.

Positive

We are working with the Dynatrace team to have POC email infrastructure.

The initial setup was complex because we needed to specify many configurations. I rate the setup a seven out of ten. A third party completed the deployment, and the maintenance was done in-house. It is not difficult to maintain.

I rate the solution a seven out of ten. Regarding advice, ensure there is proof of courses for every tool to see the best fit for your infrastructure.

We're getting the data from the CA team to Grafana, just feeding the data here from there. I used to create the standard dashboards and the custom dashboards based on the user's request.

We use the product in a logistics project where I used it for creating the dashboard for the packages and delivery kind of logistics projects.

There are multiple data fields we can create and graph models and gauge models. There are multiple kinds of models there to create dashboards, which is quite useful. 

The solution is stable.

Support is helpful.

I don't have any notes for improvement. 

There are some areas of network drives that are not showing as expected based on server usage. On the server, it was showing in GB model. However, in Grafana, It is in bytes. Therefore, the calculation it was not showing correctly. That is something that needs to be changed by the vendor team. 

The initial setup is not necessarily straightforward.

I've been using the solution for two and a half years. 

The solution is stable and reliable. There aren't bugs. It's not glutchy. It doesn't crash or freeze. 

The product works for monitoring as well, including log monitoring, monitoring, and alerting. However, we are using just the dashboard. Therefore, I cannot give my view on whether it is scalable or not.

We have about seven admins and 20 users on the solution. 

As Grafana is involved with the DX APM, we used to reach out to the vendor about any issues on the Grafana related to the DX APM. They had good expertise on Grafana and helped us a lot.

I've used other solutions. Grafana graph in representation is more clear for users. They like the view better. Any application has performance issues. We can set up the thresholds on the dashboard to 90% critical and 80% as warnings. We can update those values in the dashboards if we want. It is very colorful with multiple colors to differentiate things. It's just easier to use than anything else.

The initial setup isn't straightforward. Users need to learn the product first. At that point, it becomes easier. 

There isn't really a deployment so much as a one-time integration from the APM for Grafana.

Whenever we create a new agent or an existing agent is used to create the dashboard in Grafana, it normally takes one or two hours to create one dashboard. One dashboard means it has multiple panels like CPU, memory, and application back and front end.

There are a lot of panels. If the user request has very minimal panels, then it takes just 30 minutes to an hour. If they need multiple panels and multiple windows for the graph on a dashboard, then it takes two to three hours to complete it.

Once it is set up, the solution is easy to maintain. 

I handled the deployment myself. 

I was involved in the Broadcom DX APM. I did some POCs and created the dashboard. 

There is a feature called DX Dashboards there. It was used in the Lucene queries, and the dashboards are very innovative, and users like it a lot based on the dashboards.

We're using the solution that's the latest version. 

If a potential customer is already into any other dashboard view, I would advise them to create one free license and create dashboards and observe how it looks compared to their existing dashboard. That way, they'd be able to compare and see which would be better for them.

I'd rate the solution eight out of ten.