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

# Health Checks

> How the Velatir desktop client monitors itself, and how to read velatir health

## Overview

Velatir checks its own health every \~30 seconds. If something breaks it never blocks your traffic: it either pauses capture or steps aside so connections flow directly, then recovers on its own once the problem clears. Read the current state with [`velatir health`](/desktop-app/cli#health).

## States

| State                | Meaning                                                                                                                                |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| `Ok`                 | Everything is working; AI apps are being captured.                                                                                     |
| `DegradedInspection` | Capture is paused (for example, the certificate is not trusted). Apps keep working, but AI activity may not be traced until it clears. |
| `DegradedRouting`    | The capture path itself broke. Velatir steps aside so traffic flows directly, uninspected, until it clears.                            |

## Reading `velatir health`

```bash theme={null}
velatir health
```

```text theme={null}
Health:    DegradedRouting
Evaluated: 2026-06-05 14:31:02 (8s ago)

Checks:
  [ ok ] api-healthz-e2e
  [ ok ] cert-trusted
  [FAIL] windows-routing
         reason: traffic capture path is not running
         action: step out of the path
```

Each failing check shows a reason and the action Velatir took. The exit code is `0` when healthy and non-zero when degraded, so the command works as a monitoring probe. Add `--json` for the raw snapshot.

## If it shows a problem

A degraded state usually clears on its own. If it persists:

* **Certificate not trusted:** see [Troubleshooting → Certificates](/desktop-app/troubleshooting#certificates).
* **macOS extension not enabled:** approve it in **System Settings → General → Login Items & Extensions → Network Extensions**.
* **Anything else:** run `velatir logs --host -f`, reproduce, and share the output with support.

## Next Steps

<CardGroup cols={2}>
  <Card title="Troubleshooting" icon="life-buoy" href="/desktop-app/troubleshooting">
    Resolve a degraded state.
  </Card>

  <Card title="CLI reference" icon="terminal" href="/desktop-app/cli">
    The `health` and `test` commands in detail.
  </Card>
</CardGroup>