Rules applied by VCF Operations to groups of objects, covering thresholds, metrics, capacity settings, and alert and symptom definitions. Custom policies inherit from a base and override selected settings, while the lowest-priority Default Policy catches anything not otherwise covered.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains VCF Operations policy in context, with comparison tables and the common traps.
Terms in this definition
- VCF Operations
VCF's console for running the fleet. It covers alerting, monitoring, capacity, reporting, log analysis and licensing alongside fleet management of identity, passwords, certificates and lifecycle.
- Capacity
A reserved block of compute for a tenant whose size is fixed by its SKU; Fabric F SKUs express it in capacity units (CUs). Workspaces assigned to it unlock features like Copilot, and from F64 upwards people with free licences can view Power BI content.
- Exclusions
Scopes taken out of a policy assignment; they can only narrow its coverage, never widen it.
Related terms
- Automatic remediation
When switched on in a VCF Operations policy, an alert firing immediately launches its linked orchestrator workflow through the Management Pack for Orchestrator. This works only with workflows needing a single input.
- Base Settings
Every VCF Operations policy, starting with the Default Policy, inherits from this root, which gathers together whatever settings the installed solutions and adapters contribute.
- KPI
A metric flagged as a KPI in a VCF Operations policy, so that breaching its threshold raises an alert.