FinOps for Cloud
Sign In
  • Home
  • Open Source
  • FinOps for Cloud
    • Overview
  • Insights
    • Recommendations
      • Savings Optimization Recommendations
      • Security Recommendations
      • Clean-up Scripts Based on Recommendations
      • Archived Recommendations
    • Resources
      • Constraints
    • Pools
      • Configure Assignment Rules
      • Re-apply Ruleset
      • Delete Pools
      • Pool Constraint Policies
    • Cost Explorer
  • Policies
    • Anomaly Detection
      • Create Anomaly Detection Policies
    • Quotas and Budgets
      • Create Quota or Budget Policies
    • Tagging Policies
      • Create Tagging Policies
  • System
    • User Management
    • Data Sources
      • Amazon Web Services
        • AWS Root Account with Data Export Already Configured
        • AWS Root Account With No Data Export Configured
        • AWS Linked
        • Migrate from CUR to Data Exports CUR 2.0
      • Google Cloud Platform
      • Microsoft Azure
    • Events
    • Settings
  • Help and Support
    • Contact Support
    • FAQs
      • Why does the pricing in FinOps not match the SoftwareOne invoice?
    • Release Notes
    • Terms of Use
Powered by GitBook
LogoLogo

Company

  • About SoftwareOne
  • Careers
  • Media Releases

Policies

  • Codes of Conduct
  • Privacy Statement
  • Terms and Conditions

© 2025 SoftwareOne. All rights reserved.

On this page

Was this helpful?

Export as PDF
  1. Policies
  2. Anomaly Detection

Create Anomaly Detection Policies

To create a new anomaly detection policy:

  1. In FinOps for Cloud, select Anomaly detection in the sidebar.

  2. On the Anomaly detection page, select Add. The Create Anomaly Detection Policy page opens, allowing you to configure the parameters for the policy to be created.

  3. Enter a Policy name and select the Policy type for the new policy. The following policy types are supported:

    • Resource count - These anomalies refer to inconsistencies or unexpected variances in the number of resources being utilized or allocated compared to what is expected or what has been provisioned. These anomalies can occur in various cloud resources, such as virtual machines, storage, network bandwidth, or cloud services (like databases and application servers).

    • Expense - These anomalies are instances where the actual financial expenditure on cloud resources deviates significantly from expected or budgeted costs. These anomalies can be symptomatic of underlying issues such as inefficient resource utilization, misconfigurations, unauthorized access, or even billing errors from cloud service providers.

  4. Enter the evaluation period in days and define the threshold percentage.

  5. (Optional) Select the filters that will be used to trigger policy alerts. You can apply multiple filters to your policy.

  6. Select Save.

When an anomaly is detected, FinOps for Cloud will send you a notification email.

PreviousAnomaly DetectionNextQuotas and Budgets

Last updated 12 days ago

Was this helpful?