Enable Core Scan Debugging and Data Analytics Logging

Version 4

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2018.x

    Logging In Data Analytics is relatively straight forward. By default, all logs related to DA are located in: InstallPath\ManagementSuite\MP_Log

    All of the logs stored here, should have a name that reflects the process that was ran. In relation to Data Translation Service, if you run a rule manually, it will create a log with the file name that reflects the DTS rule that was ran along with a timestamp (ie. "Archive Computers to Asset Control-20141118132632.log"). However, if you were to set a rule Active then there will not be a separate log created like when you run rules manually and it will instead log messages to the MPCore log that will also be in the MP_Log folder on the core server. When an active rule logs to the MPCore log file, many of the events are suppressed to prevent the log from having too much information. Though this can be changed if you run into issues you'd like to get more information on.


    For instance, you may find a situation where scan files are not processing the way that you would expect through Data Analytics. When you run into issues like this you can enable Debugging and see what is happening as the scan files are being processed.


    Step 1: Shutdown the LANDesk Inventory Service


    Step 2: Create the following DWORD

    HKEY_LOCAL_MACHINE\SOFTWARE\Managed Planet\Core\DebugLevel




    Set DebugLevel = 4


    *Optional: To simplify logging you can set ThreadCount to = 1


    Step 3: After the registry is changed you will need to restart the Managed Planet Core Scan Processor service.


    Once this is completed you should find much more detail in your MPCore log as scans are being processed by DA and are prepared to be sent back to the Inventory service.


    Do not leave this enabled on a core for very long as it will fill up your hard drive if left on ***