To create good overlapping coverage for the deep URL test, a URL monitor can be combined with several shallow monitors such as a process monitor, DNS monitor, a CPU monitor, and several ping monitors. The URL monitor verifies that a page can be retrieved from the server in a timely manner, while the process monitor verifies that the Web server process is still running. The CPU monitor ensures that processing resources on the server aren't overloaded, while the DNS monitor tests whether the host name portion of the URL can be resolved. V. Internal Versus Remote Monitoring Remote monitoring refers to tests done by machines that are outside a site's internal network. An example of a remote monitor would be a monitoring machine in New York that fetches a public Web page from a Web server in San Francisco.
Internal monitoring occurs on a Web server itself, or from a machine on the internal network.
Because of the finer granularity of measurements possible, more precise problem diagnosis can be achieved. Problems detected by internal monitoring can generally be corrected by people at the site because they control the machines and the networks. Remote monitors usually don't have the security access required to initiate these actions. Remote monitoring coverage . Note the large number of components that are covered by a remote monitor, although if an error occurs, pinpointing the problem component can be difficult.