Water-utility Spectrum triage needs a fast first look at real-time fabric events. What should come first?

Water-utility Spectrum triage needs a fast first look at real-time fabric events before committing expensive deep captures. WJH real-time event analysis surfaces live discards, congestion, and path symptoms across the municipal fabric with far less overhead than targeted deep packet inspection, so it should come first in the response order and guide where—if anywhere—heavier tools are aimed.

Why the other options fail by concept: Targeted deep packet inspection of suspect flows for payload detail before any WJH review skips the live triage needed to identify those suspect flows, burns capture resources on flows that may not be the root cause, and can still stress production paths without a WJH hypothesis. Spectrum port counter polling for baseline throughput validation before any live WJH check abandons real-time discard and congestion visibility when utility AI jobs may already be failing. Scheduled NetQ validation report review for fabric compliance status as the opening step is not real-time, delays triage when utility AI jobs may already be failing, and checks compliance rather than surfacing live discards and path symptoms.

Exam caveat: WJH is a triage lens, not a complete substitute for packet-level proof when payload or protocol bugs are suspected. After WJH points to a leaf, port, or category, scoped captures or counter deep-dives remain valid next steps—just not the first step on every water-utility incident.

Operational check: for a new Spectrum symptom on the water-utility AI fabric, open WJH first, identify hot event categories and affected uplinks within minutes, record the timeline, and only then authorize a time-bounded, port-scoped capture if WJH plus counters are insufficient for closure.