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.
Special Q&A