---
title: Charmhub | Deploy Prometheus using Charmhub - The Open Operator Collection
description: Deploy the latest version of Prometheus as a Kubernetes Operator on any
  cloud. Prometheus for Kubernetes clusters
url: https://charmhub.io/prometheus-k8s
---

# Prometheus

[Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

* [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

Platform:

3.11/stable tf-3.11.1-1-g7307c58

```
juju deploy prometheus-k8s --channel 3.11/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

[Read documentation](https://documentation.ubuntu.com/observability/latest/)

#### Relevant links

* [Homepage](https://charmhub.io/prometheus-k8s)

---

#### Contacts

* [Submit a bug](https://github.com/canonical/prometheus-k8s-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

#### Prometheus for Kubernetes clusters

Prometheus K8s is a Juju charm that deploys and manages Prometheus on Kubernetes, providing a
monitoring and alerting solution based on a time-series database. It is a core component of
COS Lite, the lightweight version of the Canonical Observability Stack (COS):
https://documentation.ubuntu.com/observability

Related charms automatically register their metrics endpoints and alert rules through Juju
relations, and collected metrics can be visualized in Grafana and used to trigger alerts via
Alertmanager.

Key features:

* Automatic metrics scraping and alert rule registration via Juju relations with any charm
  that supports the prometheus\_scrape interface.
* Prometheus remote write endpoint for receiving metrics from agents such as OpenTelemetry
  Collector.
* Seamless integration with Grafana, Alertmanager, and other charms in the COS ecosystem
  through Juju relations.
* Built-in Grafana dashboards and Prometheus alert rules for self-monitoring.
* Configurable metrics retention by time and storage size, with WAL compression support.
* Per-unit ingress support for cross-model access through reverse proxies such as Traefik.
* TLS support via the certificates relation.
* Distributed tracing support via integration with Tempo.
* Persistent storage for the time-series database across container restarts.
* Configurable Kubernetes resource limits for CPU and memory.