What is your primary use case for Prometheus?

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.

We use Prometheus for observability and analyzing data for business metrics and system metrics. It helps us with messaging services observability. It also helps a lot with the architecture and scalability of the services. The solution provides system observability regarding Kubernetes information, CPU usage, memory, and whether the system is scaling or not.

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.

I use Prometheus to monitor Kubernetes clusters.

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.

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

We use Prometheus to monitor logs for microservices.

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.

We use the solution to collect monitoring data.

We use it for monitoring our infrastructure metrics.

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.

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.

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

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

We use the solution to record and store the metrics data.

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

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.

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

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.

We use Prometheus to gather business and service metrics so that we can export and visualize them through other tools like Grafana.

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.

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.

Prometheus can be deployed on-premise and in the cloud. Prometheus is an open-source network monitoring solution.