Set the Mesh access log level to ERROR by default

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Mesh
    • None
    • 1
    • 3

      The Mesh access log level should be set to ERROR by default, to prevent filling these logs with information that is not helpful, eg.

      # tail atlassian-mesh-access.log
127.0.0.1 | grpc | i@5OEIC5S6x777x8167x2 | - | - | 2024-09-17 12:57:02,573 | "ManagementService/Heartbeat" | - | - | - | - | - | - | - | -
127.0.0.1 | grpc | o@5OEIC5S6x777x8167x2 | - | - | 2024-09-17 12:57:02,579 | "ManagementService/Heartbeat" | - | 0 | 1 | 1 | 0 | 0 | - | 6
127.0.0.1 | grpc | i@5OEIC5S6x777x8168x2 | - | - | 2024-09-17 12:57:12,574 | "ManagementService/Heartbeat" | - | - | - | - | - | - | - | -
127.0.0.1 | grpc | o@5OEIC5S6x777x8168x2 | - | - | 2024-09-17 12:57:12,576 | "ManagementService/Heartbeat" | - | 0 | 1 | 1 | 0 | 0 | - | 2

      Workaround

      Until the default log level for Mesh access logs is changed, you can configure this change for your Bitbucket DC instance, by adding the following line to $BITBUCKET_HOME/mesh/mesh.properties:

      logging.logger.mesh.access-log=ERROR

            Assignee:
            Unassigned
            Reporter:
            Marek Suchecki (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: