Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-43376

Server: Handle internal vs external users better in logging (esp. redaction)

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 6.5.0, Cheshire-Cat, 6.5.1, 6.6.0, 6.6.1, 6.6.2
    • None
    • ns_server
    • 1

    Description

      Currently, internal and external users are redacted in the same manner. Given internal users (@ns_server etc) are not really user data, we should consider finding a way to differentiate between the two types and then not redact internal users from the log files.

      This will become particularly important when having to support clusters with log redaction enabled where there may be issues between the internal components.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          dfinlay Dave Finlay added a comment -

          In theory the onus is on all teams not just on the redaction logic as there's no firm contract on what content is marked up as user data. In particular in query whole predicates are marked up. To address this perfectly all teams would have to decide at runtime whether or not to mark-up depending on what kind of user data content it is.

          Practically a hackish solution would be to change the redaction logic to not redact when the content is exactly the name of one of the internal users. That would work almost always and might be sufficient for what Tim is looking for.

          Assiging to PM to tracking.

          dfinlay Dave Finlay added a comment - In theory the onus is on all teams not just on the redaction logic as there's no firm contract on what content is marked up as user data. In particular in query whole predicates are marked up. To address this perfectly all teams would have to decide at runtime whether or not to mark-up depending on what kind of user data content it is. Practically a hackish solution would be to change the redaction logic to not redact when the content is exactly the name of one of the internal users. That would work almost always and might be sufficient for what Tim is looking for. Assiging to PM to tracking.

          People

            ianmccloy Ian McCloy
            tim.bradgate Tim Bradgate (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty