Attempt best effort reverse dns for ingress connections

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking
    • Server Programmability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      On connection accepted we print the ip address of the remote host in the logs. Any efforts we could make towards doing reverse dns would help correlate ingress and egress log lines (egress are always host and port, not resolved address).

      A minimal effort might include a cache of ip address to host and port that was derived from egress connections. That would at least allow us to identify we ourselves are connecting to (like other replica set members).

            Assignee:
            Unassigned
            Reporter:
            Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: