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
When you delete a collector from your LogicMonitor account, the collector and Watchdog services stop and the collector uninstalls itself. If it does not happen, you can manually stop the collector and Watchdog services and uninstall the collector from the device. Prerequisite Before you delete a collector, you must re-assign the devices monitored by that … Continued
You can restart a collector from the LogicMonitor platform or from the collector host. When the collector is up and running, you can restart the collector from the LogicMonitor platform. If the collector is down or dead, you have to restart it from the collector host. Restarting from LogicMonitor Portal To restart a collector from … Continued
Collectors have the ability to cache collector data to disk. This enables collectors to store data in your environment during periods where your collector is unable to deliver data to your LogicMonitor account (example, as a result of network issues). Once your collector reaches your account again, the buffered data is communicated to our servers, … Continued
The amount of data that a Collector can handle depends on the Collector’s configuration and resources. You can monitor the data collection load and performance of your Collector to minimize disruption and notify when a collector is down. See Monitoring your Collectors. If you have a large environment, and are experiencing alerts on the Unavailable … 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
Typically, collector events include errors related to data collection tasks and the stopping/starting/restarting of the collector services. You can look through these events to debug your collector issues. To view collector events, follow these steps:
Grouping your collectors into logical units can streamline account management, simplify end user permission settings, improve efficiency, and more. LogicMonitor supports two types of collector groups: Standard Collector Groups Standard collector groups primarily assist with collector organization. For example, you can to organize collectors into groups based on any of the following shared characteristics: Auto-balanced … Continued
LogicMonitor Collector monitors your infrastructure and collects data defined by LogicModules for each resource in that location. You do not need to install Collector on every device, instead one Collector on a server can be used to monitor all the resources in that location. See About the LogicMonitor Collector. Installing Collector in a Container LogicMonitor … Continued
Security of customer data and our portal is of paramount importance to LogicMonitor. We ensure that vulnerabilities are preempted and handled quickly. Additionally, many customers requested for reducing the privileges to run Windows collectors. As part of our initiative to reduce attacks by malicious entities, we have adopted a principle of least privileges. To implement … Continued
