You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to manage multiple agents through opamp supervisor. However, I currently know that one supervisor can only run one agent. Supporting multiple agents is future work. So, I want to run one supervisor per agent and run multiple supervisors on one opamp server. I think then I can manage multiple agents. I would like to ask whether the opamp server can be connected to multiple supervisors.
opamp server : supervisor = 1 : N
supervisor : agent = 1 : 1
I modified the fixed instance ID 01942b7e-be22-7deb-8fe4-ad1dc54e0909 created by Supervisor to effective.yaml and persistent_state.yaml. and I ran additional Supervisor. the existing supervisor is connected to the opamp server.
{"level":"error","ts":1736489039.7722535,"logger":"supervisor.opamp-server","caller":"supervisor/logger.go:26","msg":"Cannot read a message from WebSocket: read tcp 127.0.0.1:38217->127.0.0.1:44208: read: connection reset by peer","stacktrace":"github.com/open-telemetry/opentelemetry-collector-contrib/cmd/opampsupervisor/supervisor.(*opAMPLogger).Errorf\n\t{masking}\ngithub.com/open-telemetry/opamp-go/server.(*server).handleWSConnection\n\t/home1/irteam/go/pkg/mod/github.com/open-telemetry/[email protected]/server/serverimpl.go:237"}
{"level":"info","ts":1736489039.7728827,"logger":"supervisor","caller":"supervisor/supervisor.go:220","msg":"Supervisor starting","id":"01942b7e-be22-7deb-8fe4-ad1dc54e1111"}
It seems that a websocket connection reset occurred with the opamp server, but when I connect to the client of the opamp server, the additional agent is registered. remote configure settings are also possible.
was the websocket connection established through retry after the Cannot read a message from WebSocket error occurred at first?
Another question, when I run supervisor, the settings in the effective.yaml file are always the same and fixed. Is it not possible to run it with the settings file I specified every time I run it for the first time?
Component(s)
cmd/opampsupervisor
Describe the issue you're reporting
I want to manage multiple agents through opamp supervisor. However, I currently know that one supervisor can only run one agent. Supporting multiple agents is future work. So, I want to run one supervisor per agent and run multiple supervisors on one opamp server. I think then I can manage multiple agents. I would like to ask whether the opamp server can be connected to multiple supervisors.
opamp server : supervisor = 1 : N
supervisor : agent = 1 : 1
I modified the fixed instance ID
01942b7e-be22-7deb-8fe4-ad1dc54e0909
created by Supervisor toeffective.yaml
andpersistent_state.yaml
. and I ran additional Supervisor. the existing supervisor is connected to the opamp server.It seems that a websocket connection reset occurred with the opamp server, but when I connect to the client of the opamp server, the additional agent is registered. remote configure settings are also possible.
was the websocket connection established through retry after the Cannot read a message from WebSocket error occurred at first?
Another question, when I run supervisor, the settings in the effective.yaml file are always the same and fixed. Is it not possible to run it with the settings file I specified every time I run it for the first time?
I think that effective.yaml file by combining the files in templates https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/5ee95c6f8b886f24070b2938c3418d1cbbbeadd0/cmd/opampsupervisor/supervisor/templates. If I change the file in templates, the agent's effective.yaml file created when running suervisor will change, right?
The text was updated successfully, but these errors were encountered: