In addition to the standard interactive Collector installation process, there is also a non-interactive “Silent” installation mode. The Silent mode is convenient if you are automating installation and are not around to manually answer prompts about user and proxy details.

In this article, we have explained the steps to install Windows and Linux Collectors. We recommend that you read the support article Installing Collectors to understand all the details about Collector installation.

Installing Windows Collectors

Before you install Windows Collectors, you must consider the following points:

• Ensure to specify the Collector to run as a privileged user. If you do not, the Collector will install and run as a local system. The local system may not have sufficient permissions to monitor other Windows hosts remotely.
• Ensure that there is no space following any colon when you specify the parameters.
  For example, /p:’Ex@ml!eP@5Sw0rd’ is acceptable but  /p: ’Ex@ml!eP@5Sw0rd’ is not.
• Ensure to use single quotes if the system password or the proxy password has special characters. For example, /p:’Mycroft+Holmes‘
• These parameters can be passed either after the Collector installer .exe or after the PowerShell installation URL (either bootstrap or full package installation). Ensure that the PowerShell window is open in the Administrator mode.
• The parameter /s: can be included if the Collector version is 30.102 or higher.

To install Windows Collectors in Silent mode, follow these steps:

1. In your LogicMonitor portal, navigate to Settings | Collectors | Add | Collector.
   
   
   
2. In the Add a Collector dialog, select Windows 64-bit and specify the version and memory details.
3. Select >_PowerShell and copy the PowerShell URL.
4. Launch PowerShell in Administrator mode and paste the copied URL to append the parameters.

[powershell URL or .exe] [/k] [/r:] [/d:] [/q] [/s:] [/a:] [/p:] [/m] [/PROXYHOST:] [/PROXYPORT:] [/PROXYUSER:] [/PROXYPASS:]

Example:

LogicMonitorSetup_6207.exe  /q /a:Administrator /p:'Mycroft+Holmes' /PROXYHOST:10.55.21.60 /PROXYPORT:3128 /PROXYUSER:SherlockHolmes /PROXYPASS:'221_B@BakerStreet'

For Windows Collector, the following parameters are supported:

Once the installation is complete, a message confirming successful installation is displayed on the PowerShell terminal.

Installing Linux Collectors

Before you install Linux Collectors, you must consider the following point:

• The parameters work for both bootstrap and full installation methods. Ensure that you first make the binaries executable (using chmod) before passing the parameters.
• The parameter -s can be included if the Collector version is 30.102 or higher.

To install Linux Collectors in Silent mode, follow these steps:

1. In your LogicMonitor portal, navigate to Settings | Collectors | Add | Collector.
2. In the Add a Collector dialog, select Linux-64 bit and specify the version and memory details.
3. Select Get cURL cmd and copy the URL.
4. In the terminal, paste the copied URL and append the necessary parameters to the installation URL.

./LogicmonitorSetup123.bin [-n] [-h] [-y] [-m] [-s size] [-d install path] [-u install user] [-p proxyHost:port] [-U proxyUser] [-P proxyPass]

Example:

sudo chmod +x LogicmonitorSetup123.bin
sudo ./LogicmonitorSetup123.bin -y -p 10.55.21.60:3128 -U SherlockHolmes -P 221BBakerStreet

For Linux Collectors, the following parameters are supported:

Once the installation is complete, a message confirming successful installation is displayed on the terminal.

Verifying the Installation

The steps to verify the installation for both Windows and Linux are similar.

To verify, follow these steps:

1. On the Add a Collector dialog box, under 4. Verify Connection, select the Collector installation successfully completed check box.
2. Click Verify Connection.
   
   
   
   A pop-up message confirming successful installation is displayed. This message indicates that the Collector is connected to your portal.
   

LogicMonitor stores sensitive information including credentials, secrets, etc., for hosts, devices, services. LogicMonitor also offers integration with Credential Vault and provides better control over credentials management to users using their own Credential Vault. The LogicMonitor Collector provides the integration with Delinea as a Credential Vault solution. For more information, see Delinea Secret Server documentation. 

Prerequisites

• The Delinea Vault Integration requires EA Collector versions 30.102 or higher. For more information on integrating the Delinea Vault with LogicMonitor Collector, see Integrating Credential Vault Properties.
  
