Netpath is a good for visual path to aservice that running on TCP only ..
Netpath agent is a windows only ...
Those 2 things (no UDP /open agent) make it much less attractive for me...
Cisco shop will utilize Netpath with IPSLA.
Juniper shop RPM + what ever we can get...
The next generaion is that
I think the best thing you can do is to have the "old timers" go to http://lab.solarwinds.com and watch "#45 Hacking the Internet with NetPath". Just understanding the multipath nature of the Internet should be enough to make anyone question traceroute's overall value as a troubleshooting tool. If they've ever actually reached someone in a major carrier's NOC and basically been blown off after submitting traceroute data, watching that video will go a long way to explaining why.
I guess I am an "Old Timer", and I am not yet trusting what I am seeing with NetPath. I used to use a tool called "PathView" from AppNeta that, at least to me, gave much more concrete and actionable information.