The Zurich release has arrived! Interested in new features and functionalities? Click here for more

How to identify the source of query

BhupeshG
Tera Guru

Hello All - there is one query in slow query log which is being triggered by below example trace. Kindly suggest how to identify which process it is and who is calling this..

SOAPProcessorThreadb825df9cdbea8300520916d15b96194e

com.glide.db.stats.query.QueryStats.recordQuery(QueryStats.java:51)

com.glide.db.DBI.saveStats(DBI.java:1136)

com.glide.db.DBI.sqlVerbosity(DBI.java:1130)

com.glide.db.DBI.executeStatement(DBI.java:843)

com.glide.db.DBI.executeStatement(DBI.java:821)

com.glide.db.DBQuery.executeAsResultSet0(DBQuery.java:297)

com.glide.db.DBQuery.executeAsResultSet0(DBQuery.java:272)

com.glide.db.DBQuery.executeAndReturnTable(DBQuery.java:238)

com.glide.db.DBAction.executeNormal(DBAction.java:219)

com.glide.db.DBAction.executeAndReturnException(DBAction.java:180)

4 REPLIES 4

girishkulkarni
ServiceNow Employee
ServiceNow Employee

From you left navigation type slow queries. Then locate the record in question and once you open the record, you will see "Example" on the top left that list the problem query.



Good Luck!


example says SOAPProcessorThread..


Once you open the record, scroll down and you will see various tabs like 2-hours trend, 1-day trend, etc. You will also see the actual query there. What release you are currently running on?


adamjgreenberg
ServiceNow Employee
ServiceNow Employee

Bhupesh,



Your instance tracks slow queries and even has an explain plan built in.



You can navigate to the slow queries module and search for all your slow queries using the example.



Use a slow query log