Prometheus Reviews

The solution is used for monitoring the metrics of applications. The applications have multiple functions, and each function should be monitored. I contact the developer teams to add the solution to the applications. I also use Alertmanager. If, for a specific test, a required metric is below the expected rate, the alert manager will fire a notification to the users.

The solution is useful to collect huge metrics. We have multiple applications. Collecting metrics from all the environments in my data center using the solution is very simple. The dashboards are very useful.

The product must allow users to run multiple instances to get metrics. Thanos is a bit complicated to deploy. It would be better if the solution provided a tool similar to Thanos natively.

I have been using the solution for two to three years.

The product is stable, but sometimes, when we run heavy queries like line data for the previous 24 hours, the CPU and memory utilization are very high. So, we use the product for shorter queries, like line data for the previous 30 minutes or an hour.

The scalability must be improved. More than 20 people use the tool indirectly.

My colleagues use Grafana. Grafana is integrated into Prometheus in our organization.

The initial setup is very easy. It took us an hour to deploy the tool.

It is not difficult to maintain the solution because I run it on Kubernetes.

The tool is open-sourced.

Prometheus is a famous solution. It is a useful product for monitoring application metrics. It needs a developer team to monitor the application functions completely. There are different dashboards like SLO and SLI dashboards. It also has an alert manager tool. The tool is important for modern applications because modern applications employ microservices. The product helps monitor all the functions, but it lacks scalability. Overall, I rate the solution an eight out of ten.

In order to have a visuality from Grafana, we create the metrics using Prometheus. Prometheus pushes all these metrics to Grafana. After scraping all the metrics and plotting them on a graph using Grafana, then we used Prometheus as middleware for getting all the metrics from all our applications and infrastructure.

We use Prometheus with Grafana and without either of them, it would not fit our use case.

The most valuable features of Prometheus are the many functions available. The functions are helpful for understanding the behavior of applications and infrastructure.

A slight alteration to the user interface should be made to increase efficiency and streamline the process. Currently, we are utilizing Prometheus to gather and compile metrics and then utilizing Grafana to display them in the form of a graph. However, I believe that Prometheus has the capability to handle both of these tasks on its own, with perhaps the addition of a supplementary plugin. By doing so, the need for utilizing two separate applications will be eliminated.

I have been using Prometheus for a couple of years.

We have experienced some performance issues, but I cannot say for certain whether it is due to Prometheus or if it is a result of our infrastructure. During these instances, we have noticed that the mix of metrics can become disrupted for a period of time due to high levels of CPU utilization or other factors. As a result, we are unable to retrieve metrics during these instances. This has been a challenge that I have faced while using Prometheus. It is unclear whether there is a solution, such as a resource optimization, that could help to alleviate these issues. However, it is expected that the utilization of resources should improve as the number of metrics that we scrape increases.

I rate Prometheus an eight out of ten.

I rate the scalability of Prometheus a ten out of ten.

The initial setup should be relatively uncomplicated. I haven't personally dealt with the implementation aspect but based on my previous experiences, we utilized Prometheus and Grafana together in our Kubernetes cluster. Thus, we were able to deploy it with ease, all within one unified operation.

We did the implementation of the solution in-house.

We have received a return on investment using Prometheus.

The solution is open source.

Prometheus, similar to Grafana, is incredibly useful and effective, particularly when you become more familiar with its functions and capabilities. By developing a stronger understanding of the functions utilized by Prometheus, it becomes much easier to extract relevant metrics and create visually appealing graphs. Thus, it is recommended that users invest time in learning and mastering these functions for optimal results.

I rate Prometheus an eight out of ten.

For a project I am currently working on in my company, I use Grafana, but for the data source part, I use Prometheus.

I use Prometheus in a Kubernetes cluster. I use Prometheus for the processes attached to Amazon EKS.

The UI and GUI are areas of concern in the product. The UI part of the tool should be more friendly. More GUI should be added to the solution. The UI and GUI should look good.

I have been using Prometheus for a year. I am a customer of the tool.

Stability-wise, I rate the solution a ten out of ten.

I haven't faced any scalability issues in the product. Scalability-wise, I rate the solution a ten out of ten.

Around five to ten DevOps engineers use the product. Other employees in the company don't use the solution because it is a product that is used to monitor other clusters. The DevOps team uses the product to monitor clusters.

I use Prometheus and Grafana.

I used to use Amazon CloudWatch as an in-built proprietary monitoring and alerting tool in my company. Amazon CloudWatch's use had a certain cost attached to it, but Prometheus is an open-source tool.

The product's initial setup phase was easy.

The solution is deployed on the cloud.

The solution can be deployed in three to five minutes.

Prometheus is an open-source tool.

