---
title: "System Overview"
description: "View platform version, server health, system information, and server time"
source_url: https://ai-ops.com/docs/system/information
---

# System Overview

Navigate to **System > Overview** to see a summary of your Koios deployment. The page displays four status cards at the top and a system information panel below.

---

## Status Cards

### Platform

Shows the platform name and a brief description. This card is static.

### Version

Displays the current Koios version number. If the version is a pre-release (e.g., alpha or release candidate), a yellow badge appears next to the version.

Click the card to expand a popover listing the individual version of each internal service (Data Collector, Predict Engine, Web App, etc.) and the release date.

### System Health

Shows the overall health status of the platform:

| Status | Meaning |
|--------|---------|
| **Healthy** | All services are running and reporting heartbeats |
| **Degraded** | Some services are healthy but at least one is not responding |
| **Unhealthy** | All services are unresponsive |
| **Unknown** | No health data is available |

Click the card to expand a popover listing each service with its status, last heartbeat timestamp, and any error messages.

### Server Time

Displays the current server time (updating every second), timezone, and UTC offset.

If the server clock and your browser clock are out of sync, a warning icon appears:

- **Yellow warning** — drift between 2 and 30 seconds
- **Red warning** — drift exceeds 30 seconds

Hover the warning icon to see the exact drift amount and direction.

> [!WARNING] Why clock drift matters
> Koios stamps every device read, model prediction, event, and historical sample with the host clock. Drift causes:
>
> - **Trends and history off the timeline** — samples appear at the wrong time, breaking comparisons against PLC, SCADA, or external historian data.
> - **"Live" values look stale or future-dated** — the UI flags freshness against its own clock; a server running fast or slow makes recent values look wrong.
> - **Model evaluation skews** — predictions and the device data they're scored against no longer line up.
>
> The cause is almost always either the **browser machine** or the **Koios host** drifting. Both should be synchronized via NTP. On the host, verify with `timedatectl status` — it should report `System clock synchronized: yes`. See [System Requirements > Time Synchronization](https://ai-ops.com/docs/installation/system-requirements.md) for setup details.

---

## System Information

Below the status cards, a full-width panel shows details about the host system, organized into two columns.

### Host & OS

| Field | Description |
|-------|-------------|
| **Hostname** | The server's network hostname |
| **Operating System** | OS name and version |
| **Kernel** | Kernel version string |
| **Architecture** | CPU architecture (e.g., x86_64, aarch64) |
| **Timezone** | The configured system timezone |
| **Uptime** | How long the server has been running (e.g., "2d 5h") |

### Hardware & Network

| Field | Description |
|-------|-------------|
| **CPU Cores** | Number of logical CPU cores |
| **Total Memory** | Total system RAM |
| **Total Disk** | Total disk capacity |
| **IP Address** | Primary network IP |
| **MAC Address** | Primary network MAC address |
| **Virtual Machine** | Whether the system is running in a VM, with VM type if detected |

The panel also shows the **Python version** used by backend services.

---

## What's Next

- [Services](https://ai-ops.com/docs/system/services.md) — monitor individual service status and restart services
- [Performance](https://ai-ops.com/docs/system/performance.md) — CPU, memory, and disk usage monitoring
- [License](https://ai-ops.com/docs/system/license.md) — view and manage your Koios license