Traceroute ConfigSources

was able to add the configSource and it seems to be working great for a couple of quick tests i did.

Thank you Antony.

Hi Muiz,

Try now. Thanks for pointing this out!

Antony

Hi Antony,

getting Import Error for this ConfigSource saying "LogicModule is Private, Cannot Read". Would you be able to change that? Thanks.

v1.1.0: JGZ7GK

Hi 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.

I wonder if anyone has accomplished what I'm looking for with this.  I'd like to have a known good traceroute, then have it poll every 5 minutes, then alert if outside the known good traceroute and resolve when it's back inline with known good traceroute.
The changes would be, allow us to poll config source more frequently than 1 hour.  Then set a "golden config" to compare against.

@Jono it should be possible within the proc.eachLine{} section to exclude hops that match a pattern, for example if they end '.mydatacenter.com', or you can add exceptions in the 'RouteHasChanged' diff check.

Thanks!  I tested it right away and it works great.  I gave it a test associating the traceroute with the device rather than collector and that works also.

My use case is I will have routers I am monitoring over the internet, I have a VPN so it is all private hops for traceroute.  I will apply this config to the device, with the traceroute.list property being it's own displayname.  This way I will get alerts on route changes that are already associated with the device so I can get alerts and notify people appropriately.  I tested this and it seems to work.  Next I'll be finding how to omit certain hops in our datacenter that won't indicate a true routing change.

@Jono should be good to go now, thanks!

Hello,

When trying to download this from the LogicMonitor Exchange, I get the following error,

This LogicModule is currently undergoing security review. It will be available for import only after our engineers have validated the scripted elements.

is there any update on when this will be available?