A team is complaining that their Jira project is slow to use. You are able to replicate the slow behavior by viewing and trying to edit one of their issues.
Which logging option will help you or a system administrator to diagnose the problem?
A team is complaining that their Jira project is slow to use. You are able to replicate the slow behavior by viewing and trying to edit one of their issues.
Which logging option will help you or a system administrator to diagnose the problem?
Enabling profiling globally helps to diagnose the issue by capturing detailed performance traces. These traces report the execution time of different parts of the system in tenths of milliseconds, which can pinpoint where the slow-downs occur. This level of detail is crucial for diagnosing performance issues in a comprehensive manner, making profiling the suitable logging option in this scenario.
Option C does seem correct. But in Atlassian's words, it's option D Profiling If you are experiencing performance issues with Jira, it is often helpful to see where the slow-downs occur. To do this you can enable profiling as described below, and then analyze the performance traces that Jira will produce for every request. Profiling traces report time spent in tenths of milliseconds. Source: https://confluence.atlassian.com/adminjiraserver/logging-and-profiling-938847671.html#Loggingandprofiling-profilingProfiling
The answers I chose were C