Release Compatibility#

This shows the compatibility of materialize-monitoring with various technologies.

materialize-terraform-self-managed#

The Terraform module ships inside the materialize-monitoring component rather than on a version stream of its own, so one number covers both: a module ref of materialize-monitoring/vX.Y.Z installs chart X.Y.Z. There is no mapping to maintain between the two.

Azure has no wrapper module yet and still uses the previous Prometheus + Grafana modules.

Materialize product#

Dashboards (v0.8.0+) generally require the mz_object_info metric introduced in v26.29.0, however they will gracefully degrade without it.

Scrapers (v0.1.1+) require app.kubernetes.io/name labels for environmentd introduced in v26.24.0.

Grafana#

Dashboards (v0.8.0+) require Grafana v13+ for the dashboard schema v2. Grafana v12 is generally known to work, but may run into issues.

Google Kubernetes Engine (GKE)#

GKE (v1.29+ known to work) is known to work generally with the dashboards if metric collection is enabled (on by default starting in v1.27). GKE does not expose all cAdvisor and kube-state-metrics metrics, so the GCP-optimized dashboards do not include some %-based metrics that would normally be available.

Google Cloud Monitoring Dashboards#

Importing Grafana dashboards into Google Cloud Monitoring is not yet fully supported.

The GCP optimized dashboards do have some improvements but there are still some known issues:

• $__range and $__rate_interval need to be replaced with constants
• Horizontal bar charts are not rendered
• Tabs and rows are not supported, so there is no layout
• Switch variables are not supported (e.g. “show system clusters”)
  • This breaks the downstream cluster selector variable