This document tracks people and use cases for the Prometheus Operator in production. By creating a list of production use cases we hope to build a community of advisors that we can reach out to with experience using various the Prometheus Operator applications, operation environments, and cluster sizes. The Prometheus Operator development team may reach out periodically to check-in on how the Prometheus Operator is working in the field and update this list.
Environments: AWS, Azure, Bare Metal
Uses kube-prometheus: Yes (with additional tight Giant Swarm integrations)
Details:
- One prometheus operator per management cluster and one prometheus instance per workload cluster
- Customers can also install kube-prometheus for their workload using our App Platform
- 760000 samples/s
- 35M active series
Environments: AWS
Uses kube-prometheus: Yes
Details:
- One prometheus operator in our platform cluster and one prometheus instance per workload cluster
- 17k samples/s
- 841k active series
Environments: AWS, Azure, Google Cloud, Bare Metal
Uses kube-prometheus: Yes (with additional tight OpenShift integrations)
This is a meta user; please feel free to document specific OpenShift users!
All OpenShift clusters use the Prometheus Operator to manage the cluster monitoring stack as well as user workload monitoring. This means the Prometheus Operator's users include all OpenShift customers.
Environment: Google Cloud
Uses kube-prometheus: Yes
Details:
- HA Pair of Prometheus
- 4000 samples/s
- 100k active series
Environment: AWS
Uses kube-prometheus: Yes
Details (optional):
- HA Pairs of Prometheus
- 25000 samples/s
- 1.2M active series
Environments: Bare Metal
Uses kube-prometheus: Yes
Details (optional):
- HA Pair of Prometheus
- 517000 samples/s
- 10.7M active series
Environments: AWS, Azure, Google Cloud, cloudscale.ch, Exoscale, Swisscom
Uses kube-prometheus: Yes
Details (optional):
- A huge fleet of OpenShift and Kubernetes clusters, each using Prometheus Operator
- All managed by Project Syn, leveraging Commodore Components like component-rancher-monitoring which re-uses Prometheus Operator
Environments: AWS, Azure, Google Cloud, Bare Metal, etc
Uses kube-prometheus: Yes | No
Details (optional):
- HA Pair of Prometheus
- 1000 samples/s (query:
rate(prometheus_tsdb_head_samples_appended_total[5m])
) - 10k active series (query:
prometheus_tsdb_head_series
)