Skip to main content
Altrum checks a fixed set of rules every hour. When one holds, everyone it concerns gets a notification under the bell at the top of every page, and an email if they want one. Each alert names the thing, the fact and the threshold (“Claims bot used 80% of its $4,000 monthly budget”), and opens the screen where it is fixed. Alerts are notices. The AI Gateway already enforces budgets, limits and guardrails on every request, so an alert can arrive up to an hour after the fact.

​
Where alerts show

  • The bell shows how many are unread (up to 9+) and the latest 8 open ones. Mark all read and View all are at the top and bottom.
  • Alerts, under Monitor in the sidebar, lists your own alerts, newest first, under Today, Yesterday and Earlier. Filter by severity and by rule. Click a row to open where it is fixed; it is marked read. Owners and admins also see Create incident on an open alert, which opens an incident filled in from it.
An alert clears by itself when its condition stops holding, for example when a budget resets or is raised. Cleared alerts move to Cleared and stay there as history. Notifications are read or unread; there is nothing to dismiss.

​
The rules

A budget alert counts only the budgets the AI Gateway enforces: the organization’s, an AI system’s and a key’s. A project’s budget is a sum and is never alerted on. When a budget reaches 100%, the 80% alert for that period clears, so you see one. Access review due is not on the Rules tab either: in the last 7 days of a quarter with no completed access review, it goes to owners and admins of an organization with the AI Gateway, once a quarter, and clears when a review is completed. It cannot be switched off, and does not email unless you switch it on. Incident assigned is not on the Rules tab: it is sent when an incident is assigned to you, never by the hourly check, and clears when the incident is resolved or assigned to someone else. It emails by default. An organization with only the AI Gateway has no Posture drop, Reassessment due or Waiting for approval rules. One with only governance has those three and none of the others.

​
How often each fires

Each alert fires once for its window, however many times the hour comes round:
  • A budget alert, once per level per budget period.
  • Unusual spend, a spike, a watched guardrail, the error rate, a failing provider and a refused model, once a day for each AI system, provider or model.
  • A reassessment, once when it is due soon and once more when it is overdue.
  • Waiting for approval, once each time an AI system goes into review.
  • An unused key, once until it is used again.

​
Who gets each alert

Incident assigned is the exception: it goes only to the person the incident is assigned to. Access review due goes to owners and admins only. Only active members are told.

​
Change a rule

Owners and admins change rules; everyone else sees them read only.
1

Open Alerts, then Rules

The rules are grouped by Spend, Guardrails, Traffic, Governance and Keys, each with what it fires on.
2

Switch a rule off or on

A rule switched off fires nothing, and its open alerts clear on the next check.
3

Change a threshold

Select the pencil, change the numbers within their bounds, and select Save. A value outside the bounds is refused, naming the field and its range.
Each change is recorded in the audit trail as “Changed an alert rule”.

​
Choose which alerts you get by email

Open the account menu (your initials, top right) and select Email settings. Each rule has a switch, saved as you change it. The bell always gets every alert, whatever you choose here. The email itself is described in Emails.