Context

During a critical situation where Jira is unresponsive or extremely slow, it becomes very important to capture thread dumps during the impacted period to investigate potential causes.

Atlassian support provide customized script to capture the thread dumps along with support.zip.

At time the script is not fired in sync with the support.zip or after support zip is generated. We miss proper data to collect, losing critical information. This means that they will have to wait for another incident to occur before they can then collect proper information.

Current Behaviour

Currently, only 3 thread dumps are captured with a period of 5 sec between them.

Suggestion

Please provide an interface, which generating the support zip. Where the admin can configure the number of thread dumps to capture and also configure the period of difference between the thread dumps.