Application Database Monitoring: The Middle Way

Sometimes you just need to know what a database client is doing in the database. You might be:

  • Debugging an application and trying to figure out if its database interactions are a problem.
  • Analyzing the performance of a serverless function to determine if some queries take too long.
  • Testing an application and making sure its database interactions are as expected.
  • Auditing a system to make sure it does not do anything funny in the database.
  • Reverse-engineering an application.
  • You get the picture, the list is endless.

What's the Database Doing Now?