session log questions

0 vote

avatar

We use RDM to manage all the core devices in the network as such we are planning to use session logs

as it stands it seems that you have to enable session logging in each session and you have to give each session a file name this is all well and good but i can see a coupple of ways to improve the system

in the log tab of the session it would be nice to either specify a log name or have the system create a log file at session start with a date stamp if it dose not exist or append to the file if it dose this would allow for a lot easier searching for things in the logs



the way I see it it would add additional options to the log tab in the session properties

1, an additional option to the log overwrite drop down called something like Append to date stamped file
2, an option to use the session name for the logfile name and have that file either placed in the globally define path or the specified path

then when you start a session if there is a file date stamped for today it appends if not it opens a new file with the current date stamp

4d27e524-a332-4aa0-919c-76667e79ec55.png

All Comments (12)

avatar

Hello,

Thank you for sharing your suggestions on enhancing the session logging features in RDM.

I will forward this thread to our feature request forum.

Best regards,

Carl Marien

avatar

Hello,

You should already be able to achieve this through the use of variables. You can find the list of variables by clicking the "Variables" button while editing an entry:


There are multiple variables relating to the date. Here's an example of how I've configured my SSH shell logging, using the $DATE$ and $NAME$ variables:


The result is that it will create a file called 2024-05-13-SSH Shell.log as it's resolving the $DATE$ and $NAME$ variables to create the file name. When the date changes, it will log in the new file. One thing to note is that you will probably need to restart the entry for the new date to be taken into account in the file name.

Let me know if this works for you and if you have any other questions.

Regards,

Hubert Mireault

4a88a6b4-5d24-433c-b24d-1d29ec76e70c.png

a9928384-a995-48a4-a4f7-644c0349a955.png

avatar

Hi thanks for that this worked as advised its a bit of a ham-fisted way of doing what other systems do but this was the last pain point for our team and the variable feature is nice and it dose allow for more customization of the logging structure

avatar

Hello,

Glad to hear this works well for you! If you have any other questions, let us know.

Regards,

Hubert Mireault

avatar

Hello all,

Those tips really helped a lot. However, I'd like to know how I can configure this logging option for all sessions once, because for now I'm configuring for each session separately. Can you help me on this?

Thanks

3650b575-a69c-4d8e-bcf9-ac16adfd924d.png

avatar

Hello,

You can use the Batch Edit feature to edit a selection of entry at the same time. You can find out more information about the process here: https://docs.devolutions.net/rdm/commands/edit/batch-edit/
In your case you want to select your SSH terminal entries and do "Edit entries (session type settings)". From there, you will be able to edit the log section and add the string you need.

If you'd like for your users to have this value set automatically, you could implement templates and require using them when creating entries. You can find out more about this here: https://docs.devolutions.net/rdm/commands/file/templates/

Regards,

Hubert Mireault

avatar

Understood! Thanks!

avatar

Good Morning,
came looking for the right way to format my SSH Logs and found this thread.
I´m looking for a way to name my logs as described by Hubert Mireault

2024-05-13-SSH Shell.log


However whatever I do i can´t replicate his output. Any chance you can give me a hint here?

So far I´ve tried:
$DATE_TEXT_ISO$-$TIME_TEXT_ISO$-$HOST$.log Output: 20250616-141213-10.31.80.113.log
$DATE$-$TIME_TEXT_ISO$-$HOST$.log Output: 6_16_2025-141608-10.31.80.113.log
I also tried:
$DATE_YEAR$-$DATE_MONTH$-$DATE_DAY$-$TIME_TEXT_ISO$-$HOST$.log Output: 2025-6-16-141838-10.31.80.113.log (Missing the leading "0" in the Month)

Since I have a couple of systems log into my logstorage and all of them are using the format YYYY-MM--DD-Time-Host I would like to do the same in RDM. What am I missing? I also tried switching the application language and the "use system data time format" checkbox in the usersettings. So far nothing helped.

Any points what to do here?
I´m using RDM on WIn11 in Version 2025.1.41.0 64-bit (JIT)

BR
Sebastian

avatar

Hello Sebastian,

By default, the date format is based on the language of the application, which is not always what you're looking for.

I will open a ticket to either modify the month/day variables to contain the leading '0' or to add a new variable that will contain this leading '0'. I'm still undecided what is the best way to go about this, since we have to be wary about modifying the behavior for variables due to scripting. It's probably safer to add new variables.

In the mean time, you could try enabling the options to use your system's date/time format. You can enable it by going in File > Settings > User Interface:



Note that the application will need to be restarted to have the changes apply. Maybe this workaround can help you for now.

Regards,

Hubert Mireault

3f3bf1b2-9005-4028-b191-18a08b3f1860.png

avatar

Hi Hubert,
thanks for getting back to me so quickly!
I´ve tried it with the system time but now I get the following:
$DATE$-$TIME_TEXT_ISO$-$HOST$.log Output: 17.06.2025-074417-10.31.80.113

I assume this is due to the german language setting in my OS (company settings :/ ).
I would assume new variables for day and month with always two digits would make more sense than changing the old ones and confusing people with this change...
Thanks for your help on this!
BR
Sebastian

avatar

Thanks for the feedback Sebastian, it's unfortunate that the OS settings aren't adequate for what you're looking for either.

We'll have two new variables in our next minor update, 2025.2.15.0:
$DATE_DAY_TWODIGITS$
$DATE_MONTH_TWODIGITS$

Both of these will ensure they always have two digits, so adding a leading '0' whenever the day or month is a single digit.

I hope this will help solve this issue for you, let me know if you have any additional feedback.

Regards,

Hubert Mireault

avatar

Hi Hubert,
thanks very much for the quick help and support on this! Really grateful for it!
Best Regards
Sebastian