Prometheus-AI Platform Reviews

I use Prometheus for monitoring purposes in IT infrastructure. It is particularly useful for environments using Kubernetes, as it monitors ports, containers, instances, and applications effectively.

Prometheus is a scalable and flexible tool that I can deploy on any cloud platform. It is free to use and provides valuable monitoring capabilities. It allows me to save money by avoiding costs associated with AWS native services like CloudWatch or Amazon Prometheus. The ability to deploy on any cloud platform or environment, including Kubernetes, is a major advantage.

Improvements could be made to the user interface. A GUI similar to Amazon CloudWatch would make setup and management easier, especially for new users like me who are not familiar with commands or scripting.

I have worked with Prometheus for almost three years.

The stability of Prometheus is high, depending on how well I manage it. Deploying it on multiple instances or using Kubernetes for automatic management has enhanced its stability.

Prometheus is scalable, with a rating of ten out of ten. Its scalability depends on how I manage and configure it.

Prometheus does not offer traditional technical support. Community forums and documentation are my main resources for support.

Neutral

The initial setup of Prometheus is complex and rated one out of five in ease of setup. It involves using syntax and commands, which can be challenging for a new user like me.

Using open-source Prometheus saves me money compared to AWS native services.

Prometheus is cost-effective for me as it is free. Using cloud-native alternatives like Amazon Prometheus would incur charges.

As a new user, I should be familiar with syntax and commands. Online resources like Google and ChatGPT can be helpful. I should consider using cloud-native tools for ease of management if not using Kubernetes. 

The overall rating for Prometheus is eight out of ten.

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.

Our company is a FinTech financial institution. We expose financial APIs for major FinTechs in the US. Basically, we are a bank and have a lot of applications running behind the scenes. APM is super crucial to our organization. We need to be able to interact, understand, and get a holistic or 360-degree view about everything going on in the organization. This view includes the infrastructure and the application sides. 

The solution helps developers get a holistic view of their application performance under the AKS environment. This is especially important in lower environments where developers need to interact with everything from performance to logging perspectives. In the very early stages, the solution gives developers a quite good overview about how they are developing products and how they can make them work more efficiently. 

The solution is on-premises at our own data centers. We have an additional, hybrid installation with Amazon that includes a private cloud. 

We have 150 engineers who use the solution for applications running under the Kubernetes environment. 

The sky is the limit because the solution is a very flexible open box that can be used vastly to do anything you need to monitor applications. There is nothing that you cannot do with it. Every day, our developers or SRE teams are adding additional features with the ability to think outside the box and configure whatever they want. 

The solution is the most common, major tool for FinTech or high-tech companies. Every technology company using Kubernetes is using the solution. 

The setup could be made easier for new users because it requires a bit of advance knowledge or experience. 

I currently manage our teams that use the solution. Previously, I had hands-on experience with the solution. 

The solution is stable with no reported issues. 

The solution is scalable. 

We have not needed technical support. 

The setup is not too complicated. If you have experience with the solution, then setup is an easy task. I rate setup a five out of ten. 

The basic configuration and deployment parts are easy. The more complicated part is creating the benchmark and alert behind it to make sure it gives us what we need from the application side. Customizing the solution for our needs takes more time. 

We implemented the solution in-house. We have a big devops team and a big SRE or platform engineers team. This is their bread and butter and they create Terraform infrastructures or services for a living.

If you use the solution, then you will definitely realize ROI. 

The solution is not expensive. In comparison to the pricing of New Relic or Datadog, the solution is basically free. 

We use several tools to accomplish our goals including the solution, New Relic APM, Datadog, Elasticsearch, and Amazon OpenSearch. 

New Relic APM and Datadog are closed box legacy tools. You cannot reconfigure them to do whatever you want. We use them because they have certain abilities but they cannot be customized for our specific needs.  

The solution is an open box Kubernetes tool so we have the ability to play with it. 

Make sure that you have dedicated manpower to configure and manage the solution. It requires handling, not necessarily on a daily basis, but it definitely requires someone who is focused and has expertise with the solution. 

Know in advance what you want to gain from the solution. Don't jump in to configuring or deploying before knowing what you expect from it. 

I like the solution very much. I think it is a major tool, especially in advanced environments. The open box provides a lot of flexibility and gives a very holistic view of the entire Kubernetes environment. 