• Verify access of Delinea Secret Server API using Postman client. For more information, see Delinea Secret Server REST API.

Delinea Secret Server REST API:

The Delinea Secret Server publishes REST API to manage various entities. For more information, see https://docs.delinea.com/secrets/current/api-scripting/rest-api-reference-download/index.md.

The Secret Server (SS) REST API guides are version-specific. Please ensure you refer to the correct version Secret Server guide.

The LM Delinea Secret Server integration uses the OAuth2 token-based REST API of the Delinea Secret Server. In this approach, you receive the OAuth2 token for authentication, which is used to perform the various entity operations of the Delinea Secret Server.

Configuring Delinea Vault 

To configure the Delinea vault, complete the following steps: 

1. Configure the vault properties on the devices. The properties consist of the vault metadata and vault keys. For more information, see the Delinea Vault properties section.

2. Once the vault properties are configured, set the vault.bypass agent configuration as false.

Delinea Collector Agent Configuration Settings:

The below table contains the collector agent configuration related to the vault.

You can view the agent configuration properties by navigating to Settings > Collector > click the gear next to the required collector name > Support > Collector Configuration.

Delinea Vault properties

Vault properties, such as Vault Metadata and Vault Keys for the Collector, can be configured at the device or device group level.

Vault Metadata

The following table lists the Vault Metadata properties.

Configuring Delinea lmvault.keys

You can configure lmvault.keys in the following three ways: secret id, secret path, and a combination of secret id and secret path.

• Secret id—lmvault key value can be configured with the secret id. This is the most efficient method and is recommended by Delinea.
  
• Secret path—LogicMonitor provides another out-of-the-box approach for configuring the lmvault.key value. lmvault value consists of the secret path and secret name. 

LogicMonitor calls the Delinea API to get the secret id for these secret paths, and these secret ids are further used for the credentials retrieval. 

Example:

LogicMonitor provides the two approaches for the secret id retrieval using the secret path: 

• Default Approach—LogicMonitor searches for the folder and Secrets. In this approach, the folders and the secrets are searched to form the secret_path_name relation with secret id.
• Delinea Reporting—LogicMonitor uses Delinea reporting to retrieve the secret id using a secret path. This is an efficient approach for the secret path as compared to the Default Approach. 

Note: Ensure that you can access the Delinea Report “What secrets a user can see” in the Delinea Secret Server portal. For more information on configuring the Delinea reports, see Configuring Delinea Report Properties.

• A combination of secret ID or secret path along with a Delinea field—You can configure devices to pull the secret values for a property from the secret ID or secret path. The field name is attached to the property to fetch the secret value from the Delinea field. The .lmvault property is configured to have the information of the Delinea field appended within the enclosed symbol “<>” at the end. You can use the template RecordID<FieldName> /  RecordPath:Name<FieldName>. For example,

Configuring Delinea Report Properties

To configure Delinea report properties, complete the following steps:

1. Navigate to Settings > Collector > select the required collector and click the Gear icon.

2. On the Manage Collector dialog box, select Collector Configuration from the Support drop-down list.

3. Click the Agent Configurations tab and enter the following Delinea report properties :

Troubleshooting

1. How to confirm API using postman?

Ans: The LogicMonitor Delinea Secret Server integration uses the OAuth2 token-based REST API of the Delinea Secret Server. You will receive the OAuth2 token for authentication, which is used to perform the various entity operations of the Delinea Secret Server. The APIs can be confirmed using the postman. To confirm APIs using Postman, refer to the following images:

2. How to get collector vault logs?

Ans: To get the collector vault logs, use the !tail debug command. The vault logs are a part of the wrapper.log file, which you can directly access. For more details, refer to the following screenshot:

 3. How to enable the debug logs for the vault to get more data?

Ans: To enable the debug logs for the vault, complete the following steps:

1. Navigate to Settings > Collectors > select the required collector.

2. On the Manage Collector, select Collector Configuration from the Support drop-down list.

3. Click the Agent Config tab and set the logger.level value as debug.

4. Once you have added the configuration details, click on Save and Restart.
Refer to the following image:

