Study guide
13.2 Custom Alert Policies and Behavioural Anomaly Detection
Nutanix Certified Associate NCA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Nutanix Cloud Platform & HCI Foundations
1.1 Nutanix NCA Exam Overview, Format, and Objectives 1.2 Hyperconverged Infrastructure (HCI) vs. Traditional 3-Tier Architecture 1.3 The Nutanix Enterprise Cloud Portfolio (NCI, NUS, NCM, EUC, NC2)
2 Chapter 2: Platform Architecture & Distributed Core Services
2.1 Hardware Building Blocks: Nodes, Blocks, Clusters, and Quorum 2.2 Controller VM (CVM) Architecture, Datapath, and Autopathing 2.3 Core Distributed Services: Cassandra, Stargate, Curator, Zookeeper, and Genesis
3 Chapter 3: Prism Administration & Cluster Operations
3.1 Prism Element vs. Prism Central Architecture and Interface Navigation 3.2 Entity Management, Categories, and Role-Based Access Control 3.3 Nutanix Licensing Tiers, Add-ons, and Pulse Telemetry
4 Chapter 4: AOS Distributed Storage Fabric & Data Placement
4.1 Storage Pools, Storage Containers, and vDisk Virtual Architecture 4.2 Redundancy Factor (RF2 vs. RF3), Failure Domains, and Fault Tolerance 4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)
5 Chapter 5: Storage Optimization & Business Continuity
5.1 Storage Efficiency: Compression, Deduplication, and Erasure Coding (EC-X) 5.2 Space-Efficient Redirect-on-Write (ROW) Snapshots and Zero-Byte Clones 5.3 Protection Domains, Consistency Groups, and Disaster Recovery Replication
6 Chapter 6: AHV Virtual Machine Lifecycle Management
6.1 AHV VM Provisioning, Resource Allocation (vCPU, vRAM, Disks), and Boot Types 6.2 Nutanix Image Service and Virtual Machine Templates 6.3 Nutanix Guest Tools (NGT) Architecture, Features, and Deployment 6.4 AHV High Availability (HA), Acropolis Dynamic Scheduling (ADS), and Affinity Rules
7 Chapter 7: AHV Networking & Flow Security Fundamentals
7.1 AHV Virtual Networking Architecture, Open vSwitch (OVS), and Bridges 7.2 Host Network Uplinks, Virtual Switch Configuration, and NIC Bonding Modes 7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM 7.4 Nutanix Flow Network Security & Microsegmentation Fundamentals
8 Chapter 8: Cluster Maintenance, Health Monitoring & Support
8.1 Nutanix Cluster Health Monitoring, Alerts, and Events Engine 8.2 Nutanix Cluster Check (NCC) Architecture and Execution 8.3 Life Cycle Manager (LCM) and Rolling Non-Disruptive Upgrades 8.4 Nutanix Support Ecosystem: Diagnostics, Log Gathering, and Support Bundles
9 Chapter 9: Recognizing Nutanix Solutions, Hypervisors & the Product Portfolio
9.1 Supported Hypervisors for NCI and Feature Supportability 9.2 NCI Core Components, Configurations, and Common Deployment Scenarios 9.3 Nutanix Unified Storage: Files, Objects, and Volumes Use Cases 9.4 Nutanix Database Service (NDB) and Database Automation 9.5 Nutanix Kubernetes Platform, Enterprise AI, and End-User Computing
10 Chapter 10: Nutanix Tools — Migration, Deployment, and Validation
10.1 Nutanix Move: Cross-Hypervisor and Cloud Migration 10.2 Foundation and Foundation Central: Imaging and Cluster Deployment 10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory
11 Chapter 11: Cluster Configuration, Security & Hardware Maintenance
11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP 11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin 11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown 11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities 11.5 Out-of-Band Management and Remote Console Access
12 Chapter 12: Storage, Network, and Software Administration Tasks
12.1 Volume Groups, vDisk Placement, and Live vDisk Migration 12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation 12.3 The Software Compatibility Matrix and Upgrade Path Planning 12.4 Taking and Managing VM Snapshots in Prism 12.5 License Operations: State, Assignment, Reclamation, and Expiry
13 Chapter 13: Performance Analysis, Reporting & Support Operations
13.1 Prism Analysis: Metric Charts, Entity Charts, and Custom Reports 13.2 Custom Alert Policies and Behavioural Anomaly Detection 13.3 Interpreting Workload Performance: CPU Contention, CPU Ready, Memory, and I/O Latency 13.4 Creating Support Cases, Required Documentation, and Insights
13.2 Custom Alert Policies and Behavioural Anomaly Detection
Key Takeaways Explain This Topic AI
Objective 4.2 asks you to determine use cases for custom alert policies, which supplement rather than replace the built-in cluster health checks.
A custom alert policy defines a condition on a metric, a scope of entities usually chosen by category, a severity, and an action.
Static thresholds are appropriate when a fixed number genuinely matters; behavioural anomaly detection is appropriate when normal varies by time of day or day of week.
Scoping policies by category is what makes different thresholds possible for production and development workloads on the same cluster.
Alert severity in Nutanix is Critical, Warning, or Info, and choosing severity deliberately is what keeps the alert list meaningful.
Last updated: September 2026
13.2 Custom Alert Policies and Behavioural Anomaly Detection
Section 8.1 covered the built-in alert and health engine — the several hundred checks Nutanix ships that watch the platform itself. Objective 4.2 asks for something different: "determine use cases for Custom Alert Policies."
Why Built-In Checks Are Not Enough
Built-in checks are about the platform : a drive failing, a service down, capacity approaching a limit, a node unreachable. They are excellent at that and they are the same on every Nutanix cluster in the world.
What they cannot know is your context :
That this particular VM is a payments gateway where 20 ms of storage latency is a customer-visible problem, while the same latency on a build server is irrelevant.
That your batch window runs 01:00 to 04:00 and CPU saturation during it is expected, not alarming.
That a specific application must never exceed a memory ceiling agreed with its vendor.
A custom alert policy encodes that context.
Anatomy of a Custom Alert Policy
Created in Prism Central , a policy has four parts:
- Part What you specify
- Scope Which entities the policy watches — usually selected by category rather than individually
- Condition The metric and the trigger: a static threshold, or a behavioural anomaly
- Severity Critical, Warning, or Info
- Action What happens — raise the alert, notify, or in more advanced setups trigger automation
- Scope by category is the important design decision
This is where categories (section 3.2) pay for themselves. A policy scoped to Environment: Production applies to every production VM automatically, including ones created next month. A policy scoped to Environment: Development can carry looser thresholds on the same cluster.
Building a policy against a hand-picked list of VMs instead means the policy silently stops covering new workloads — the classic way monitoring quietly decays.
Static Thresholds vs. Behavioural Anomaly Detection
Two ways to define "wrong," and choosing correctly is the substance of this objective.
- Static thresholds
- "Alert when this metric crosses this number."
Right when a specific value genuinely matters regardless of context:
A contractual or vendor-mandated limit.
A hard capacity ceiling.
A known application breaking point.
Wrong when normal varies. A static CPU threshold on a workload that is idle at night and saturated during a batch window either fires every night or never fires at all — there is no single number that is correct at both times.
- Behavioural anomaly detection
- "Alert when this metric departs from what is normal for this entity, at this time ."
The platform learns each entity's pattern over time — including time-of-day and day-of-week rhythms — and flags deviation from that learned band rather than from a fixed number.
Right when:
Normal is genuinely cyclical (batch windows, business hours, month-end).
You do not know what the correct threshold is, which is common for a new application.
You want to catch a workload behaving unusually even while still inside acceptable absolute limits — the early signal a static threshold cannot give.
The blueprint references "Behavioral Learning Tools" under Objective 4.4 for exactly this. The richer behavioural and predictive capability, including capacity forecasting, belongs to NCM Intelligent Operations and its X-Fit engine (section 1.3).
Tip
Exam discriminator: if a scenario describes a workload whose normal load varies predictably by time , the answer is behavioural anomaly detection . If it describes a fixed limit that must not be crossed , the answer is a static threshold .
Choosing Severity Deliberately
Nutanix classifies alerts as Critical , Warning , or Info . Severity is not decoration — it determines what gets escalated and what gets ignored.
- Severity Reserve for
- Critical Something is broken or imminently will be; someone should act now
- Warning A trend needs attention within a working day
- Info Worth recording; no action expected
The failure mode to avoid is alert fatigue . A cluster that raises forty Critical alerts a day has effectively no Critical alerts, because nobody reads them. Marking a genuinely urgent condition as Warning is equally bad in the other direction.
Given an Alert, Determine Impact and Plan a Resolution
The last knowledge statement under Objective 4.2 asks you to reason from an alert to an action. A workable order:
Read the severity and the entity. What is affected, and how urgently?
Assess impact. Is a workload degraded now, is resiliency reduced, or is this a forward-looking warning?
Check whether it will auto-resolve. Many Nutanix alerts clear themselves when the underlying condition passes (section 8.1); a transient condition may need no action.
Correlate. Use an entity chart (section 13.1) to see what else was happening on that object at that time.
Run the relevant NCC check for a targeted diagnosis (section 8.2).
Act, or escalate — collect logs and open a support case (section 13.4) if the cause is not clear.
Note how the parts connect: alerts point to an entity, charts explain the entity, NCC diagnoses the platform, and support takes over what remains.