• 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
      • Coordinated workers
      • Peripheral charms
        • Blackbox Exporter
    • 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
      • Terraform module versioning
  • How-to guides
    • Deploy and manage
      • Install
      • Configure strict reproducibility
      • Configure the Juju model
      • Configure the Grafana database
      • Configure TLS encryption
      • Configure ingress
      • Cross-track upgrade instructions
    • Migrate
      • Migrate from LMA to COS Lite
      • Migrate Grafana PostgreSQL data before refresh
      • Migrate from Grafana Agent to OpenTelemetry Collector
    • Integrate
      • Integrate COS Lite with uncharmed applications
      • Expose a metrics endpoint
      • Configure scrape jobs
      • Monitor SSL certificates with blackbox exporter
      • Instrument machine charms
      • Use the Loki HTTP API
      • Use Catalogue
      • Send telemetry to external backends
      • Tier OpenTelemetry Collector with different pipelines per data stream
      • Correlate node-exporter metrics with multiple co-located VM charms
      • Add tracing to COS Lite
      • Manually enable a Tempo HA tracing receiver
      • Add alert rules
      • Integrate Alertmanager with external receivers
      • Set up SLOs with Sloth
      • Sync alert rules from a git repo
      • 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
      • 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
      • Alertmanager
        • SLIs
      • Grafana
        • SLIs
      • Loki
        • SLIs
      • Mimir
        • SLIs
      • Prometheus
        • SLIs
      • Tempo
        • SLIs
    • Topology
    • Networking
    • Lifecycle
    • Glossary
    • Coordinated workers roles & meta-roles
  • Release notes
Back to top
Contribute to this page

Migrate¶

Transition from older observability stacks to COS Lite or the full COS.

Stack migration¶

Replace an older LMA deployment with the COS Lite stack.

  • Migrate from LMA to COS Lite

Agent migration¶

Switch the telemetry agent layer to OpenTelemetry Collector for broader protocol support.

  • Migrate Grafana PostgreSQL data before refresh
  • Migrate from Grafana Agent to OpenTelemetry Collector
Copyright © 2026
Last updated on Jun 04, 2026
Manage your tracker settings
Contents
  • Migrate
    • Stack migration
    • Agent migration