Skip to content

RDoc-3350 & RDoc-3351 Add section about cluster nodes availability #2066

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -30,12 +30,35 @@ status.
{PANEL: Cluster Health}

**Cluster Health** helps keep your cluster healthy by providing suggestions and incidents history.
This dashboard has two separated sections:
This dashboard has three separated sections:

- [Cluster Nodes Availability](cloud-maintenance-troubleshooting#cluster-nodes-availability)
- [Incidents History](cloud-maintenance-troubleshooting#incidents-history)
- [Suggestions](cloud-maintenance-troubleshooting#suggestions)

---
## Cluster Nodes Availability

The **Cluster Nodes Availability** section shows the availability status of each node within your cluster.
It provides a real-time, visual overview of how reliably each node has been operating in the current month.

Each node is represented by a gauge showing its availability percentage, helping you quickly assess the overall health of your system.
The availability is calculated based on whether the node has been up and responsive.

### Availability Status Thresholds

Each node's status is color-coded based on its availability percentage:

| Availability | Status | Color |
|--------------|----------|-----------|
| > 99.9% | Healthy | 🟢 Green |
| 95% – 99.9% | Degraded | 🟡 Yellow |
| < 95% | Critical | 🔴 Red |

These thresholds help you identify which nodes might require attention:

- **Healthy** nodes have consistently high uptime and are performing reliably.
- **Degraded** nodes may have experienced occasional downtime or disruptions.
- **Critical** nodes have had significant availability issues and may require immediate investigation.

## Incidents History

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading