Wavefront

Teams using Wavefront needed collectors that connected cluster measurements with the hosted service’s queries, dashboards and alerts. This historical chart installed that telemetry collection path. Its own package and the documented successor chart repository are now archived, while the backend product has a separate vendor and support history. For an existing tenant, establish the currently supported collector before changing it, then preserve the metric names, tags and source identities that make the monitoring useful.

Current guidance

The historical stable/wavefront chart collected Kubernetes telemetry for the Wavefront service. Its metadata directs readers to wavefrontHQ/helm, but that repository is itself marked archived as of January 16, 2026. An old chart-to-chart relocation therefore is not sufficient evidence of a currently supported installation path.

Do not infer that the hosted backend disappeared merely because a chart repository was archived. Broadcom’s current knowledge-base article refers to DX OpenExplore and the former Wavefront name. Check the product and support agreement attached to the actual tenant, then obtain the presently supported collector and authentication guidance for that environment.

For an existing deployment, inventory collectors, proxies, endpoints, API tokens and metric naming before changing components. Confirm how tags and source identifiers feed dashboards and alerts; a replacement that accepts telemetry can still change query meaning or cost through cardinality. Test buffering and delivery during a brief network outage, and compare representative metrics and alert behavior before removing the old collector. These are migration review steps, not a verified successor recipe. Kubedex has established the two chart archive states but has not established support for a particular tenant, collector image or replacement package.