From 23578b9c747ab672b7139c68dcef9a709e5395a3 Mon Sep 17 00:00:00 2001 From: Lucas Laibly Date: Fri, 11 Sep 2026 14:14:32 -0400 Subject: [PATCH 1/2] add new initiatives section to dbm so that project info can be more easily shared --- hugo/config/_default/menus/main.en.yaml | 5 ++++ .../new_initiatives/_index.md | 14 +++++++++ .../new_initiatives/dbm_dev_material.md | 29 +++++++++++++++++++ 3 files changed, 48 insertions(+) create mode 100644 hugo/content/en/database_monitoring/new_initiatives/_index.md create mode 100644 hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md diff --git a/hugo/config/_default/menus/main.en.yaml b/hugo/config/_default/menus/main.en.yaml index 79cb84d3f2f..dd64df0a219 100644 --- a/hugo/config/_default/menus/main.en.yaml +++ b/hugo/config/_default/menus/main.en.yaml @@ -5315,6 +5315,11 @@ menu: parent: dbm identifier: dbm_guides weight: 20 + - name: New Initiatives + url: database_monitoring/new_initiatives/ + parent: dbm + identifier: dbm_new_initiatives + weight: 21 - name: Data Streams Monitoring url: data_streams/ pre: datastreams-monitoring diff --git a/hugo/content/en/database_monitoring/new_initiatives/_index.md b/hugo/content/en/database_monitoring/new_initiatives/_index.md new file mode 100644 index 00000000000..e3840c41c3f --- /dev/null +++ b/hugo/content/en/database_monitoring/new_initiatives/_index.md @@ -0,0 +1,14 @@ +--- +title: New Initiatives +private: true +disable_toc: true +cascade: + algolia: + rank: 20 + category: Guide + subcategory: New Initiatives +--- + +{{< whatsnext desc="DBM initiatives:" >}} + {{< nextlink href="database_monitoring/new_initiatives/dbm_dev_material" >}}DBM Dev Material{{< /nextlink >}} +{{< /whatsnext >}} diff --git a/hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md b/hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md new file mode 100644 index 00000000000..15d6fa78f1b --- /dev/null +++ b/hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md @@ -0,0 +1,29 @@ +--- +title: DBM Dev - PR Comments +private: true +disable_toc: false +--- + +## Overview + +DBM Dev: PR Comments is a GitHub bot that surfaces Database Monitoring production insights directly inside pull requests. When a PR introduces or modifies a query or database migration, the bot automatically posts a comment with risk assessments, production impact data, and optimization suggestions — before issues reach production. For existing queries, the bot correlates changes against live DBM telemetry and surfaces execution volume, average execution time, share of total database workload, and links back to DBM query signatures. For new queries, the bot assesses for anti-patterns and includes optimization suggestions regardless of production history. Comments are informational and do not block merges. + +## What is required + +To enable PR Comments, the following must be in place: + +1. **Active Database Monitoring** — the bot relies on DBM telemetry. Customers without DBM cannot receive signals. +2. **Datadog GitHub App installed** — the GitHub integration must be installed and connected to the relevant repositories. Request access to all repositories; negotiate for as many as possible if full access is not granted. +3. **Feature flag enabled** — contact the DBM team to have the feature flag applied to the customer account. + +Once the above are in place, the bot enters a shadow mode for 24–48 hours to validate signal quality before comments go live. No additional engineering setup is required after the integration is active. + +## Supported databases + +- PostgreSQL +- MySQL +- Microsoft SQL Server +- Oracle +- ClickHouse +- MongoDB +- Supabase From ed8910ddc45f11c36c0966b5980bbd7509084860 Mon Sep 17 00:00:00 2001 From: Lucas Laibly Date: Fri, 11 Sep 2026 16:55:31 -0400 Subject: [PATCH 2/2] Update Database Lab PR Comments content and overview Co-Authored-By: Claude Sonnet 4.6 --- .../new_initiatives/dbm_dev_material.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md b/hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md index 15d6fa78f1b..490e536cc9d 100644 --- a/hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md +++ b/hugo/content/en/database_monitoring/new_initiatives/dbm_dev_material.md @@ -1,12 +1,14 @@ --- -title: DBM Dev - PR Comments +title: Database Lab - PR Comments private: true disable_toc: false --- ## Overview -DBM Dev: PR Comments is a GitHub bot that surfaces Database Monitoring production insights directly inside pull requests. When a PR introduces or modifies a query or database migration, the bot automatically posts a comment with risk assessments, production impact data, and optimization suggestions — before issues reach production. For existing queries, the bot correlates changes against live DBM telemetry and surfaces execution volume, average execution time, share of total database workload, and links back to DBM query signatures. For new queries, the bot assesses for anti-patterns and includes optimization suggestions regardless of production history. Comments are informational and do not block merges. +Database Lab gives developers production database context at the moment they need it most. By surfacing real telemetry directly in the development workflow, Database Lab's helps engineers understand the downstream impact of their changes without requiring deep database expertise or manual investigation. + +PR Comments is the first milestone of Database Lab. It is a GitHub plugin that surfaces insights from Database Monitoring in relevant pull requests. When a PR adds or modifies a query or migration, the bot posts a comment with risk assessments, production impact, and optimization suggestions before issues reach production. For existing queries, it correlates changes against live DBM telemetry, surfacing execution volume, average execution time, share of total database workload, and links to DBM query signatures. Net new queries are a concept that will be supported soon as Database Lab's expands the capabilities of ephemeral databases. Comments are informational and never block merges. ## What is required @@ -15,8 +17,12 @@ To enable PR Comments, the following must be in place: 1. **Active Database Monitoring** — the bot relies on DBM telemetry. Customers without DBM cannot receive signals. 2. **Datadog GitHub App installed** — the GitHub integration must be installed and connected to the relevant repositories. Request access to all repositories; negotiate for as many as possible if full access is not granted. 3. **Feature flag enabled** — contact the DBM team to have the feature flag applied to the customer account. +## What's next -Once the above are in place, the bot enters a shadow mode for 24–48 hours to validate signal quality before comments go live. No additional engineering setup is required after the integration is active. +| Milestone | Description | +| --- | --- | +| **Rules and Customizations** | Customers can upload their own logic for the PR bot to apply to relevant PRs. Experience similar to SKILLs for frontier models, helps with enforcing team-specific best practices and guardrails automatically at review time. | +| **Workbench** | Access an ephemeral database to test changes, versions, migrations, and new queries before opening a PR, against databases that mirror production. | ## Supported databases