Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-19430

Update Mesh sidecar for JMX monitoring with alternate approach

    XMLWordPrintable

Details

    • 4
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.
    • EWT - Ignore

    Description

      On the Bitbucket Mesh sidecar document, we suggest creating a local `bitbucket.properties` file to pass JMX-related JVM parameters for the Mesh sidecar. To do this, you need to create a symbolic link between the `bitbucket.properties` file and `$BITBUCKET_HOME/shared/bitbucket.properties`.

      However, there is an alternate approach that can be used instead. This must be added to the Bitbucket Mesh sidecar document page

      An alternative method for configuring JMX-related JVM parameters for the Mesh sidecar process is to include the JMX related configuration in a local bitbucket.properties file within the $BITBUCKET_HOME directory itself.

      To implement this, create a $BITBUCKET_HOME/bitbucket.properties file and move all the JMX-related parameters to that file. Only the common parameters/configurations that are consistent across all other Bitbucket nodes should remain in the $BITBUCKET_HOME/shared/bitbucket.properties file.

      Attachments

        Issue Links

          Activity

            People

              500376cac1e1 Daria Shatsylo
              5338c0aa34f9 Danny Samuel
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: