Mark Jira Data Center Logs for Easier Troubleshooting

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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

Troubleshooting errors from large log files is easier when the logs are marked before and after the problem occurs, narrowing the search scope.

Environment

All versions of Jira Data Center (inherited by Jira Software and Jira Service Management).

Marking the logs

Mark the logs via the following steps:

  1. Navigate to Jira Administration >> System >> Logging and profiling >> Mark Logs (<baseURL>/secure/admin/ViewLogging.jspa).
    A form to mark Jira log files. It includes a field for an optional message and a checkbox for log rollover, which starts the logs in fresh files. A Mark button submits the form.
  2. Mark the logs with "replication starts here".
  3. Replicate the problem. 
  4. Mark the logs again with "replication ends here".

The logs will have the following entry:

2016-05-06 11:22:31,180 http-nio-8712-exec-4 uri:/j712/secure/admin/ViewLogging!markLogs.jspa username:admin INFO admin 682x4670x1 1k1ukiz 10.60.3.51 /secure/admin/ViewLogging!markLogs.jspa [c.a.j.util.log.LogMarker] 
    
    ***********************
    replication starts here
    ***********************
    
2016-05-06 11:22:48,525 JiraTaskExectionThread-1 INFO admin 682x4705x1 1k1ukiz 10.60.3.51 /secure/admin/IndexReIndex.jspa [c.a.j.w.a.admin.index.IndexAdminImpl] Re-indexing started
2016-05-06 11:22:48,528 JiraTaskExectionThread-1 INFO admin 682x4705x1 1k1ukiz 10.60.3.51 /secure/admin/IndexReIndex.jspa [c.a.j.util.index.CompositeIndexLifecycleManager] Reindex All In Background starting...
...
2016-05-06 11:22:50,828 JiraTaskExectionThread-1 INFO admin 682x4705x1 1k1ukiz 10.60.3.51 /secure/admin/IndexReIndex.jspa [c.a.j.w.a.admin.index.IndexAdminImpl] Re-indexing finished
2016-05-06 11:23:00,104 http-nio-8712-exec-19 uri:/j712/secure/admin/ViewLogging!markLogs.jspa username:admin INFO admin 683x4735x1 1k1ukiz 10.60.3.51 /secure/admin/ViewLogging!markLogs.jspa [c.a.j.util.log.LogMarker] 
    
    *********************
    replication ends here
    *********************

All log files under $JIRA-HOME/log/ are marked simultaneously, as well as the $JIRA-INSTALL/logs/catalina.out file.

For more info, please see Useful log files in Jira.


Last modified on Feb 20, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.