Skip to content
English
Submit a support ticket
Back to www.opslogix.com
  • There are no suggestions because the search field is empty.

Enable debug logging for the VMware MP

Turn on detailed logging with registry keys when you troubleshoot the VMware MP.

Applies to: OpsLogix VMware Management Pack (all versions) · SCOM 2019, 2022, 2025
Last updated: October 2026 · Reading time: 2 minutes

Goal

Turn on detailed (debug) logging for the VMware Management Pack, for example when OpsLogix support asks for it. Debug logging is controlled with registry values.

Prerequisites

  • Administrator rights on every SCOM management server that runs the VMware monitoring (where the OpsLogix VMware Collector runs).

Steps

Do these steps on every management server that runs the VMware monitoring.

  1. Run these commands as administrator. The first one sets the level for all management pack modules, the second one for the OpsLogix VMware Collector: 
    reg add "HKLM\SOFTWARE\OpsLogix\VMware" /v "DebugMode" /t REG_DWORD /d 5 /f
    reg add "HKLM\SOFTWARE\OpsLogix\VMware\Collector" /v "DebugMode" /t REG_DWORD /d 5 /f

    To debug only one workflow instead of all modules, set DebugMode under HKLM\SOFTWARE\OpsLogix\VMware\Client Modules\<ACTION>\<TYPE>, for example Client Modules\DISCOVERY\VIRTUALMACHINE. See VMware Management Pack registry settings.

  2. Stop the Microsoft Monitoring Agent service and the OpsLogix VMware Collector Service.
  3. Save the Operations Manager event log if you still need the existing events, then clear it.
  4. Increase the maximum size of the Operations Manager event log.
  5. Start the Microsoft Monitoring Agent service and the OpsLogix VMware Collector Service again.

To debug the VMware MP Configuration dashboard: on the computer where you run the SCOM console, add this value and restart the console:

reg add "HKLM\SOFTWARE\OpsLogix\VMware\ui" /v "DebugMode" /t REG_DWORD /d 7 /f

The dashboard logs to the Operations Manager event log on the console computer, with the sources Opslogix Configuration UI and Operations Manager.

Debug levels

Value What is logged
0 Nothing
1 Critical errors only
2 Errors
3 Warnings and errors (default when no value is set)
4 Information, warnings and errors
5, 6 or 7 Everything (trace). Use 5 unless OpsLogix support asks for another value.

Verify it worked

Open the Operations Manager event log. You should see debug messages from the event sources OpsLogix IMP VMware (management pack modules) and OpsLogix VMware Collector.

Warning: at trace level (5 or higher), the management pack modules also log their workflow configuration. That includes the encrypted vCenter password and the license key. Turn trace logging off as soon as you're done, and share the event log only with OpsLogix support.

Turn debug logging off again

When you're done, delete the registry values you added in step 1, then restart the services as in steps 2 and 5. Don't set them to 0: that turns off all logging, including errors. Debug logging creates a lot of events, so don't leave it on.

Note: to remove the dashboard setting, delete the whole HKLM\SOFTWARE\OpsLogix\VMware\ui key, not only the DebugMode value. If the ui key exists without a DebugMode value, the VMware MP Configuration dashboard doesn't load.

See also