Next week DrupalCon 2013 is happening right in the backyard of our Engineering HQ in Portland. And we’ve been busy crafting new Drupal specific improvements to our PHP agent in time for the conference. (Those updates came out Wednesday!) But before we talk about those great enhancements, let’s take a look at the other major and minor features we’ve released to give you the best application performance management for your Drupal application!
We’ve added support for audit logging. The audit log contains all the data that New Relic sends up to our servers. This gives Sys Admins and Security Admins a view of the data being sent to New Relic. That’s one more feature that gives you additional confidence in your web application security.
The PHP agent now captures the error types for any errors that occur. This allows you to selectively include or exclude certain error messages. This is especially good news when you work with frameworks that can be overly chatty with some warning errors.
Have you always wanted to know how much time was used for a particular transaction trace? Now you can! We’ve added the additional information for transaction traces to report the CPU burn that occurred to satisfy that transaction. You can now investigate those CPU-intensive transactions, which will save both time and money.
Show Full URL in External Transaction Traces
For all your external services calls, New Relic will now show you the full URL instead of displaying only the domain. You can also choose to configure New Relic so that the trace includes the URL parameters.
The biggest feature we released recently in PHP land is support for Key Transactions. This feature allows you to identify those important business transactions you want to monitor and manage – regardless of the overall application throughput. With just a couple of clicks, you can track the most important transactions in your business. Now you can make sure they perform well compared to their historical norms.
Key Transactions works well with related features such as Alerting, SLA reports, and App Map to give you more ways of staying informed about your business-critical transactions. To learn more about Key Transactions, please read about the feature launch and the follow up post, which includes a video.
In our next post, we’ll give a tour of the latest and greatest improvements in our performance monitoring support for Drupal users. Stay tuned for more information on the New Relic presence at the conference – where you can talk to our PHP team and learn even more!