Skip to main content

Release Summary

This release introduces significant enhancements to cost categorization across all services, standardizing the use of canonical resource categories and improving the accuracy of cost attribution, credits handling, and reporting. Numerous improvements and bug fixes have been implemented to streamline data processing, enhance UI clarity, and ensure consistent behavior across AWS, Azure, and Kubernetes integrations.

aws-scanner​

  • 🔧 Standardized node categorization using a centralized resource type record; improved mapping to canonical categories.
  • 🔧 Enhanced RDS snapshot listing to run once per SnapshotType, with improved validation for AWS Backup cluster snapshots.
  • 🔧 Introduced a dedicated page budget for AWS/Snapshot listings, aligning with AWS quotas.
  • 🔧 Added resourceArn fields to VpcEndpoint and Route 53 hosted-zone nodes, and assigned empty-region ARNs to CloudWatch dashboard nodes.
  • 🔧 Updated category assignments for SageMaker/ElastiCache types and improved ARN handling for VpcEndpoint, CloudWatch dashboard, and Route 53 zone nodes.
  • 🔼 Updated dependencies to address security vulnerabilities.

chronom-backend​

  • 🔧 Declared additional cost indexes to support queries by resource and category.
  • 🔧 Ensured indexes required by other services are retained during boot, preventing unintended index drops.
  • 🔧 Automated index creation on first boot after deployment for dailyaccountcostexplorers.
  • 📣 Deployment order guidance: deploy before cost readers that count by category.

chronom-client​

  • 🔧 Enhanced cost chart to stack credits below zero, improving visual representation of spend versus credits.
  • 🔧 Updated tooltip and bar chart logic to display spend before credits, with clear labeling for credits, tax, and total.
  • 🔧 Improved dashboard banner to reflect cost coverage and canonical category labels.
  • 🔼 Updated dependencies to resolve security advisories.

k8s-scanner​

  • 🔧 Migrated to a newer Kubernetes client library, adopting ESM-only support and updating related build processes.
  • 🔧 Removed unused checkClusterHealth function and associated legacy dependencies.
  • 🔧 Added canonical resource categories for Role, ClusterRole, RoleBinding, ClusterRoleBinding, ServiceAccount, Node, and PodDisruptionBudget.
  • 🔧 Created a README with vocabulary and color alignment to aws-scanner.
  • 🔼 Updated dependencies to resolve security advisories.

policy-service​

  • 🔧 Refined anomaly graphs to categorize credits distinctly, removing negative-cost exclusion rules.
  • 🔧 Enhanced cost counting by row category, aligning with other services.
  • 🔧 Improved anomaly matching logic to use cost category, with robust handling of legacy data and normalization of category values.
  • 🔧 Optimized index declarations and removed unused indexes.
  • 🔧 Cleaned up obsolete files and interfaces.

typesense-mongodb-sync​

  • 🔧 Improved cost rollup logic to use the row's category for account-level totals.
  • 🔧 Restored node costs per account, ensuring accurate cost attribution and robust upsert matching for account containers.
  • 🔧 Enhanced error handling to prevent single document failures from affecting batch updates.
  • 🔧 Improved matching logic for account containers, ensuring case-insensitive handling and correct assignment of totals.
  • 🔧 Enhanced RDS cluster cost attribution using cluster resource identifiers.
  • 🔧 Updated category handling for Typesense imports.
  • 📣 Noted absence of automated tests in CI.

azure-scanner​

  • 🔧 Aligned cost category filters with the canonical table, ensuring consistency across services.
  • 🔧 Updated cost category mapping to include new patterns and remove obsolete or shadowed patterns.
  • 🔧 Improved documentation to clarify category handling logic.

dedicated-scanner​

  • 🔧 Introduced a dedicated credits category for cost attribution, ensuring credits and refunds are distinctly tracked.
  • 🔧 Refined AWS and Azure cost row handling to accurately attribute negative costs and corrections.
  • 🔧 Enhanced attribution summary logic to use the row's category for totals.
  • 🔧 Improved EC2 - Other part categorization for accurate storage and network attribution.
  • 🔧 Implemented queue-driven cost scans with robust timeout, retry, and deduplication handling.
  • 🔧 Improved RDS cluster cost attribution and error handling.
  • 📣 Noted absence of automated tests in CI.

be-ms-cost​

  • 🔧 Added a credits category to cost charts and homepage summaries, ensuring credits are visually and logically separated from spend.
  • 🔧 Refined cost aggregation logic to use row categories, improving consistency across UI and backend.
  • 🔧 Implemented a new coverage endpoint and improved category summaries.
  • 🔧 Enhanced resource daily cost attribution for RDS clusters.
  • 🔧 Cleaned up obsolete files and improved test reliability.
  • 🔼 Updated dependencies to address security findings.

anomaly-detection​

  • 🔧 Introduced a dedicated credits category for anomaly detection, removing negative-cost exclusions.
  • 🔧 Standardized resource group assignment using canonical cost categories.
  • 🔧 Removed legacy categorization logic and aligned with scanner category tables.
  • 🔧 Updated model training and loading logic to reflect new category handling.
  • 📣 Noted absence of automated tests in CI.

reports-generator​

  • 🔧 Added a credits row per bucket, ensuring accurate reporting of credits and refunds.
  • 🔧 Improved handling for accounts with no data, skipping unnecessary model calls.
  • 🔧 Standardized daily cost rollup logic to use the row's category.
  • 📣 Updated report prompts for clarity.

be-ms-inventory​

  • 🔧 Updated documentation to consistently reference the canonical resource category vocabulary.
  • 🔧 Implemented warnings for off-vocabulary filter values.

Additional Improvements​

  • 🔼 Updated dependencies across multiple services to address vulnerabilities and improve stability.

helmChart​

  • 📣 No changes in this release.

Disclaimer: The release notes are generated by OpenAI ChatGPT and may not be accurate. Please contact our support team for more information.

2026-Oct-08T11:24:06