Problem description:

In a recent version of Bitbucket (8.18+), IPD logs generated for the SCM Command and Hosting data views are empty due to changes in the Mesh configuration.
This breaks the important part of the functionality.

Steps to reproduce

1. Standup a Bitbucket instance at version 8.18 or higher (version forces Mesh usage)
2. Generate scm traffic against the instance eg.: push commits to a repo hosted in the instance
3. Generate a support zip and provide ipd logs to PerfLog viewer
4. In Perflog viewer navigate to SCM Tickets

expected result

• Mbean metric data for scm hosting and command tickets is displayed

actual result

• "no data" is displayed

Context:

Bitbucket uses 'tickets' as a mechanism for creating back-pressure to prevent the system from being overloaded with requests. There are two types of tickets, hosting tickets and command tickets. Previously, we implemented this and unfortunately, now this functionality is broken.

Possible solutions:

1. This functionality needs to be re-implemented to account for the new SCM Mesh code path
2. Data needs to be collected from mesh nodes
3. PerfLogViewer need to be able to parse additional data from new files

Acceptance Criteria:

•  The data about SCM Command and Hosting tickets is present in logs and available in the PerfLogViewer
• It's investigation ticket; provide necessary information in order to move on and create a new ticket for that