Cloud costs can fluctuate for many reasons — scaling, configuration errors, or unexpected workloads. Without monitoring, these changes may remain unnoticed until they result in unnecessary overspending. Uniskai’s Anomaly Detection feature empowers users to set flexible thresholds, automatically track consumption, and receive alerts whenever usage crosses defined limits. Notifications are sent by email and, if a personal Slack account is connected, directly into Slack as well. Read more about notifications here. The Anomaly settings are located in the Organization Settings, please refer to this manual for access instructions.
Note: Only organization owners or admins can edit anomaly settings.
Anomalies are identified based on configured thresholds. Owner or Admins can define both a percentage threshold and a cost threshold, and then choose whether these conditions should be applied together or separately. With the AND option, anomalies are triggered only when both the percentage and cost thresholds are exceeded. With the OR option, anomalies are triggered when at least one of the conditions is met. This flexibility allows teams to fine-tune detection rules to match business needs.
Uniskai supports two monitoring schedules: daily and monthly. Each can be configured independently with its own thresholds and notification settings. Daily monitoring is useful for detecting short-term spikes, while monthly monitoring highlights longer-term consumption trends. Both daily and monthly monitoring can be completely turned on or off at any time, giving organizations full control over how anomalies are tracked.
Thresholds can be applied globally or at the account level. Default thresholds cover all accounts unless a specific account threshold is defined. Account level thresholds allow specific accounts to be monitored differently from the rest. If an account does not have a Account level threshold, the system automatically applies the default values.
In addition to this flexibility, anomaly detection can be managed at the account level. Users can disable anomaly searches for specific accounts directly from the interface or update thresholds for individual accounts when needed. Actions include updating thresholds, resetting them to default, or disabling detection entirely for chosen accounts.
By combining threshold configuration, independent daily and monthly monitoring, and per-account controls, Uniskai’s Anomaly Detection feature ensures that no unusual consumption goes unnoticed. This proactive approach helps organizations prevent overspending, identify misconfigurations, and maintain effective cost management.

