[SERVER-10755] Port additional mongoS network-level logging to the main branch Created: 12/Sep/13  Updated: 11/Jul/16  Resolved: 05/Feb/14

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: 2.6.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Greg Studer
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

mongoS


Issue Links:
Depends
Related
Participants:

 Description   

We should have additional IP-level logging for easier problem troubleshooting.

For instance, at logLevel 1, we could really benefit from additional logging for every outgoing connection, on connect, which includes the IP address.



 Comments   
Comment by Githook User [ 05/Feb/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-10755 report shard host from SSV in setting shard error msgs
Branch: master
https://github.com/mongodb/mongo/commit/45fe9173ee01d69ff7e8286b37460424472bc06c

Comment by Githook User [ 18/Jan/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-10755 additional client connection logging, as well as setShardName logging
Branch: master
https://github.com/mongodb/mongo/commit/69908f52f07b7faefff68e87e1d8822f6d22fcd0

Generated at Thu Feb 08 03:23:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.