If your environment does not allow the Collector to directly connect with the LogicMonitor data centers, you can configure the Collector to communicate through an HTTP proxy. Updating SSL and Proxy Settings By default, Collectors are not configured to use proxies. To change this, you will need to make updates to several proxy settings located in one of the Collector’s configuration … Continued
You can control the behavior of LogicMonitor Collectors using configuration files. The agent.conf configuration file is located in the Collector’s installation directory in the following default file path: You can view and update the settings in the agent.conf on a per-collector basis in the LogicMonitor user interface. Editing the Collector Configuration Files
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. The … 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
The service account used by the collector needs the ability to restart the collector services. Without this right, the collector and its associated watchdog will not be able to restart each other. If you find your collectors periodically going down after 8 hours or so, group policy permissions could be preventing them from restarting themselves or one … Continued
If you find you need to update the credentials provided when installing the collector, you must log on to the collector computer and update the services. It is common to have to update this account if you mistakenly installed the collector with Local System context and now need to monitor remote computers. To change the context … Continued
WinRM is Microsoft’s implementation of WS-Management Protocol, a standard SOAP-based firewall friendly protocol that allows hardware and operating systems from different vendors to interoperate. Thus, WinRM provides a way to get management data from a local computer or a remote computer using WS-Management protocol. Prerequisites You must meet the following prerequisites to configure and use WinRM … Continued
You can control the behavior of LogicMonitor collectors using configuration files. Configuration files are located in the collector’s installation directory at the following default file path: You can view and update the settings in the collector configuration files on a per-collector basis on the LogicMonitor user interface. It is recommended that you use the LogicMonitor … Continued
If your environment does not allow the Collector to directly connect with the LogicMonitor data centers, you can configure the Collector to communicate through an HTTP proxy. Updating SSL and Proxy Settings By default, collectors are not configured to use proxies. To communicate with HTTP proxies, you need to make updates to several proxy settings … Continued
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