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
When renaming a collector backend in the UI, the sidecar picks up the new configuration and starts another process of the same type.
In my case I renamed a filebeat backend and saw two running filebeat processes. The sidecar should have stopped the old one and started a new one with the new name.
We might want to consider using the backend ID instead of the backend name as an internal identifier in the sidecar.
Restarting the sidecar process helped. Only the backend with the new name got started after a restart.
Steps to reproduce the problem
Create a collector backend in the UI
Create a collector configuration and use the newly created backend
Assign the new collector configuration to a collector on a sidecar node
Wait until the sidecar has started the collector process
Rename the collector backend in the UI
Wait until the sidecar received the update configurations
* Remove defaultTemplate from collector summary
* Use collector_id for status reference
* Fix typo
* Move collector loading to StatusPage
* Use arrow function and prevent load time warning if collectors list is not ready yet
* Fix collector status on Sidecar administration page
FixesGraylog2/collector-sidecar#255
Problem description
When renaming a collector backend in the UI, the sidecar picks up the new configuration and starts another process of the same type.
In my case I renamed a filebeat backend and saw two running filebeat processes. The sidecar should have stopped the old one and started a new one with the new name.
We might want to consider using the backend ID instead of the backend name as an internal identifier in the sidecar.
Restarting the sidecar process helped. Only the backend with the new name got started after a restart.
Steps to reproduce the problem
Environment
The text was updated successfully, but these errors were encountered: