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 use Grafana for MYSQL monitoring, monitoring the system, and application monitoring.

The best thing about Grafana is the visualization. The colors and the ease of use make it very user-friendly. Grafana has a huge community, so we can simply Google it and get the answer if we have any doubts.

The second best thing about Grafana is its alerting system, which is easy to define within Grafana rather than defining alerts in Prometheus.

Thirdly, Grafana is completely free of cost. I use Grafana for many things, and all of them at zero-dollar cost. On the other hand, other monitoring tools in the market, like New Relic and Datadog, offer many features, but Grafana is a good monitoring tool for a small-scale company.

One thing I got to know is that Grafana doesn't provide anything for reporting. As a DevOps engineer, I would like to get a weekly report expressing the system's overall performance in the last week. For example, how many alerts were triggered, how many APIs responded with bad requests, and how many failures occurred? All these things are generally required at the beginning of the week so that we can better research and optimize everything that's required.

Currently, Grafana sends a PDF version of the report, and they are not doing anything beyond that. So, that's a feature that Grafana can work on to make it more accurate and better.

In the additional features, I would like to see logs. Logs are basically created when an API is hit. The log contains information such as the API that was hit, the status code, and the time taken. For instance, the log file would store the error message if there was an error in the API. It makes it easier for the developer to debug the API that showed an error. Grafana claims that it has Loki, which is used for logging and saving logs. However, I could not configure Loki with Grafana to see my logs. Grafana could look into this field and make changes to improve it.

I have been using this solution for three months now. I am using the latest version, 7.4.

Grafana is stable. There were some bugs in the previous version, but the latest version is bug-free.

Grafana is scalable for product-based companies, but for service-based companies with multiple projects, it's difficult to scale using Grafana. However, since it provides all the features for free, it's manageable.

We are a small company of 70 people, and I am currently the only one using Grafana. We started using it after I researched and decided to use Prometheus and Grafana for monitoring.

The customer support team of Grafana is available for the enterprise and pro versions. However, there is a vast community of Grafana users, and if you require any help, you can post your query, and you will undoubtedly receive an answer. Most likely, your question may have already been asked and answered in the community forum, so checking there first is worthwhile.

Setting up Grafana can be a bit tricky. If I rate the difficulty level on a scale of one to ten, I would say it's around five. But once you have connected one data source, it becomes easier to connect with other things.

Grafana is not entirely open source, as it has three versions: the free, enterprise, and pro versions. Most of the required features are available in the free version of Grafana, which you will use as a visualization tool, while Prometheus will serve as your monitoring tool.

Therefore, you won't use Grafana as a monitoring tool. If you use Grafana's features, they are free of charge. Hence, you can use Prometheus and Grafana to fulfill your needs. However, if you are using MongoDB as your database, its plugin is not available in the free version of Grafana, and you'll need to purchase the enterprise version.

I will be able to comment on whether Grafana is useful for you or not, depending on various factors. For instance, I would like to know the scale of your company, the products you are making, the scale of production, and whether you are a product-based or service-based company. Additionally, I would like to know what other features you require from your monitoring system.

If Grafana meets your criteria, I suggest using it because it is either free or comes at a cost. The free version of Grafana is usually sufficient for most users.

Overall, I would rate Grafana an eight 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 use the tool to monitor metrics on dashboards. 

It's easy to make changes. We can put many dashboards in one place. There's no delay in showing data - what you see on Grafana matches the server metrics.

Grafana could improve by having its own query language. Currently, it uses languages like Prometheus or InfluxDB, which not everyone knows. Their query language should be easier.

I have been using the product for four years. 

Stability-wise, our on-premises version was mixed, but the cloud version is stable.

My company has 2000 users. 

Setting up Grafana is moderately difficult, especially writing query languages and custom metrics. Creating custom metrics requires writing new query language at the server level, which can be challenging.

If you want to use Grafana for the first time, I'd say you can. It's cost-effective compared to other products like Datadog. But if cost isn't an issue, I'd recommend Datadog. For beginners, learning to use Grafana is moderately difficult. I rate it a seven out of ten. 

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.

My main use case is the dashboard. For example, we have screens created in the last step, and we integrate Grafana with that so that we can see the dashboards with the data. What does the traffic look like? What do the errors look like? So the is our main use case. 

The most valuable aspect is customization. There are many customizations possible, so I like that.

There is room for improvement in terms of stability. 

I have been using Grafana for more than a year. 

I would rate the stability an eight out of ten because sometimes I find issues with Grafana. For example, I am unable to open some services there. Then, we have to open ten different tabs to get it fixed. And it's annoying when there's something going on we want to check Grafana, and it throws four different errors. 

We have never had any issues with scalability. 

Everyone in our organization uses this solution. So, we have over 10,000 end users. 

The initial setup is straightforward. You simply see what you want to do. You want to add a row. You want to add a panel. So it's easy for me to set it up. 

Overall, I would rate the solution an eight out of ten. 