Speaking about how I have implemented the product for my company's infrastructure, I would say that I have a simple Prometheus in my cluster, which is Amazon EKS' cluster using a Helm Chart. Helm Chart is a package manager for Kubernetes-based applications. I have installed Prometheus and Grafana using Helm Chats, which is very easy to install.

In terms of the benefits of the tool attached to the performance monitoring part, I use Prometheus as a data source. Prometheus helps me to pull my Kubernetes cluster data. Basically, Prometheus helps me as it serves as a one-stop destination for my Kubernetes cluster data. I export data from Prometheus to Grafana, which helps me with the visualization part. In general, Prometheus helps me visualize my data and gives me a structure for my clusters.

I would say that I use Grafana for the alerting feature that helps maintain system reliability. I use Prometheus for my data sources and by adding it. From the data, I create email alerts. The first point of contact for me is Prometheus for Grafana's dashboard and for each and every alerting feature as well. I can say that Prometheus is very useful for me if I consider its alerting features.

I have only used Prometheus to monitor my Amazon EC2 servers and Amazon EKS clusters. My use cases indicate that I have been using Prometheus to monitor Amazon EC2 server and Amazon EKS clusters. I don't use the product extensively for anything else apart from the fact that I use it to monitor Amazon EC2 server and Amazon EKS clusters.

I recommend the product to those who plan to use it.

I would like to mention that if you use Prometheus and if you integrate it into other tools, then it will save a lot of costs as it is a free and open-source product with a strong community. Prometheus will be getting an updated version soon, which is very soon.

I rate the tool an eight out of ten.

In Prometheus, the graphs and everything are too complicated. With Prometheus, you need to sit down and study it properly. Though the product offers a pretty interface, if you don't know what you are doing, then the tool doesn't provide you with customized reports. The product sends its users email reports, which they need to look into.

The query language in Prometheus is an area of concern where improvements are required.

The ability to generate customized reports should be made available in the product.

I have been using Prometheus for three years.

Once the product is properly configured and installed, it works perfectly.

It is a scalable solution.

Around 600 people in my company use the product.

I have experience with Sophos. There are some problems with the GUI of Prometheus. The GUI of Sophos is simple and easy to use.

I would recommend others to choose Zabbix over Prometheus.

I rate Zabbix a nine out of ten.

The product's initial setup phase is not easy as one needs to know the Unix language.

Considering that there is a need to update and upgrade the Linux part, the solution can be deployed in an hour. It may take a day for someone who does not know the product's installation phase.

Prometheus is available as an open-source product.

Prometheus for monitoring our company's infrastructure and applications is useful, as it serves as a network monitoring tool that helps you understand the bandwidth capabilities while also ensuring that you get to know who is accessing what at what time of the day. The tool provides details on where the company's network bandwidth is used.

Speaking about how Prometheus has helped in our company's system observability and alerting processes, I think it's just an added tool in our environment because we don't use it as a primary solution. Primarily, my company is dependent on Sophos. The other solutions probably don't give you the results you want, but it all depends on how well you have done your policies. The aforementioned reason may prompt a user to use Prometheus.

Features of Prometheus for metrics collection and monitoring stem from the ability that the product provides to track bandwidth.

It is a task to deal with Prometheus' query language because it is not as clear as you would expect it to be, which poses a challenge.

The integration of Prometheus with Zabbix can be a nightmare, and it can be quite challenging. There are also chances that you may get errors when trying to integrate Prometheus with Zabbix. You have to wait for the next release of Prometheus and Zabbix to be able to install them together.

The product is easy to maintain.

The product works fine in terms of its abilities related to incident detection and resolution, but the product has to do something with the GUI part, which is not appealing enough as someone would not want to sit in front of it and look at graphs.

Those planning to use Prometheus should be aware of the syntax part in programming before using it.

I rate the overall tool a seven out of ten.

We use Prometheus for observability and analyzing data for business metrics and system metrics. It helps us with messaging services observability. It also helps a lot with the architecture and scalability of the services. The solution provides system observability regarding Kubernetes information, CPU usage, memory, and whether the system is scaling or not.

The resilience of the solution's metric collection is very nice. Although it's very strict about the number of unique metrics for each service, the metrics collection is very powerful.

There is a tool called Prometheus Exporter that doesn't work well. I don't know if Prometheus maintains it or if it's an open-source service. When we have Cron jobs from our services, Prometheus needs a live endpoint to collect the metrics.

Since Cron jobs have a time limit, I rely on Prometheus Exporter to collect metrics. When I send metrics for Prometheus Exporter, it doesn't work very well.

I have been using Prometheus for four to five years.

I’ve never had any stability issues with the solution.

I rate the solution’s stability ten out of ten.

Prometheus is a scalable solution.

I would recommend the solution to other users.

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

The most valuable features of Prometheus are its ability to collect metrics and its integration with Grafana.

