EmployeeEmployeeHi Jono,
Briefly and off the top of my head, one way to accomplish this could be as follows:
1. Set a device property to list the steps of the known good route, e.g. "10.0.0.1, 10.0.0.55, edgerouter.mynetwork.local, isp.whatever.com"
2. Have a scripted DataSource (not ConfigSource) that ran the traceroute script every five minutes.
The DataSource would be able to pull in the known good route from the device property and compare the listed steps to the result of the traceroute and either confirm the two lists were a match, or not, outputting a suitable 1/0 code which could then be alerted on. Alternatively, it might output 0 if all steps matched vs the step number of the first mis-match.
Clearly you'd have to do some clever parsing if the steps might vary within a domain, e.g. if *.whatever.com were acceptable at step 4 in the above.
Not necessarily pretty, but probably achievable.
