Skip to main content
Welcome to the docs for the latest version of Metoro’s self-managed offering. 12.0.0 brings self-managed installations up to date with Metoro Cloud. It runs on the same new-generation telemetry storage engine as 11.x (JSON-native attributes, retention-cohort partitioning) and adds:
  • Kubernetes-native ingestion rules: drop logs and traces at ingest with the new MetoroClusterIngestionRule CRD, and opt individual pods out of telemetry with pod annotations.
  • Near-instant CRD sync: changes to Metoro CRDs (alerts, dashboards, webhooks, RBAC and ingestion rules) and to ConfigMap-backed alerts and dashboards are picked up in seconds instead of on the periodic full sync.
  • Webhook secrets from Kubernetes Secrets: MetoroWebhook resources can take header and body values from secretKeyRefs, mirrored by the exporter and stored encrypted in the hub. See Webhooks and the secret store setup.
  • Alert and dashboard tags: tag alerts and dashboards (including through spec.tags on the CRDs), filter by tag, and group dashboards into tag-based tabs.
  • Dashboard and alert improvements: a dashboard-wide chart interval selector, optional threshold units on multi-metric alerts, and alert lifecycle and destination delivery logs.
  • Traces: the linkedTraceId filter finds spans by a propagated W3C trace id, and trace filters can be scoped to specific environments.
  • Guardian: Guardian can draft GitHub pull requests from chat, stale Guardian issues are closed automatically, and the Guardian code sandbox supports a scoped AppArmor profile for Ubuntu 24.04+ nodes (see Metoro AI).
  • Performance: permission-filtered listings (dashboards, alerts, folder trees) are up to 100x faster on large installations, and query cache fills run in parallel.

Upgrades

  • From 11.x: 12.x is an in-place helm upgrade; install hub chart 12.0.2 (12.0.0 left bundled PostgreSQL short of connections for Temporal, and Guardian chat failed on hubs served over plain HTTP before 12.0.2). See Upgrading from 11.x.
  • From 10.x: no in-place upgrade. 10.x hubs store telemetry in the previous-generation tables, which 12.x neither writes nor reads. See Upgrading from 10.x.
New installations should follow the installation guide.