Get the list of all JQL's fired in JIRA

[Sridhar Nimmagadda]

I am interested in getting all the JQL's that are fired by a JIRA instance, the atlassian-jira-slow-queries.log will only log the queries that take > 400ms to execute..so that leaves me with remaining queries that take < 400 ms to execute.

[MattS]

From my older book "Practical JIRA Plugins" (O'Reilly):

You can display the original JQL query and its associated Lucene query in the JIRA log file by adding the following lines to log4j.properties file:

log4j.logger.com.atlassian.jira.issue.search.providers.LuceneSearchProvider = \ INFO, console, filelog

log4j.additivity.com.atlassian.jira.issue.search.providers.LuceneSearchProvider = false 

but this is likely to impact your JIRA performance

[Jobin Kuruvilla [Adaptavist]]

If you must, turn on access logs and use some tools like the ELK stack to drill down the JQL calls.

[Sridhar Nimmagadda]

hmm looks like an option. will try it

[Sateesh Chandra]

Every jql query internally fires a database query. The slow query logs actually display the sql queries. The complete list will almost cannot end.

[Sridhar Nimmagadda]

All JQLs fire SQL ? whats the purpose of Lucene Indexes ?

[Nic Brough -Adaptavist-]

I don't think Sateesh meant to say that. JQL doesn't generally run much SQL against your database - it does check permissions, but most of the work in a search is done against the Lucence index. So whatever you're really looking for here, you're probably looking in the wrong place. Could you explain why you think you want to do this? What's the problem you're trying to solve by looking at JQL activity?

[Sridhar Nimmagadda]

I am looking for all JQL's fired during a time period and optimize them...well i understand if a JQL takes <400ms there is nothing to worry about it..still checking out if i can get the complete list.

[Nic Brough -Adaptavist-]

You can't "optimise" JQL. It's not SQL.