LogicMonitor stores sensitive information including credentials, secrets, etc for hosts, devices, services. The LogicMonitor Collector provides the integration with CyberArk as a Vault solution. For more information, see CyberArk documentation. 

To integrate the CyberArk Vault with LogicMonitor Collector, see Integrating Credential Vault Properties.

Prerequisites

• The CyberArk Vault Integration requires EA Collector versions 29.108 or higher. Note that support for the vault integrations are not yet available in GD Collector versions.

CyberArk Application Authentication Methods

The CyberArk Credential Provider provides multiple methods to authenticate applications. For more information, see CyberArk documentation on Application authentication methods and Add applications.

LogicMonitor Collector and CyberArk integration support the following methods for the application authentication:

1. Allowed Machines
2. Path
3. Hash
4. Client Certificates.

Note: We recommend configuring Dual Accounts in CyberArk for widely-used, frequently rotated credentials to avoid account lockouts during rotation. For more information, see CyberArk documentation on Configure dual accounts.

Authentication to Privileged Access Security (PAS) Solution

The CyberArk AIMWebService application is deployed on the IIS Server. LogicMonitor Collector and CyberArk integration uses Basic Authentication to the IIS Server.

You can log on to the Vault by using the password that is provided to you. After logging into the Vault, we recommend that you change your password.

CyberArk Collector Agent Configuration Settings

The following  table contains the collector agent configuration related to the Vault:

Vault properties

Vault properties, such as Vault Metadata and Vault Keys for the Collector, can be configured at the device or device group level.

Vault Metadata

The following table lists the Vault Metadata properties.

Vault Keys

Vault keys need to be specified at the device level with suffix .lmvault. For example, ssh.user information should have the key specified as ssh.user.lmvault.

LogicMonitor Collector and CyberArk Vault integration

1. Multi-Safe support: Specify the multiple safes under a device to retrieve the credentials from Multiple Safe. 

2. Multi-Vault support: You can use multiple vaults for the devices under the collector. Each of the devices can point to a single Vault.

3. You can call Vault API over HTTP or HTTPS. However, if you are calling the Vault APIs over HTTPS, you must configure the RootCA cert. For more information, see RootCA cert.

4. You must complete the CyberArk Authentication. For more information, see  CyberArk Application Authentication Methods section. 

Note: Device-specific cache is implemented at the Collector to avoid frequent requests to the Vault API.

Configuring CyberArk certificates

You must configure the following CyberArk files at the requesting application side:

• RootCA cert
• client.pfx file
• client.cert and client.pem files

RootCA cert

You must enable the Require SSL checkbox for including the RootCA cert file in the trust store of the requesting application’s server. 

To import RootCA cert for the collector, complete the following steps:

• Windows: RootCA cert must be imported in the collector’s trust store in JRE within the Collector installation folder. By this, the CyberArk endpoint will be considered a trusted source.
  
  

• Collector’s installation directory. The default file path is:

• Linux Collectors: /usr/local/logicmonitor/agent/conf
/agent.conf
• Windows Collectors: C:\Program Files (x86)\LogicMonitor\Agent\conf\agent.conf

To import RootCA certificate in the collector’s jre default trust store, use the command:

keytool -importcert -file Path_For_Root_CA_Folder/RootCA.crt -alias CyberArkRootCA -keystore /usr/local/logicmonitor/agent/jre/lib/security/cacert -storepass Store_Password

client.pfx file

CyberArk provides client.pfx file which is a pkcs12 file containing the client certificate and client key. The client certificate and client key must be present in the HTTP request to authenticate the application request to IIS. As the client.pfx is a key store containing the client certificate and client key, this file can be directly used to authenticate the collector’s request with Vault Service deployed on IIS.

To use the client.pfx file, set the below properties at the device/device group level at the Santaba:

vault.meta.keystore.path=Path_For_Client_Keystore_Folder/client.pfx
vault.meta.keystore.pass=Password_For_Client_Keystore

Note: The default keystore password for client.px store is CyberArk 1. We recommend that you change this password.

client.cert and client.pem files

Though CyberArk provides the client.pfx key store containing the client certificate and client key, it still provides the client.cert and client.pem files. These files can be used to create the custom key store. Such a custom key store can be used to authenticate the applications/collector’s request to the IIS server on which Vault Credential Service is deployed.

