Issue Summary

Support often needs thread dumps that were taken at the time of the issues and it may not be possible for the customers to catch such times. Sometimes they just go ahead and restart the service to avoid service disruption on end users.

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 Errors
   5. to be added

Expected Results

There should be diagnostic data for the time such as thread dumps to analyze the incident without waiting for the next occurrence. It would be great if this feature can be enabled from ATST on Administration > System > Troubleshooting and Support Tools.

Actual Results

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

Workaround

Customers use custom cron scripts to catch such problems.

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