A developer has created and successfully installed a new design using the VCF Operations Management...

The correct troubleshooting sources are the Request Log , the Management Pack Builder Adapter log , and the Integration Designer Controller log . Management Pack Builder troubleshooting is centered on validating the API requests, collection execution, adapter behavior, and server-side design processing. The VCF 9.0 documentation states that every test request or test collection in Management Pack Builder exposes request tabs showing the body, headers, and logs; these are used to diagnose response-code errors and request/response issues . For collection problems after installation, the administrator should review Management Pack Builder Adapter logs , located under $VCOPS_BASE/user/log/adapters/MPBAdapter on the selected node or cloud proxy, because these logs show adapter-side warnings and errors during collection . If the issue appears to be with Management Pack Builder itself, the official guidance identifies /usr/lib/vmware-vcops/user/log/integration-designer-controller.log as the server-side log to review . The Design Screen is used to build and verify definitions, but it is not one of the listed troubleshooting data sources. Observability Workbench is for infrastructure troubleshooting, not Management Pack Builder design diagnostics. Reference topic: Objective 4.8 – Management Pack Builder / Troubleshooting a Design .