Custom File Naming for Session Recordings via Devolutions Gateway

Hello,

Thank you for the feedback.

Before we evaluate this, we would like to better understand what level of customization you need. Today, Gateway recordings rely on a structured layout using internal identifiers, such as the session ID, recording manifest, and generated recording file names. This structure is important because Gateway uses it to know where recordings are stored, how to list them, retrieve them, delete them, and associate them with the correct session. Because of that, naming customization may need to be limited to avoid breaking recording traceability and retrieval.

We should also mention that Gateway currently has access to a limited amount of metadata when saving recording files. Depending on what you need in the filename, we may need to evaluate whether additional metadata should be passed to Gateway or stored with the recording.

Could you clarify the following?

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

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?

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.

If some of those values are not currently available to Gateway, would it still be useful if we supported a smaller set first, such as session ID, timestamp, protocol, and recording type?

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

This will help us determine whether the best approach is to support a display/export filename, a limited configurable naming template, or a broader metadata enhancement for Gateway recordings.

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,

Thank you for the additional details, and sorry for the delayed follow-up.

Gateway recordings are primarily intended to be accessed through Devolutions Server rather than directly from the recording storage folder. This is important because the recording storage layout is also used by Gateway and DVLS to keep recordings associated with the correct session, retrieve them, delete them, and preserve traceability.

There is also a playback aspect to consider. A single recorded session may be represented by multiple recording files, depending on the session type and how the recording was produced. Accessing the files directly with a local video player may work in some cases, but the DVLS/Gateway recording player provides a more reliable and user-friendly way to view the complete recording.
That said, I understand the need for better file names for external archiving, indexing, or custom workflows. I will bring this use case to our product managers.

From a technical point of view, changing the recording folder name is more difficult because the folder structure is tied to the recording/session identifier used by Gateway and DVLS. However, we could evaluate other approaches, such as adding more metadata to the recording manifest, or improving the generated recording file names while keeping the folder structure stable. For example, the recording files could use more descriptive names, and the manifest could include additional metadata that would make custom indexing easier on your side.

So the most realistic direction would probably be:

• keep the recording folder structure based on the internal recording/session identifier;
• improve the recording file names where possible;
• add useful metadata to the recording manifest for external indexing or automation scenarios.

I cannot confirm yet whether or when this could be implemented, but your feedback is clear and I will make sure the requirement is shared with the product team.

Regards,