Details

    • Similar Issues:
    • Epic Link:

      Description

      There are several reusable attributes for audit events across Jenkins. These attributes should be generated and committed to the audit catalog API. Some example attributes that would be useful to start with:

      • userId - string (corresponds to the user who initiated the action)
      • requestId - string (used as a correlation id for logs)
      • requestUri - string (contains the original request URI used for action)
      • nodeName - string (contains the name of the node where action took place)
      • timestamp - string (ISO-8601 datetime format, using UTC timezone) (note that log4j audit doesn't currently define a date or time attribute type; we have the option of using a string or long value, or we could work on contributing a date type upstream)

        Attachments

          Activity

          jvz Matt Sicker created issue -
          jvz Matt Sicker made changes -
          Field Original Value New Value
          Epic Link JENKINS-54082 [ 194705 ]
          lathasekar Latha Sekar made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          lathasekar Latha Sekar made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          jvz Matt Sicker made changes -
          Assignee Latha Sekar [ lathasekar ]
          jvz Matt Sicker made changes -
          Status In Review [ 10005 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Released As https://github.com/jvz/audit-log-plugin/pull/2
          mide David Olorundare made changes -
          Component/s audit-log-plugin [ 24638 ]
          Component/s core [ 15593 ]

            People

            • Assignee:
              lathasekar Latha Sekar
              Reporter:
              jvz Matt Sicker
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: