Skip to content

Namespace datadog blackhole target metrics & default off - #1926

Open
GeorgeHahn wants to merge 2 commits into
mainfrom
hahn/datadog-target-prefix
Open

Namespace datadog blackhole target metrics & default off#1926
GeorgeHahn wants to merge 2 commits into
mainfrom
hahn/datadog-target-prefix

Conversation

@GeorgeHahn

@GeorgeHahn GeorgeHahn commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Two breaking changes:

  • Apply a prefix to target metrics received by the datadog blackhole for consistency with other target metrics collectors.
  • Disable metrics recording by default.

@GeorgeHahn GeorgeHahn changed the title feat(datadog): namespace recorded series under target/ prefix Namespace datadog blackhole target metrics Aug 6, 2026
@GeorgeHahn GeorgeHahn changed the title Namespace datadog blackhole target metrics Namespace datadog blackhole target metrics & default off Aug 6, 2026
Datadog blackhole now prefixes recorded metric names with target/,
matching the prometheus and expvar target metrics collectors. The record
policy continues to match on the unprefixed series name.

Also changes the default record policy to Disabled, so no target metrics
are recorded unless explicitly configured.

Both are breaking changes for consumers relying on unprefixed metric
names or default-all recording behavior.
@GeorgeHahn
GeorgeHahn marked this pull request as ready for review August 6, 2026 16:37
@GeorgeHahn
GeorgeHahn requested a review from a team as a code owner August 6, 2026 16:37
@datadog-prod-us1-4

This comment has been minimized.

use crate::proto::datadog::intake::metrics::MetricPayload;

/// Namespace for incoming metrics; matches other target-originated metrics.
const TARGET_PREFIX: &str = "target/";

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this imply that we'll have a metric rename happening?

My concern is with the variety of dashboards/tools/scripts that already exist that use these.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes for experiments that use the datadog blackhole. Those experiments will also need adjustment to explicitly opt into target metric collection.

@preinlein preinlein left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no clean way to double-emit and do a "migration" with our users. We'll have to let this be a breaking change, make comms, and let our on-call know.

Comment thread CHANGELOG.md
## Unreleased

## Changed
- **Breaking Change**: Datadog blackhole now records received series under the

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, that answers my previous question.

Going to approve but we should let the team/users know when we do the release.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Absolutely yeah. I'll land the experiment changes along with teams' update PRs and keep the breaking notes in the public announcement.

@GeorgeHahn
GeorgeHahn force-pushed the hahn/datadog-target-prefix branch from d396c37 to 6ea30a5 Compare August 6, 2026 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants