Issue Summary

Turning on profiling(Performance Profiling) has no effect on generated logging in Crowd

This is reproducible on Data Center: yes

Steps to Reproduce

Crowd DC 5.1.3

1. Step 1: Enable Performance Profiling
2. Step 2: Test to login with some user.

Expected Results

The log will be output like the following KB document.

• Performance Profiling

Actual Results

The log won't be output like the following KB document.

Workaround

When you get Performance Profiling, you need the following configurations.

• Enable Profiling Logging
  • Add com.atlassian.util.profiling.Timers as DEBUG
  • Add com.atlassian.util.profiling.UtilTimerStack as DEBUG

• sample: atlassian-crowd.log

  2023-06-20 07:25:05,741 http-nio-8095-exec-3 DEBUG [atlassian.util.profiling.Timers] [1.2ms] - ApplicationService.getCurrentEventToken()
   [1.2ms] - ApplicationService.getCurrentEventToken()
    [1.2ms] - ApplicationService.getCurrentEventToken()
  
  2023-06-20 07:25:06,061 http-nio-8095-exec-20 DEBUG [atlassian.util.profiling.Timers] [2.9ms] - ApplicationService.searchUsers()
   [2.6ms] - ApplicationService.searchUsers()
    [2.6ms] - ApplicationService.searchUsers()
     [1.9ms] - DirectoryManager.searchUsers()
  
  2023-06-20 07:25:06,409 http-nio-8095-exec-23 DEBUG [atlassian.util.profiling.Timers] [4.2ms] - ApplicationService.searchGroups()
   [3.8ms] - ApplicationService.searchGroups()
    [3.8ms] - ApplicationService.searchGroups()
     [2.9ms] - DirectoryManager.searchGroups()
  
  2023-06-20 07:25:06,711 http-nio-8095-exec-10 DEBUG [atlassian.util.profiling.Timers] [5.0ms] - ApplicationService.getMemberships()
   [4.1ms] - ApplicationService.getMemberships()
    [4.1ms] - ApplicationService.getMemberships()