feat(sdk-metrics): add MeterConfigurator support

[Ayushgupta2408]

Fixes #6952

sdk-metrics currently has no way to configure per-meter behavior at
runtime — the MeterConfigurator concept described in the metrics SDK
spec
is not implemented. sdk-logs already implements the equivalent
LoggerConfigurator (#5991); this PR ports that pattern to sdk-metrics.

Short description of the changes

• Adds MeterConfig (packages/sdk-metrics/src/MeterConfig.ts): currently
  a single disabled?: boolean field, matching the spec's minimal
  MeterConfig definition.
• Adds MeterConfigurator type and createMeterConfigurator() helper
  (packages/sdk-metrics/src/MeterConfigurator.ts): builds a configurator
  from an ordered list of { name, config } conditions, matching meter
  names by exact string or *-wildcard pattern (first match wins).
• Wires the configurator through the existing meter-creation path:
  • MeterProviderSharedState now accepts an optional meterConfigurator
    and computes the MeterConfig for a scope in getMeterSharedState().
  • MeterSharedState's constructor now accepts and forwards that
    MeterConfig to Meter.
  • Meter stores the resolved config and, when disabled: true, returns
    the no-op instrument (createNoopMeter()) from every create*
    instrument method and no-ops addBatchObservableCallback, instead of
    registering real storage.
• MeterProviderOptions.meterConfigurator (already present on the
  interface) is now actually passed through to MeterProviderSharedState
  — previously it was accepted but silently ignored.
• Exports MeterConfig, MeterConfigurator, MeterConfiguratorCondition,
  and createMeterConfigurator from the package's public index.ts.
• Adds test/MeterConfigurator.test.ts covering:
  • exact-name match, wildcard match, first-match-wins with multiple
    conditions, and no-match → null
  • end-to-end: a MeterProvider configured with a disabled pattern
    produces no recorded data points for matching meters while unrelated
    meters record normally.

Type of change

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing
  functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• npx tsc -p tsconfig.json --noEmit — passes with no errors.
• npx nx run sdk-metrics:lint — passes.
• npx nx run sdk-metrics:test — new MeterConfigurator.test.ts suite
  passes alongside the existing sdk-metrics test suite.
• Manually verified that a MeterProvider without a meterConfigurator
  behaves identically to before (backward compatible — meterConfig
  defaults to undefined → DEFAULT_METER_CONFIG → disabled: false).

Checklist:

• Followed the style guidelines of this project
• Changelog entry added (CHANGELOG.md)
• Unit tests have been added
• Documentation has been updated (packages/sdk-metrics/README.md)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Ayushgupta2408 / name: Ayush kumar gupta (96b4dd8)

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-js.

Important reminders:

• Read our Contributing Guidelines.

• Sign the CLA if you haven't already.

• Follow the OpenTelemetry Generative AI policy: disclose any AI use in your contribution, and communicate (PR descriptions, review replies) in your own words rather than AI-generated text.

• Give reviewers at least a few days before pinging them for feedback.

• If you need help with general setup, development process, or contributor etiquette, ask in #opentelemetry-new-contributors.

• Add an entry describing your change to the appropriate changelog file: Stable packages, Experimental packages, API or Semantic Conventions. Add your entry under the ## Unreleased section.

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-08-22 08:02 UTC

Review the latest changes.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.