SysOrb Network Monitoring System Administrator's Guide: For version 3.6.0 | ||
---|---|---|
Prev | Chapter 3. Installing SysOrb | Next |
The LogChecks configuration has changed between SysOrb version 2.4.0 and 2.4.1. This means that any LogChecks configured on a version 2.4.0 system must be manually reconfigured on the new version in order to work after upgrading.
In version 2.4.0 all configuration data including paths to logfiles and matching rules was defined on the agent in the log configuration file (default: log.conf), specified in the agent configuration (default: agent.conf). This would make the log files available for monitoring on the SysOrb Server.
In version 2.4.1 and up only the paths for the logfiles to monitor is defined in the log configuration file. The matching rules configuration has been moved to the SysOrb server. Furthermore, the LogCheck logic has been much improved. This means you have a few more configuration options.
In order to move version 2.4.0 LogChecks to version 2.4.1 you need to do the following after upgrading your SysOrb server (See the User's Guide and Section 8.5 for more information on LogChecks):
Rename the log configuration file (default: log.conf) on the SysOrb Agent host to log.conf.old.
As an example, we take that the above file contained a LogCheck definition like this:
[Syslog] logfile='/var/log/messages'; incremental; rules '^RPC: garbage': warn; '^nfs:.*server OK': ok; '^nfs:': warn;
Make a new log configuration file in place of the original and add the path of each log file you want to monitor, one path per line.
With the above example, you would insert this one line:
/var/log/messages
Auto-upgrade the agent, or manually upgrade the Agent.
If doing manual upgrade, make sure to restart the SysOrb Agent.
Using the Web interface go to the AgentCheck configuration dialog. In order to do this, click configure, find the host and click edit. Click AgentChecks. Click 'Rescan'. Wait for next Agent Checkin (default: 30 seconds) and Click 'Show all'. Click the 'log checks' folder and click down through the tree to reach the desired log file. Click '[Add]' on the log file to be monitored.
Copy the rule lines (not including the rules keyword itself) from the 'log.conf.old' file, to the Rules text box in the web interface.
With the above example, you would enter the following in the rules field:
'^RPC: garbage': warn; '^nfs:.*server OK': ok; '^nfs:': warn;
Click OK.
Be sure to read the User's Guide and Section 8.5 for more information the LogChecks and the enhanced configuration options.