Hello community,
We sometimes have actions which are consuming a lot of resources and could make our Jira crash. I would like to identify those actions.
What would be the way to do that ? I tried to check the access log at the time when we had the latencies/crash but not always relevant I think.
Thanks for the help.
Hi Arthur,
it might be a candidate for the logging & profiling section:
https://confluence.atlassian.com/adminjiraserver/logging-and-profiling-938847671.html
Using this you can try to narrow down what causes your instance trouble in the moment the effects occur.
Please keep in mind that a lot more circumstances might add up to the situation or at least influence it - some deeper knowledge of your system and users would be required. This is nearly impossible to debug from over here.
It also seems to me it can be useful to pass this knowledge base article - but you need to investigate and evaluate further where to start from:
In case of specific findings I am sure somebody from Community is happy to catch up. Provide as many details as possible (please do not forget to anonymize relevant parts if you want to paste log file snippets for example).
Cheers,
Daniel
Thank you for your reply Daniel,
I will dig that ASAP. :)
Cheers,
Arthur
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.