Overview ConfigSources are templates based on Groovy or Powershell scripts that define how LogicMonitor should access, collect, and alert on your devices’ configuration files. Similar to other LogicModules, LogicMonitor installs with pre-configured ConfigSources for many common systems and applications. However, you can also create your own custom ConfigSources. Note: In order for ConfigSource data collection … Continued

Overview ConfigSources generate alerts based on config checks. Much like a datapoint and threshold in a DataSource, a config check monitors the availability of a config file or specific contents of the file and triggers an alert when defined criteria are met. There are five types of config checks, each providing a specific method to … Continued

Configs Tab Overview If configuration file monitoring is established for a resource, the config files are viewable as instances within the Resources tree underneath their associated device. Note: If the ability to monitor and alert on configuration files is not currently available in your LogicMonitor platform and you would like to learn more, reach out … Continued

Some devices may have multiple config files that should be monitored. For these devices, a ConfigSource should have multi-instance and Active Discovery enabled and have an appropriate script to discover and create desired config file instances. Note: If the ability to monitor and alert on configuration files is not currently available in your LogicMonitor platform … Continued

Overview From Settings | LogicModules | ConfigSources, you can search, add, edit, and create ConfigSources. Each ConfigSource has a definition that tells the LogicMonitor Collector how to SSH into a device, collect a config file, and when an alert should be triggered. Note: If the ability to monitor and alert on configuration files is not … Continued