Monitoring the final destination implicitly monitors the intermediate hops as well. This is because data has to go through the intermediate hops to reach the final destination, so if an intermediate hop is dropping packets or adding latency, the final destination should show that.

If an intermediate hop is showing latency or packet loss that is not showing at the final destination, then it may not be a problem at all. See here for details on this:

http://www.nessoft.com/kb/24

With PingPlotter Pro we may be able to create an add-in that always makes sure a specific alert is always tied to all intermediate hops. Before we go too far down this path, though, we should make sure this is really necessary. Maybe you can send some .pp2 files to our support team (support@pingplotter.com) referencing this post and we can have a look at your data?