Skip to main content

​
Overview

Every optimization audit is persisted with its full timeline — goal, strategy, start time, completion time, and the associated action plan outcome. Reviewing audit history helps you track optimization trends, identify recurring imbalance patterns, and validate that executed plans have produced lasting improvements.
Prerequisites
  • At least one completed audit in your environment
  • Project access with the member role or above

​
View Audit History

Navigate to Audits

Log in to the Xloud Dashboard (https://connect.<your-domain>) and navigate to Admin → Resource Optimizer → Audits.

Review audit list

The audit list shows all historical audits sorted by creation time (newest first).
ColumnDescription
NameAudit display name
GoalOptimization objective
StateSUCCEEDED, FAILED, or CANCELLED
Created AtAudit creation timestamp
IntervalScope of the audit (CLUSTER or ZONE)

Open an audit

Click any audit to view its full detail, including:
  • The strategy that was applied
  • Any parameters that overrode the defaults
  • A link to the associated action plan
Click the Action Plan UUID to view the migration plan and its execution outcome.

​
Audit State Reference

StateMeaning
PENDINGQueued, not yet started
ONGOINGDecision Engine is running the analysis
SUCCEEDEDAudit complete and action plan generated
FAILEDAudit could not complete due to a data source or engine error
CANCELLEDManually cancelled before completion
Use audit history to identify patterns that indicate structural cluster issues:
If server_consolidation audits consistently produce empty action plans (no recommended migrations), the cluster is already well-balanced — or the utilization threshold is set too high and no hosts fall below it.Check current host utilization:
Check host utilization
openstack hypervisor list --long
If hosts are genuinely well-distributed, no action is needed. If hosts appear underutilized but no plan is generated, ask your administrator to lower the threshold parameter in the strategy configuration.
If noisy_neighbor audits consistently find high-contention pairs, the cluster may have insufficient capacity to separate contending workloads. Consider adding compute capacity or reviewing instance sizing.
Review the action plan list for plans in PENDING (approved but not executed) or RECOMMENDED (not yet approved) state. Stale plans are outdated within 24 hours by default — run a new audit to generate a current plan.

​
Export Audit History

Export audit list to JSON
watcher audit list -f json > audit-history.json
Export with full details for each audit
for audit_id in $(watcher audit list -f value -c uuid); do
  watcher audit show $audit_id -f json
done > audit-details.json

​
Next Steps

Run an Audit

Start a new optimization audit to continue improving cluster efficiency.

Action Plans

Review and approve pending action plans from past audits.

Troubleshooting

Diagnose failed audits and strategies reporting insufficient data.

Admin Guide — Scheduling

Automate recurring audits on a schedule for continuous optimization.