Dash0 updates from November 2025

Starting with release 0.87.0, the Dash0 operator supports widely used Prometheus CRDs like ServiceMonitor, PodMonitor and ScrapeConfig.

The new feature can be enabled by deploying the operator with prometheusCrdSupportEnabled=true and having at least one namespace with a Dash0Monitoring resource with prometheusScraping enabled.

From that point on, the Dash0 collectors will scrape the metrics endpoints defined in the Prometheus CRDs and the new metrics will be available in Dash0.

For more information, refer to the operator's documentation.

Every dataset now supports three roles: Viewer, Editor, and Maintainer. Viewers can explore all data and build non-intrusive assets like dashboards and views. Editors extend that by creating new check rules and synthetic checks. Maintainers hold the keys to telemetry-impacting settings - from spam filters to semantic convention versioning.

The result is flexibility with clarity. You can give broad access to non-critical datasets without worrying about accidental changes in production. And because roles are transparent, it’s always clear who has which level of control.

This is a major step toward balancing collaboration with protection, ensuring that Dash0 grows safely alongside your organization.

Read more

Starting with release 0.86.0 of the Dash0 operator, it now has full support for Google GKE Autopilot. Dash0 is now a GKE Autopilot partner, and the Dash0 operator can run as a privileged workload in Autopilot clusters.

Enable the Dash0 operator's autopilot mode by deploying the operator into your GKE Autopilot cluster with operator.gke.autopilot.enabled=true, and benefit from out-of-the-box telemetry collection that just works.

For more information, refer to the operator's documentation.