Prometheus Group Reviews

Our primary use case for this solution is collecting, monitoring and analyzing logs in the cloud environment. We use this solution in an Azure environment and Cloud space.

The dashboard is very valuable because it provides the ability to collect and compare logs from various resources.

The setup process could be more straightforward and user-friendly.

We have been using this solution for six months.

The solution is stable.

The solution is scalable.

I rate this solution a seven out of ten. The solution is good but can be improved by creating a more straightforward setup process. I advise people considering this solution to spend some time reading the documentation to ensure they understand the type of features available.

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.

Prometheus can be deployed on-premise and in the cloud.

Prometheus is an open-source network monitoring solution.

Prometheus is very flexible. We use it for network monitoring and we can always add new servers, equipment, or whatever that we want to monitor with it.

I have been using Prometheus for approximately two years.

Prometheus is stable.

The scalability of Prometheus is very good.

We have the solution rolled out across multiple small businesses. We have hundreds of users collectively using the solutions.

I have not used the technical support from Prometheus.

Prometheus has a learning curve when setting it up. It definitely requires a little bit more hands-on than other solutions. It is an open source solution which means you do need to go through and read the literature that they have online for setting it up. The setup could be made easier.

I am the one who manages Prometheus and does the maintenance.

Prometheus is free. We use the solution for monitoring and it has worked well.

The price of Prometheus is good, it is affordable because it is open source and there is no cost to it. You put it on your own server and the costs incurred completely depend on how you set it up.

Prometheus can directly compete against other solutions, such as Zabbix or any other network monitoring solution.

My advice to others is to read all the documentation before usage.

I rate Prometheus an eight out of ten.

I rated it an eight because it is easy to use but the installation can be difficult.

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.

We use Prometheus to monitor logs for microservices.

The product has an easy-to-understand interface.

They could provide efficient logs in terms of clarity and ease of access similar to Datadog’s paid version. Additionally, they should release real-time updates and a graphical interface for logs.

I used it three months ago.

We have five Prometheus users in our organization.

The initial setup is easy.

The product is expensive compared to Datadog.

The platform’s alerting functionality improves incident response time. It offers an open-source toolkit for startups and new students. While its free version offers efficient capabilities, opting for paid features can unlock additional functionalities, particularly beneficial for larger enterprises with heightened security needs and extensive service requirements. The decision to invest in Prometheus is influenced by factors such as data volume, security considerations, and the need for seamless error detection and notification mechanisms.

I rate it an eight out of ten.

We use the solution as a centralized system to monitor multiple servers.

The solution's most valuable feature is exporters. It helps us extract data from multiple sources and store it in a single place. It is a user-friendly data voucher that gets insights and essential information about our servers. It works well for the end production environment.

The solution's documentation needs improvement. Presently, we need help to get metrics. Whenever CPU utilization is high, we should receive alerts on emails. But, we encounter difficulties here as the documentation is unclear.

I have been using the solution for the last two months.

It is a stable solution. We have deployed it for around 20+ servers and multiple dashboards.

It is a scalable solution. We have around 50 solution users in our organization.

We used CloudWatch before. Later, we switched to Prometheus for centralized dashboards and extensive data capacity.

The solution's initial setup process was relatively easy. We followed the documentation to understand the essential steps required for deployment.

We use the solution's open-source version.

I recommend Prometheus as it has multiple exposures. I rate the overall solution a seven out of ten.

My use cases include monitoring, scraping logs from the Kubernetes deployment, scraping Kubernetes logs, and pushing it over the final.

Prometheus is quite reliable and has a fast data storage system and database. I found metric collection and sterilization of the metrics a valuable feature.

Prometheus' UI color can improve. Using the Prometheus UI for configuration or analyzing queries is a horrible experience.

I have been using Prometheus for longer than three years.

Prometheus is quite a good solution in comparison with, for example, Vatix, which I evaluated for my checks collections named. Prometheus is a great solution for monitoring.

I would give this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

Our primary use case is for the integration with Grafana to receive metrics. We use it as a pulling and a pushing mode to send information from applications to servers.

The most valuable feature is that we can receive information in different formats.

I would like to see improvement in the analysis tools and customization features. I would like to see some visualization tools potentially even though it is not their main marketing point for customers.

I have been using Prometheus for the past three years.

There is stability with Prometheus.

There is scalability with Prometheus. We have around three hundred engineers using the solution daily.

Customer support is handled through documentation since it is open source.

The initial setup is somewhere between simple and complex.

This is an open-source solution.

I would rate Prometheus an eight out of ten.