Planning

Alerts

See every alert a workspace has and everything that fired in one place, and learn where each kind of alert is created, edited and delivered.

The Alerts page, under Planning, is one view over several kinds of alert. Cost alerts are created and edited here; budget thresholds and report schedules are still changed where they live, and a budget's thresholds open their budget.

Before you start

  • Every team role can view the page. Creating, editing, pausing and deleting cost alerts needs the Editor team role in a workspace your team can edit.
  • Alerts that should reach Email, Slack, Microsoft Teams or a webhook need a notification channel.

The Alerts page with the Configured alerts table and the What fired feed

The Alerts page for the Production workspace: budget thresholds, cost alerts and a report schedule, then the feed of what fired.

Configured alerts

Configured alerts lists budget thresholds, cost alerts and report schedules with their Name, Kind, Threshold, State and Last fired. A budget threshold's name opens its budget, and a cost alert's name opens its settings, as in Edit, pause, resume or delete a cost alert. Filter by kind narrows the list to one kind, and each column but Threshold sorts it. The kinds are:

KindWhat it watchesWhere it is created
Budget thresholdSpend for a budget's period reaching a percentage of its amountBudgets
Budget forecast thresholdThe forecast for a cost budget's period end reaching a percentage of its amountBudgets
Spend thresholdSpend rising by an amount against a comparison period, or month-to-date spend reaching an amountThis page or Insights, with "New alert"; a saved cost report, with "Create alert"; or the Public API
Percentage changeSpend rising by a percentage against a comparison periodThis page or Insights, with "New alert"; a saved cost report, with "Create alert"; or the Public API
Low tag coverageTag coverage falling below a percentageInsights, with "Set alert"
Report deliveryA scheduled cost reportShare and schedule reports

Last fired is when the alert last fired: for a budget threshold, when spend crossed it; for a budget forecast threshold, when the forecast reached it; for spend threshold, percentage change and low tag coverage alerts, the newest event in What fired. It stays empty until the alert first fires.

State says what an alert is doing now, in the sense of the Overview's Active alerts card, which lists the firing ones:

StateMeaning
FiringThe alert fired and its measure is still past the threshold. Firing alerts are listed first.
ArmedThe alert is watching and is not firing.
ScheduledA report schedule that is active.
PausedThe alert is not evaluated. A cost alert paused until a time reads "Paused until" that time, in the workspace's time zone, and its first evaluation after it resumes the alert.

What fired

What fired is one feed of cost alert events and the anomalies detected on the workspace's connections, newest first. A cost alert's entry names the alert, whose name opens its settings, and states what it fired on as its email does: the threshold, the measured value and, for an alert that compares, the cost it was compared with, for example "Spend threshold of €500.00 crossed: €2,140.50 (+€660.25) against €1,480.25 (previous day)", and a low tag coverage alert's states the coverage it fell to, as in "Low tag coverage: 79.9%, below 80%". An anomaly's entry names the service and its severity, describes the anomaly as Insights does, and shows the observed and expected amounts: "Observed …, expected …". "Open in report" opens a new cost report with the anomaly's evidence, as on Insights, and "Acknowledge", offered on an open anomaly to anyone who can change its status, marks it as seen. An entry someone has already acknowledged is marked Acknowledged. The feed shows its newest ten entries, and Show more shows ten more. Budget threshold and budget forecast threshold crossings are not in the feed; they show in Last fired. See Insights for how anomalies are detected and acknowledged.

Create a spend or change alert

Spend threshold, percentage change and month-to-date spend alerts are created on this page, on the Insights page's Cost alerts card or from a saved cost report.

  1. On Alerts, select New alert in the page header; the Cost alerts card on Insights offers it too. Or open a saved cost report, open More actions in its header and choose Create alert; a report with unsaved changes asks you to save them first.
  2. Enter a Name. From a report, the alert starts with the report's title and its filter.
  3. Choose the Kind: Spend threshold fires when spend rises by an amount, Percentage change when it rises by a percentage, and Month-to-date spend when the spend since the 1st of the month reaches an amount.
  4. Enter the Threshold. The field shows its unit: % for a percentage, which reads as written, so 2.5 means 2.5% and 0.05 means 0.05%; for an amount, the currency the workspace presents figures in, which the new alert takes and keeps.
  5. For a spend threshold or a percentage change, choose what it is Compared with: Previous day, Previous week, same days, Previous month, same number of days or Same day last month. A percentage change needs one; a spend threshold compares with the previous day unless you choose another.
  6. Optionally, on a percentage change, enter a Minimum increase: the alert then fires only when the increase is also at least that amount.
  7. Optionally, narrow the alert with a Filter, built as on a report. Without one it watches all of the workspace's spend.
  8. Optionally, pick notification channels under Send to. An in-product notification is always sent too.
  9. Select Create alert.

The New cost alert dialog with Name, Kind, threshold, Compared with, Minimum increase, Filter and Send to

A new percentage change alert: 10% against the same days of the previous week, with a minimum increase.

An alert made from a report copies the report's filter rather than linking the report, so changing the report later does not change the alert. It counts cost with the default cost settings and without the saved filters of the folders the report sits in; the form says so when the report counts cost differently or sits in a filtered folder.

Create cost alerts through the API

