New - Enable Proxy Support for Declarative Configs#414
Merged
cleverchuk merged 1 commit intomainfrom Feb 12, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds HTTP proxy support to the declarative configuration system and migrates all signal exporters (traces, metrics, logs) from gRPC to HTTP/protobuf protocol with custom SolarWinds component providers.
Changes:
- Added new
ProxyParserto extract proxy configuration from declarative configs - Created custom OpenTelemetry
ComponentProviderimplementations for logs and traces exporters - Migrated all exporters (metrics, traces, logs) from gRPC to HTTP/protobuf protocol with proxy support
Reviewed changes
Copilot reviewed 10 out of 11 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
ProxyParser.java |
New parser delegating to ProxyConfigParser for proxy URL parsing from agent.proxy config key |
ProxyParserTest.java |
Tests for proxy parser covering config key, null handling, and parsing with/without credentials |
LogExporterComponentProvider.java |
New custom component provider for log exports using HTTP/protobuf with proxy support |
LogExporterComponentProviderTest.java |
Tests verifying component name and type for log exporter provider |
SpanExporterComponentProvider.java |
New custom component provider for trace exports using HTTP/protobuf with proxy support |
SpanExporterComponentProviderTest.java |
Tests verifying component name and type for span exporter provider |
MetricExporterComponentProvider.java |
Updated to use HTTP/protobuf exporter instead of gRPC and added proxy configuration |
MetricExporterComponentProviderTest.java |
Added testGetType() test for consistency with other component provider tests |
SharedConfigCustomizerProvider.java |
Added proxy parsing, replaced gRPC exporters with custom providers, added signal-specific endpoint paths |
SharedConfigCustomizerProviderTest.java |
Updated test assertions to reflect new endpoint paths and custom component providers |
...a/com/solarwinds/opentelemetry/extensions/config/provider/SpanExporterComponentProvider.java
Show resolved
Hide resolved
.../com/solarwinds/opentelemetry/extensions/config/provider/SharedConfigCustomizerProvider.java
Show resolved
Hide resolved
cheempz
approved these changes
Feb 12, 2026
Contributor
cheempz
left a comment
There was a problem hiding this comment.
LGTM, thanks @cleverchuk!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR adds HTTP proxy support to the declarative configuration system and migrates all signal exporters (traces, metrics, logs) from gRPC to HTTP/protobuf protocol with custom SolarWinds component providers.
Changes
New Components
ProxyParserA new parser that extracts proxy configuration from
DeclarativeConfigPropertiesusing theagent.proxykey. Delegates to the existingProxyConfigParserfor URL parsing and validation.LogExporterComponentProviderCustom OpenTelemetry
ComponentProviderfor log exports:swo/logExportervia@AutoServiceOtlpHttpLogRecordExporter(HTTP/protobuf)ConfigManagerif availableSpanExporterComponentProviderCustom OpenTelemetry
ComponentProviderfor trace exports:swo/spanExportervia@AutoServiceOtlpHttpSpanExporter(HTTP/protobuf)ConfigManagerif availableModified Components
MetricExporterComponentProviderOtlpGrpcMetricExportertoOtlpHttpMetricExporterConfigManagerSharedConfigCustomizerProviderKey changes:
parseProxyConfig()to extract and store proxy settings during configuration customizationgetSolarwindsConfig()method to centralize retrieval of SolarWinds-specific configuration with null validationOtlpGrpcExporterModelwith customSpanExporterComponentProviderusingSpanExporterPropertyModelOtlpGrpcExporterModelwith customLogExporterComponentProviderusingLogRecordExporterPropertyModel{endpoint}/v1/traces{endpoint}/v1/metrics{endpoint}/v1/logsgrpctohttp/protobufcreateModel()method (no longer needed after migration away fromOtlpGrpcExporterModel)File Relocations
ProxyConfigParser.java: Moved fromcustom/tolibs/shared/for shared accessTechnical Rationale
HTTP/protobuf over gRPC
The migration to HTTP/protobuf provides:
Custom Component Providers
Using
withAdditionalProperty()pattern with custom component providers allows:ConfigManagerCentralized Proxy Configuration
Proxy settings are parsed once during model customization and stored in
ConfigManager, making them available to all component providers during exporter creation.Tests Added
LogExporterComponentProviderTestSpanExporterComponentProviderTestProxyParserTestMetricExporterComponentProviderTesttestGetType()for consistencySharedConfigCustomizerProviderTest/v1/logs,/v1/metrics)Test services data