Prometheus-AI Platform Reviews

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

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

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.

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 Prometheus to gather business and service metrics so that we can export and visualize them through other tools like Grafana.

The solution helps us to scale our products and services, and it helps me by gathering those metrics. 

The DSL could be improved. 

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

The product is stable. 

The solution is scalable; our engineering team of 80 staff members uses it, and three staff are responsible for maintenance. 

The initial setup is straightforward.

We didn't evaluate other options. We went straight for Prometheus.

I would rate this solution eight out of ten.