JIRA doesn't log com.atlassian.support messages by default

Summary

JIRA doesn't include logging for com.atlassian.support, com.atlassian.troubleshooting packages by default.

Steps to Reproduce

1. Do any action in STP

Expected Results

Logging present in JIRA logs.
For example:

• com.atlassian.support.tools.hercules.LogScanTask

  2017-05-10 17:48:01,257 hercules INFO admin 1066x97x2 k85kiv 127.0.0.1 /plugins/servlet/stp/view/hercules/execute [c.a.s.tools.hercules.LogScanTask] Scan failed:
  java.lang.InterruptedException
          at com.atlassian.sisyphus.DefaultSisyphusPatternMatcher.matchLine(DefaultSisyphusPatternMatcher.java:95)
          at com.atlassian.sisyphus.DefaultSisyphusPatternMatcher.match(DefaultSisyphusPatternMatcher.java:78)
          at com.atlassian.support.tools.hercules.LogScanTask.call(LogScanTask.java:57)
          at com.atlassian.support.tools.hercules.LogScanTask.call(LogScanTask.java:24)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:745)
  

• com.atlassian.support.healthcheck.DefaultSupportHealthCheckSupplier

  2017-05-10 17:46:55,393 http-nio-8081-exec-8 DEBUG admin 1066x100x1 k85kiv 127.0.0.1 /rest/supportHealthCheck/1.0/check/process/ [c.a.support.healthcheck.DefaultSupportHealthCheckSupplier] Supplying health check from descriptor: com.atlassian.jira.plugins.jira-healthcheck-plugin:hsqlHealthCheck (jira.healthcheck.hsql.description)
  

another example

2019-04-25 11:50:20,005 heartbeat-scheduler-0 INFO      [c.a.t.j.h.scheduler.impl.HeartbeatSchedulerImpl] Scheduling job with : JobConfig[jobRunnerKey=com.atlassian.troubleshooting.jira.healthcheck.schedu
ler.impl.HeartbeatSchedulerImpl,runMode=RUN_LOCALLY,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=null,intervalInMillis=10000]],parameters={}]

Actual Results

No logging.

Notes

See related atlassian-jira/WEB-INF/classes/log4j.properties.
Default level is WARN:

...
# To turn more verbose logging on - change "WARN" to "DEBUG"
log4j.rootLogger=WARN, console, filelog, cloudAppender
...
log4j.logger.com.atlassian = WARN, console, filelog, cloudAppender
log4j.additivity.com.atlassian = false

log4j.logger.com.atlassian.jira = INFO, console, filelog, cloudAppender
log4j.additivity.com.atlassian.jira = false
...

Workaround

Manually enable DEBUG logging for com.atlassian.support classes. This need to be done after each restart.

1. Navigate to [ Administration > System > Logging & Profiling ]
2. com.atlassian.support package is not present by default, so Click Configure logging level for another package.
3. Fill the form as follows:
   • Package name: com.atlassian.support
   • Logging Level: DEBUG

Or modify atlassian-jira/WEB-INF/classes/log4j.properties and include com.atlassian.support logger

same for com.atlassian.troubleshooting logger

log4j.logger.com.atlassian.troubleshooting  = INFO, console, filelog