jvaillant

Hello,

Thank you for your feedback, it’s great to hear about the requested feature.

As for logging queries, I believe priority should be given to queries executed via RDM, since we intend to use the integrated SSMS instance.

However, depending on the level of complexity, why not leverage the "Access Query logs" in MSSQL? That is also a viable approach.

Are both options feasible?

For your information, please note that I have two Devolutions Gateways and one Devolutions Server in my environment.

Best regards,

Jacques

Dear Support Team,

In our current workflow, we are using Devolutions Server via Remote Desktop Manager.

We have successfully configured Microsoft SQL Server entries, and the connections are working as expected. However, we would like to know if Remote Desktop Manager provides any native functionality to:

1. Trace or record SQL queries executed by a user during an active session.

2. Consult a history of queries launched once the session has ended.

If such a feature exists, could you please provide us with the configuration procedure? If not, is there a recommended method using your tools to ensure this type of auditing?

Thank you in advance for your assistance.

Best regards,

Hello,

Thank you for your feedback. No problem, please find the details below.

In first about my environnement, i have :

• 1 server Devolutions-server + 1 server MSQL

• 1 Devolutions Gateway farm with 2 Gateway

  • In the Dvls Gateway 1 & 2, the "RecordingPath" is customized --> Dedicated storage

What filename is currently generated in your environment, and what filename would you like to see instead?

Currently, the files are generated as follows:

• Directory Name = ID (9046b68c-b219-4194-8671-40acfbd54cde)

• Recording Name = recording-0.webm

As part of the local testing, I customized it as follows, and this would be the desired result:

• SRVTEST01 - John Doe - 2026-05-19 08 h 48.webm

Do you need to customize the actual file name stored on the Gateway, or would it be enough to customize the name when the recording is downloaded, exported, or archived?

At the start/end of each session via RDM, the directory name is therefore generated using its UID, and the session file is named recording-0. This is where our requirement comes into play, namely customizing the directory name or the .webm filename.

Regarding the recordings, they are not stored on the Gateway, but directly on a dedicated storage space.

Configuration of my gateway.json:

Which values would you need in the filename? For example: session ID, username, target host, start date/time, protocol, entry name, ticket number, or custom fields.

For my tests, I used the following variables:

$NAME$ - $DATA_SOURCE_USERPROFILE_FIRSTNAME$ $DATA_SOURCE_USERPROFILE_LASTNAME$ - $DATE$ $TIME$

Result :

Server – Users – Date & Time

Are you reading the recordings directly from the Gateway storage folder, or retrieving them through an API or another integration?

The recordings are accessed directly from the destination configured in the gateway.json.

Nothing is stored on the recording gateways.

Regards

Hello,

After several tests, we noticed a difference in behavior between local recording through RDM and remote recording through Devolutions Gateway.

We understand that:

• Local recording via RDM is managed directly from the user workstation, which provides more flexibility regarding certain output parameters, specially the generated file name.

• Remote recording through the Gateway is designed more for centralized management, session traceability, and auditing purposes, with a more controlled and consistent handling of recordings.

However, in our environment, we would need the ability to customize file names for recordings generated through Devolutions Gateway as well, in order to better integrate them into our workflow and archiving processes.

Would it be possible to consider adding this functionality in a future version of Devolutions Gateway?

Thanks for your feedback.