We are getting a query which taking almost 10 min time for execution in dt database dashboard as shown below.
Whereas when we checked for this query in database we haven't found this query taking that much of time.
But what we have observed is number of execution in dt is much lesser than AWR report.
is it so that dt is combining the number of executions together and showing that it is running for long time?
Solved! Go to Solution.
Based on the Screenshot this SELECT statement is executed 432 times with an average execution time of 2.5s which is totalling up to 10mins. You also have a wide spread execution time range. Min is 0.51 - Max is 544s.
Everytime you open a dashlet like this you will see an aggregated view of all calls to each SQL statement in the specified timeframe -> the default timeframe is 30 minutes. So - when you compare data sets from dynatrace and AWR make sure you look at the same timeframe
Also remember that dynatrace sees execution time as seen from the application as we instrument JDBC/ADO.NET. If there is a network issue between your App Server and the Database dynatrace would include that network time in the database as well
surprising the time-frame for both that is dt as well as AWR report is 1 hr so time frame is same.
still the execution count differs drastically between AWR report and dt report.
Well. The other thing is that Dynatrace only sees those SQL Executions that are executed in the context of a PurePath. By Default you will get PurePaths for your web requests. I dont know your application - but - could it be possible that your application is also doing some background work in worker threads that are not yet captured by Dynatrace as PurePaths? If that is the case you can configure custom entry point sensors so that dynatrace also captures these types of transactions that are not triggered by an end user.