Configuration, registry and log locations
Use the documented local directories to understand which evidence belongs to configuration, the service registry or captured output. These locations are not cleanup instructions and should not be deleted or shared wholesale.
Local locations
| Location | Contents and purpose | Handling |
|---|---|---|
~/Library/Application Support/FleetConsole | Registry and configuration | Preserve service identities and settings; do not edit the registry to correct a status |
~/Library/Logs/FleetConsole | Daemon and service logs | Read locally; redact secrets and private command output before sharing |
Inside the application at Contents/Resources/bin/fleetctl | Bundled CLI | Use the actual installed bundle's path |
| Owner-only Unix socket | Local controller communication | A missing or inaccessible socket needs diagnosis, not permissive access changes |
The home-directory prefix refers to the user running Fleet Console. Do not inspect another user's data directory to work around missing local evidence.
Configuration and observations differ
Configuration expresses choices such as visible sections, polling intervals or expected listeners. The registry records services and their history. Logs capture output, which can contain information the application printed even if environment values were not persisted in service metadata.
The existence of a registry or log directory does not establish a running controller. A historical event is not a live process check. Likewise, changing a file is not proof the controller accepted or activated a new configuration.
Share a narrow report
Prefer a concise description of the exact action and non-secret error to an archive of local data. This personal worksheet can help structure a report; it is not a Fleet Console configuration schema:
# Support report
- Product and installed version:
- Exact action:
- Expected result:
- Observed result and non-secret error:
- Relevant operation/run ID, if safe to share:
- Steps already tried:
- Work preserved before retrying:
Do not include credentials, full process inventories, private files or raw authenticated requests. Use doctor for bounded diagnostics and shared support for a safe handoff. The maintained project documentation identifies the local storage locations.