Known limitations of the 0.9.0 beta#

The Community release is a beta, version 0.9.0. It ships with the limitations below known and not hidden. Read them before you rely on a figure.

Findings come from 42 detectors: 21 for AWS, 11 for Azure, 10 for GCP. The Azure and GCP rules are tested on fixtures and have not been run against a real subscription or project. Core's detection run reaches AWS accounts only for now, so an install shows no finding from the Azure and GCP rules yet. Kubernetes, Snowflake, Databricks and VMware come with the Enterprise ingestors.
A saving is an estimate, and some are cruder than they look. Four rules (EC2, RDS and DynamoDB over-provisioning at 50 percent of the current price; the old EC2 generation at 15 percent) take a share of the price and say so in the finding. Treat every figure as an order of magnitude to check, not a quote.
A missing price gives a finding with no saving. The finding says "Finding detected; savings unavailable because pricing data is missing." and states no figure. It is never a zero you are meant to believe.
Some findings appear a week late. A resource first seen already stopped or unattached counts as in that state since the first scan, so the 7-day rules find it 7 days later. A rule that needs 7, 28 or 30 days of metric history waits in silence until it has them.
The scan stays inside the Community Edition limits, and says so. A scan cut by the resource limit is recorded and shown as a partial scan. A service or region the account cannot read is named with its reason.
Owners are confirmed by a person. Core does not read an owner from tags. A finding without an accountable person says so and points to the ownership review, where someone is confirmed. Hyvop does not change or delete resources: remediation is a plan a person reviews and applies.
A finding that disappears says why in general terms. A finding closed after its detector ran twice without finding it says the rule no longer applies or the resource is gone, because core cannot tell a removed resource from a fixed one.
Azure and GCP services that have no rule are not marked. Catalog-only services are ingested and no rule is defined for them; the product does not say "inefficiency rule not defined".
The Community Edition keeps 30 days of metrics. Day counts follow the ClickHouse server's time zone, which should be UTC.
Not every limit has a screen yet. The user interface does not show the note on a missing price, and no page lists all limitations in one place.

For anything this page does not answer, see troubleshooting.md or write to contact@hyvop.com.