Vast.ai Control-Plane Observability

Overview

Measure provider state and workload health separately. Alerts must identify a resource, threshold, evidence link, responder, and safe action; a dashboard without terminal-state and billing coverage is incomplete.

Prerequisites

• Instance, endpoint, workergroup, deployment, and account scopes
• Latency, error, queue, utilization, state-age, balance, and cost objectives
• Collection interval, retention, alert routing, and incident owner

Instructions

Step 1: Inventory labeled resources

Map instance labels and Serverless IDs to service, environment, release, cost center, and owner.

Step 2: Collect structured control state