-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Diagnostics, Networking
-
None
-
Fully Compatible
-
Service arch 2020-07-13, Service Arch 2020-07-27
In tests I often see:
[js_test:remove_newly_added_field_after_finishing_initial_sync] 2020-04-16T18:46:08.548+0000 d20030| 2020-04-16T18:46:08.548+00:00 I NETWORK 51800 [conn24] "client metadata","attr":{"remote":"10.122.28.155:60072","client":"conn24","doc":{"driver":{"name":"NetworkInterfaceTL","version":"4.5.0-745-g6388b97"},"os":{"type":"Linux","name":"Red Hat Enterprise Linux Server release 6.2 (Santiago)","architecture":"x86_64","version":"Kernel 2.6.32-220.el6.x86_64"}}}
but have no idea what's on the other side of conn24. Being able to see the host and port or the process id, and maybe the type of process (mongod, mongos, shell), of whatever process is on the other side of the connection would be really helpful in diagnostics. If for some reason this is only doable in our tests, even that would be enormously beneficial.
- is duplicated by
-
SERVER-49038 remove embedded_options_helpers
- Closed
- related to
-
SERVER-50085 Make it easier to correlate mongo process names, ports, PIDs in logs of fixtures started by resmoke
- Closed
-
SERVER-62683 LOG 51800 For Client Metadata Information Should Show Pid In Testing Mode
- Closed