Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Are there any guides to Jira log files?

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 https://tomcat.apache.org/tomcat-7.0-doc/logging.html - 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 http://www.loggly.com/ultimate-guide/troubleshooting-with-java-logs/ 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!

Like # people like this

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.

Not an option :(

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

Mahendran 

 

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

Hi,

 

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
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

329 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you