View source for KitsNet Operations:Services:Docker:High Availability NAS:Monitoring

== Trigger thresholds ==

=== HA triggers ===

{| class="wikitable sortable"
! Condition
! Persistence
! Severity
! Operational meaning
|-
| No master JSON data
| 30 seconds
| High
| Agent, user parameter, collector, or communication path is unavailable.
|-
| <code>collection_ok=0</code>
| 15 seconds
| High
| The collector is returning controlled failure snapshots.
|-
| Collection duration above 1,000 ms
| 5 minutes
| Warning
| Wort or libvirt query latency is elevated.
|-
| Coherence code 1
| Continuously for 20 seconds
| Warning
| A release or acquisition transition is taking too long.
|-
| Coherence code 2
| Continuously for 15 seconds
| High
| Authority, lease, intent, domain, disk, or fencing state is inconsistent.
|-
| Coherence code 3
| Immediate
| Disaster
| Storage attachment is unsafe.
|-
| Lease age above 10 seconds
| Continuously for 15 seconds
| Warning
| Heartbeat delivery is delayed well beyond its normal two-second interval.
|-
| Lease age above 20 seconds
| Continuously for 10 seconds
| High
| The owner has little active-lease headroom remaining.
|-
| Lease age above 25 seconds
| Immediate
| Disaster
| The active lease is within five seconds of its 30-second limit.
|-
| Lease invalid
| Continuously for 10 seconds
| High
| Owner, generation, boot identifier, or age validation failed.
|-
| Fencing control invalid or disabled
| Immediate
| Disaster
| Automatic fencing cannot be considered fully operational.
|-
| Fox or Anchor domain not running
| Continuously for 15 seconds
| High
| A NAS member is unavailable, including a node deliberately destroyed during fencing.
|-
| More than one live production-disk attachment
| Immediate
| Disaster
| Possible double attachment; treat as a data-integrity emergency.
|-
| No live production-disk attachment
| Continuously for 20 seconds
| High
| No NAS node has served as production storage owner for too long.
|-
| Any persistent production-disk attachment
| Immediate
| Disaster
| The deployment violates the live-attachment-only design.
|}

The lease-age triggers intentionally overlap. During a worsening event, Zabbix may show Warning, High, and Disaster problems together. The highest severity describes the current urgency; the earlier events preserve the escalation timeline.

=== Scheduler-delay triggers ===

The same thresholds apply separately to Fox and Anchor.

{| class="wikitable"
! Delay
! Persistence
! Severity
|-
| Above 5 percent
| 5 minutes
| Warning
|-
| Above 15 percent
| 2 minutes
| High
|-
| Above 30 percent
| 1 minute
| Disaster
|}

Scheduler delay is a pressure indicator, not proof that a failover is imminent. Interpret it alongside lease age, collector duration, guest service monitoring, and host resource pressure.