We have many, many protocol jumps and recording is required. Every additional protocol jump initiated creates a 2nd, 3rd, 4th, etc. recording, and the overhead on the user's machine grows exponentially. It would be useful to record only once with the first protocol jump initiated, instead of every single one.
To alleviate this exceptional recording overhead, I have two possible suggestions.
Option 1 -- Initiate recording on the first jump (of any kind), and simply include the additional jumps in the same, single recording, regardless of how many more are initialized or closed out. Recording stops when the last protocol jump (or other jump) is closed down, regardless of whether it was the first jump initiated or not.
Option 2 -- Have the ability to create a single IP/FQDN protocol jump that can then proxy for multiple IP's/FQDN's on the other side. That way, we can create a single protocol jump for multiple servers, with multiple ports, and enable ONE recording.