Channel Revision Published Runs on
3/stable 156 27 Feb 2024
Ubuntu 22.04
3/candidate 156 27 Feb 2024
Ubuntu 22.04
3/beta 156 27 Feb 2024
Ubuntu 22.04
3/edge 165 18 Apr 2024
Ubuntu 22.04
juju deploy kafka --channel 3/stable
Show information



Integrate custom alerting rules and dashboards

This guide shows you how to integrate an existing set of rules and/or dashboards to your Charmed Kafka and Charmed Zookeeper deployment to be consumed with the Canonical Observability Stack (COS). To do so, we will sync resources stored in a git repo to COS Lite.


Deploy the cos-lite bundle in a Kubernetes environment and integrate Charmed Kafka and Charmed ZooKeeper to the COS offers, as shown in the How to Enable Monitoring guide. This guide will refer to the models that charms are deployed into as:

  • <cos-model> for the model containing observabilities charms (and deployed on k8s)

  • <apps-model> for the model containing Charmed Kafka and Charmed ZooKeeper

  • <apps-model> for other optional charms (e.g. tls-certificates operators, grafana-agent, data-integrator, etc.).

Create a repository with a custom monitoring setup

Create an empty git repository, or in an existing one, save your alert rules and dashboard models under the <path_to_prom_rules>, <path_to_loki_rules> and <path_to_models> folders.

If you want a primer to rule writing, refer to the Prometheus documentation.
You may also find an example in the kafka-test-app repository.

Then, push your changes to the remote repository.

Deploy the COS configuration charm

Deploy the COS configuration charm in the <cos-model> model:

juju deploy cos-configuration-k8s cos-config \
  --config git_repo=<repository_url> \
  --config git_branch=<branch> \

The COS configuration charm keeps the monitoring stack in sync with our repository, by forwarding resources to Prometheus, Loki and Grafana. Refer to the documentation for all configuration options, including how to access a private repository.
Adding, updating or deleting an alert rule or a dashboard in the repository will be reflected in the monitoring stack.

You need to manually refresh cos-config’s local repository with the sync-now action if you do not want to wait for the next update-status event to pull the latest changes.

Forward the rules and dashboards

The path to the resource folders can be set after deployment:

juju config cos-config \
  --config prometheus_alert_rules_path=<path_to_prom_rules>
  --config loki_alert_rules_path=<path_to_loki_rules>
  --config grafana_dashboards_path=<path_to_models>

Then, integrate the charm to the COS operator to forward the rules and dashboards:

juju integrate cos-config prometheus
juju integrate cos-config grafana
juju integrate cos-config loki

After this is complete, the monitoring COS stack should be up, and ready to fire alerts based on our rules. As for the dashboards, they should be available in the Grafana interface.


In this guide, we enabled monitoring on a Kafka deployment and integrated alert rules and dashboards by syncing a git repository to the COS stack.