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.

Positive

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 manage log processing with Grafana because we found that it is much easier for us to manage it on our infrastructure on AWS. We can maintain all the things we do not need. DataDog told us we have to wait and that they need to provide features we need to develop, so it does not suit our needs.

We are still using DataDog, but for important assets that we need to analyze the logs, we send it to Grafana.

The challenges we face with DataDog compared to Grafana include the need to analyze very important brands, network trafficking, and maintaining many websites, most of which are very important domains that cost a lot of money, so we are getting attacked each day and we need to analyze all of the logs. Sometimes we have false positives and things similar to that, so we have to make sure that we are doing the correct decision of blocking or trying to mitigate attacks. Using the logs with Grafana it is much easier for us to analyze rather than DataDog. DataDog has their own language and they want you to plot things with their own vocabulary. We do not have time to memorize things. We especially wanted to use something that was open source at the beginning, and then other people started using it, took that product and modified it for extra cost, but it is a better solution for us.

We switched from DataDog to Grafana because we wanted to reduce the logs costs, as we are streaming approximately five million logs or even less.

We can find information with Grafana much more quickly compared to DataDog because it was open source and there was extensive documentation about it, enabling us to fetch data or information much more quickly using AI tools. With DataDog, they always wanted us to have a meeting or talk with us on a call. It was redundant. We just wanted to get to the solution without making a big deal out of it.

Grafana saves us hours compared to DataDog. It takes about two weeks to figure out what is going on with DataDog, but with Grafana, we just started to initialize the service, had a few issues, fixed them, and that was it. I did not have any major problems that forced me to halt everything in my work. It cost me hundreds of hours with DataDog because I needed to see all the documentation and all the special caveats they have there.

I would rate Grafana overall as an eight out of ten. It is pretty good, and I would recommend it. I would give it a ten if it were much simpler for users who just want to get a simple objective in Grafana and are not experienced with technical configuration. It would be better if users could simply state they want to see the amount of requests on a graph through an AI implementation. For example, when getting attacked, users should be able to easily filter all requests to a specific site or resource, or identify IPs that were recently attempting access.

I would describe Grafana's ease of use as a necessity to just get things fixed. We are working in a marketing company, and if something does not work great, or people are looking for the solution, I am looking to get a temporary solution until I can fix it properly, and then I can reach support if I cannot fix it for the long-term.

I have been using Grafana for quite a long time, but we have only recently started using all of its features.

I would rate Grafana's overall stability as much more stable because when it is not working, users are given a much broader oversight of what is not working, rather than talking to DataDog and asking them to check it out. When something in their dashboard does not work, because it is open source, I am able to find all the relative combinations that people are having, making it much easier for me to fix.

The size of our infrastructure affects using Grafana as it really depends on that. We are considered quite small or medium at least, so it is quite easy for us. In terms of our company, the infrastructure is using two availability zones in AWS, one is US East, so we are looking to expand. Currently, we have only two availability zones to deploy, so it is quite easy for us right now.

I do not use Grafana's support for technical issues because I have found solutions on Stack Overflow and ChatGPT helps me as well.

On a day-to-day basis with Grafana, I tend to refrain from using their support, not because of their level of professionalism.

Positive

We switched from DataDog to Grafana because we wanted to reduce the logs costs, as we are streaming approximately five million logs or even less.

I initially learned to use Grafana by working locally and seeing how it works and presenting a proof of concept. We started to make a small plan of how we could make the change, how to deploy the switch, making the changes and checking it in other environments that we have. We are working with Agile, so I have to work with development first and then we are staging it. It is a long process but eventually we made the switch quite quickly, it was just a simple day when we deployed it.

Three people manage Grafana in our organization: one is a sysadmin, another one is a DevOps full-time, and I am managing the entire operation.

The costs associated with using Grafana are somewhere in the ten thousands because we are able to control the logs in a more efficient way to reduce it. That is pretty much great for us.

My recommendation for future users of Grafana is that it is all great. I am hoping that all the companies, at least the open-source projects, do not go closed source because then users will have to find something else. That is what we love to do - we love to use open source projects and improve them for our usage, not something that follows an agenda of another company's product.

My recommendation to other users of Grafana is to not be afraid and always look online. I started using it a long time ago for different projects. Users need to learn about the basics before they can really understand what is going on. There are people who start the self-hosted web server and see all the metrics going to their server, but they do not really understand what is happening, they just see a small count of the graph. Users need to understand that configuration is necessary. I experienced this when I started and was clueless, thinking of going to DataDog. Then I realized I just did not understand it correctly - there is much more once you see a bigger horizon of things that you could do.

Overall rating: 8/10

My main use case is monitoring. We use a lot of different products for monitoring, but Grafana is specifically for monitoring Kubernetes. We use Grafana mainly for Prometheus.

The features I appreciate most are the dashboards and the integrations with multiple data sources. The feature that sets Grafana apart from its competitors is how easy it is to set up data sources. The integration helps our organization in centralizing and analyzing data from diverse sources.

Regarding joining between queries, merging between two queries that give the same information could be simple, and there are some ways to do that, but if there was something even easier, it would be great.

The deployment process was completed before I joined the organization. We have been using it for a couple of years, but it was deployed previously.

We never had any issues with Grafana at all.

Grafana's customer support is mainly for developers. We didn't need to reach out to them for troubleshooting or any issues.

Positive

We centralize all the metrics from Prometheus and also from Graphite and all other data sources. We have dashboards to integrate Grafana's real-time metrics with visualization capabilities. We're not using Grafana's role-based access control and multi-tenancy features.

Seeing the metrics helps in finding issues, such as memory leaks or spikes and some optimization. We use Grafana on a day-to-day basis to get a better look at our environments and the usage of our resources.

We don't use Grafana for alerting, just for visualization. For alerting, we have different tools. On a scale of 1-10, I would rate Grafana as 8.5.

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. 

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.