Jira Data Center debug logging reference

Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

This article serves as a reference to Support Engineers and Jira admins to identify which packages need to have DEBUG logging enabled while troubleshooting issues in Jira.

Logging levels can be configured in Jira as indicated in Change logging levels in Jira Server.

Solution

Reference table

Operation

Package(s)

Ref/Notes

Cache replication

com.atlassian.jira.cluster.cache.ehcache

Class: BlockingParallelCacheReplicator

Directory sync

com.atlassian.jira.crowd

com.atlassian.crowd

Disaster Recovery Replication

com.atlassian.jira.cluster.disasterrecovery

DVCS sync

com.atlassian.jira.plugins.dvcs

Class: RepositorySyncServiceImpl

External (delegated) directory authentication

com.atlassian.crowd.directory

Class: DelegatedAuthenticationDirectory

Index replication

com.atlassian.jira.index.ha

Class: DefaultIndexRecoveryManager

Indexing

com.atlassian.jira.index

com.atlassian.jira.issue.index

Lexorank balancing

com.atlassian.greenhopper.service.lexorank

com.atlassian.greenhopper.manager.lexorank

Mail

com.atlassian.mail

com.atlassian.mail.incoming

Service Management SLAs

com.atlassian.servicedesk.internal.sla

SQL

net.java.ao.sql

XML restore

com.atlassian.jira.bc.dataimport

WebHooks

com.atlassian.webhooks

Ref.: How to collect data to troubleshoot WebHook failure in Jira

Microsoft Teams

com.microsoft.teams.lifecycle

com.microsoft.teams.lifecycle.scheduler

com.microsoft.teams.oauth

com.microsoft.teams.service

Updated on April 21, 2026

Still need help?

The Atlassian Community is here for you.