Get warned before a link breaches, while there’s still time to act.
Slow-burn problems such as growing demand, a creeping error rate or a filling disk give plenty of notice, if anything is looking at the slope. The Predictive view does, and it keeps score of its own misses.
Recognize it
You’re here if
- A link’s utilization has risen for weeks and nobody has a date.
- Capacity is raised only after applications start failing.
- You want a lead time, not just a status.
Do this
5 steps, in order
See what is on a path to breach
Open Predictive and read the feed of forecasts, each with an entity, a metric and an ETA.
Open Predictive- Look for
- Entities projected to cross a threshold, with a time estimate.
- What it means
- The soonest ETA with the highest consequence is first.
Read the forecast, not just the date
Open a forecast and check the trend and how it was fitted.
Open Predictive- Look for
- A robust trend over recent history, with a guard that ignores normal daily cycles.
- What it means
- A daily peak is not a ramp. The guard is there so it does not warn you every morning.
Act with the lead time you have
For capacity, raise the order or shift bulk traffic off-peak. For errors, open the repair ticket now.
Open Remediation- Look for
- Recommendations that fit the ETA.
- What it means
- A three-week lead time is a purchase order. A three-hour one is a QoS change.
Check the track record
Open Accuracy and switch to the predictive lead-time tab.
Open Accuracy- Look for
- How often past forecasts were followed by a real breach, and with what lead time.
- What it means
- Weight your reaction by this. A forecast that has been right often earns an earlier response.
Let situations surface it
Look for the banner on Situations that counts entities on a path to breach.
Open Situations- Look for
- A count and a link back to Predictive.
- What it means
- That puts forecasts in front of whoever already reads situations.
Then decide
What you found decides what you do
IfThe ETA is weeks away and the trend is structural
ThenOrder capacity and shape traffic until it arrives. Voice dies at the same hour daily →
IfThe ETA is hours away
ThenTreat it as an incident in waiting. Contain now.
Watch out
Where this goes wrong
- Forecasts are observe-only by default. They appear in Predictive and on Situations but do not page anyone until you enforce them.
You know what is heading for a breach, how much time you have, and how much to trust the estimate.
Keep going
Often next
Find what thresholds miss
Let a seasonality-aware detector flag what is wrong for this hour of this week, then decide whether to promote it.
~15 minNOC engineer, Network leadIt’s up, but it’s badVoice dies at the same hour daily
Find the bulk transfer starving real-time traffic, and fix it without buying bandwidth.
~15 minNOC engineer, Network leadRun the NOCApprove or hold a fix
Read the recommendation, the rollback plan and the blast radius, then decide.
~10 minNetwork lead, NOC engineer, Security analyst