I have used Grafana mainly to build custom dashboards. We haven't got Grafana Enterprise due to billing issues. I have used Grafana, installing it physically on a server to build custom dashboards using plug-ins. I have used Enterprise Grafana cloud for many integrations, like RabbitMQ, JMSQs, and datasets. We are mainly focused on dashboards and not on alerting.

Grafana's built-in integration with third-party tools, databases, and MQs is an amazing feature. Now they are leading many integration modules as well for RabbitMQ specifically. You will get a prebuilt dashboard. You have to configure the RabbitMQ, and you will have all the monitoring available. You don't have to actually develop a dashboard and identify what needs to be monitored.

Setting up alerts via Grafana is a bit complicated, and alerting needs to improve. We used Azure for our alerts and Grafana purely as a dashboard tool.

The solution's stability needs improvement.

I have been using Grafana for three to four years.

I have come across multiple issues with Grafana, like getting shut down automatically, the process getting killed, etc. Grafana, on a main level, is good, but the stability of the underneath platform supporting Grafana's UI needs to be improved.

I rate Grafana an eight out of ten for stability.

While using the Grafana open-source version, scalability will definitely be a big challenge because you are not using an enterprise version. Grafana's open-source version is not scalable. It's useful for small use cases and specific use cases. Using the Grafana open-source version will be challenging if you want to deploy a hundred applications and bring up a hundred dashboards for different reasons. While it is possible to do, you will end up having issues.

For open source, Grafana does not have technical support. It has an open forum where you can post your questions, and they will respond to you. However, their response on the open forum was good. Being an open-source solution, having a big community to support is an added advantage compared to other tools.

Grafana's deployment takes around two hours. It's not super complicated, and it's pretty straightforward. Everything is available on the internet. You can browse the internet and get a bunch of documents to complete the deployment.

Since Grafana is an open-source solution, it is free of cost.

It's very good to start with the open source and very seamless. You can directly connect your data sources to the solution. You won't have to worry about managing the Grafana UI because Grafana comprises two things, namely, the data source where you are connecting and the dashboard. Getting started with Grafana Cloud is good because it's very seamless, good, and helpful. If you want to scale and use Grafana as an observability tool, I would say you have to think twice before choosing it because there are a lot of gaps, especially on the APM side of its application and performance monitoring side. The infrastructure gets complex as it scales. For a small use case, for independent use cases, or for building simple dashboards, I recommend Grafana.

With Grafana's open-source, you download a package, put it in your server, and run it. I've used Grafana Cloud as well. For Grafana open-source, the login is limited to two or three people. More people cannot log in, and you can create multiple users. You can create around five to six dashboards and use 10 to 12 plugins. If you have just one or two use cases to be used, like if you have order delivery and you are looking for a tool, Grafana is a great one because the integration is pretty simple.

Overall, I rate Grafana a nine out of ten.

We use Grafana for application metrics and data utilization for consumer databases. We also use it to connect and evaluate clients and create databases where we upload client data.

We find Grafana essential for our company because of the visualization function for all application metrics in our environment.

What I found most valuable in Grafana is that it has a lot of integrations and features that I need for data processing and visualization.

One area for improvement in Grafana is that depending on your version, you have to pay for the features, making the license expensive. It would be great if the licensing model could be more flexible.

In the next release of Grafana, I want cluster creation to be available, which would help in Grafana deployment and scaling. Currently, the scaling process for the solution is a bit complicated.

Easier integration is also what I want to see in Grafana in the future.

I've been using Grafana for four years.

Grafana is a very stable solution.

Scaling Grafana is a bit complicated, so I want to create a cluster to promote high availability in the solution, deploy in one step, and for Grafana to scale automatically.

My company has the open-source version of Grafana, so it gets support from the community. The community support is good.

In terms of standalone visualization tools, I've only used Grafana. I used another monitoring solution, but the visualization was only integrated.

Other solutions can provide what Grafana provides, but you need to pay. Grafana, on the other hand, has an open-source version, and as an open-source solution, it's complete, at least for my company's needs.

Compared to other software, it can take some time to get used to how Grafana works, but you can live with it because you can learn to use it.

One person deployed Grafana for my company, and the process only took twenty minutes maximum.

My company uses the open-source version of Grafana, so it's free.

I'm currently using Grafana.

My company is a Grafana customer.

I'm using the open-source version of Grafana, 9.3.

Between sixty and one hundred people, mostly software engineers, use the solution in my company.

Grafana requires maintenance, and that's the responsibility of the entire team.

There's a plan to increase the usage of Grafana in other areas besides engineering. My company plans to create dashboards for data in other areas.

I advise people who want to use the solution to try it out first. For example, Grafana has many good integrations if you need to gather metrics, and you can technically use any query to create dashboards and graphs inside Grafana. I advise that you explore the solution.

My rating for Grafana is eight out of ten because it's a very good product. It's complete and has an open-source version with many features. However, some of its interface capabilities could be cheaper.