Graylog2 / Graylog2/graylog2-server
Collector onboarding UI failure detection missing agent crashes
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
## Expected Behavior
The onboarding UI should take into account the component health reports to indicate deployment problems, which is available since #26840 was merged.
## Current Behavior
Currently, if the collector process crashes, this information is not properly detected and the onboarding does not show the system logs.
## Possible Solution
Evaluate the health field.
## Steps to Reproduce (for bugs)
1. Start a crashing collector through the onboarding flow, e.g. force enable journald sources on macos.
2. Observe errors in the system logs (sent and in collector log files)
3. No state change is visible in the UI
Contributor guide
Research direction
Start in the collector onboarding UI flow and trace how component health reports are consumed, focusing on the health field introduced by #26840. Reproduce the crash scenario by force-enabling journald sources on macOS, then verify that the UI changes state and displays the relevant system logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100