In order to reduce the amount of space used by logs, I'd like to disable them. I have checked the JIRA settings and noticed that all of the logs disabled (for example HTTP Access Logs), but I do still get access_log.YYYY-MM-DD files in the log directory.
Also, stdout logs seem to be really big. Is there a way to disable them?
Hi,
I think this can help you,
https://confluence.atlassian.com/display/JIRA/Logging+and+Profiling
https://confluence.atlassian.com/display/JIRA/How+to+change+the+location+of+stdout+and+stderr+logs
https://confluence.atlassian.com/display/JIRA/User+access+logging
Please read the above for details of disabling it.
Hope it helps.
Hi Nitram!
Thanks for the links, I was able to disable the access logs :) But the documentation about stdout only tells me how to change the location of the files, not how to disable them. Isn't this possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have configured the logging trough the tomcat7w.exe, and just left the log dir empty - it doesn't create any stdout log anymore. Do you think this might have some bad effects somewhere else or is that good practice to disable the log?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's very bad practice to disable the logs fully. Logs are generated for a reason, and if anything goes wrong, you'll need the information that's been put into them.
I'd relocate them to a larger disk to begin with, and then think about turning down the information going in them - the logging and profiling link @Nitram gave you above is where to start - you can set everything in there to a very "quiet" level and the logs will then grow very slowly. You'll then be able to turn if back up if you need to debug something. You can also set the log rotation on the server side to something quite aggressive (maybe keep only 2 days worth of log)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I'll go with Nic regarding keeping the log for few days, As I will also suggest the same, instead of disabling it fully. Since it contains important information, tomorrow if your jira is not working, then you can raise a support request in atlassian by submitting the logs. That might help them and keeping the latest logs wont take much space than keeping all the logs.This is my suggestion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.