DocumentaciónHelp

Cost anomalies

Detect sharp increases in a resource's daily cost against its median over the last few days, with an incident that closes on its own when it normalizes.

On this page

An anomaly is a day on which a resource costs much more than usual: a process left running, a scale-up that did not scale back down, a configuration error. ARGUNIS detects it by comparing each full day with the median of the previous days for the same resource.

Before you start

  • View permission on Cloud costs (FinOps); Administer to change the thresholds.

Review the anomalies

  1. Go to Costs → Anomalies.

  2. Read the current rule at the top: how many times the median, over how many days and the minimum difference per day.

  3. Choose Open or All.

  4. Each anomaly shows the resource and provider, since when, the Baseline, the Last day, the Peak, its Incident and its status.

  5. Click the ticket to open the incident.

If event only appears instead of the ticket, an alarm policy kept it as an event without opening an incident.

Change the thresholds

  1. Click Thresholds.

  2. Adjust:

    • Times the median: for example, 2.5 is a day that costs 2.5 times the usual.

    • The minimum difference per day, so you are not notified over cents.

    • Median days: how many previous days are compared.

  3. Save.

What happens next

Each anomaly opens a Costs incident in Core and closes on its own when the cost normalizes. It is checked at each sync, with days in UTC.

Display currency is on this same page. See Display currency.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close