Prometheus Reviews

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.

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.

Our primary use case for Prometheus is collecting metrics.

The feature I found most valuable is the number of integrations. It is the industry standard for metrics.

If you are not quite technical, it can be pretty hard to understand the way it works and how to query data in Prometheus.

In the next release, I'd like to see a more user-friendly interface where you can have more options on the graphical interface and more integrations that can help with the scalability.

I have been using Prometheus for about five years.

I would rate the stability of Prometheus a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution a five, on a scale from one to 10, with one being the worst and 10 being the best.

In case you want to make it more scalable, you can add other open-source projects like Thanos that can integrate with Prometheus.

I have not contacted technical support because there is none. The community is the technical support.

The initial setup of Prometheus was easy.

The deployment time mostly depends on the desired use case for Prometheus.
For example, monitoring a couple of servers would take about one hour to deploy. On the other hand, if you are planning to deploy several clusters or Kubernetes and other managed services, that adds complexity, and then deployment takes days or even weeks.

The reason we didn't go with, for example, AWS X-ray, Azure Monitor, or AppDynamics is that we didn't want to be tied to a specific provider.

I would advise others that before buying this solution they make a good design and think about their use case because the metrics can scale rapidly as can the amount of data you ingest. Without a good design, that might not be possible.

Overall, I would rate the Prometheus solution a nine, on a scale from one to 10, with one being the worst and 10 being the best. The reason for this is because it's open source, so there are no fees. There are no licenses to pay for and it has a great community. 

Prometheus became the standard of the industry for metrics as you can find a lot of documentation, forums, and many answers to any questions online. Also, Prometheus has constant updates to improve applications and to fix either the box or the issues. The ability to integrate with a wide range of other applications makes this solution even better.

We have Prometheus deployed in both the public cloud and on-premises.

There are about 100 users of Prometheus in our company.

We use it for monitoring our infrastructure metrics.

It is highly valuable as it serves as the foundation for our infrastructure monitoring tools.

The installation process proved to be exceptionally straightforward.

The interface is not particularly user-friendly and that could be improved.

We have been using it for two years.

I would rate its stability abilities eight out of ten.

I would rate its scalability capabilities eight out of ten.

The initial setup was straightforward, thanks to our utilization of the Kubernetes operator.

In terms of ROI, you can potentially save a few weeks, or perhaps two to three days, depending on the use case.

We evaluated Elastic and Kibana.

I recommend it because it's an incredibly useful tool, and its installation and usage are very straightforward. Overall, I would rate it eight out of ten.

I use Prometheus to monitor my application, system, and database.

The best thing about Prometheus is its integration. It's completely flexible and customizable, which is great. You have a lot of flexibility with Prometheus.

Prometheus can definitely improve its visualization. For example, the matrices represented in Prometheus do not have a very good visualization on their dashboard. The graphs displayed in Prometheus are not well-animated, so that is the area Prometheus can work on to make it more precise and better.

In the future release, logs are the thing I would add here. Currently, Prometheus does not have anything to log in to an application. So, I would definitely like to add that feature. Additionally, Prometheus has a lot of exporters, but they do not have any exporters for a database except MySQL. So, I would like to add more exporters for other data sources like databases.

I have been using this solution for three months now. I am using the latest version of Prometheus. The previous version I used was 2.43.0.

It is a stable product.

Prometheus is a scalable product.

Prometheus is an open source tech. You can go over to the online community for support, and your queries will be answered. 

It's an easy setup. I would rate it a three on a scale of one to ten, where one is very easy, and ten is very complex. The whole setup took around a week.

I would say that you can use Prometheus as it's definitely good to work with, and if you need any support from me, you can definitely contact me.

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

We use all of the metrics of Prometheus as an indicator if something goes wrong with our own applications as part of our on-call service. We represent the data on Grafana because Grafana is tightly integrated with Prometheus.

It has lots of APIs and libraries to integrate with any kind of language, including Python, Perl, PHP, Java, and Kotlin. You can easily plug and play integrating Prometheus with many operators. The official operators can be run on top of Kubernetes. It is a widely known and good solution for monitoring. 

The simplicity of the query language could be improved. The current query language is not easy to work with.

I have been using Prometheus for the past year.

Prometheus is definitely stable.

I do not handle scalability because it is managed by other teams.

I would recommend that you use it with simple applications, by running a Docker inside the Docker. It is a good and robust solution, and it is widely known by many companies across the software domain. I would rate Prometheus a nine out of ten.

We mainly use it for server monitoring and exposing the metrics format.

I like its lightweight configuration functions.

There are multiple solutions that we use alongside Prometheus while working. These include AM Solutions and Grafana. These are different systems that are logged into and have different technologies and spaces. However, it is difficult to navigate through them at times, so a single dashboard will be something that will be appreciated.

Moreover, there isn’t much clarity regarding the issues that happen at the server end. It is a push model and from the client’s point of view, it needs to look better and solve remote issues.

I have been using Prometheus for more than an year.

The stability is alright and I don’t see any issues. I will give it a seven out of ten as there are some remote issues.

We have a technical department and an internal platform team who contact them on our behalf.

Comparing AppDynamics with Prometheus, AppDynamics has a full suite of solutions, whereas Prometheus is mainly used for monitoring purposes.

We have the solution deployed by a Grafana vendor who made it a cloud version.

It is a good solution overall, so I can rate it a seven out of ten.  

We use the solution to collect monitoring data.

The product’s scalability is valuable.

The product must improve its documentation.

I have been using the solution for three years.

The tool is stable.

More than ten people were using the solution in my organization.

The solution is deployed both on AWS and Azure. The deployment is easy. There are multiple ways to do it.

The product is free.

I would recommend the solution to others. Overall, I rate the product a nine out of ten.