What is the relationship between cmd/opampsupervisor and extension/opampextension

[shenlvcheng]

Component(s)

cmd/opampsupervisor

Describe the issue you're reporting

What is the relationship between cmd/opampsupervisor and extension/opampextension

From what I understand, these two components work in conjunction. However, there's a question that confuses me: the configuration in opampsupervisor includes the setting for the OpAMP server address, and the opampextension also has a configuration for the server address. Why do both configurations specify the server address?"

[github-actions]

Pinging code owners:

• cmd/opampsupervisor: @evan-bradley @atoulme @tigrannajaryan

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[zzadxz]

Hey @shenlvcheng!
This is because each component is designed to operate independently in different environments. Since they shouldn't rely on a shared configuration, they both need to know the server address individually. They both interact with the same server but they do it in different ways and for different purposes. Let's say the supervisor might not be configuring or managing server parameters but the extension might be using services provided by the server. Hope that answers your question!

[shenlvcheng]

Hey @zzadxz !
If we consider each component separately, your explanation is fine. However, it doesn't address my question. After reviewing the relevant specifications and documentation, it's clear that these two components are supposed to interact with each other. But here's the issue: both components are WebSocket clients. In the opampsupervisor specification, there's a mention of a server, but I can't find the configuration for it anywhere. Can you tell me how to configure the server in opampsupervisor?

[srikanthccv]

In the opampsupervisor specification, there's a mention of a server, but I can't find the configuration for it anywhere. Can you tell me how to configure the server in opampsupervisor?

The configurable settings for the OpAMP server are here https://github.com/open-telemetry/opamp-go/blob/fcfa0954c545e1b842a3d64adada28d0c032a518/server/server.go#L12-L36

[tigrannajaryan]

There are 2 ways to use OpAMP with the Collector.

1. You can use opampextension just on its own, without the opampsupervisor. In that case opampextension connects directly to the OpAMP server and needs to know the server's location.

2. You can also use opampextension together with opampsupervisor. In this case opampextension is a helper for opampsupervisor. opampextension connects to locally running opampsupervisor and opampsupervisor connects to the actual OpAMP server running somewhere else, that's why opampsupervisor needs to know the server's address. In this scenario the opampserver's server setting points to the supervisor, not to the final server. See the design here https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/cmd/opampsupervisor/specification#supervised-operation

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• cmd/opampsupervisor: @evan-bradley @atoulme @tigrannajaryan

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.