Integrating with the Rancher management tool gives the solution even more abilities. There are several tools that we use behind the scenes to ease the process but the solution on its own is a very good tool. 

I rate the solution an eight out of ten. 

I use Prometheus to monitor my infrastructure and applications by setting up targets for scraping metrics, writing queries in PromQL to analyze the data, and configuring alerts to notify me of any issues. It is great because it can efficiently handle large amounts of metrics.

Prometheus has been incredibly helpful in improving my system's observability and alerting processes. It provides metrics for monitoring various aspects of my infrastructure and applications, helping me identify issues quickly.

The most valuable features of Prometheus for metrics collection and monitoring are its stability, robustness, and rich set of features. Being an open-source product, it offers reliability and flexibility, and if something is missing, it is easy to extend its functionality through integrations or custom solutions.

While Prometheus is an excellent product overall, one potential area for improvement would be fixing the occasional glitches and bugs.

I have been using Prometheus for almost seven years.

I'm generally happy with Prometheus's stability. Although there might be occasional glitches, we usually address them swiftly by reporting issues. Over the past year, we have seen improvements in memory usage.

When we need to scale Prometheus, we do that by using specific products. Considering its purpose, it is fairly scalable. About 1,000 users within our company use Prometheus for monitoring and alerts.

The initial setup was very simple and deployment only took us about 15 seconds. Maintaining Prometheus is just a regular part of our responsibilities, like managing any other system in our infrastructure. It doesn't demand extra effort or special attention beyond our usual routine tasks.

Integrating Prometheus with our existing systems and tools was easy. We seamlessly connected it with VCS, Grafana for visualization, and Slack for notifications, making management and monitoring straightforward.

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.

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.

It is for monitoring.  Although we have the main guys who test the site to do the scanning process most of the time, it's all automated. 

Overall, it's easy to set up monitoring and get a lot. It helps me to enable best practices. 

And it lets me proactively identify and resolve system issues. This, in terms of,  most of the time, really reduces downtime. Because when there are notifications on time when we engage it quickly on time, our downtime is highly reduced. So basically, Prometheus is for monitoring and alerting.

When it comes to deployment, if you have no experience with something like a CI/CD pipeline, it might be a challenge. But anyone can do it with a little studying beforehand.

I have experience with this product. Like, I have been using it for a year now. 

In a cloud environment, it's wise to be prepared for anything. I'd rate it a solid nine out of ten. There is no absolute ten for me, especially when it comes to availability; it is always A -1 approach.  

There are about three or four end users in our immediate ecosystem.

I would rate the scalability a nine out of ten. 

Scalability is good.

Prometheus's support team is quite good. If it wasn't good, I don't think my company would engage with it. 

Positive

The initial setup isn't overly complex. But, some prior knowledge and experience would always help.

Our deployment is cloud-based.

I highly recommend it to others.

Overall, I would rate the solution a nine out of ten. 

My company uses Prometheus because Zabbix is only useful for server machines.

In Prometheus, users can see the logs and containers while also getting to do HTTP monitoring under a single platform.

The most valuable feature of the solution stems from the fact that the HTTP monitoring capabilities offered by the solution help our company monitor SSL certificates while also helping us know if a site can be reached or not. The aforementioned details can be easily acquired with the help of the tool. On the normal desktop, you can create a dashboard from Grafana by using Loki's console.

The services offered by the product are good. Zabbix's site needs improvement.

In Prometheus, everything is query-based. Users can write up queries based on the metrics. In Prometheus, everything is fully for query-based applications. If you want to collect details of metrics, you should be able to write a query for it directly. I want the product to offer better queries for the metrics.

I have three years of experience with Prometheus. I am a user of the tool.

Right now, I don't see any bug-related issues in the product. In the performance part, everything seems to be good.

My company has opted for a centralized setup of the tool, so we have one dashboard set up for multiple applications. Our company's main goal of using the tool is to monitor our applications.

The product's initial setup phase is very easy.

The solution is deployed on an on-premises model.

It is an open-source tool.

Whether I would suggest the product to others or not is something that depends on the applications they use. If you use applications in the government sector or any other sector, then you need to know that the tool fully monitors the applications, and if there are any issues, the details of such problems can be directly acquired through the solution.

The tool is easy to learn and use.

I rate the tool a ten 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.