Any recommendations on how to setup monitoring for long running JQL queries in Splunk?
I am following this as well. Or is there any possibility to check long running jql's? (so we can reach out to the customer to see if there is a need of tweaking)
I don't mind if this is on database level or something else...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try checking out the following
https://community.atlassian.com/t5/Jira-questions/Slow-JQL-Logging/qaq-p/401338We do this and use Splunk to find anything higher than 20s and send a report.
Still have a question?
Get fast answers from people who know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.