chore(otel): fix telemetry collection for otel metrics

[mabdinur]

What does this PR do?

Ensures configurations used in OpenTelemetry Metrics SDK are reported to the instrumentation telemetry platform. Updates configuration fallback logic to properly detect when metrics-specific configs use default values and fall back to general OTLP exporter configs per OpenTelemetry spec.

Motivation:

Emit diagnostic data about the state of the OpenTelemetry Components.

Change log entry

None.

Additional Notes:

How to test the change?

Regression was caught by system tests. This update to system tests will be merged after this PR: DataDog/system-tests#5811

[github-actions]

Thank you for updating Change log entry section 👏

^{Visited at: 2025-12-17 19:59:20 UTC}

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-12-18 19:16:29

Comparing candidate commit 0db7126 in PR branch munir/track-telemetry-otel-metric with baseline commit 2cb8be7 in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 44 metrics, 2 unstable metrics.

[datadog-official]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
• Patch Coverage: 69.57%
• Overall Coverage: 95.25% (-0.02%)

View detailed report

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0db7126 | Docs | Datadog PR Page | Was this helpful? Give us feedback!}

[y9v]

This PR fixes a bug, but there is not a single test here, which verifies that the bug is fixed now. Would it be possible to add tests?

I don't want to block the PR since I am planning to take some days off

[mabdinur]

This PR fixes a bug, but there is not a single test here, which verifies that the bug is fixed now. Would it be possible to add tests?

I linked the the system tests for this change in the PR description. I can duplicate these tests in dd-trace-rb but I think that reduces the value of having shared tests. I prefer not writing the same test cases multiple times but I can make this change if it is required to merge this PR

[y9v]

This PR fixes a bug, but there is not a single test here, which verifies that the bug is fixed now. Would it be possible to add tests?

I linked the the system tests for this change in the PR description. I can duplicate these tests in dd-trace-rb but I think that reduces the value of having shared tests. I prefer not writing the same test cases multiple times but I can make this change if it is required to merge this PR

Sorry, I missed the link to system-tests PR. It's up to you, but I would suggest to add at least one test here - simply because it makes it easier to spot a mistake early on in the future. If I am working on the library code, I run the tests we have, but not necessarily system tests (which are more like a contract).

[mabdinur]

This PR fixes a bug, but there is not a single test here, which verifies that the bug is fixed now. Would it be possible to add tests?

I linked the the system tests for this change in the PR description. I can duplicate these tests in dd-trace-rb but I think that reduces the value of having shared tests. I prefer not writing the same test cases multiple times but I can make this change if it is required to merge this PR

Sorry, I missed the link to system-tests PR. It's up to you, but I would suggest to add at least one test here - simply because it makes it easier to spot a mistake early on in the future. If I am working on the library code, I run the tests we have, but not necessarily system tests (which are more like a contract).

Yup, I can do that. This change only impacts instrumentation telemetry. I'll add a test cases that captures all supported configs and the success metrics

[p-datadog]

@mabdinur Can you please adjust the changelog section of the PR to be compliant with the requirements stated in the first comment above?

[github-actions]

Typing analysis

Note: Ignored files are excluded from the next sections.

Untyped methods

This PR introduces 1 partially typed method, and clears 1 partially typed method. It increases the percentage of typed methods from 55.78% to 55.8% (+0.02%).

Partially typed methods (+1-1)

❌ Introduced:

sig/datadog/opentelemetry/sdk/metrics_exporter.rbs:19
└── def export: (untyped metrics, ?timeout: ::Float?) -> Integer

✅ Cleared:

sig/datadog/opentelemetry/sdk/metrics_exporter.rbs:15
└── def export: (untyped metrics, ?timeout: ::Float?) -> Integer

If you believe a method or an attribute is rightfully untyped or partially typed, you can add # untyped:accept to the end of the line to remove it from the stats.