-
Title
What is the command that the LogMonitor agent uses on Linux or Unix hosts? -
Description
What are the commands that the FileLogMonitorAgent agent runs to get the content of the logs? This is sometimes required by sysadmins to grant permissions. -
Cause
The FileLogMonitorAgent agent deploys an executable binary to the monitored host. This is typically copied to /tmp on Unix-based systems, but the name is dynamically generated at the moment of deployment.
E.g. /tmp/fglam-FileLogMonitorAgent-fms-FMSServer--254140837-logmonitor
-
Resolution
A workaround for this, is to manually copy the executable binary from the Agent Manager to the monitored host to a specific directory.
The executable binary is located on the FglAM at:
$FGLAM_HOME/client/$IC_VERSION/bin/$PLATFORM
Copy the "logmonitor" file to the desired directory in the target monitored host. (E.g. /tmp/logmonitor)
After deploying this executable manually, the path to the executable needs to be specified in the Agent Properties:
- Navigation Panel | Dashboards | Administration | Agents | Agent Status
- Select the LogMonitor Agent that will monitor this host.
- Click on Edit -> Edit Properties
- Click on "Modify the private properties for this agent"
- Edit (or clone then edit) the "Monitored Hosts" Secondary Property list
- On the Remote Collector Executable column, add the full path and name to the logmonitor executable. (E.g. /tmp/logmonitor)
- If sudo will be required, make sure Secure Launcher is also properly specified. (E.g. /usr/bin/sudo)
- Click "Save Changes"
See documentation reference here.