Remove Explicit Creation of Metric Exporter in AKS Auto-Attach Scenario

[JacksonWeber]

Per the spec https://github.com/aep-health-and-standards/Telemetry-Collection-Spec/blob/main/ApplicationInsights/AKS_AutoAttach_Metrics.md#sending-otel-metrics-to-amw the OTEL_METRICS_EXPORTER env var should be populated when in AKS auto-attach scenarios.

The OTel code that controls creation of the metric exporter in the even that this env var is populated exists here: https://github.com/open-telemetry/opentelemetry-js/blob/dac72912b3a895c91ee95cfa39a22a916411ba4c/experimental/packages/opentelemetry-sdk-node/src/sdk.ts#L115

[Copilot]

Pull Request Overview

Removes manual setup of the OTLP metrics exporter in AKS auto-attach scenarios—relying instead on the OTEL_METRICS_EXPORTER environment handling—and drops the now-redundant test.

• Deleted explicit otlpMetricExporterConfig.enabled logic
• Removed the unit test for manual OTLP exporter creation

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
test/unitTests/agent/aksLoader.tests.ts	Dropped the test that asserted manual OTLP exporter addition
src/agent/aksLoader.ts	Removed explicit OTLP exporter configuration setup

Comments suppressed due to low confidence (2)

test/unitTests/agent/aksLoader.tests.ts:62

• After removing the old manual-exporter test, consider adding a new test to verify that the OTLP metric exporter is still initialized automatically by the SDK when the OTEL_METRICS_EXPORTER environment variable is set.

        assert.equal(loggerProvider["_sharedState"]["registeredLogRecordProcessors"][1]["_exporter"].constructor.name, "AzureMonitorLogExporter");

src/agent/aksLoader.ts:16

• [nitpick] Add a brief comment or docstring here referencing the spec URL to explain that explicit OTLP exporter config was removed because the SDK now handles OTEL_METRICS_EXPORTER automatically in AKS auto-attach scenarios.

        if (this._canLoad) {

[rads-1996]

LGTM

[hectorhdzg]

LGTM