# Costs and thresholds

Base savings on your real costs, and alerts on your own thresholds.

## Your costs

As long as you set none, Naoshift calculates its savings on **reference values**, which are neither yours nor a supplier's price list. The **Savings** and **Recommendations** pages always say which base they count on.

1. Open **Settings › Analysis › Costs**.
2. Enter what you know, and leave the rest empty.
3. Click **Save**. The change applies to the next calculation.

| Cost | It prices |
|---|---|
| **vCPU**, per month | Right-sizing, idle machines |
| **Memory**, per GB and per month | Right-sizing, idle machines |
| **Storage**, per GB and per month | Space reclaim, snapshots, powered-off machines |
| **Energy**, per kWh | Consolidation: the energy of a removed host |
| **Licensing**, per core and per year | Consolidation: the licenses freed |
| **Hardware maintenance**, per host and per year | Consolidation: the maintenance saved |

An empty field takes the value of the parent company if there is one, otherwise the reference value. The screen says where each value comes from.

## Your thresholds

Alert rules have default thresholds. You can adapt them to your company.

1. Open **Settings › Analysis › Alert thresholds**.
2. On a rule, enter the warning and critical thresholds, then save.
3. Add an exception for an asset: 90/95% on a very large datastore, for example.

Emptying both fields of a rule brings it back to the defaults.

> Before raising a threshold, ask whether the alert is wrong. For an asset that is out of scope, an [exclusion with a reason](/en/read/decide-on-an-alert) is more accurate: it can be seen, and it can have an end date.

### The amounts have not moved

The change applies to the next calculation. Reload the **Savings** page, and check the base cited at the bottom of the page.

### I do not know all my costs

Leave empty the ones you do not know. An approximate but assumed figure is better than one nobody can defend.