The Public API's cost alert endpoints create the same alerts, and take the connections an alert watches, which the form does not offer. An alert names:

  • a thresholdType, absolute, percentageIncrease or budgetPercentage, and a comparisonPeriod of previousDay, previousWeek, previousMonth or sameDayLastMonth, which percentageIncrease requires and absolute takes as previousDay when it is left out;
  • the thresholdValue, greater than zero: on an absolute alert the increase in the alert's currency, on a percentageIncrease alert a percentage, on a budgetPercentage alert the month-to-date spend in the alert's currency;
  • on a percentageIncrease alert, an optional minimumAmount in the alert's currency: the alert then fires only when the increase is also at least that amount, so a large percentage of a small cost stays quiet. Sending 0 removes it;
  • the connections it watches, providerIds;
  • the notification channels to deliver to, appIds;
  • how often to evaluate it, evaluationFrequencyMinutes, between 15 and 1440 minutes.

An alert's currency is the workspace's currency when the alert is created, and the alert keeps it when the workspace's currency changes later. The alert measures its cost in that currency: with currency conversion disabled, a window not billed in that currency alone is not measured, and the alert does not fire on it. With currency conversion enabled, cost billed in a currency with no exchange rate into the alert's currency is not counted, as on a cost report, and the alert's notification, in the product and by email, Slack, Microsoft Teams or webhook, names that cost in the window it fired on, per currency.

Alerts of all three types measure only days whose cost has settled, and an absolute or percentageIncrease alert fires on an increase only. A provider delivers the last day or two late, so every window ends on the last settled day, the day before yesterday in UTC: yesterday and today are never counted, because a day still arriving reads low against a complete one and would hide an increase. Cost is dated by the provider's UTC billing day, so that day is the same whatever the workspace's time zone, and an increase on a given day is measured from two days later. For an absolute or percentageIncrease alert, the comparisonPeriod sets the two windows compared:

comparisonPeriodMeasuredCompared with
previousDaythe last settled daythe day before
previousWeekthe week up to the last settled day, from its Mondaythe same days of the week before
previousMonththe month up to the last settled day, from its 1stthe same days of the month before
sameDayLastMonththe last settled daythe same date a month earlier

The month before can have fewer of those days, as February has 28 against the 31 of March. The two windows are then compared at their daily averages: the month before counts at its cost per day over as many days as the month so far, so unchanged daily spend is no increase, and an absolute threshold is the increase over the month so far. The comparisonValue of a fired previousMonth alert event is this figure, not the month before's own total.

A budgetPercentage alert compares with no earlier period, so comparisonPeriod does not apply to it. It measures the month-to-date spend, the month up to the last settled day, from its 1st, in the alert's currency, and fires once that spend reaches thresholdValue. Despite its name, it measures no percentage and references no budget: the name stays so configurations that already send it keep working. To be alerted at a percentage of a budget, use a budget: its thresholds are percentages of its amount.

An alert without providerIds measures every connection of its workspace. An alert can also carry a filter in the filter language; it then measures only the matching cost, as a report's filter narrows its cost. An alert whose filter no longer reads, for example because a virtual tag it names was deleted, is not evaluated.

See API authentication and the API reference.

Edit, pause, resume or delete a cost alert

Spend threshold, percentage change, month-to-date spend and tag coverage alerts open from their name on Alerts, and a firing one on the Overview's Active alerts card or a cost alert's notification in the bell opens it there too. They are listed on the Insights page's Cost alerts card with their Name, Kind, Status and Threshold; All alerts there leads to Alerts.

  • Edit: the pencil icon opens the alert in the same form it was created with, its Kind shown but fixed. Change its Name, its Threshold, what it is Compared with, on a percentage change its Minimum increase, its Filter and its Send to channels, and select Save; emptying the minimum increase or the filter removes it, and "Cost alert saved" confirms the change. A member who only views the workspace has the eye icon, View, instead, and reads the same settings without changing them. A tag coverage alert changes only its name, threshold and channels. The dialog also shows the evaluation Frequency and when it was Last evaluated, and says when the alert is limited to connections set through the API or Terraform, which saving keeps.
  • Pause and Resume: a paused alert is not evaluated.
  • Delete: confirm with Delete in Delete cost alert. Evaluation stops immediately.

Where alerts are delivered

Planned: budget alert notifications

Not yet available in Costfluent.
SourceDelivered to
Budget thresholdsAn in-product notification, plus the enabled channels the budget names
Spend threshold, percentage change, month-to-date spend and low tag coverage alertsAn in-product notification, plus the enabled channels the alert names
Detected anomaliesAn in-product notification in the workspace, plus the channels the workspace chose under Anomaly notifications
Report deliveryThe email channels chosen on the schedule

How it behaves

  • Costfluent looks for cost alerts due for evaluation every 15 minutes, and evaluates each one at its own frequency.
  • An alert fires once when its measure crosses the threshold. It stays triggered and silent while the measure stays over, and fires again only after an evaluation finds the measure back under the threshold.
  • A low tag coverage alert measures the share of cost on tagged resources over the last 30 days, the number the "Tag coverage" card on Insights shows. Once the workspace has a tag policy with rules, it measures instead the share of cost carrying every key the policy requires, as the policy's report counts it. It is not evaluated while the workspace has no cost in that window.
  • Every new workspace starts with one low tag coverage alert, "Tag coverage below 80 %", over the whole workspace and with no channels, so it notifies in the product only. Pause, change or delete it like any other on the Insights page's Cost alerts card. Set alert on the "Tag coverage" card opens New tag coverage alert, which adds another alert beside it and says which tag coverage alerts the workspace already has.
  • A percentage change alert does not fire when the comparison period has no cost.
  • A spend threshold or percentage change alert that fires marks the day on the chart of each saved report whose filter is the same as its own, as an annotation; see Annotations.
Measure over the threshold, the alert fires Measure back under the threshold Under the threshold Triggered and silent
An alert fires once when an evaluation finds its measure over the threshold, stays triggered and silent while the measure stays over, and can fire again only after an evaluation finds it back under.