Workspace defaults
The defaults UnitVane runs with, which settings an admin can change, and where to change them.
UnitVane is fully managed, so there are no servers or environment variables to configure. These are the defaults every workspace starts with; admins change most of them in Settings.
Billing
| Setting | Default | Purpose |
|---|---|---|
| Daily billing read | 06:00 UTC | Anchors the daily billing and allocation chain |
| CUR format | CUR 2.0 | Set per AWS integration; the original CUR is also read |
| Net costs | On | Discounts, credits and commitments reflected in cost |
| History on first connect | 180 days | Billing read on first connect (up to 366) |
| Restatement window | 3 days | Recent days re-read on every run |
Allocation and ownership
| Setting | Default | Purpose |
|---|---|---|
| CPU and memory weight | 50 / 50 | Split of node cost between CPU and memory |
| Team labels | project, team, owner | Labels that carry the team |
| Cost center labels | cost_center, dept, department | Labels that carry the cost center |
| Application labels | product, application, app | Labels that carry the application |
| Auto-discover owners | On | Create teams and cost centers from label values |
Governance
| Setting | Default | Purpose |
|---|---|---|
| Anomaly minimum increase | $50 a day | Smallest increase flagged as an anomaly |
| Anomaly minimum percentage | 30% | Smallest relative increase flagged |
Retention
| Data | Default |
|---|---|
| Billing rows | 90 days |
| Raw pod samples | 30 days |
| Usage and assistant ledger | 365 days |
Allocated costs and reports are kept for the life of the workspace, so cost history outlives the raw billing rows. Snapshots are deleted by the bucket's 14-day lifecycle rule. Every default, with what stays available after it expires, is in the retention table.
Need help with this guide?Contact support