Describe the enhancement:
Add support to Fleet Server for offering connection settings for arbitrary non-OpAMP, non-own-telemetry destinations to OpAMP clients. These are named endpoints (with associated headers and TLS material) that the managed agent needs to connect to for purposes other than OpAMP itself or the agent's self-observability — e.g., downstream backends, databases, or other external services specific to the agent.
This corresponds to the other_connections field of ConnectionSettingsOffers and is gated by the client's AcceptsOtherConnectionSettings capability. Note that destinations for the agent's own telemetry (traces/metrics/logs about the agent itself) are a separate concern covered by TelemetryConnectionSettings and the client's ReportsOwn{Metrics,Traces,Logs} capabilities, which are not in scope for this issue.
Capability advertisement vs. offering:
Per the OpAMP spec, Fleet Server MUST advertise OffersConnectionSettings in the capabilities field of the first ServerToAgent message unconditionally. However, Fleet Server may only actually populate other_connections for clients that have advertised AcceptsOtherConnectionSettings in their most recent AgentToServer message. Advertisement is unconditional; offering is gated on client capability. See the Connection Settings Management section of the spec.
Testing:
⚠️ This feature cannot currently be tested end-to-end with the upstream OTel Collector supervisor. Although the supervisor's README and specification both describe AcceptsOtherConnectionSettings as implemented (for populating exporter connection settings from the other_connections named map), inspection of the supervisor source confirms the capability is not actually wired up: there is no config key, no capability bit set in SupportedCapabilities(), and no code handling other_connections from incoming messages. This gap is tracked upstream in opentelemetry-collector-contrib#44294. Testing will require upstream implementation. See the OpAMP Supervisor README and the OTel Collector contrib releases page.
Describe a specific use case for the enhancement or feature:
Fleet centrally configures where a managed agent connects for non-OpAMP, non-self-telemetry purposes — for example, directing a managed collector's pipeline exporters to specific backend endpoints without per-agent manual configuration.
Describe the enhancement:
Add support to Fleet Server for offering connection settings for arbitrary non-OpAMP, non-own-telemetry destinations to OpAMP clients. These are named endpoints (with associated headers and TLS material) that the managed agent needs to connect to for purposes other than OpAMP itself or the agent's self-observability — e.g., downstream backends, databases, or other external services specific to the agent.
This corresponds to the
other_connectionsfield ofConnectionSettingsOffersand is gated by the client'sAcceptsOtherConnectionSettingscapability. Note that destinations for the agent's own telemetry (traces/metrics/logs about the agent itself) are a separate concern covered byTelemetryConnectionSettingsand the client'sReportsOwn{Metrics,Traces,Logs}capabilities, which are not in scope for this issue.Capability advertisement vs. offering:
Per the OpAMP spec, Fleet Server MUST advertise
OffersConnectionSettingsin thecapabilitiesfield of the firstServerToAgentmessage unconditionally. However, Fleet Server may only actually populateother_connectionsfor clients that have advertisedAcceptsOtherConnectionSettingsin their most recentAgentToServermessage. Advertisement is unconditional; offering is gated on client capability. See the Connection Settings Management section of the spec.Testing:
AcceptsOtherConnectionSettingsas implemented (for populating exporter connection settings from theother_connectionsnamed map), inspection of the supervisor source confirms the capability is not actually wired up: there is no config key, no capability bit set inSupportedCapabilities(), and no code handlingother_connectionsfrom incoming messages. This gap is tracked upstream in opentelemetry-collector-contrib#44294. Testing will require upstream implementation. See the OpAMP Supervisor README and the OTel Collector contrib releases page.Describe a specific use case for the enhancement or feature:
Fleet centrally configures where a managed agent connects for non-OpAMP, non-self-telemetry purposes — for example, directing a managed collector's pipeline exporters to specific backend endpoints without per-agent manual configuration.