To create the key store using client.cert and client.pem files, use the below command.

openssl pcks12 -export -in Client_Cert_Folder/client.crt -inkey Client_Key_Folder/client.pem -out myclient.pfx -passout pass:Password_For_Generated_Keystore

The Credential Vault integration for the LogicMonitor Collector makes it possible to store and manage sensitive information (including credentials and secrets for hosts, devices, services, etc.) in an external credential vault. 

LogicMonitor Collector supports the following vault integrations:

• CyberArk Vault Integration
• Delinea Vault Integration

Integrating Credential Vault Properties

1. In LogicMonitor, navigate to Resources > Device> required Collector > Info tab.
   For more information on vault properties, see Adding Vault Properties.
2. Click Settings on the left panel and select Collectors.
3. Select the required Collector and click the Settings icon under the Manage column.
   

4. On the Manage Collector dialog box, select Collector Configuration from the Support drop-down list.
   
5. Ensure to set the vault.bypass value to false in agent.conf. Additionally, you can add the required agent configuration properties to set the Collector. For more information, see  Collector Configurations.
   

Collector Configurations

The following table lists the configuration properties to set in the Collector agent.conf.

Adding Vault Properties

For adding vault properties, such as Vault Metadata and Vault Keys, navigate to Resources > Device > Collector, click Info on the Collector page.

Vault Metadata

The following table lists the Vault Metadata properties.

Vault Keys

Vault keys need to be specified at the device level with suffix .lmvault. 

LogicMonitor supports installing and running the Collector in a Docker container for the following services:

• Microsoft Azure Kubernetes Service (AKS)
• Amazon Elastic Kubernetes Service (EKS)
• Google Kubernetes Service (GKS)

Installation of a containerized Collector does not support all options–These are noted under Limitations. See Dockerhub to find the Docker image for running the LogicMonitor Collector.

Prerequisites

• LogicMonitor API Token Access ID and Access Key with sufficient permissions to perform the requested actions.

Limitations

• The installation does not support the “bootstrap” option. You can only run the “full package” installation.
• The collector deployed in a Docker Container is based on Linux. Linux collectors do not monitor Windows-based WMI collectors.

Installation Example

The following example creates a new Collector named “lm-collector”, that is a large Collector with the latest version:

docker run --name lm-collector -d \
  -e account=<your portal name> \
  -e access_id=<your api access id> \
  -e access_key=<your api access key> \
  -e backup_collector_id=<backup-collector-id> \
  -e COLLECTOR_NON_ROOT=false \
  -e collector_group=DockerCollectors \
  -e collector_size=large \
  -e description='My Dockerized Collector' \
  -e enable_fail_back=yes \
  -e escalating_chain_id=1 \
  -e resend_interval=60 \
  -e suppress_alert_clear=no \
  -e cleanup=true \
  -e proxy_url=<your proxy url> \
  -e proxy_user=<your proxy user> \
  -e proxy_pass=<your proxy password> \
logicmonitor/collector:latest

Required Parameters

Optional Parameters

Configuring agent.conf Properties for the Collector

You can dynamically configure certain advanced Collector parameters by mounting a YAML configuration file inside the container.
This method is useful for setting agent.conf properties that are not easily controlled through environment variables. 

1. Create a file named collector-conf.yaml in the following format:

debugIndex: 0
agentConf:
  - key: resend_interval
    value: 2
  - key: service.read_timeout
    value: 180
  - key: escalationChainId
    value: 2

2. Mount the file when deplyoing your Collector container as follows:

docker run \

 -v ~/collector-conf.yaml:/etc/collector/collector-conf.yaml \

 logicmonitor/collector:latest

Memory Requirements

The containerized Collector installation supports all Collector sizes. The size of the Collector you choose to install has the following minimum memory requirements:

For more information, see Collector Capacity.

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 default file path is:

• Linux Collectors: /usr/local/logicmonitor/agent/conf/agent.conf
• Windows Collectors: C:\Program Files\LogicMonitor\Agent\conf\agent.conf

