hardScenarioDesignSeniorStaff
A planned upgrade window opens and correlation stops working, so operations sees thousands of uncorrelated alarms. What is wrong with your inventory and change data?
5 min readUpdated 2026-08-15
Answer
Short answer
Correlation is a traversal of the inventory graph, and an upgrade changes exactly the part being traversed. Model planned as well as as-built state, carry the set of resources a change touches as data, scope suppression to that set rather than to the time window, and confirm recovery positively.
Was this answer helpful?
Likely follow-ups
- How do you keep a service visible when only one of its two redundant paths is in the window?
- The upgrade replaces a card and its ports come back with different identifiers. What breaks?
- What positive check proves the estate came back, rather than proving it stopped complaining?
- Who is allowed to declare a window, and what does the system require them to supply?
Related questions
- A release goes out and afterwards users can see records they were never entitled to. How would you find out, and how long would it take?hardAlso on change-management6 min
- A maintenance script updates your permissions table and every user in one tenant can suddenly edit everything. What should have stopped that, and how would you have found out?hardAlso on change-management6 min
- You are pushing a configuration change into the mobile core tonight. How do you stop one change taking the whole network down?hardAlso on change-management6 min
- Sales keep selling broadband at addresses we cannot actually serve, and the order fails at survey. What is wrong with the inventory behind that?hardAlso on network-inventory6 min