> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review of the health system

> How Axottle continuously monitors nodes, connection circuits and dependencies, reduces signals to statuses and offers recovery - manually or according to Flow Guard's permitted policy.

Axottle’s health system continuously monitors infrastructure: it checks nodes, Flows, gateways, input and transit nodes, WARPs, external proxies, CDNs, and routing rules; it reduces disparate signals to understandable statuses and levels of severity (severity), shows them on the health dashboard, and maintains a tape of incidents.

> [!NOTE]
>
> For whom: panel administrator, SRE, duty engineer. Required rights: panel administrator session.

## Monitoring and recovery

Health collects checks and offers action. For Flow, [Flow Guard](https://docs.axottle.com/en/connection-units/recovery.md) is available: a manual plan with pre-check and confirmation, or a pre-authorized self-recovery policy.

By default, modifying actions require manual confirmation. If the operator has enabled the automation of a particular Flow, the server can execute authorized versions of plans and switch the route to explicitly selected reserves. You need fresh data of the running version, confirmation of the failure and compliance with pauses and limits.

An AI diagnostic report alone does not allow for infrastructure change; maintaining a user plan does not include it in an automatic policy either.

Turning off the automation stops the next steps, but does not roll back the ones already performed. An unconfirmed switching result requires the operator to be checked before restarting.

## What exactly is being observed

The checks are organized according to levels, from basic network achievability to end-to-end route verification and external regional samples. For more details, see [Levels of Checks](https://docs.axottle.com/en/health/probes.md).

## How to read the state

Each sample returns status; the status of the sample is summarized in the general status of the node, the circuit, and the entire park. `healthy`, `degraded`, `critical`and `unknown` (data not yet available) and `unsupported` Severity incidents are deduced from the general status: `critical → error`, `degraded → warning`return to `healthy → info`The detailed logic of the summary and the table "state → what it means → what to do" - on the page [Conditions and severity](https://docs.axottle.com/en/health/states.md).

## Section map

> [card] [Conditions and severity](https://docs.axottle.com/en/health/states.md)
>
> Sample statuses and summary states, severity, quorum logic according to the connection scheme.

> [card] [Levels of inspections](https://docs.axottle.com/en/health/probes.md)
>
> That checks each level (behavioral), manual and routine checks.

> [card] [dashboard health](https://docs.axottle.com/en/health/dashboard.md)
>
> Summary, tables of nodes and diagrams, incident tape, check button.

> [card] [Recovery (self-heal)](https://docs.axottle.com/en/health/self-heal.md)
>
> Event → Identification → Proposed Action → Limitation → Escalation.

> [card] [Health policies](https://docs.axottle.com/en/health/policies.md)
>
> Verification intervals, AI trigger policy, notification channels, scheduler.

> [card] [Node suppression](https://docs.axottle.com/en/health/suppression.md)
>
> Temporary disabling of notifications and participation of nodes without stopping monitoring.

> [card] [Runbook.](https://docs.axottle.com/en/health/runbooks.md)
>
> Step-by-step scenarios for critical allerts: symptom → diagnosis → recovery.

## Related sections

* [The life cycle of the node](https://docs.axottle.com/en/nodes/lifecycle.md) - as the status of the node is composed of Remnawave signals, health checks and an agent.
* [Flow review](https://docs.axottle.com/en/connection-units/overview.md) What are connection schemes whose health is observed?
* [Notifications](https://docs.axottle.com/en/panel/notifications.md) - how to set up health transition alerts.
* [Axosun](https://docs.axottle.com/en/axosun/overview.md) is a built-in AI assistant to which diagnostics is connected.
* [Incident Response](https://docs.axottle.com/en/operations/incident-response.md) - General procedure for failure.

Check the availability of features in the installed version in the panel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.