Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35540

Attempt best effort reverse dns for ingress connections

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Networking
    • None
    • Service Arch

    Description

      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).

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            mira.carey@mongodb.com Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: