Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-2320

Add hostname to all atlassian log entries

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Audit Log
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The Sample log file below has no information on its node of origin. 

      192.168.65.1 | http | o@1KR8IGTx161x22x0 | admin | 2025-01-30 02:41:53,473 | "GET /rest/ui/latest/dashboard/pull-request-suggestions HTTP/1.1" | "http://localhost:4990/dashboard" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36" | 200 | 0 | 60 | - | 12 | 1kddahh |

      This is fine for single-node instances; however, in a cluster setup, having the hostname in the log would help customers and support engineers run quick analytics to capture the statistics per node without having to manually sort out the logs. It would also be suitable for observability tools like Grafana, ELK stack, and Splunk.

            [ACCESS-2320] Add hostname to all atlassian log entries

            Jocelyn Salada added a comment -

            These aren't the kinds of logs we have in Atlassian Guard/Amin audit logs

            Jocelyn Salada added a comment - These aren't the kinds of logs we have in Atlassian Guard/Amin audit logs

              Unassigned Unassigned
              ced0c047cfeb Joel Mwangi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: