GUI-Based Log Level Management & Log Downloading for CID Endpoint

Sean Culp

• February 23, 2026 14:09

I’d like to submit a feature request regarding the Stratusphere UX Connector ID on Windows endpoints.

 

Currently, changing the LOGLEVEL and collecting logs requires several manual steps, including editing the logconfig file and manually deleting or retrieving .txt log files from the installation directory. While the Connector ID Control Panel already includes buttons to start and stop the services, the remaining steps still require direct file-system access and manual configuration.

 

I’d like to request the following enhancements to streamline troubleshooting and log management:

 

1. GUI-Based Log Level Management It would be very helpful to have an option within the Connector ID Control Panel to adjust the LOGLEVEL using a dropdown or similar interface. Ideally, this feature would:

• Update the logconfig file automatically
• Clear existing .txt log files when the service is restarted
• Integrate smoothly with the existing Start/Stop service buttons

2. Built‑In Log Downloading A “Download Logs” button within the Control Panel would make troubleshooting significantly easier. This feature could gather all relevant log files and package them into a ZIP file for quick download, eliminating the need to browse the file system manually.

 

These enhancements would reduce administrative overhead, improve consistency across environments, and make it easier to collect logs when working with your support team.

Thank you for considering these improvements. Please let me know if any additional details would be helpful.

2

• Official comment

  

  Ryan Wilp

  • February 24, 2026 22:21

  Hey Sean!  Great idea for a feature request; I've opened a ticket to for adding Connector ID agent debugging functionality to the CID applet in a future release.  It is currently limited, but you can do some of the functions you're asking for by running idcontrol.exe as in CMD as admin.

  C:\Windows\System32>"C:\Program Files\Liquidware\Connector ID\idcontrol.exe" -v
  Usage: idcontrol [-v] <command>
      -v : verbose
  Commands:
      start: start Connector ID
      stop: stop Connector ID
      clean: clean Connector ID
      callback: force update stats
      debug: display current debug state
      debug {off|on}: turn debugging off or on
      version: print version information
      properties: print the CID settings
      status: print the CID status

  For example, idcontrol.exe clean && idcontrol.exe debug on && idcontrol.exe start would remove the txt files (and stop the CID), turn on debug level 5 (only option for now, will only keep 1 Summaryreport.txt file), and then start the CID.  You could then verify debug is on with idcontrol.exe debug and that the CID is running with idcontrol.exe status.
  

  Lastly, Liquidware CommandCTRL, our Saas-based Real-Time DEX Diagnostics & Remediation product, will be updated in Q2 this year to add CID debug gathering on endpoints within it's console.  Reach out to your Sales rep for more info if interested!

Please sign in to leave a comment.