Preserve Kueue resource tags for other metrics

[gjulianm]

What does this PR do?

Retains the original resource tag on Kueue metrics emitted as other.

Motivation

Unmapped resources otherwise cannot be distinguished after sharing the other metric name.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[datadog-datadog-prod-us1]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 82.94%

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: a5746ca | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run

[datadog-datadog-prod-us1]

More details

The resource transformer preserves the original resource tag only for metrics normalized to other, while mapped resources such as GPU still omit that tag. Existing and adversarial executions covered unknown vendor resources and explicit other mappings without exposing a behavioral regression.

Was this helpful? React 👍 or 👎

_{📊 Validated against 4 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit a5746ca · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[mbertrone]

suggestion (non-blocking): this proves the tag is preserved, but not the collision it guards against. The fixture has exactly one unmapped resource (example.com/fpga; cpu/memory/nvidia.com/gpu are all in RESOURCE_NAME_MAP), so kueue.cluster_queue.resource_usage.other only ever carries a single series here. The bug being fixed is that two distinct unmapped resources previously collapsed onto the same .other name with identical tags and overwrote each other (gauge is last-write-wins), and that path never fires with one resource. Add a second unmapped resource to a resource metric in metrics.txt (e.g. example.com/tpu) and assert ...resource_usage.other yields two series with distinct resource: tags. That exercises the no-collision property directly instead of inferring it from the single-series case.

[mbertrone]

suggestion (non-blocking): this closes the collision for the implicit other bucket, but the same class of bug survives for custom mappings. The guard keys off resource_name == 'other', so any resource_name_map that collapses two distinct resources onto one name still strips their resource: tags and emits colliding series. {'a.com/x': 'accel', 'b.com/y': 'accel'} → both normalize to accel at check.py:104, both take the != 'other' branch, both lose the distinguishing tag, second overwrites first. Scoping this PR to other is defensible since duplicate custom names are an unusual config. Worth either preserving the tag whenever the resolved name is non-injective, or noting in the config docs that custom names must be unique.

[gjulianm]

For now we only have one resource type for non-other resources