Problem Definition

While troubleshooting DVCS issues, we need to enable DVCS debug logs very frequently. Due to the size of the implementation (No. of repositories and Orgs), very often the logs get too spammy to identify clearly what's happening.
This not only makes it difficult to troubleshoot DVCS issues, but also spamming the atlassian-jira.log with the DEBUG logging can obscure relevant logging for other issues as well.

Suggested Solution

Create separate log4j.properties definition for DVCS logger and redirect them to a different set of files instead of atlassian-jira.log.

Workaround

None