Monitoring Your Fleet

The Fleet Management page in app.aurva.ai gives you a single pane of glass across every cluster and cloud account where AIOStack is deployed. The page auto-refreshes every 30 seconds.

Storage Summary

At the top of the page, the storage summary shows aggregate telemetry volume across your entire fleet:

• Total Primary Storage — primary telemetry data stored
• Total Secondary Storage — secondary/processed data stored
• Total Records — total number of runtime events collected across all outposts

AIOStack uses state-of-the-art compression algorithms to minimize storage footprint — the numbers you see here are already compressed, so raw event volume is significantly higher than what's stored. Use these numbers to track data volume growth over time, especially as you add new clusters or workloads to the fleet.

Fleet Summary

The fleet summary gives you a quick count of your deployment footprint:

• Total Outposts — number of outpost installations registered to your account
• Active Outposts — outposts currently connected and reporting
• Total Regions — number of distinct cloud regions covered
• Total Providers — number of distinct cloud providers (AWS, GCP, Azure) in the fleet

Outposts

Each outpost is shown as a card (or table row) with the following details:

• Install ID — unique identifier for the outpost installation
• Status — ACTIVE, DEGRADED, or INACTIVE
• Account ID / Project ID — the cloud account or GCP project the cluster belongs to
• Cluster — the Kubernetes cluster name
• Type — deployment type (e.g. kubernetes)
• Build Version — the outpost image version currently running (e.g. trueID-delta, latest)
• Last seen — timestamp of the most recent event received from this outpost
• Region — the cloud region the cluster is deployed in

You can filter outposts by cloud provider (aws, gcp) or status (ACTIVE, DEGRADED, INACTIVE), and toggle between card and table view.

Multi-cloud support

AIOStack supports deployments across AWS, GCP, and Azure in the same fleet view. Each outpost is automatically associated with the cloud provider and region detected at install time. All telemetry flows into a single unified inventory in the console — so an identity chain that spans an EKS cluster in AWS and a GKE cluster in GCP is visible in one place.

On-premises and standalone deployments

Enterprise deployments support the full range of AIOStack capabilities on bare-metal servers, private cloud environments, and standalone EC2 instances — giving you runtime AI visibility in environments where Kubernetes is not in use.

Adding a new outpost

To add a new cluster to your fleet, run the installer on the target cluster:

curl -fsSL https://aurva.ai/install.sh | bash

The new outpost will appear in the fleet view once the installation completes and the outpost connects to the control plane.

Keeping the fleet healthy

• All outposts show as Active — a DEGRADED or INACTIVE outpost means telemetry has stopped flowing; check outpost connectivity to hq.aurva.ai:443 and review outpost logs
• Last seen is recent — if an outpost's last-seen timestamp is drifting, investigate before it goes fully inactive
• Build versions are consistent — mixed versions across a fleet can produce inconsistent detection behavior; see Upgrades

For any fleet-level issues, see Troubleshooting or contact support@aurva.io.