Hello,
When viewing the Database Dashboard and looking at the response times of used sql queries, we are only able to see selects and inserts while we have stored proc's that are being run also.
There is one stored proc that does show up for some reason but all of the rest do not show up.
Answer by Andreas G. ·
We should not make a difference between "regular" SQL and stored procedures. I wonder though if your Stored Procedure calls are made in transactions that you do not get a PurePath for.
So - let me ask you this: do you have a PurePath that shows the code execution where you expect the Stored Procs to be called but dont see them?
What we often see with other applications is that there are background worker threads that execute database statements. By default you dont get a PurePath for these transactions as they are not initiated by a Web Service or HTTP Request. Make sure that you see these transactions - then check again if you also get to see these Stored Proc calls.
In case you do have transactions like that you need to define your own custom Entry Point Sensors that will start new PurePaths for your background jobs
Andi
There are background threads but these are purely clean up procs and things like that. All of the stored procs we are looking for have been initiated by a web service call.
If this is a test environment you could try to set the JDBC sensor to "active and start PurePath". then see whether you get to see all these SQL Calls. If you get to see them after that change it means that these SQL Calls are not made on a transaction that is currently captured by a PurePath.
JANUARY 15, 3:00 PM GMT / 10:00 AM ET