Announcing SQL Traces and High Security Support in the Agent SDK

We have a couple Agent SDK announcements for you this week. First, we deployed two major releases since our last blog post, adding support for High Security Mode and SQL Traces. Second, there is now a public Agent SDK category on our Community Forum. This will make it easier for you to find help and relevant information on the Agent SDK and how to use it.

Now for a quick overview of the updates in versions 0.12 and 0.13.

SQL Traces

The Agent SDK now sends traces for your worst-performing SQL statements, which show up under the Database tab. For those of you already using the SDK, all you need to do is provide SQL wherever you’ve instrumented datastore segments and the Agent SDK will do the rest. It’ll automatically obfuscate, aggregate, and determine which statements were the worst-performing each minute before a harvest. You can also provide your own custom obfuscater as well as tell the agent how to aggregate your SQL traces.

SQL Traces

SQL in Transaction Traces

Now, if a Transaction Trace includes any database segments, you’ll be able to see the SQL that was run, which may point to why a particular transaction was so slow.

SQL in Transaction Traces

High Security Mode

Since version 0.12, the Agent SDK has supported New Relic’s High Security Mode, a setting that protects sensitive data from being collected and sent to New Relic.

Let us know if you have any feedback or comments about these updates in the Forum!

Abner Germanow was formerly Senior Director of Partner Marketing & Evangelism at New Relic. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!