Get the right alerts, where you want them
Each person picks, per event, the channels they want. Nothing is sent to a channel you have not enabled.
2 min read
Preferences
In your profile: Channels to connect them and Notifications to choose.
- Channels
- Email works out of the box. Chat channels such as Telegram must be connected first, and you can send a test message to check them.
- Per event
- Each row is an event and each column a channel. Tick what you want and save. Greyed channels need to be set up first.
Events
- Budget alerts
- When a budget crosses a threshold of its monthly amount, or is forecast to exceed it by the end of the month.
- Cost anomaly alerts
- When a service spends well above its baseline. One alert per episode: quiet while the overspend persists, re-armed when the service returns to normal.
- Weekly digest
- A Monday summary of the organization: cost evolution, tracked resources and new recommendations.
- Job failed
- For admins: a background job failed and will be retried.
Tuning anomaly alerts
Organization settings, Costs → Anomalies.
- Sensitivity
- Low flags only clear breakouts, medium is recommended and high catches smaller jumps with more noise.
- Minimums
- A flag only becomes an alert when it clears both the minimum extra monthly spend (10 by default) and the minimum jump over the baseline (50 percent by default). Anything below stays visible on the Anomalies tab without alerting.
Other events
- Tracking limit reached
- Your plan's resource limit stopped new resources from being tracked.
- Invoices
- A new invoice for the organization is ready to view.
- Support replies
- When our support team answers one of your tickets you always get an email, in copy to the ticket's participants. It is not configurable (see Support).