Procedure:

1. Configure the appliance to record the scan results
   1.  Helix Discovery:  Administration > Other Settings, set Recording mode to "Record"
   2. On-premise Discovery :  Administration > Discovery Configuration, set Recording mode to "Record"
      
      
2. While there are no scans executed by the outpost, delete the content of the folders below (files and subfolders, keep the one in bold). The installation folder is typically C:\Program Files\BMC Software\.

   <Outpost  installation folder>\var\record
   <Outpost  installation folder>\var\pool
   <Outpost  installation folder>\runtime\Outpost_Credential_Proxy\var\record
   <Outpost  installation folder>\runtime\Outpost_Active_Directory_Proxy\var\record
   
   

3. Enable DEBUG logs in the Outpost
   1. On the Outpost UI open  Manage > Configuration and setting logging level to DEBUG
      
      
4. Start a Discovery run
   1. Scan the IP, an API or a cloud environment that support needs to review or troubleshoot.
   2. Enable the session logs in the the Discovery run if this is a Linux or a Windows PowerShell scan 
   3. Wait for the end of the scan
   4. Confirm that the resulting scan completed or reproduced  the issue support needs to review
      
      
5. Zip up the folders below (with all the subfolders)
   <Outpost installation folder>\var\record
   <Outpost installation folder>\var\pool
   <Outpost  installation folder>\runtime
   
    
6. If required by BMC, collect the outpost logs as documented in this article and add them to the zip file
   1.  <Outpost installation folder>\log 
   2.  <Outpost  installation folder>\runtime\<proxy>\log
      
      

Vote for this RFE if you need the UI to help you collecting this files.

Once requested data is sent to support do the following: 

1. Set Record Mode back to off  in in  Administration
2. Set  DEBUG logs back to INFO