A new Flexera Community experience is coming on November 25th. Click here for more information.
The Docker monitor consumes the same configuration source as other agent tools. On Linux it uses the existing INI files to load its configuration while on Windows it uses the registry.
There's a couple of unique Docker settings that control it:
Therefore reconfiguring the DockerInventoryPeriod to 86400 should do the trick...
Thanks,
‎Dec 07, 2022 04:53 AM
The Docker monitor consumes the same configuration source as other agent tools. On Linux it uses the existing INI files to load its configuration while on Windows it uses the registry.
There's a couple of unique Docker settings that control it:
Therefore reconfiguring the DockerInventoryPeriod to 86400 should do the trick...
Thanks,
‎Dec 07, 2022 04:53 AM
Thanks for the details @JohnSorensenDK
‎Jan 04, 2023 01:56 AM
Hi @JohnSorensenDK , where exactly in the registry can I find these settings on a Windows machine?
‎Jan 04, 2023 02:04 AM
It will be in this structure:
HKLM\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Tracker\CurrentVersion
Thanks,
‎Jan 04, 2023 03:50 PM
How do we verify if that setting has limited the inventory generation? We have a ndi replication setting enabled and I can see the NDI files which are being processed out of it I see the docker files being maximum and with this change how can I verify from the replication that the particular server related docker file is only 1 instead of multiple files? There is no name of the server on the docker file name.
‎Jan 25, 2023 03:15 AM
I think that it may be easier for you to investigate what actually happens at the Docker level through the fnms-docker-monitor.log generated (locally on one of the hosts running a Docker daemon) than trying to trace this through the .ndi files generated.
The .ndi files generated will be Docker image .ndi files plus host .ndi files where the latter contains the container instances as additional hardware classes...
Thanks,
‎Jan 25, 2023 04:39 AM