The VCF Operations rule that decides when an alert fires for a given base object type. It brings together symptoms and optional recommendations, and sets the alert's criticality, type, subtype, impact, and how many cycles to wait before raising or cancelling it.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Alert definition 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.
- Base object type
Every VCF Operations alert definition or view targets exactly one kind of object, Host System for instance. Its symptoms can be tested against that object or against parents, children, ancestors or descendants related to it.
Related terms
- log symptom
A VCF Operations symptom driven by the content of logs, which becomes available after VCF Operations for logs is integrated. A single alert definition can mix log and metric symptoms, and log-based alerting arrived in version 9.0.
- Wait cycle
Number of collection cycles for which symptoms have to remain active in a VCF Operations alert definition before an alert appears; its counterpart, the cancel cycle, counts how long they stay inactive before the alert is withdrawn. Neither may be below 1.