Pack: node-health
Compute-node health from a JSON list of per-node reports that a site's own health exporter writes to node-health/records.json (each report has node, cluster, observed_at and checks, a list of name, status ok or warn or fail, and detail).
| Field | Value |
|---|---|
| Kind | context |
| Version | 0.1.0 |
| Needs a credential to publish | no |
| Okg modules it needs | document_starter, person, extraction |
| Packs it needs | none |
In which bundles
- Default in: none
- Optional in:
cluster-manager
Add it to an instance with archi add node-health.
Sources
node-health.node_health
Questions
archi init asks these. Answer one with --answer node_health_<id>=VALUE.
| Id | Type | Required | Default | Prompt |
|---|---|---|---|---|
cluster_name |
string |
no | cluster |
Cluster name |
Credentials
The manifest names no credential variable.
Freshness limits
archi doctor compares each source's age with its limit.
| Source | Longest acceptable age |
|---|---|
node-health.node_health |
6h |
Link coverage targets
| Name | From | Edge | To | Direction | Minimum share | Severity |
|---|---|---|---|---|---|---|
check_node |
node_health_check |
contains |
compute_node |
in | 0.99 | warn |
Invariants
The pack owns these checks. They leave with it.
| Name | Severity | What it checks |
|---|---|---|
node_health_coverage |
error | The node-health source must have live nodes and checks. Required live subtypes: compute_node, node_health_check. A missing one means the input was empty or the connector regressed. |
Playbooks
The pack ships no playbook.