As discussed in Editing the Collector Config Files, it is highly recommended that any changes or additions to the agent.conf file be made via the LogicMonitor UI (from the Collectors page) as there are safeguards in place to prevent errors. Manually modifying this file from the local Collector is not recommended and is performed at your own risk.

There are more than 600 settings that can be configured in the agent.conf file, providing you with very granular control of your Collector’s behavior and operations. Some settings display in the file by default; some may need to be added if you’d like to override the default values that are defined in the code. All values declared in the agent.conf file supersede values defined in the code.

Note: In the majority of cases, your Collector will run as needed out of the box as long as it is appropriately sized. As a general rule, we recommend approaching the customization of agent.conf settings with caution and, ideally, at the direction of a support representative.

Settings are listed next, organized by function.

General Collector Settings

Data Collection Method Settings

Data collection settings are organized by the following data collection methods:

Global Data Collection Settings

AWS Data Collection Settings

BatchScript Data Collection Settings

CIM Data Collection Settings

Data Pump Data Collection Settings

DNS Data Collection Settings

ESX Data Collection Settings

JDBC Data Collection Settings

JMX Data Collection Settings

Memcached Data Collection Settings

Mongo Data Collection Settings

NetApp Data Collection Settings

Perfmon Data Collection Settings

Ping Data Collection Settings

Script Data Collection Settings

SDK Script Data Collection Settings

SNMP Data Collection Settings

TCP Data Collection Settings

UDP Data Collection Settings

Webpage Data Collection Settings

WMI Data Collection Settings

Xen Data Collection Settings

Event Collection Method Settings

Event collection settings are organized by the following collection methods:

• Global
• HTTP
• Log file
• Script
• SNMP trap
• Syslog
• Windows event log

Global Event Collection Settings

HTTP Event Collection Settings

Log File Event Collection Settings

Script Event Collection Settings

SNMP Trap Event Collection Settings

Syslog Event Collection Settings

Windows Event Log Collection Settings

Active Discovery Settings

AutoProperties Settings

ConfigSource Settings

Credential Vault Settings

The following table lists the configuration properties to set in the Collector agent.conf.

CSProxy Settings

LM Logs

For more information about syslog properties, see Configuring Resource Mapping in Sending Syslog Logs.

Logger Settings

Logger settings control Collector logging. They are not related to LM Logs or EventSources.

Network Traffic Flow (NetFlow) Settings

PowerShell Settings

Proxy and SSL Settings

Remote Session Settings

SBProxy Settings

SSE Settings

Topology Mapping Settings

Watchdog Settings

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 higher allow you to store these Auth tokens in a cache between collection intervals until the token expires.

Using ScriptCache

The ScriptCache class contains the following methods:

The expireIn value is optional and can be set for each key that is stored in the cache. If the value is not set for a particular key, the default expire timeout will be the value set in the collector.script.cache.timeout in agent.conf. For example:

collector.script.cache.timeout=30 //30 minutes

New scripts with ScriptCache won’t work with older versions of the Collector. Importing ScriptCache will throw an exception in older collectors. The following script example will work in all Collectors:

def scriptCache
try {
    scriptCache = this.class.classLoader.loadClass("com.santaba.agent.util.script.ScriptCache").getCache();
    //new way
    String token = scriptCache.get("token1");
    if(token == null){
         //make connection, fetch new token and store it in cache
         scriptCache.set("token1", "asfioajfiqu920200rdaoj9au");
    } else{
         //make connection
    }
} catch (Exception ex) {
    //old way
}

In this script, if the import statement fails for the ScriptCache class, it will default to the old way of saving tokens with files. If it passes, it will use ScriptCache.

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. For example, on RedHat ES/CentOS glibc-2.5-24 and earlier does not respect DNS TTLs correctly, meaning that you will need to run a later version or disable NSCD.

If the NSCD returns a stale record for an hour, it would impact your ability to monitor devices and communication between LogicMonitor datacenters.

SE Linux

Some distributions of Linux (such as RedHat, CentOS, and Fedora) may have Security-Enhanced (SE) Linux enabled, which may restrict access and permissions that can impact the Collector’s ability to monitor.

Use the /usr/sbin/getenforce or /usr/sbin/sestatus commands to check the status of SELinux.

