Prometheus-AI Platform Reviews

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.

I use the solution in my company for monitoring purposes and metrics.

The most valuable feature of the solution stems from its ability to provide metrics and to set up the blackbox exporter to monitor microservices to see whether they are up or down, how requests are coming in, and how much data it can handle.

Setting up the rules in Prometheus can be confusing, making it an area where improvements are required. My company has to rely on a blackbox exporter to get the metrics and make the solution easy for us.

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

It is a good and stable solution. Stability-wise, I rate the solution an eight and a half out of ten.

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

Once you get to know about the product, the setup phase becomes easy. It would be difficult to handle the product's setup phase for newbies.

Development, DevOps, and QA teams use the product in our company to monitor the application responses. Around 60 people in my company use the product.

I have experience with Grafana. I use Terraform as an IaC tool. I am an open-source contributor to Terraform.

There are no restrictions on whether the solution can be deployed on the cloud or an on-premises model. The deployment model depends on the requirements of the users. The product can be deployed on a cloud server or an on-premises server.

The solution can be deployed in thirty minutes.

My company uses the open-source version of the product.

I have implemented Prometheus for our company's infrastructure monitoring. Our company uses Kubernetes clusters on which we deploy the monitoring stack. The alert management in Grafana helps with the metrics part, which are visual representations. There are also Helm charts available to help with the setup.

The most beneficial features of the solution for our application stem from how we can customize the metrics and rules as per requirements. For microservices, our company can do searches at a CPU level and see how load gets distributed and how requests come into a particular service or application.

The product's alerting capabilities are helpful, but I need to set up the alert manager, and there is a config file where all the configurations need to be mentioned while also setting up the services or API endpoints.

That are a lot of ways to set up the product and use its integration capabilities with the other tools in the monitoring ecosystem of our company. In our company, we can run it as a service over our local servers, and we can also set it up as a monitoring tool using Kubernetes cluster.

The product was used as a monitoring tool in India for Yes Bank's application named Yes Genie.

I would tell the product's potential users that Prometheus is one of the best tools in the market for monitoring purposes.

I rate the overall tool a nine 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 the product for financial transaction monitoring.

Prometheus provides a flexible and adjustable querying and describing time, allowing for more responsive monitoring. The integration with long-term storage solutions like VictoriaMetrics is a valuable feature.

There is a need for a more comprehensive overview of exporters, especially when dealing with many of them. We currently deal with 20 exporters; sometimes, the labels don't match. Clarity and detailed information on relabeling would benefit users, including explanations on enabling different behaviors and understanding labeling methods.

There could be more granular UI and integration with Grafana. The metric inventory and dictionary could be simpler to understand with a flexible UI. Additionally, they should provide support drill-down selection for Grafana, similar to Azure Monitor.

We have been using Prometheus for more than three years.

It is a stable platform. However, sometimes we encounter stability issues with Kubernetes environment configuration.

The product is suitable for enterprise businesses.

I found a lot of good support articles and case studies. I have a positive opinion about the technical support services.

My previous company used InfluxDB. In comparison, Prometheus has a much better and more scalable monitoring system.

The complexity of the initial setup depends on the particular task. The deployment time varies from a few minutes to a few days per project requirement, including development, staging, and production. The time for data pipeline creation also varies as per different parameters. We have a team of more than 20 executives to monitor the process. Further, it is easy to maintain.

We evaluated Dynatrace or other APM solutions.

We managed services in Azure and AWS. Prometheus is a better product than other native monitoring systems. It provides an efficient bridge between multi-cloud infrastructure. I rate it a nine out of ten.

We use the solution to understand different metrics: RAM usage, CPU usage, application utilization, application performance, container metrics, port metrics, and network metrics.

Prometheus is an open-source product that helps mold and improve it per our requirements. It is a lightweight solution that gives you many different metrics you can use in your application. The product offers complete granularity of your infrastructure. 

It integrates seamlessly with other tools like Grafana, which offers dashboard visibility. Prometheus is an extensively used product. I haven't seen any organization that is not using it. 

Prometheus can be initially difficult for users since it has its query language, PromQL. The minimalistic interface is complicated to understand. They need to improve their interface so that users who don't know PromQL can also use it. You can only leverage the tool when you know PromQL. 

I have been using the product for a year. 

Prometheus is very stable. 

The solution is lightweight, and you can scale it however you want. It is used mainly by our DevOps team, which consists of 10-20 people. 

We haven't contacted the tech support team yet. The tool has rich documentation and a good Slack community. It is a mature tool, and there are a lot of people who have used it. You can get answers to any query or confusion from them. 

Prometheus' deployment is easy and can be completed in seconds. 

Prometheus has both licensed and open-source versions. Most people use the open-source version. The licensing costs are not expensive. 

I rate the product 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.