How do I change the location of compliance import logs?

[#1]

Summary

This article covers how to modify the location where log files for the Compliance Import are stored in the Web UI versions of FNMS

Question

The logs for the inventory import, reconciliation or business import tasks are stored in C:\ProgramData\Flexera Software\Compliance\Logging\ComplianceReader by default - how can this be changed?

Answer

Within the C:\ProgramData\Flexera Software\Compliance\Logging\ directory is a 'ComplianceReader.config' file and this contains most settings related to the logging of ComplianceReader.exe jobs. The part related to the log file location has the following by default:

<appender name="file" type="Flexera.Common.Logging.Source.Custom.CleanupFileAppender, Flexera.Common.Logging">
<file type="log4net.Util.PatternString" value="%property{ComplianceLoggingPath}\ComplianceReader\%property{TenantUID}\importer%property{TenantUID}%property{Concurrent}-[%date{ddMMyyyy}]-[%processid].log" />
<appendToFile value="true" />

You can change the "log4net.Util.PatternString" tag to be something different, for example:

<file type="log4net.Util.PatternString" value="E:\LogFiles\ComplianceReader\%property{TenantUID}\importer%property{TenantUID}%property{Concurrent}-[%date{ddMMyyyy}]-[%processid].log" />

This will then store the compliance reader logs in E:\LogFiles\ComplianceReader using the same file name format as the default location (which is recommended).


NOTE: You must keep compliancereader.config in the C:\ProgramData\Flexera Software\Compliance\Logging directory or this change will be ignored. The logs will be written to the location specified but the config file itself must remain in the default location.

Additional Information

The same steps can be applied to any of the logs listed in C:\ProgramData\Flexera Software\Compliance\Logging\ directory as they all contain the "log4net.Util.PatternString" tag. If you do move these to another location, please ensure that you maintain the sub-folder structure e.g. ComplianceReader, BeaconEngine etc as this stops all of the logs going to a single folder.

In addition, you can also change the base logging directory used by the '{ComplianceLoggingPath}' variable (by default this is 'X:\ProgramData\Flexera Software\Compliance\Logging\ where I is the installation volume') to apply this to all log file types. To do this, please create the following registry entry as type 'String' (REG_SZ):

HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\LoggingBaseDirectory

And then set this to the base path you require, for example:

D:\Flexera Software\Compliance\Logging\


The above LoggingBaseDirectory string will allow all config files apart from ComplianceReader.config file to be moved away from the default location; ComplianceReader.config must remain in the default even with the above registry modification.

There is an enhancement - FNMS-18451: Beacon ProgramData folder should be customizable at install time - which once complete should allow ComplianceReader.config to be moved as well. This is currently planned for one of the 2017 releases.