RDM globally log all SSH terminal console outputs to a local folder

RDM globally log all SSH terminal console outputs to a local folder

avatar
hunorszep

Hi everyone,
I'm trying to configure RDM to globally log all SSH terminal console outputs to a local folder, similar to how PuTTY handles it, dynamically naming the files with the hostname and timestamp.
I am currently running version 2026.2.18.0

Whenever I open an SSH session, I want a log file of the terminal text automatically created in a specific folder with a naming convention like: Host_Date_Time.log

What I have done so far. I went to File > Settings > Entry types > Sessions > Terminal > Settings and configured the Logging section as follows:

  • Default path: C:\PuttyLog\$HOST$_$DATE_TEXT_ISO$_$TIME_TEXT_ISO$.log
  • Log overwrite mode: Append


When I launch an SSH session and interact with the terminal, no log files are being generated in the C:\PuttyLog\ directory at all. The folder remains completely empty.

Are there any other settings I need to enable globally for this to trigger? Do individual session properties override this by default, or is there a specific "Printable output" toggle I missed in the global settings menu?
Any help is appreciated

All Comments (2)

avatar
Alexis Geller Peiro

Hi @hunorszep,

Thanks for the detailed report. You're running RDM Windows 2026.2.18.0. Could you confirm which data source / workspace you're using (local file, DVLS, SQL, or Cloud)? That helps us make sure the steps below match your setup.

What's happening: the Default path you configured under File > Settings > Entry types > Sessions > Terminal only sets the template RDM will use when an entry's "Log path type" is set to Global. It does not turn logging on for any session, and it does not fill in the filename. Those need to be configured on each individual SSH entry, in Terminal > Logs (full reference here):

  1. Open the SSH entry's properties, go to the Logs tab (under Terminal).
  2. Check Enable logging.
  3. Set Log path type to Global (to use the default path you already configured).
  4. Set Log mode to Printable output. This is the mode that logs everything visible in the terminal, similar to PuTTY, and it's also the mode that respects the "Log overwrite mode: Append" setting you configured globally. The "Event" mode (the default) only logs core events, not full terminal text.
  5. Save and open a new session.


I hope this helps clarify things. Let us know if it resolves the issue, or if any questions remain.

Best regards,

Alexis Geller Peiro

avatar
hunorszep

thanks for getting back to me so quickly!

To answer your question, i am just using the default local data source (the local database that RDM automatically creates when you first set up the application).

your instructions were spot on! the logs are generating perfectly now exactly how I wanted. thanks again for the help!