Forum Discussion

Antony_Hawkins's avatar
Antony_Hawkins
Icon for Employee rankEmployee
8 years ago

Traceroute ConfigSources

Update:

A ConfigSource, for use with LM Config, to monitor and alert on changes of route from the collector to any of a list of destinations. This is now combined a single ConfigSource that will run for both Windows and Linux collectors:

v1.1.0: JGZ7GK

If you really want to have a different ConfigSource per OS, the original two OS-specific ConfigSources are at: EK4HEG (Windows v1.5.0); HCPCXA (Linux v1.2.0).

To use, you'll need to add a property 'traceroute.list' to the Windows or Linux collector device* you want to use to check the route from, with the value being a comma separated list of destinations, e.g. '8.8.8.8,www.logicmonitor.com'

*You can modify the AppliesTo such that this datasource could apply to any device, however it will always be the collector running the script and doing the traceroute / tracert.

The ConfigSource will run the trace and print a summary of the results in a way that can easily be alerted on (if you really want to) in the event of a route change, plus a full dump of the route information including hop timings for information, in a way that is excluded from alerting.

Credit to @Jake Cohen for the basis of the script these are built from. :)/emoticons/smile@2x.png 2x" title=":)" width="20">

lmconfig
  • Antony_Hawkins's avatar
    Antony_Hawkins
    Icon for Employee rankEmployee
    7 years ago

    New, OS-agnostic version (basically, it's a merge of both of the above, that runs the relevant Linux- or Windows-specific commands dependent on the collector operating system).

    This is now the only one you need...

    v1.0.0: RLG279

    :)/emoticons/smile@2x.png 2x" title=":)" width="20">

  • Andrey_Kitsen's avatar
    Andrey_Kitsen
    Former Employee
    7 years ago
    18 hours ago, Rob said:
    503 : This LogicModule is currently undergoing security review. It will be available for import only after our engineers have validated the scripted elements.
     
    :(

     

    Hey @Rob , the modules are now available for importing.

    Enjoy

  • Rob's avatar
    Rob
    7 years ago
    503 : This LogicModule is currently undergoing security review. It will be available for import only after our engineers have validated the scripted elements.
     
    :(
  • Antony_Hawkins's avatar
    Antony_Hawkins
    Icon for Employee rankEmployee
    8 years ago

    Hi Tom,

    It has occurred as a possibility, yes. I believe it may already have been done. The problem is reliability - each hop would be an instance of the DataSource, which means if a route changes at all a hop may disappear (no data) or not be recorded until Active Discovery next runs. For routes that change frequently (particularly if they change in response to a routing problem) the returned data would not be particularly useful or reliable as a means of generating actionable alerts.

    As a diagnosis tool (rather than a pro-active alerter) the ConfigSource will allow a 'collect now' action, so for troubleshooting you can quickly and simply get a capture of the current route and hop times.

  • Tom_Lasswell's avatar
    Tom_Lasswell
    8 years ago

    Curious, have you thought about a datasource to calculate hop latency for each hop? We've had requests like that in the past and there's other tools like Ping plotter that do something similar to this. It's an interesting metric to know about if the latency is being caused by some hop down the line. 

  • Antony_Hawkins's avatar
    Antony_Hawkins
    Icon for Employee rankEmployee
    8 years ago

    Updated the Windows version to v1.5.0 to accommodate hop outputs recorded as <1ms.