Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing collector status does not get reset in UI #238

Closed
bernd opened this issue Jun 27, 2018 · 0 comments
Closed

Failing collector status does not get reset in UI #238

bernd opened this issue Jun 27, 2018 · 0 comments
Milestone

Comments

@bernd
Copy link
Member

bernd commented Jun 27, 2018

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

  1. Create a collector configuration and assign it to a sidecar
  2. Wait until the collector has started
  3. Introduce a syntax error in the collector config
  4. Wait until the sidecar overview page shows a "Failing" status
  5. Fix the syntax error in the collector config
  6. Wait until the sidecar has successfully restarted the collector
  7. Check the web sidecar overview page, it still shows a "Failing" status
  8. Check the sidecar details page, it still shows the longer description of the "Failing" state as well
  9. Restart the sidecar process
  10. Check sidecar overview and details page ➡️ The "Failing" status is gone

Environment

  • Sidecar Version: 1.0.0-alpha.1 (rev d92f8e5)
  • Graylog Version: 3.0.0-alpha.2-SNAPSHOT (rev 20ab7325e)
@bernd bernd added the bug label Jun 27, 2018
@bernd bernd added this to the 3.0.0 milestone Jun 27, 2018
@joschi joschi added the triaged label Jul 2, 2018
@bernd bernd closed this as completed in #244 Jul 3, 2018
bernd pushed a commit that referenced this issue Jul 3, 2018
This was referenced Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants