Known Issue: Some expected details are not included in discovery.log files (IOK-1139954)

[#1]

Summary

Logging generated in discovery.log files by discovery operations on beacons does not include some expected details due to a misconfiguration in the default BeaconEngine.config file included in some FlexNet inventory beacon versions.

Symptoms

Logging produced by discovery processes should normally include details like the following examples (although exact details depends on the exact configuration of the discovery task):

2024-06-11 02:16:57,196 [coveryThreadedExecutor|   Async] [INFO ] Starting 20 threads for device property and service discovery.
2024-06-11 02:16:57,212 [coveryThreadedExecutor|   Async] [INFO ] Starting 10 threads for device discovery.
2024-06-11 02:16:57,212 [coveryThreadedExecutor|   Async] [INFO ] Starting 10 threads for DNS lookup.
2024-06-11 02:16:57,228 [coveryThreadedExecutor|   Async] [INFO ] Starting 1 threads for network scanning.
[...]
2024-06-11 02:16:57,275 [veryExportDeviceSource|DeviceSource] [INFO ] Processing exported disco files extracted in the folder 'C:\ProgramData\Flexera Software\Beacon\DiscoveryExport\351': 1 files to be processed.
[...]
2024-06-11 02:16:57,290 [veryExportDeviceSource|DeviceSource] [INFO ] Processing exported disco file 'C:\ProgramData\Flexera Software\Beacon\DiscoveryExport\351\1.disco'
[...]
2024-06-11 02:16:57,415 [ource.NMapDeviceSource|  IPScan] [INFO ] Starting a port scan.
2024-06-11 02:16:57,446 [iscovery.NMapDiscovery|  IPScan] [INFO ] Building command line with TCP ports:22,139,445 and UDP ports 
2024-06-11 02:16:57,446 [iscovery.NMapDiscovery|  IPScan] [INFO ] Command line for mgsipScan:  -p T:22,139,445 -oX "C:\Windows\TEMP\ManageSoft\discovery\mgsipscan-t-2024611_21657-41ab0c6067-6b59-4da7-8332-ad3df0559bd0.xml" -Pn -sS 10.75.18.52
[...]
2024-06-11 02:17:10,777 [ource.NMapDeviceSource|  IPScan] [INFO ] Completed a port scan.
2024-06-11 02:17:10,777 [.DiscoveryTaskExecutor|PropertyDisco] [INFO ] Skipping Device Property Scan discovery for device 'svr01234': Device is not discovered in the current rule execution.
2024-06-11 02:17:10,809 [.DiscoveryTaskExecutor|PropertyDisco] [INFO ] Performing OS credentials discovery for device 'svr01234'
2024-06-11 02:17:10,871 [.DiscoveryTaskExecutor|PropertyDisco] [INFO ] Completed OS credentials discovery for device 'svr01234': Can administer: 'True', administration account name 'Administrator', discovered OS family 'Windows', agent status 'unadopted', agent version ''
[...]
2024-06-11 02:17:13,845 [coveryThreadedExecutor|   Async] [INFO ] Shutdown of 10 threads for device discovery.
2024-06-11 02:17:13,861 [coveryThreadedExecutor|   Async] [INFO ] Shutdown of 10 threads for DNS lookup.
2024-06-11 02:17:13,861 [coveryThreadedExecutor|   Async] [INFO ] Shutdown of 1 threads for network scanning.
2024-06-11 02:17:13,906 [coveryThreadedExecutor|   Async] [INFO ] Shutdown of 20 threads for device property and service discovery.

When this issue occurs, details like shown in the above example are not included in log files.

This issue is only applicable to versions of the FlexNet inventory beacon that use the NLog logging library. The first 2 lines of the C:\ProgramData\Flexera Software\Compliance\Logging\BeaconEngine.config file appear as follows with these versions:

<?xml version="1.0"?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xsi:schemaLocation="NLog NLog.xsd"

Remediation

To make the expected information visible in discovery.log files, the following lines in C:\ProgramData\Flexera Software\Compliance\Logging\BeaconEngine.config must be changed:

<logger name="Flexera.RemoteExecution.Discovery" minlevel="${var:InventoryRuleLogLevel}" writeTo="Discovery" final="true" />
<logger name="Flexera.RemoteExecution.Discovery" final="true" />
<logger name="Flexera.Beacon.Engine.ActionExecution.DiscoveryManagement" minlevel="${var:InventoryRuleLogLevel}" writeTo="Discovery" final="true" />
<logger name="Flexera.Beacon.Engine.ActionExecution.DiscoveryManagement" final="true" />

These lines should be changed to the following (note the addition of “.”* at the end of each logger name):

<logger name="Flexera.RemoteExecution.Discovery.*" minlevel="${var:InventoryRuleLogLevel}" writeTo="Discovery" final="true" />
<logger name="Flexera.RemoteExecution.Discovery.*" final="true" />
<logger name="Flexera.Beacon.Engine.ActionExecution.DiscoveryManagement.*" minlevel="${var:InventoryRuleLogLevel}" writeTo="Discovery" final="true" />
<logger name="Flexera.Beacon.Engine.ActionExecution.DiscoveryManagement.*" final="true" />

Fix status

This issue has been fixed in the following FlexNet Manager Suite release: 2024 R1.1 / Jul 2024 (Cloud)

This issue is planned to be addressed in the following future FlexNet Manager Suite release: 2024 R2 (On Premises)

Other information

Affected components: Discovery

Master issue ID: IOK-1139954

Also known as: ITAM-7805