Skip to main content
12.x runs exclusively on Metoro’s new-generation telemetry tables, the same tables as 11.x. A 10.x hub stores its telemetry in the previous-generation tables, which 12.x neither writes nor reads.
Do not helm upgrade an existing 10.x hub to 12.0.0. The upgrade would stop writing the tables your existing telemetry lives in and make that data invisible to queries. Unlike 11.0.0, the 12.0.0 chart no longer has a fresh-install acknowledgement value that blocks this, so the upgrade would render and apply without an error.

What to do instead

  • New installations: install 12.0.0 directly by following the installation guide.
  • Existing 10.x hubs: stay on the 10.x release line and contact Metoro support. Metoro support will confirm a migration plan that backfills existing telemetry into the new-generation tables before your hub moves to the 12.x line.
Most 10.x values carry over to 12.x unchanged. 12.x drops the 11.x-only newTelemetryTablesAcknowledged and ingester.tablesV3* values, and adds the optional values described in Upgrading from 11.x.

Why this is a hard break

The new-generation tables change the physical storage layout: attributes move from map columns to typed JSON columns, and tables are partitioned by retention cohort. Queries against one generation cannot read the other’s data, so a hub must either keep serving from the old tables (10.x) or have its history migrated before serving from the new ones (11.x and later). Metoro chose an explicit migration step over a silent in-place flip so that no installation loses sight of its existing telemetry.