I am using it myself. My specialty is application performance monitoring, but when I'm putting systems monitoring in place for the backend, Grafana is the best solution for views and dashboards.

I have utilized Grafana's integration capabilities with Prometheus. In a previous role, we displayed some data with Elasticsearch. I have used it heavily with Zabbix integration as well. I have done Nagios in the past. It depends on the toolset that the customer has, but Grafana is very appealing because the business appreciates the views that come out of Grafana as it gives them the views they want.

I have employed real-time metric visualization capabilities. That's basically what monitoring is - a real-time view. I build up these dashboards or real-time views, but they can also be used as historical views, pulling out more data.

Grafana's role-based access control and multi-tenancy features are important for my organization. At the moment, most of our Grafana is on-premises, but we're looking at cloud options as well. Multi-tenancy is quite important because we have customers that will only want to see their information and not any other. They're not allowed to see some of the other data that we collect, so it's important to have a multi-tenant system.

The most valuable feature is Grafana's ability to plug in data or events and monitoring data from any kind of source. The graphing capability is what I use the most.

I have made use of Grafana's customizable dashboards and templating features. These features have enhanced my data visualization and analytical processes by enabling me to give real-time views to our end-users of what they're doing or what their service is doing. The historical and trend data allow people to pull up data from Grafana and from whatever source to display it and examine how an environment is being used.

I have employed real-time metric visualization capabilities for monitoring and real-time views. These dashboards can also be used as historical views, pulling out more data.

The effectiveness of Grafana in delivering real-time notifications through its alerting system is quite good. The widgets are able to highlight errors if they happen in real-time on the dashboard. The alerting functionality is improving. I generally tend to use the monitoring tool for alerting rather than Grafana, but I have had to use Grafana occasionally without any issues.

Grafana could be improved through enhancement of graphs and visualizations and providing more integrations. Grafana is going to start working with OpenTelemetry, which would be helpful to have the same sort of design across all different platforms.

I would appreciate additional features in the next release to make it closer to a perfect score. Improved templates would be beneficial in some aspects. Some of the older templates that I used to be able to get in Grafana are only available with a license.

I have been using Grafana for about five or six years.

The product has been stable. I have never really had any major issues. There have been times when the integrations don't work as smoothly, but that's usually a configuration issue, not the tool itself.

I usually solve problems by myself. I very rarely get in touch with technical support as we don't have that option.

I used the built-in graphing from the tools themselves before Grafana. I have pushed some data into Power BI as well in the past. I have used various displays, mainly just whatever the platform provides, such as Nagios dashboards, Zabbix dashboards, or SCOM. It depends on what monitoring tool the customer has.

The initial setup for Grafana was very straightforward. I followed along and did some design work. I had to calculate the database size and figure out requirements, but beyond that, it's not difficult to install at all.

I did not evaluate other options before choosing Grafana for graphing. Grafana seemed the logical choice. There aren't many other platforms that offer the kind of flexibility and number of integrations that Grafana does. They are quite niche in the graphing and dashboarding space.

I find the pricing of Grafana to be reasonable. I have only ever used the free tier of Grafana, so I cannot comment on the pricing model itself.

Based on my experience, I would recommend Grafana to others.

I rate Grafana an 8 out of 10.

For my personal usage, I do use Grafana, and it does make life easier for solving stuff.

The main benefits I have seen from using Grafana in my day-to-day activities is the visualization of the metrics, specifically Dora Metrics. Instead of saying 'I feel the team is developing bad or slow,' you can actually have metrics to support that. You can actually show that this team could work better here, in this case, or needs to focus more on peer reviews or on deployments. The visualization of the data is key.

For my personal usage of Grafana, I think there could be improvements, particularly that I use the Grafana Cloud SAS solution. The integration guides could be simpler and easier.

Regarding the clarity of the official documentation for installation, I think the official documentation, which has something called Alloy, the Alloy integration, is not that clear. It was mostly for personal usage that I'm talking about right now.

I have been using Grafana for around a year, maybe more.

Grafana is stable; however, in the previous company, we also had Grafana for a long period of time, and its stability depends on the load. Once you get to a higher load, you need to re-evaluate your architecture and put that into account.

In assessing Grafana's scalability, we started noticing logs missing or metrics not syncing in time, which indicated a bottleneck that we had to address by updating the infrastructure.

I'm not familiar with Grafana's feature in terms of community and documentation since I've been here only a few months. The community provides extensive knowledge about Grafana. You will get faster answers about Grafana than about Datadog from the community.

My advice for people who are new to Grafana or considering it is to reach out to the community mainly, as that's the primary benefit of Grafana.

The reasons for moving from Grafana to Datadog include the fact that Datadog is a SAS solution, and we don't need to manage it. I was told, and as I mentioned I'm kind of new, there was already Datadog running, so it's not creating a new one but just moving the data. The main benefit of Datadog versus Grafana is the ease of creating a dashboard, which is just simple for the user.

In the previous company, about three or four people worked on Grafana implementation. It was an ongoing effort that took several months to complete.

Grafana is easier to sell to management compared to Datadog and other solutions because it has an open-source tier, which makes it easier.

If I'm coming as a personal user, then Grafana is the best solution out there right now. But if we're looking at it as an enterprise, then when money is less of an issue, Datadog is much easier to use and implement than Grafana.

Managing and maintaining Grafana is kind of managing another application; as far as Grafana itself, you don't have much to do. It's mostly about the infrastructure, resources, and if you're deploying it in high availability, maybe more instances. So it's mostly infrastructure work and less about Grafana itself.

I rate Grafana an eight out of ten.

The primary use case for Grafana is to display data from Prometheus in a graphical user interface for easy monitoring and analysis of metrics. It is used for end-to-end tracing of applications and integrates with AWS services.

Grafana improves the organization by showing data from Prometheus in a user interface.

Grafana provides a user-friendly interface for viewing infrastructure metrics through dashboards. It integrates with Prometheus to pull data and offers a straightforward setup process.

Users can monitor metrics with greater ease, and the tool aids in quickly identifying issues by providing a visual representation of data. Grafana's integration capability is straightforward, which facilitates building dashboards as needed.

Grafana could consider building its own metrics system to eliminate the reliance on other tools like Prometheus, providing a one-stop solution.

I have used Grafana for the last four to five years.

There are some instances, about one to two percent of the time, where dashboards do not work, however, these are manageable and typically attributed to the underlying data source.

Grafana is pretty scalable as it can source data from multiple providers without limitation.

The initial setup was straightforward. Those familiar with deployment find it easy to manage and deploy.

The implementation is managed by a different team, and issues with integration have been minimal.

I used the open-source version for my learning, which was free. In an enterprise setting, pricing is reasonable, as many customers use it.

I rate Grafana eight or nine out of ten. The deployment of multiple tools could be streamlined into a single solution for better efficiency.

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

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.

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.