Graylog2 / Graylog2/graylog2-server
Health Status alerts are not actionable
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
## Expected Behavior
As a user, when I get an alert about "Connectivity" issue on the Alerts page, I want to be able to dig into exact error details and find out what happened and if it is still a problem.
## Current Behavior
The way these alerts are presented currently are lacking all details and are not actionable at all:
## Possible Solution
Include details about the problem in the alert itself and/or link to a page where details can be seen by the user.
## Steps to Reproduce (for bugs)
1.
2.
3.
4.
## Context
## Your Environment
* Graylog Version:
* Java Version:
* OpenSearch Version:
* MongoDB Version:
* Operating System:
* Browser version:
## Checklist
[] This issue fix need to be backported.
[] Does this issue have **security** implications?
Contributor guide
Research direction
Start from the Alerts page and inspect how the current "Connectivity" health alert is presented. Done means the alert includes exact error details or links to them, allowing users to understand what happened and whether the problem is still active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100