WIP (2026Q2)
This is a new repository built around a first-class observability initiative for Materialize.
As of Materialize 27.0 (2026Q2), this repository is still under active development and not supported.

Pipelines as Code#

Instead of hand-maintained alloy config files, we author pipeline definitions as YAML, validate them against a project-owned JSONSchema, and render them to config.alloy via the mz-monitoring-build gen-pipelines subcommand. Sources live under packages/alloy-pipelines/; schemas under packages/mzmon-lib/schemas/alloy/; the Rust renderer and validator live under packages/mzmon-lib/.

The audience for this section is repo contributors — SRE, Field Engineering, CloudOps, Database Engineers — and AI agents reading the corresponding pipelines-as-code skill. The pipelines themselves target machines (alloy), not end users, so the conventions below favor contributor ergonomics: IDE autocomplete, schema-driven docs, escape hatches when reality outpaces the typed model.

In this section#

  • Authoring — schema model, strict-attributes policy, when to use raw: vs. extend the schema, how to add a new typed component or stage.
  • Logging — log pipeline conventions, label families, retention.
  • Metrics — metrics pipeline conventions.

The pipelines-as-code Claude skill at .claude/skills/pipelines-as-code/SKILL.md is the live state snapshot — current pipeline inventory, in-flight stubs, schema gaps — and links back into the pages above for stable reference.

Backward Testing Authoring Forward