resources_current — the newest complete snapshot for each configured subscription — so a resource that disappears from a later ARG collection does not linger in the current view. The inventory page presents this current snapshot through a filterable, paginated dashboard with cost and performance enrichment layered on top.
Inventory view
The inventory table supports the following filters, which can be combined freely:
Results are paginated with a configurable page size, up to 2,000 resources per request. The full filtered result set can be exported as CSV or XLSX using the export button, which applies the same active filters without the pagination limit.
Enrichment fields
Each resource in the inventory carries standard ARG fields (ID, name, type, subscription, resource group, region, tags) plus the following enrichment columns populated during synchronization:Cost fields
estimatedMonthlyCost and amortizedMonthlyCost — pulled from the most recent cost snapshot for the resource’s subscription.Utilization
utilizationPercent — the governed CPU p95 value from the most recent telemetry run, with a source field indicating Azure Monitor or LogicMonitor.Opportunity fields
opportunityKind, opportunityReason, and estimatedMonthlySavings — populated when the resource has an active Flux Signals or Advisor finding.Changes and drift detection
The Changes view shows exact consecutive-snapshot inventory diffs. Flux compares each new complete ARG snapshot against the immediately preceding one for each subscription and records the delta. Change types are:
Each change record includes the resource identity, the before and after field values as evidence, and the snapshot timestamps that bracketed the change.
Change anomalies
Flux evaluates whether the total volume of changes in a snapshot interval is unusual for that scope. The method is a median/MAD (median absolute deviation) baseline:1
Build a baseline
Flux accumulates the per-scope change counts across completed drift intervals. A minimum of
FLUX_DRIFT_MIN_BASELINE_POINTS intervals (default 5) must be completed before the scope is eligible for anomaly classification.2
Compute a robust deviation score
For each new interval, Flux calculates how many MADs the observed change count is from the scope’s median. Scores above
FLUX_DRIFT_MAD_THRESHOLD (default 3) are flagged as anomalous change volume.3
Surface the anomaly
Anomalous scopes appear in
/api/changes/anomalies with the current count, baseline median, MAD score, and the raw interval evidence.
Scopes with fewer than
FLUX_DRIFT_MIN_BASELINE_POINTS completed intervals are reported as warming up rather than anomalous or normal.
Sync schedule
resources_current always reflects the newest complete snapshot. If an ARG collection for a subscription completes but returns zero resources (for example, due to a permission failure on a scope), Flux retains the previous successful snapshot rather than replacing it with an empty set — this is the last-good retention behavior.