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.

We actually work with BMC and similar solutions, and while I wouldn't say that they are the same as a full, fully-fledged APM, we're working our way up using open source and everything, so I don't know how far we'll get with that. We're a government agency, and although these costly tools are very efficient and useful, it's hard for me to convince the organization about that, especially since we're not allowed to use public cloud solutions, so we have an on-prem solution, which makes us a demanding customer.We use BMC Helix with the AIOps solution, and while all of these are public domain knowledge because we have to be open with how we procure and purchase our services, I am not the one who would purchase such a system. I would be the customer to it and someone else would host it, while I work more with observability, such as the Grafana stack and the cloud-native solutions.We're working with Grafana more actively now for maybe a couple of years, and we are looking at Tempo and the tracing solutions to see if it will scale. We have metrics back-ends and everything, and we're basically late-stage discovery, early-stage implementation at large scale, with 1,400 people in our tech organization and a 14,000 people organization, where the technology side is just 10%.We get alerts from the alerting tools, and we act on them. I'm looking now at logs, Grafana, trace profiles, and while we're not yet into AI/ML and root-cause analysis, we do focus on alerting and, to some extent, plugins and app observability, mainly utilizing the basics for now.

We use Tempo for tracing and, of course, alerting and monitoring metrics. We've tested some features but we're only using a few of them actually, so I can't provide the full range of what different tools Grafana offers as an open-source project, but it's definitely useful for monitoring, alerting, logs, and analysis.Grafana integrates with some of the tools we've chosen beforehand, and while I'm not the right person to elaborate on this since I'm more focused on managing big teams, the teams working with it seem happy. We used to have performance issues, which could be due to running it in an OpenShift environment, but functionality-wise, it seems to be useful, albeit not offering the same power tools as APM such as AppDynamics.

The whole AI capability would be useful for Grafana in the future, and while I don't think we're mature yet, I would want to see improvements, especially in the tracing part, where following different requests between different services could be more powerful.

Depending on how you define use, whether it's in production or just dabbling with it, I would say that using it actively with a subset of the team has been for maybe two years.

You have to scale horizontally to deal with issues.

We might have gotten help from technical support, but I'm not sure how much since I haven't seen an invoice for purchasing support, so it's probably community open-source style.

I would probably recommend Grafana for monitoring and analytics tasks, but since I haven't really pushed it to the limits from a non-functional perspective, I would hesitate if someone from a high-scale Telco environment asked for my recommendation.I rate Grafana a six out of ten.

I use Grafana mostly for monitoring purposes, such as tracking errors or alerts. When certain thresholds of warnings or errors are breached, Grafana sends me an alert because I am supplying it with data. Another use case I have is monitoring CPU usage and bandwidth.

I find Grafana beneficial due to its numerous plugins. Its alerting feature is effective because it allows me to set thresholds to send an email if a certain threshold is met. User management is good, and the administration features enable me to control user access.

The interface is not well-liked by my customers. Grafana cannot be easily embedded into certain applications and offers limited customization options for graphs. I think predictive capabilities in alerting could also be improved.

Scalability is uncertain for me since I installed Grafana on only one server and did not scale it further.

The setup process was easy for me to follow. I just needed to adhere to a step-by-step guide which was quite straightforward.

I end up using my own customized open-source visualization tool instead of Grafana. Most of the time, I deal with technical aspects.

I rate the overall product seven 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.

I use Grafana to deploy OpenVideo and to write an article on Medium on how we can deploy some open source projects with CloudFormation.

I have installed Grafana to see custom metrics like the number of connected users, number of rooms, and CPU usage.

All the features are complicated. It's comparable to Terraform, and I prefer CloudWatch.

The features are complicated and not intuitive. It would be better if they made the technology easy to use without needing to read extensive documentation. The dashboard interface is too wide, and it's challenging to find buttons or features.

Grafana is stable and has great engineers.

I would rate the scalability at six out of ten. It meets some needs, however, it could be improved.

I prefer CloudWatch over Grafana due to its ease of use.

The initial setup is too complicated. Even at a junior level, I found it challenging to navigate without guidance.

I prefer CloudWatch with custom metrics.

Make the interface intuitive and user-friendly. Highlight features clearly on the interface so that users can easily find and access them.

I'd rate the solution four out of ten.

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