Knowledge Base

Collected data versus usable evidence

A successful query is only one part of a supported assessment.

← Knowledge Base

Collected

Data was acquired from a source. Its timestamps, gaps, workload attribution, and observation window still matter. A recent point is not the same as a complete history.

Usable

The assessment needs enough relevant, attributable information and the applicable checks for that resource. CPU and memory can have different readiness and constraints. Missing OOM history cannot establish that no OOM occurred.

Learning or withheld

Learning means evidence is still developing; it promises no fixed completion time. A withheld assessment explains why a recommendation cannot be published. Follow the stated reason: additional waiting cannot repair a missing permission or an unretained metric.

Current is not historical

Compare the observation and assessment times. A historical recommendation does not establish the workload’s current configuration. Verify a proposed change against current source and cluster state before acting.

Review support availability

One Problem at a Time · Episode 2 · 1:13

What happens when your monitoring data isn't good enough?

How gaps and short observation windows can prevent a supported recommendation.

Includes an earlier AKS test-workload assessment dated October 26, 2026, shown in the November 4 recording. The generic recommendation card is an illustration, not RATIVERA output. The CPU history threshold shown belongs to that assessment policy; memory protective increases can have different requirements.

English captions are burned into the video. An optional English caption track and transcript are also available. Use fullscreen for small screen details.

Collected versus usable evidence · Why a recommendation is withheld

Episode page & transcript · Download MP4