In our production system, Stash logs are pretty huge ( more than 100 MB ). It is often difficult to upload these log files to Atlassian support when needed.
Is there a way to configure Stash log files ? Thanks
Yes and no. We use Logback for our logging, but the default configuration file is quite customised, and we would prefer that people don't change it. The files should be rolled per day, and we start removing entries after a month. Unfortunately there isn't an easy way to override that value without configuring the appenders again, which may not be future proof.
Is there any reason the logs are so huge by the way? Just having a quick look through your tickets, I found a large support zip that had debug enabled which is definitely going to generate much bigger logs. You could disable debug, although I agree it makes diagnosing problems much easier for us. Is it possible to manually backup/move some of the older logs to a different folder, maybe via a cron job?
I agree that few logs ( atlassian-stash.log, atlassian-stash-access.log, atlassian-stash-mail.log) are rotated and cleaned-up automatically.
How about the other following logs ? Do we need to clean them up manually ?
Have you try the method to generate a Support Zip file as per https://confluence.atlassian.com/display/STASH/Raising+a+request+with+Atlassian+Supportarticle ? What about try to compress the log files to .zip or .7z ?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot