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

Anomaly Detection

PreviousCost ExplorerNextCreate Anomaly Detection Policies

Last updated 12 days ago

Was this helpful?

Anomaly detection is an integral part of a cloud security and management strategy, helping you preemptively address potential issues before they cause significant damage or disruption. Cloud anomaly detection is crucial for maintaining the integrity and performance of cloud services.

In FinOps for Cloud, you can find the Anomaly detection page in the Policies section of the sidebar. The page provides information about all anomalies that have been created under your specified policies.

You can track the dynamics in the Status column and hover over it to view the average and current values. The filters show the instances in which this policy is available. An en dash (–) in the Filters column means the policy is available for all cases.

To view detailed information for a policy, select the policy name. You can then view the general information, date of violation, status, average, and actual counts for easy comparison and a quick assessment of the situation. You can also modify the policy name. Clicking the Actions icon displays all resources.

Anomaly detection page
Anomaly detection details page