How does PyCharm differentiate deployment log content between SFTP and Docker targets when diagnosing transfer failures

Deployment Log Differentiation in PyCharm

PyCharm's Deployment tool window consolidates logs for each deployment session, but the underlying structure varies significantly between server types. For SFTP deployments, logs originate from SSH channel operations and include detailed file transfer metadata with permission and ownership information. Docker deployments, however, surface container stdout/stderr streams through the Deployment interface, creating a different diagnostic context.

When a transfer fails, the error presentation and available context differ between these protocols. SFTP failures may show protocol-level rejections with specific error codes, while Docker failures might display container exit codes or runtime exceptions. The Deployment tool window's filtering capabilities and search functionality may also behave differently depending on the target type.

Key constraints include the lack of unified log aggregation across multiple targets, session-scoped log persistence, and the separation between transfer diagnostics and application runtime errors. Users cannot easily correlate failures across different deployment targets or trace application-level issues that occur after successful file transfers.

What specific log filtering or export mechanisms exist to isolate protocol-specific failure patterns? Does the Deployment tool window provide different diagnostic views for different server types, and how can users effectively distinguish between transfer failures and application runtime failures when both may appear in the same session?