Overview LogicMonitor Collectors have configuration files that can be used to control their behavior. The most robust of these configuration files is the agent.conf file. Data collection, Active Discovery, auto properties, event collection, and many other Collector-specific behavior settings are maintained by this configuration file. The agent.conf file is located in the Collector’s installation directory. … Continued
This feature is available for Collector versions 29.100 or higher. Overview Collector scripts require authentication tokens to communicate with certain entities. In older versions of the Collector, these Auth tokens are stored in files, which means that read and write operations are done in every LogicModule that needs to access the files. Collector versions 29.100 or … Continued
We’ve compiled some helpful tips for troubleshooting common Linux Collector issues. Name Service Caching Daemon (NSCD) The LogicMonitor Collector makes DNS queries to resolve the hosts it is monitoring and to determine which LogicMonitor servers to report data to. If you are running an NSCD, you should make sure that it respects positive DNS TTLs. … Continued
We’ve compiled some helpful tips for troubleshooting common Windows Collector issues. Error 1069 A common error encountered for Windows Collectors: Error 1069: The service did not start due to a logon failure. The account used to run the LogicMonitor Collector service on Windows must have “Log on as a service” rights on the host machine’s … Continued
The LogicMonitor Collector monitors your infrastructure and collects the data defined by LogicModules for each resource in that location. You do not need to install a Collector on every device, instead one Collector on a server should be used to monitor all the resources in that location. See About the LogicMonitor Collector. This article walks … Continued
