• Logo
    Observability
  • canonical.com/observability
  • More resources
    • Discourse
    • Matrix
    • GitHub
Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Observability documentation
Observability documentation
  • Tutorial
    • COS on Canonical K8s
    • COS Lite on Canonical K8s
    • COS Lite on MicroK8s
  • Explanation
    • Overview
      • What is observability?
      • Model-driven observability
      • What is COS?
    • Architecture & topology
      • Design goals
      • Juju topology
      • Juju topology labels
      • Model topology for COS Lite
      • Telemetry flow
    • Telemetry
      • Overview
      • Logging architecture
      • Telemetry labels
      • Telemetry collection
      • OpenTelemetry Protocol (OTLP) Juju topology labels
      • Telemetry correlation
    • Alerting & dashboards
      • Overview
      • Charmed alert rules
      • Generic alert rules
      • Dashboard upgrades and deduplication
    • Operations & data
      • Data integrity
  • How-to guides
    • Deploy and manage
      • Cross-track upgrade instructions
      • Configure TLS encryption
      • Configure ingress
    • Migrate
      • Migrate from LMA to COS Lite
      • Migrate from Grafana Agent to OpenTelemetry Collector
    • Integrate
      • Integrate COS Lite with uncharmed applications
      • Expose a metrics endpoint
      • Configure scrape jobs
      • Instrument machine charms
      • Tier OpenTelemetry Collector with different pipelines per data stream
      • Add tracing to COS Lite
      • Add alert rules
      • Testing with Minio
    • Configure and tune
      • Sync alert rules from Git
      • Disable built-in charm alert rules
      • Evaluate telemetry volume
      • Selectively drop telemetry using scrape config
      • Selectively drop telemetry using opentelemetry-collector
      • Redact sensitive data
      • How to customize storage options
      • How to reference a specific cloud to deploy COS
      • Configure the memory limit of the OpenTelemetry Collector
    • Validate and troubleshoot
      • Validate COS deployment
      • Troubleshooting
      • Diagnose false alerts
  • Reference
    • Sizing guide
    • Storage
    • Release policy
    • Security hardening guide
    • Cryptographic documentation
    • Integration matrix
    • COS components
    • Topology
    • Networking
    • Lifecycle
  • Release notes
Back to top
Contribute to this page

Juju topologyΒΆ

The Juju topology is a set of metadata associated with each piece of telemetry collected by the COS monitoring stack to uniquely identify which workload is the telemetry reporting about.

See also:

  • Juju Topology Labels

  • https://ubuntu.com/blog/model-driven-observability-part-2-juju-topology-metrics

© 2026 Canonical Ltd.
This page is licensed under CC-BY-SA-3.0
Last updated on Apr 21, 2026
Contents
  • Juju topology