Run the fabric after day 1: name a drop instead of counting it, stream the right counters at the right interval, drive NVUE from templates and the REST API, and upgrade without losing the config or the data plane.

1. 5.1 What Just Happened: naming the dropThree nights of drops nobody can nameAp
2. 5.2 NetQ 5.1: validation instead of inspectionTwo engineers on two leaves, both rightAp
3. 5.3 Streaming telemetry: OTLP, high-frequency counters, latency measurementThe stall that never appears on the dashboardAp
4. 5.4 Automating NVUE: REST API, config templates and AnsibleThe first question is not technicalC
5. 5.5 Upgrades that do not lose the fabricFifty minutes before the change boardAn
6. Checkpoint