Including locality fields in trace events

We have the host name as a standard field in trace events, which can be useful when identifying issues that are occurring for multiple instances on the same host. On Kubernetes, the host name field is not very useful, because it is populated with the pod name. Could we consider an option to populate other fields from the locality information in trace events, as a way to give additional context when analyzing logs?

Start by locating the trace-event handling and the locality information used by FoundationDB, then examine how the existing host name field is populated. Determine which locality fields should be exposed and how an option would affect trace analysis; the issue is done when the intended fields and configuration behavior are defined and covered by appropriate trace-event tests.

Written by the indexing model from the issue text.