Start with the service and its dependencies
Identify the network, compute, storage and supporting power systems behind an important service. Assign each source to its real site and owner. A useful first scope answers a concrete question, such as whether a branch incident coincides with a WAN interruption or an overloaded host.
Account for private reachability
Place an authorized Site Edge where it can reach private sources. Review firewall policy, DNS, time synchronization and read-only credentials before collection. Public HTTP checks complement internal observations; they do not replace private network monitoring.
Make handover useful
Agree on who reviews incidents, which support hours apply and how missing coverage is escalated. Share a report with the exact observation period and timezone. Local context is a planning input, not a promise of a staffed office or universal onsite coverage.