Search the Community

Showing results for tags 'lmconfig'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • LogicModule Exchange
    • LM Exchange
    • LM Staff Contributions
  • Product Announcements
    • LogicMonitor Notices
  • LogicMonitor Product Q&A
    • Feature Requests
    • Ask the Community
    • From the Front

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Found 7 results

  1. Antony Hawkins

    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.0.0: RLG279 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. ',' *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.
  2. Hi Guys, We just implemented LMConfig and I'm trying to run a report to see what devices do not have the IOS configuration successfully downloaded. We have some legacy equipment still not Configured for SSH and TACACS accounts. so I'm trying to get out of having to manually hunting through all our devices to determine what ones need SSH configured and what ones need the TACACS account added. Even just being able to pull a report on all devices and what ones have the ConfigSources - IOS Configs field would be a big help. See attached pic for a visual Cheers and Thanks in advance Joel
  3. Currently, users need Manage rights to access the Config view. We need our junior sys admins to be able to view configurations without having the Manage rights. Please add a View only right for Config. The View Config right should only allow viewing of already collected configurations, but not permit Collect Now.
  4. The attached images show the CPU utilization when a Collector starts to collect configurations for our devices. We would like to have more options to stagger the collections of device config throughout the day. When the collections are all attempted at about the same time we see the CPU utilization jump and also get many failed collection warnings. Please make it so that we can specify different collections times for groups of devices.
  5. Please add LMConfig collection tasks to Task Queue graph, see attached. We experience config retrieval failures a lot but we are unable to see if this is due to queuing or too many other tasks at the same time.
  6. Currently the only option available is to alert each time a config retrieval fails. I would like to be able to say "only alert if config retrieval fails n number of times in a row". For some of my devices, I'm not so concerned if daily config retrieval fails, but I'd like to know about it if it was failing for 3 or more days in a row.
  7. Currently, a ConfigSource only provides a limited choice of options for when to collect a device configuration (1 hour, 4 hours, 8 hours, 1 day). There is not control over when the collection occurs and it appears to automatically happen at or around midnight of each day. We have 1,000+ network devices and we are seeing frequent config retrieval failures, and we suspect it is because the Collector is trying to do too much at once. We are distributing the load to a second Collector, but with a couple of hundred, some collections fail. Sometimes it's just one of the four Cisco configs, other times all four fail. The request is to be able to somehow tell the Collectors to stagger their config collections.