Issue Summary

Support often needs diagnostic information that were taken at the time of the issues and it may not be possible for the customers to catch such times. Sometimes incidents happen during night or admin unattended time.

Steps to Reproduce

1. Jira goes into a situation such as
   1. High CPU Utilization/ Load Average
   2. High number of DB connections (more than 80% of mx db conns)
   3. High number of stuck threads
   4. Health check failures

Expected Results

There should be diagnostic data for the time such as thread dumps to analyze the incident without waiting for the next occurrence. Having an option to save Java Flight Recorder data in case of such occurrences will be invaluable.

There is only Jira logs, stat logs and IPD data. if not rotated since the incident.

Workaround

Admins have to save a fresh support zip or increase the JFR collection settings.

Currently there is no known workaround for this behavior. A workaround will be added here when available