Grafana Reviews

We use it to monitor user behavior. We have AI LLM models in NVIDIA Triton. NVIDIA Triton gives us some metrics. These metrics are integrated with Grafana and Prometheus. We monitor user traffic to visualize metrics like p99 latency, increase in user and CPU performance, utilization of the GPUs, RAM utilization, and CPU utilization.

We use the free templates of the solution. We have tested some alerts on metrics. We like the alert features. We plan to use it more. Slack and PagerDuty alerts in Grafana are helpful.

It was pretty complicated to integrate the product into our workflow. We relied on templates we found on the GitHub open-source repositories. It is pretty hard to integrate Grafana and set it up according to our use case. The solution must provide tutorials and guides.

We are a small team. We don't have the time to learn Grafana end-to-end, but we want some guides to help us use it quickly. Prebuilt templates will help a lot. The product must provide more alerting metrics. It must be integrated with iOS and Android mobile phones.

I have been using the solution for four months.

The tool’s stability is quite good. I rate the stability a nine out of ten.

I rate the tool’s scalability a six out of ten. Scaling is complex. We have four developers in the organization who use the product.

We have good Docker experience, so the setup was pretty straightforward. We had to run a couple of Docker commands. We integrated everything with Docker Compose. As we scale up, the setup will get complicated. If the number of users increases, we might consider switching to the cloud.

Compared to Elasticsearch, ELK Stack, and Logstash, Grafana is pretty strong. Grafana is way ahead of its competitors. SigNoz is also an alternative to Grafana and Prometheus. SigNoz is pretty easy to set up.

We haven't worked or dived deep into the documentation and tutorial. I will recommend the product to users willing to take the time and patience to set up and learn Grafana in-depth. There are a lot of tools that we can use to build excellent integrations and get the most out of them with little knowledge. However, to leverage the value of Grafana and Prometheus, we must learn the tools in depth. It will save us time, and we can get much value if we invest time and effort. Overall, I rate the solution an eight out of ten.

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.

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 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. 

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.

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 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.

I use Grafana since it is interconnected with Zabbix. I also use Grafana for the dashboard of machines from VMware and for some network devices connected to Zabbix.

The ability to use Grafana with Zabbix is a valuable feature for me. Zabbix provides me with alerts and information if something goes wrong, while Grafana offers a better dashboard that is more stable. If you know Grafana well, it can show you everything, like the uptime of different sources and other areas.

I have a problem with Grafana in the area of documentation. There is a problem in the area of some graphs where you connect elements. With Grafana, there is only one name that can be included for ten hours. In Grafana, only one big field with one text name is shown in the documentation. When it comes to production, it is only for a period of time that some fields on each side give the information they have. I researched on Google and other forums and saw that people face problems when they can't connect a field with the same value. The aforementioned area in the tool needs improvement.

I have been using Grafana for nine months. I am a customer of the product.

I have always had a stable version of the product. In general, I have not had any issues with the product.

The technical personnel in my company use the tool, and it is possible to add or delete devices and other statuses in the solution. Around five people in my company use the product.

I have always used the online forums or the internet to find information related to the product. I have not contacted the tool's technical support.

The product's initial setup phase was very easy.

The solution is deployed on an on-premises model.

For me, Grafana is a cheap tool because I don't have to spend much time learning the product since it is a simple solution. I don't know if there are different paid versions of the product.

My company chose Grafana over other products in the market considering its integration capabilities with Zabbix, good documentation, and the many topics about the tool that are available on the internet.

I would suggest Grafana to those who use Zabbix because it helps users get a lot of information on networks and resolve a lot of problems.

I could do everything in Grafana with the help of graphs and documentation and get information on different types of devices.

I rate the overall tool an eight to nine out of ten.