Milestone 4: Monitoring and operations explored

This is the fourth milestone checkpoint. The instructor will review the monitoring and observability work from this section before the final part of the lab.

✅ Explored the difference between the main health dashboard (what is broken now) and the analytics dashboard (how the network is performing over time)
✅ Understood Intent-Based Analytics and how Apstra evaluates telemetry against design intent rather than raw thresholds
✅ Reviewed live anomalies and historical anomaly trends — understanding when issues appeared and when they were resolved
✅ Used the integrated CLI to run show commands directly from the Apstra UI, with full design context already present
✅ Explored Time Voyager, walked through the rollback workflow, and confirmed the live network remained unchanged

The common thread across this section is a shift from reactive to informed operations. Conventional tools tell you something is wrong. Apstra tells you what is wrong, where it is, why it matters relative to your design intent, and what the network looked like before the problem started.

That shift does not just save time during incidents. It changes how you think about risk. When you know that any committed change is a reversible snapshot — and that rolling back means a single operation, not a manual undo across dozens of devices — you can operate with more confidence.

This is the last section of the lab. You will use Data Centre Assurance — Juniper’s cloud-based AIOps platform — to see what happens when you combine Apstra’s intent model with machine learning and Flow data across multiple sites.

You will need to sign up for the demo environment. The sign-up link and steps are at the start of the next section.

Ready? Let’s move on!