Description

Ensure each Public Cloud project has a consumption alert that sends an email when the project's monthly spend reaches a set threshold, so unexpected costs are noticed quickly.

Rationale

Public Cloud is billed on usage, and costs can grow quickly because of mistakes, runaway autoscaling, or a compromised account used for crypto-mining. Without an alert, this may only be noticed when the invoice arrives. A consumption alert gives early warning so action can be taken.

Impact

  • Unexpected spending is noticed early

  • Helps detect misuse of the project

  • Thresholds must be updated as normal usage changes

Default Value

By default, no consumption alert is set on Public Cloud projects.

Pre-Requisites

  • Permission to manage the Public Cloud project

  • Access to the OVHcloud API console

  • An agreed monthly spending threshold

Test Plan

  1. Open the OVHcloud API console at https://eu.api.ovh.com/console/ (or your region's console) and log in.

  2. Run GET /cloud/project/{serviceName}/alerting, replacing {serviceName} with your project ID.

  3. For each returned ID, run GET /cloud/project/{serviceName}/alerting/{id} and check the email, monthlyThreshold, and delay values.

  4. If no alert exists, follow the implementation steps.

Implementation Steps

  1. Open the OVHcloud API console at https://eu.api.ovh.com/console/ (or your region's console) and log in.

  2. Run POST /cloud/project/{serviceName}/alerting with: email (the address to notify), monthlyThreshold (the monthly amount in your account currency), and delay (seconds between two alerts, for example 3600).

  3. Run GET /cloud/project/{serviceName}/alerting to confirm the alert was created.

  4. With Terraform, you can use the ovh_cloud_project_alerting resource instead.

Backout Plan

  1. Run PUT /cloud/project/{serviceName}/alerting/{id} to change the threshold, or DELETE /cloud/project/{serviceName}/alerting/{id} to remove the alert.

Reference