- About LogicMonitor
- Cloud Monitoring
- Collector Overview
- Collector Installation
- Collector Management
- Collector Failover
- Collector Configurations
- Collector Troubleshooting
- Collector Groups
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
LogicMonitor Collectors have configuration files that can be used to control their behavior. These configuration files are located in the Collector’s installation directory. The default file path is:
- Linux: /usr/local/logicmonitor/agent/conf
- Windows: C:\Program Files (x86)\LogicMonitor\Agent\conf
Editing the Collector Config Files
The settings established in the Collector config files can be viewed on a per-Collector basis from within the LogicMonitor interface. Updates can also be made from the interface and it is highly recommended that you use the interface (and not manual modification of the local Collector configuration files) to make any required updates as there are safeguards in place in the UI to prevent errors. Manually modifying the local Collector configuration files should be done at your own risk.
In general, you will not need to change the vast majority of the settings found in the Collector configuration files. However, in the event that you need to modify your Collector configuration, you can do so by following the next set of steps.
To edit a Collector configuration file:
- Navigate to Settings | Collectors.
- From the Collectors page, find the Collector you wish to configure and click the corresponding cogwheel icon from the Manage column to display its settings.
- From the Support button’s dropdown menu, select “Collector Configuration.”
- Open the appropriate configuration file (e.g. agent.conf, watchdog.conf, etc.) and toggle the Edit <name>.conf manually slider to the right to enable editing.
- Once edits are complete, click the Save and Restart button to restart the Collector and apply the changes to the configuration file.
In this Article: