Configure logging levels with Nlog

IT Asset Management (Cloud)

In IT Asset Management, log files are generated by the Nlog logging platform for the beacon. Note: The Nlog logging platform does not apply to the agent.

Nlog allows users to write to several different targets (database, file, console) and change logging configuration on an ad hoc basis. For more information about Nlog, visit Nlog's website.

It's common for customers to change the log level value in a config file. The highest log level value is FATAL, followed by ERROR, WARN, INFO, DEBUG and the lowest log level value TRACE. When a particular log level is set in a config file, higher log levels will also display. For example, on setting the INFO log level, the FATAL, ERROR and WARN log levels will also display.

This determines the log type. For example, INFO will provide informational messages in the log files.

Some customers may also change the MaxAgeDays value (default = 30) to 90 (this value determines how many days the logs will be kept for). Some log files have config settings for how large the log file is allowed to become before it's deleted (10mb, 50mb).

The default base directory containing Nlog config files for IT Asset Management is C:\ProgramData\Flexera Software\Compliance\Logging\. Generated log files are saved to the same location.

This base directory may be overridden by setting the registry entry HKLM\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\LoggingBaseDirectory.

Each config file is an XML document containing Nlog configuration options. The logging level can be edited using a text editor. For example, see the beacon Nlog config file below.

The beacon Nlog config file:

<nlog xmlns="" xsi:schemaLocation="NLog NLog.xsd"
      <add assembly="Flexera.Common.Logging"/>
      <!-- the targets to write to -->
      <!-- write logs to file -->
      <target xsi:type="Console" name="console" layout="[${date:format=yyyy-MM-dd HH\:mm\:ss.fff}] [${level:padding=-5:fixedLength=true:uppercase=true}] ${message:exceptionSeparator=\r\n:withException=true}" />
      <target xsi:type="File" name="file" maxArchiveFiles="1000" archiveNumbering="Date" filename="${gdc:item=ComplianceLoggingPath:whenEmpty=${baseDir}}/InventoryBeacon/inventorybeacon.log"
      archiveEvery="Day" archiveDateFormat="yyyy-MM-dd" layout="${date:format=yyyy-MM-dd HH\:mm\:ss,fff} [${logger:padding=-22:fixedLength=true}] [${level:padding=-5:fixedLength=true:uppercase=true}] ${message:exceptionSeparator=\r\n:withException=true}" />
      <logger name="*" minlevel="Info" writeTo="file" />
      <logger name="*" minlevel="Info" writeTo="console" />

To change the logging level value, two different levels towards the end of the config file can be configured (<logger name="*" minlevel="Info" writeTo="file" /> and <logger name="*" minlevel="Info" writeTo="console" />). One level outputs to a file and the other logs to the console. There are six levels:

Logging level Details

Informational messages


Error messages


Warnings which don't appear to the user of the application


Less detailed and/or less frequent debugging messages


Very detailed log messages, potentially of a high frequency and volume


Fatal error messages. After a fatal error, the application usually terminates

Configuring logging for the beacon server

The following table provides default logging configuration details for various beacon server components & subsystems.

Component / Subsystem Location under C:\ProgramData\Flexera Software\Compliance\Logging

Active Directory import

This log captures the execution of Active Directory imports which are configured on the 'Active Directory Imports' page in the Beacon UI. This log captures the LDAP connection being established with the domain controller and the import of Active Directory information. The import produces an .actdir file which is uploaded to the inventory server.


Beacon engine service

This log captures events from the Beacon Engine Service. This is one of the main log files on a beacon server and captures information about a lot of the background activities performed by a beacon. An example of some of the main events that are captured include; downloading and loading beacon policy, downloading updates to discovery & inventory rules, download discovery export file, downloading updated importer xml files.


Beacon IIS app

Captures events from the beacon's web server component. The beacon web server generates and serves agent policy, settings, and upgrade files and accepts incoming files from agents.


Compliance Reader logs

Captures events from compliance reader imports reading data from external systems. To see the configured imports on a beacon you can look at the 'Inventory systems' page in the Beacon UI.


Compliance upload

Logs events about the upload of inventory extracted from external databases and business adapter data. ComplianceUpload.exe is launched by the 'Upload third party inventory data' scheduled task.

This process does not include the upload of files received from FlexNet inventory agents (such as inventory .ndi files and others).


Discovery and inventory rules

Logs events from the execution of Discovery & Inventory rules. You can see the configured rules in the Beacon UI on the 'Rules' page. Each rule execution will generate a new GUID (the task's unique SessionUID) which is used in the directory path when storing the log files.

Tip: When troubleshooting, sort the InventoryRule logging folder by the last modified date to find the most recently created folder after triggering rule execution manually in the Beacon UI.


Inventory Beacon UI and processes

Captures events from the Beacon UI and various other tasks performed by the local inventory beacon. The BeaconEngine.log will generally be the main log to look at when troubleshooting a beacon but it's worth checking this too.


IT Asset Management (Cloud)