https://materializeinc.github.io/materialize-monitoring/reference/internal/queries/Recent content in Queries on materialize-monitoring DocumentationHugoen-ushttps://materializeinc.github.io/materialize-monitoring/reference/internal/queries/overview/Mon, 01 Jan 0001 00:00:00 +0000https://materializeinc.github.io/materialize-monitoring/reference/internal/queries/overview/<h1 id="queries-as-code">Queries as Code<a class="anchor" href="#queries-as-code">#</a></h1> <p>Monitoring queries are authored once as YAML under <code>packages/queries/</code>, validated against a project-owned JSONSchema, and rendered per backend query language. A query is written for PromQL first; the other engines are translations of the same definition, carried in the same entry.</p> <p>The audience for this section is <strong>repo contributors</strong> — the people adding a panel, an alert, or a metric to the registry. The audience for the <em>rendered</em> queries is the operator reading a dashboard, so the descriptions attached to each query are end-user voice; see <a href="https://materializeinc.github.io/materialize-monitoring/reference/internal/dashboard/style-guidelines/">Dashboard Style Guidelines</a> for that.</p>https://materializeinc.github.io/materialize-monitoring/reference/internal/queries/datadog/Mon, 01 Jan 0001 00:00:00 +0000https://materializeinc.github.io/materialize-monitoring/reference/internal/queries/datadog/<h1 id="datadog-translations">Datadog Translations<a class="anchor" href="#datadog-translations">#</a></h1> <p>Every query in <code>packages/queries/</code> carries a <code>datadogQuery</code> alongside its <code>promQL</code>. They render side by side as tabs on <a href="https://materializeinc.github.io/materialize-monitoring/reference/stable-metrics/common-queries/">Common Queries</a>; this page is the conventions behind them, for whoever is adding or correcting one.</p> <p>These are <strong>translations, not a tested dashboard set</strong> — there is no Datadog test environment in CI, so nothing here has been run against a real Datadog account. Treat them as a starting point you copy into a widget or monitor and correct, not as something that works unedited.</p>