Once all work has been completed to ensure that AuditClientAttrs always has the expected client IP addresses and ports, mongo-formatted audit log events can rely on it instead of the Client's transport::Session to retrieve this data.

With this piece in-place, mongo-formatted audit logs can be integration-tested to ensure that they properly contain the client IP address/port even when behind a proxy.