• The getenforce command returns Enforcing, Permissive, or Disabled. The command returns Enforcing when SE Linux is enabled.
• The sestatus command returns the SE Linux status (Enabled, Disabled) and the mode (Enforcing, Permissive, Passive) being used.

If you are having monitoring problems in your Linux server and SE Linux is enabled, you may be able to use Permissive mode to review the logs and identify the issue:

setenforce Permissive

In Permissive mode, more denials are logged because actions that would otherwise be denied in Enforcing mode are allowed.  After you run the Collector services in permissive mode and SE Linux logs to identify the permissions that need to be enabled, you should enable the necessary permissions.

To put SE Linux back into enforcing mode, run:

setenforce 1

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 local security policy.

To update the local security policy:

1. Log on to the Collector host as a Local Administrator.

2. From CMD, PowerShell, or Run launch secpol.msc.

3. Expand “Local Policy” and click “User Rights Assignment”.

4. Right-click “Log on as a service” and select “Properties”.

5. Click “Add User or Group” to add the account which is to run the LogicMonitor Collector services.

6. In the “Select Users or Groups” dialog, find the user account and click “OK”.

7. In the “Log on as a service” properties window, click “OK” to save your changes.

If you are not able to make these changes (for example options may be greyed out or unavailable), you may need to look into what is enforcing the local security policy settings on the host–it may be the local or domain Group Policy settings or another configuration management tool.

Windows Monitoring Scenarios

Common monitoring scenarios on Windows use WMI and Perfmon. If you have issues related to monitoring WMI or Perfmon, refer to the following resources:

• Troubleshooting WMI
• Troubleshooting Perfmon Access
• Monitoring Services and Processes

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.

Installing the Collector in a container

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.

Installation Settings

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.

Choose Where to Install a Collector

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.

Requirements for Collector Servers

The following table lists general requirements for choosing a server to host the Collector.

Monitor the Collector’s Performance

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.

Select a Collector

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.

Collector Type

Select the appropriate Collector download file for your server: Linux or Windows. For both Windows and Linux, we support only 64-bit Operating System. 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.

Collector Version

Select from the available General Release and Early Release Collectors.

You can always change the version by uninstalling and installing a new Collector.

Collector Size

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:

Assign Collector Group

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.

Download and Install

This step provides options for you to download the installer file for the collector you selected.

Installer Options

Under Download a Collector, you can choose between two installer packages:

• “Bootstrap” downloads a smaller installation package (~500kB) for a faster install using the LogicMonitor CDN.
• “Full package” downloads the installation package which is approximately 200MB.

Installing a Windows Collector

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 a user account with the least privilege permissions or a Local System account. 

If this Collector is not monitoring other Windows systems:

• Run the service as a Local System. This is not recommended for the least privilege.
• Run the service as a user account with the least privilege permissions. For more info on credential configuration, see Credentials for Accessing Remote Windows Computers.
• Are not part of the same domain, run the service and connect to each resource with the least privilege permissions. You may choose to set up the password so that it doesn’t expire to reduce authentication issues between the Collector and its monitored resources. See Credentials for Accessing Remote Windows Computers.

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.

Installing a Linux Collector

Note: There are a number of requirements for Linux environments:

• For Collectors running version 28.500 (or higher numbered versions), the Bourne shell is required for the Linux installation script. You may need to install the “vim-common” package to get the “xxd” binary that the installer depends on.
• For Collectors running version 28.100 (or higher numbered versions), the “sudo” package must be installed on Linux when running the Collector as a non-root user. The installer will also make additions to /etc/sudoers to handle service restart and memory dumps.
• In Linux environments with the Collector running in containers, the Collector must run as root: suid root is /bin/ping.

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:

# ./<installer-file>.bin

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 want to install Linux collector as root, please contact LogicMonitor product team or technical support team.

If you have issues with your Linux collector, see Troubleshooting Linux Collectors.

Verify Connection

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.

Collector Hostname

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.

• For Linux, the Collector will resolve the hostname by running the hostname -f or hostname commands. If both commands fail, the hostname defaults to: localhost.localdomain.
• For Windows, the hostname is a combination of the domain and computername.

Next Steps

After installing a Collector, you can start adding resources to be monitored.