Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Are there any guides to Jira log files?

Rob Horan Community Leader Oct 18, 2016

Atlassian documentation offers some very light information, but I was hoping there might be a more robust guide to interpreting the information in all of the logs somewhere out there.

2 answers

1 accepted

2 votes
Answer accepted

There's two main log files for a JIRA - the catalina.out is the application server (tomcat) log file, and there's some stuff over at - again, it's more about general config and changing it, but it's a start on understanding the file.

The other one is the atlassian-jira.log - this is probably the one you're more interested in.  It's in a pretty standard format and basically captures everything if there's a hint of something going wrong.  It is, however, a java log, which is aimed at developers and can be very unfriendly to read. 

I'm not sure that there's much a "guide" can tell you though.  Some of it is intuitive, you can see dates and times, users etc.  When there's a fault or crash, you'll mostly see an "exception" of some sort, which are followed by a stack trace of hundreds of lines of file names and numbers (these really are hardcore dev messages - it's actually the line of source code in that file it is telling us!  So it's useless unless you have the source code).  You'll see batches of informational lines prefixed with warn or info, and then whatever messages the developers have chosen to output in their code.  That's what we can't write a guide for - each class could be doing anything at all, and we need the authors to code to spit out the messages we want!

I've found helped me get my brain around it last time I was stuck, but obviously, that's not a JIRA guide.

Personally, I prefer to sling the logs through a log analyser or monitor - something that can look for patterns (e.g. lots of import related errors at 3am every day) and/or simplify the raw output to something more human.  Even better, I have the option of asking colleagues for help reading them!

Rob Horan Community Leader Oct 21, 2016


Like # people like this
Rob Horan Community Leader Feb 18, 2021

Since I posted this, mostly within the last few months, I've spent a lot of time in the logs, and I can tell you that a guide, or at least a breakdown of the sections would definitely have been useful.

There's an assumption that people looking at these logs have a certain base level of expertise with various things.  That's not always the case.

Yeah, that's why I throw them through log analysers to be honest.

Rob Horan Community Leader Feb 18, 2021

Not an option :(

Rob Horan Community Leader Oct 18, 2016

Thanks - while those give information on where to find the logs, there isn't a lot of information on how to interpret the information in the logs.

Like # people like this



Any suggestion for how to user jira log analyzer in windows for analysing .


(Atalassian-jira.log) log file.

1. throws an error. 

Error parsing atlassian-jira.log at line 100 : Unable to find a request chunk surrounded by double-quotes.

Like Rafael Corredor likes this



Me too!  I use 'access-log-analyser-2.0.1.jar' and all the time it returns this parsing error :(

Any idea?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events