Display the name and ID of the current Stash Data Center node in page footer

XMLWordPrintable

      As a Stash user I want to see the current Data Center node so I can include it in problem reports to my administrator.

      As a Stash administrator I want to know the Data Center node where problems occur so I can quickly identify the correct logs.

      Problem Definition

      When problems arise in a Stash Data Center installation it is difficult to determine which node the problem has affected. This information is available in HTTP headers but this hard for users to access, adding difficulty for the administrator.

      Suggested Solution

      Add the current cluster NodeID and NodeName to the footer, similar to JIRA DC, Confluence DC, and stash.atlassian.com.

      Workaround

      For the cluster at stash.atlassian.com a plugin was created that shows the current Node ID in the footer. This plugin is closed source, not fully tested, and officially not supported. That said, we used it with Stash 3.10 and 3.11 (not yet released) for over a year so no problems are expected.

      We strongly recommend that you test this plugin in a test or stage environment prior to using it in production.

      1. Download the latest plugin version from the Atlassian Marketplace.
      2. Go to Administration > Add-ons
      3. Click the Upload add-on link at the top right side of the page
      4. Select the Add-on jar file you downloaded using the file chooser
      5. Click Upload.

      The plugin will be installed first to your current node then mirrored to the others in your cluster.

      By default the NodeID will be shown which is a difficult to remember GUID. You can give each node a human-readable name via this JVM startup parameter:

      -Dcluster.node.name=DESIRED_NODE_NAME
      

              Assignee:
              rikf
              Reporter:
              Morgan Knicely (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: