Last month, we released a beta version of the Agent SDK, which lets you build your own custom agent in any language. Some of you have already started using it and are ready for us to release the next feature. Nice work! So here you have it: the latest beta, now supporting database transactions. Take a look at how to get started for more information.
With database support you can view how much of a web transaction’s time is spent performing database operations. This is useful information when you’re investigating a performance problem and need to determine whether or not it’s a database issue. You can now drill down further to track which database operations are taking the most time and how many times they’re being called during a web transaction.
For example, let’s say that you’ve discovered your view_cart transaction is particularly slow. You can take a look at the transaction’s breakdown table to determine which operations are taking the longest and see how many times they’re being called.
Here you can see the breakdown of a view_cart transaction. There are seven database operations that occur during this transaction and 38% of the time is spent querying the cart_item table. You’ll also notice that the cart_item table is being queried four times during the transaction, which is something that you could optimize.
With this update, you’ll be able to see the standard New Relic database features such as the database throughput, response time, and top 5 operations by wall clock time charts.
Finally, you’ll also see a table with database transactions that you can sort and click on to get more detailed information.
Here, database transactions were sorted by “Most time consuming” and we’re looking at the detailed information regarding the SELECT query on the cart_item table. You can view its response time, throughput, and the time it consumes during each of the web transactions that call it.
So there you have it! The Agent SDK supports yet another feature, and there will be many more to come.