Canonical Observability Stack Lite

Canonical Observability | bundle

Channel	Revision	Published
latest/stable	11	21 Oct 2022
latest/candidate	10	21 Oct 2022
latest/beta	9	21 Oct 2022
latest/edge	18	20 Jun 2023
1.0/stable	16	21 Oct 2022
1.0/candidate	14	21 Oct 2022
1.0/beta	13	21 Oct 2022
1.0/edge	12	21 Oct 2022

Learn to deploy on juju >

Platform:

Relevant links

Homepage

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

Join the discussion

A COS Lite deployment is made up of numerous juju relation.

For clarity and readability, the bundle topology is depicted here using several separate diagrams. Each line indicates a separate juju relation.

Ingress view

The workloads that make up COS Lite are servers that need to be reachable from outside the model they are deployed in.

Grafana (“ingress-to-leader”) is the main UI, amalgamating telemetry from all datasources into dashboards.
Prometheus and Loki (both “ingress-per-unit”), ingest telemetry pushed from grafana agent from another model.
Alertmanager (“ingress per app”), has a UI for acknowledging or silencing alerts.

Datasource view

The workloads that make up COS Lite are datasources for each other:

Grafana queries loki, prometheus for telemetry and alertmanager for alerts.
Promtetheus and loki evaluate alert rules and post alerts to alertmanager.

We need to be made aware if the observability solution itself is functioning properly. Self-monitoring relations within COS Lite, together with cos-alerter, are meant to alert for outages of the observability stack itself.

Help improve this document in the forum (guidelines). Last updated 11 months ago.

Canonical Observability Stack Lite

Relevant links

Ingress view

Mermaid Diagram

Datasource view

Mermaid Diagram

Self-monitoring view

Mermaid Diagram