How to generate and gather support zips from remote mesh nodes

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

When running remote mesh nodes it is possible to generate and gather support zips from select or all mesh nodes using a rest endpoint. This rest endpoint returns a zip which can be extracted or uploaded to support for further analysis.

Solution

Support zips can be generated and then streamed to a client using the following rest endpoints:

1 2 3 4 5 // All mesh nodes GET <Bitbucket-Base-URL>/rest/api/1.0/admin/git/mesh/support-zips // Specific mesh node GET <Bitbucket-Base-URL>/rest/api/1.0/admin/git/mesh/support-zips/<Mesh-Node-ID>

The return data will be of archive/zip format. You can use wget or other tools to collect the zip. Replace <Bitbucket-Base-URL> and <Mesh-Node-ID> respectively.

This endpoint is the same for every Bitbucket node, so it is only required to be run once on any node to get the mesh support zips.

Example

Linux

We can use wget to gather the logs.

1 wget --auth-no-challenge --user=admin --ask-password -O support-zips.zip http://bb.atlassian.com:7990/rest/api/1.0/admin/git/mesh/support-zips

Windows

Newer versions of windows (10+) contain curl in powershell, which can be used:

1 curl -u admin http://bb.atlassian.com:7990/rest/api/1.0/admin/git/mesh/support-zips -outfile support-zips.zip
Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.