Know which two systems must never be down together.
The dependency between two systems is not written in any spreadsheet. It is written in the traffic between them.
A conflict warning before you book
Window A — 01:00 to 03:30
Window B — 03:00 to 05:00
Thirty minutes of overlap between two linked systems. The warning comes before the save, not after it.
The problem
The spreadsheet does not know who talks to whom.
Two coordinators book two windows on the same night, each certain their system stands alone. It does not. You find out at 3am, with both of them down.
- 01
Mapping
A nightly sync pulls host-to-host network relationships from your monitoring and turns them into relationships between business systems via the inventory.
- 02
Attribution
The system name comes from the inventory, not from monitoring — the inventory is the reliable answer to who owns a host. A host with no match is recorded with no system, and the edge is still kept.
- 03
The check
At scheduling time, any overlap between windows on linked systems is flagged. The check does not block the save — some nights that is the right call — but it does not let you make it unknowingly.
- 04
The map
The connections page shows one system and its neighbours. Past twenty neighbours it switches to a matrix, where legibility does not collapse with size.
Monthly calendar with a collision visible between two events
Waiting on sign-off to publish the demo estate
The topology comes from the monitoring you already run.
- Dynatrace
- Host inventory
- The event calendar
A warning, before the save
Naming both systems, the number of host pairs linking them, and the other event already booked at that time.
Show us your worst window.
Bring the one that keeps slipping. Thirty minutes, your estate, no slides.