Include account and possibly other request details in TxMetadata

[teq0]

What would you like to be added or enhanced

Include additional attributes in TxMetadata to track the user/account that made the change, and, if possible, other info like the client IP address.

Why is this needed

For full auditability we need to not just be sure that records haven't been tampered with, we need to know how they were created i.e. by whom and from where. One simple case would be to be able to distinguish between updates made by "systems" versus updates made by humans (obviously there are credential management requirements also necessary for this to work). Having additional info like IP address could also help achieve this.

Additional context

#1575

[jeroiraz]

What would you like to be added or enhanced

Include additional attributes in TxMetadata to track the user/account that made the change, and, if possible, other info like the client IP address.

Why is this needed

For full auditability we need to not just be sure that records haven't been tampered with, we need to know how they were created i.e. by whom and from where. One simple case would be to be able to distinguish between updates made by "systems" versus updates made by humans (obviously there are credential management requirements also necessary for this to work). Having additional info like IP address could also help achieve this.

Additional context

#1575

Thanks for opening the feature request @teq0. It'd be great if you can help us investigating the best approach to obtain client IP address from the grpc connection

[teq0]

Happy to.