Use OTLP/Protobuf Exporter for AMW Endpoint #1470
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates how OTLP metric exporters are handled in the
AKSLoaderagent, switching from the HTTP-based OTLP metrics exporter to the protobuf-based version. It also adds a new unit test to verify that the correct exporter is created when the environment variable for protocol is set tohttp/protobuf. Additionally, the dependencies inpackage.jsonare updated to reflect this change.Dependency and exporter updates:
@opentelemetry/exporter-metrics-otlp-httpdependency with@opentelemetry/exporter-metrics-otlp-protoinpackage.json, ensuring that the project uses the protobuf-based exporter for OTLP metrics.aksLoader.tsto useOTLPMetricExporterfrom the protobuf package instead of the HTTP package, aligning the code with the new dependency. [1] [2]Testing improvements:
aksLoader.tests.tsto verify that when theOTEL_EXPORTER_OTLP_METRICS_PROTOCOLenvironment variable is set tohttp/protobuf, theAKSLoadercorrectly creates an OTLP protobuf metrics exporter.