Make SQL Server database_metrics.instance_metrics.enabled gate collection - #24953
Merged
Conversation
Contributor
|
✅ All CI checks and tests passed. 🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: 872cd40 | Docs | View more details | Give us feedback! |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3588c7500a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
evalya-impact-summaryevalya impact analysis |
jasonmp85
force-pushed
the
jmp/sqlserver-3b-inert-instance-metrics
branch
2 times, most recently
from
August 24, 2026 18:36
4df358c to
9f66892
Compare
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jasonmp85
force-pushed
the
jmp/sqlserver-3b-inert-instance-metrics
branch
from
August 25, 2026 15:46
9f66892 to
db824b6
Compare
ethanperez
reviewed
Aug 25, 2026
azhou-datadog
previously approved these changes
Aug 25, 2026
temporal-github-worker-1
Bot
dismissed
azhou-datadog’s stale review
August 25, 2026 19:06
Review from azhou-datadog is dismissed. Related teams and files:
- database-monitoring-agent
- sqlserver/assets/configuration/spec.yaml
- sqlserver/datadog_checks/sqlserver/config_models/deprecations.py
- sqlserver/datadog_checks/sqlserver/data/conf.yaml.example
- sqlserver/tests/test_unit.py
Contributor
Validation ReportAll 21 validations passed. Show details
|
azhou-datadog
approved these changes
Aug 25, 2026
jasonmp85
enabled auto-merge
August 25, 2026 19:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Makes
database_metrics.instance_metrics.enabledactually gate instance metric collection, and marks the legacyinclude_instance_metricsoption as deprecated in favor of it.Measured effect
Three configurations against the same bench instance, expected fan-out 1,400 samples:
instance_metrics.enabled: trueinstance_metrics.enabled: falseinclude_instance_metrics: falseThe documented option goes from inert to working. On master, setting it to
falseproduced byte-identical output to setting it totrue; on this branch it emits zero samples and zero residual metric names. The legacy option continues to work, so nobody's existing configuration changes meaning.Motivation
The documented switch is currently inert. A user following the current documentation to turn instance metrics off gets no effect and no warning — the check keeps collecting and they keep paying for it, with nothing in the logs to suggest the option was ignored.
Review checklist (to be filled by reviewers)
qa/requiredif this PR needs QA validation, orqa/skip-qaif it does not. Exactly one of the two is required.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged