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
If a collector cannot be started by the sidecar because the config file is invalid, the UI correctly shows a "Failing" status. The problem is that the "Failing" status is still visible when the config file problem has been solved and the collector backend is started successfully.
Steps to reproduce the problem
Create a collector configuration and assign it to a sidecar
Wait until the collector has started
Introduce a syntax error in the collector config
Wait until the sidecar overview page shows a "Failing" status
Fix the syntax error in the collector config
Wait until the sidecar has successfully restarted the collector
Check the web sidecar overview page, it still shows a "Failing" status
Check the sidecar details page, it still shows the longer description of the "Failing" state as well
Restart the sidecar process
Check sidecar overview and details page ➡️ The "Failing" status is gone
Problem description
If a collector cannot be started by the sidecar because the config file is invalid, the UI correctly shows a "Failing" status. The problem is that the "Failing" status is still visible when the config file problem has been solved and the collector backend is started successfully.
Steps to reproduce the problem
Environment
The text was updated successfully, but these errors were encountered: