← All questions
What operations are part of AI Usage Observability, Attribution & Continuous Calibration?
GQ-0216
41 results
- Align Cost Periods & Dimensions
- Attach Request-Level Metadata
- Attribute Variance to Drivers
- Calculate Realized Optimization Benefit
- Calibrate Cache & Route Assumptions
- Calibrate Latency & Capacity Assumptions
- Calibrate Retry & Failure Assumptions
- Calibrate Token Distribution Assumptions
- Classify Optimization as Retain, Revise, or Roll Back
- Compare Estimated & Actual Performance
- Compare Estimated & Actual Request Volume
- Compare Estimated & Actual Token Usage
- Compare Estimated & Actual Unit Cost
- Define Latency & Outcome Telemetry
- Define Model & Provider Dimensions
- Define Optimization Baseline Window
- Define Token Usage Telemetry
- Define Workflow & Stage Dimensions
- Define Workload Attribution Keys
- Detect Routing or Model-Mix Anomaly
- Detect Unit-Cost Anomaly
- Detect Usage Anomaly
- Establish Usage Baseline
- Identify Reconciliation Differences
- Identify Replanning Trigger
- Ingest Provider Cost Records
- Investigate Anomaly Driver
- Map Provider Dimensions to Workload
- Map Provider Usage Fields
- Measure Post-Optimization Quality & Latency
- Measure Post-Optimization Usage & Cost
- Normalize Model & Service Dimensions
- Normalize Token Classes
- Preserve Provider-Specific Extensions
- Publish Revised Workload Plan
- Re-run Candidate Evaluation
- Reconcile Usage-Derived & Reported Cost
- Refresh Baseline Scenario
- Track Plan Version & Effective Period
- Validate Attribution Coverage
- Version Calibrated Baseline