Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
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 you through the steps to install a Collector in your LogicMonitor portal.
LogicMonitor also supports installing and running the Collector in a Docker container. Installation of a containerized Collector does not support all install options. For example, you can only run the full installation, not the bootstrap, and you will need to run the Collector process as root. See Installing the Collector in a Container.
In your LogicMonitor portal, navigate to Settings | Collectors | Add | Collector:
Follow the steps in the Add a Collector dialog to complete and verify the Collector installation.
The first step in adding a Collector is deciding which device will host the Collector.
For each location of your infrastructure, we recommend that you install a Collector on a Windows or Linux server that is physically close to or on the same network as the resources it will monitor. Most often, Collectors are installed on machines that function as syslog servers or DNS servers.
To ensure reliability, the Collector should not communicate across the internet to poll resources in another datacenter, through firewalls or network address translation (NAT) gateways.
The following table lists general requirements for choosing a server to host the Collector.
We recommend that you check the option: Monitor the Device on which the collector is installed. This will allow you to keep track of the CPU utilization, disk usage and other metrics to ensure that the Collector is running and keeping up with its data collection load. See Monitoring Your Collectors.
You may also assign the Collector device into a Device Group. If you leave the device “Ungrouped”, LogicMonitor will automatically add it to the dynamic group “Collectors”. See Device Groups Overview.
The next step in adding a Collector is specifying the type, version, and the monitoring capacity (size) for the Collector you will install onto your server. You may also assign the new Collector to a Collector Group.
Select the appropriate Collector download file for your server:
The type of Collector you choose to install depends on the resources it will monitor. For example, to collect data from Windows devices, you need to install the Collector on a Windows server.
Select from the available General Release and Early Release Collectors.
You can always change the version by uninstalling and installing a new Collector.
The Collector size refers to the monitoring capacity for the Collector.The number of resources that a Collector can monitor depends on the data collection method that it uses (such as SNMP, JDBC, WMI, and so on). See Collector Capacity.
You can choose from four available Collector sizes:
You may assign the new Collector to an existing Collector Group or create a new group. Collector Groups pool your Collectors based on their physical locations, defined environments (QA, Development, or Production), or if you are an MSP customer and streamlines the configuration and management of multiple Collectors. See Collector Groups.
This step provides options for you to download the installer file for the collector you selected.
Under Download a Collector, you can choose between two installer packages:
1. Download the installer file directly to your server or use one of the download command options.
For Windows, we provide options to download and install using PowerShell or a URL. Click on the option to copy the download command to your clipboard and then run it on your server.
2. After downloading the installer onto your Windows server, open it to start the Install Shield Wizard.
The Install Shield Wizard will extract the binary and prompt you for credentials. These credentials will correspond to the account that the Collector will run under, which may be Local System or a domain account with local administrator permissions .
The LogicMonitor Collector service must be granted “Log on as a service” under “Local Policy/User Rights Assignment” in the Windows server’s local security policy settings. See Troubleshooting Windows Collectors.
If the Windows server is running antivirus software, you will need to add a recursive exclusion for the LogicMonitor Collector application directory. See About the LogicMonitor Collector.
Note: There are a number of requirements for Linux environments:
1. Download the installer file directly to your server (if your server supports web browsing) or onto another server and use a file transfer option (such as scp) to copy it to the server where you will install the collector.
For Linux, we also provide options to download and install using cURL or Wget. Click on the option to copy the download command to your clipboard and then run it on your server.
2. After downloading the installer onto your Linux server, change the permissions to make the binary executable:
# chmod +x <installer-file>.bin
3. Run the executable:
When the installation completes, you will see a message that it installed successfully.
Note: Installing the Collector on Linux creates a default user, called logicmonitor, to run the Collector as a user without root privileges. Although you can select a different user or run as root, LogicMonitor recommends using this logicmonitor user created by the install script.
If you have issues with your Linux collector, see Troubleshooting Linux Collectors.
After successfully installing the Collector on your Windows or Linux server, return to the “Add a Collector” dialog in LogicMonitor and verify that the Collector is connected to your portal.
Each Collector has a name or ID that is registered with the LogicMonitor server when you download the Collector. The Collector’s hostname refers to the IP address or DNS name of the server that the Collector has been installed on.
After installing a Collector, you can start adding resources to be monitored.
In This Article