The primary area where Prometheus could be improved is in terms of pricing, particularly when used with managed services like AWS. Many clients have found the pricing for managed services steep, prompting them to switch to the open-source version. This switch has led to the adoption of Prometheus with Amazon EKS. Still, it has also resulted in high data transfer costs due to the multitude of microservices and the associated cluster logs. As a result, clients are facing higher bills, primarily driven by increased data transfer rates and bandwidth usage.

We have been using Prometheus for two and a half years.

It is a stable product.

It is a scalable platform.

The initial setup is easy if you have good knowledge of Helm. It requires setting two to three commands. Without using Helm, you have to create custom file deployments. Overall, it is a simple process.

The alerting functionality provided by Prometheus has significantly improved our incident response time. It enables us to gather data from various instances or ports within our environment, such as ETS.

I advise others to gain essential knowledge of query optimization and Grafana. It is an expensive product if utilized with managed services. It would be beneficial to use the open-source version.

I rate it a nine out of ten.

Prometheus is an open-source monitoring system, but Amazon offers a managed service that takes care of all the setup and maintenance for us. 

We also use Grafana on top of Prometheus to create dashboards that visualize the metrics collected by Prometheus. This is a common setup that many companies use for monitoring their containerized workloads.

We go and see the metrics for any issues with our code. You get to know CPU consumption, memory consumption, all that. That's how we use it for monitoring purposes.

The good thing is it integrates well with the Grafana dashboard. It comes with a UI where you see everything as a graph. And that's similar to what New Relic also gave. So, it's in tandem with Grafana to experience the UI. We have a graph and a software dashboard. We see all the metrics.

There is always room for improvement. 

In future releases, I would like to see more automation. For example, Prometheus automatically picks up some of the metrics from the infrastructure or from the application using its own plugins that it deploys. 

I have been using this tool for around three years.

It is a stable solution.

From a scalability point of view, it's pretty scalable because we are using it for multiple applications and for multiple applications. 

We are on a Kubernetes cluster. We are on a multiple-names basis. So it's pretty scalable. It depends on how you use it. I did a POC long back, so for Amazon, that's pretty much scalable. That's why people use managed services because Amazon or any cloud vendor is responsible for scaling up and scaling down as we are using it. So the management is scalable, for sure.

We have around 200 end-users using this solution in my team.

Prometheus installation is pretty easy. We are using the managed one from Amazon. So that's easy. You don't have to install anything. It comes as a service, like a software service from AWS. But even then, installing that, I've done it long back. It's not complex; it's pretty easy.

The deployment doesn't take more than half an hour. However, for any unmanaged solution, you have to maintain it. For example, there will be updates to the solution on your end. But if you're using the managed ones from Amazon, you don't have to worry about those updates. Maintenance: that mechanism will take care of it. You just have to use it and consume it. 

Prometheus is open source, so you can install it on your own or use a managed service like Amazon Managed Prometheus. We chose to use a managed service because it's easier to manage and scale.

We have the open-source version, so we don't pay for it.

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

I am responsible for looking after the security part of my company, for which I received Prometheus from the operational and IT teams. I am not a direct user of the solution, and I am responsible for the decisions regarding the security part.

The solution fixes system health issues while offering features like operational monitoring of our company's current infrastructure and business applications.

I do not have an opinion on the most valuable features of the solution since, in our company, we are not concerned with comparing Prometheus, Grafana, and Wazuh. My company wants to see how the internal tools and processes we have in place could be augmented or expanded to cover security monitoring before deciding to move to an outsourced solution from a managed service provider.

The solution has shortcomings regarding security monitoring-oriented features to support custom use cases, like out-of-the-box test scenarios and threat-related use cases of its users. The aforementioned area can be improved in future releases of Prometheus.

I have been using Prometheus for three years.

It is a stable solution.

The users of the solution in my company are between the range of 50 to 100.

I have experience with Zabbix and Grafana, mainly for operational purposes like monitoring. Now, my company wants to focus on security monitoring, for which we need something more robust, like Wazuh.

Based on the feedback I have received from my colleagues in our company's IT department, the setup phase of the solution is relatively easy. Rather than focusing on the maintenance of the solution, my company focuses on the flexibility of the new features and the customization capabilities introduced.

The solution is deployed on the cloud.

My company doesn't need to pay for the licensing cost of the solution.

My company is in the process of deciding whether or not to proceed with an in-house SIEM and SOC structure source services completely to a managed service provider. In my company's evaluation process, we have assessed tools like Wazuh considering the scenarios, like our in-house resources and capabilities.

I would say Prometheus needs a very low maintenance effort from a maintenance perspective.

I recommend the product to those planning to use it.

Based on the fact that my company has been using the solution for the last couple of years, I rate the overall solution a seven out of ten.