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

# Monitoring & Analytics

> Understand how Altostrat SDX turns heartbeats, metrics, faults, reports, and notifications into an operating view of your fleet.

Monitoring in Altostrat SDX is designed for operators who need to know what is happening now, what happened earlier, and who needs to act. Managed routers send heartbeats and metrics into SDX, the platform normalizes faults, and the portal presents that data through dashboards, fault logs, reports, and notifications.

```mermaid theme={null}
flowchart LR
  Site["Managed sites"] --> Heartbeat["Heartbeats and metrics"]
  Heartbeat --> Faults["Fault detection"]
  Heartbeat --> Dashboards["Dashboards and metrics"]
  Faults --> Logs["Fault log"]
  Faults --> Notifications["Notifications"]
  Logs --> Reports["SLA reports"]
  Faults --> Workflows["Workflow triggers"]
```

## What You Can Monitor

<CardGroup cols={2}>
  <Card title="Dashboards and Metrics" icon="layout-dashboard" href="./dashboards-and-metrics">
    View fleet, site, interface, inventory, and WAN health from the portal.
  </Card>

  <Card title="Fault Logging" icon="triangle-alert" href="./fault-logging">
    Investigate active and resolved events with severity, type, cause, message, and duration.
  </Card>

  <Card title="Reporting" icon="chart-area" href="./reporting">
    Schedule SLA reports across all hours or business hours, then share or download generated reports.
  </Card>

  <Card title="Notifications" icon="bell-ring" href="./notifications">
    Route operational events to the right people and channels with muting and topic controls.
  </Card>
</CardGroup>

## Heartbeat Sensitivity

Routers send SDX a heartbeat about every 30 seconds. A site is treated as offline after 10 missed heartbeats, which gives site availability detection a roughly five-minute sensitivity window. Downtime begins at the first missed heartbeat and clears on the next successful heartbeat.

This timing matters when you compare dashboards, fault logs, and SLA reports. A short interruption may appear differently from a sustained outage because SDX waits for missed heartbeat evidence before declaring the site offline.

## Operating Pattern

1. Use dashboards for current health and quick triage.
2. Use the fault log to understand event history and resolution.
3. Use notification groups so incidents reach the right team.
4. Use SLA reports for service review, customer reporting, and trend analysis.
5. Use workflow triggers when a monitored event should start an automated response.

<Tip>
  For event-driven automation, see [Triggers and Webhooks](../automation/workflows/triggers-and-webhooks). Fault events can start workflows such as WAN offline, WAN packet loss, site offline, and site online handling.
</Tip>