When DevOps experts need to track down the cause of errors in an app, it’s not always easy to get to the root of the problem. Using applied intelligence, New Relic APM error profiles is designed to help by automatically comparing one set of events to another to make it easier to identify the issue.

The error profiles feature is now available to all paying New Relic APM customers, and customers using APM error analytics will be able to leverage error profiles. The error profiles feature is designed to help software engineers quickly identify what is unusual about an error or set of errors, and lets them quickly filter to focus on what they are interested in. With a quick scan, an engineer can find the most likely culprit and get to work right away resolving the errors.

Error profiles uses statistical measures to surface the errors that deviate most dramatically from the non-error transactions in your app. Each error profile provides visual details about differences in the frequency of values for the events, showing you where to focus your attention without making you manually click through all the dimensions.

new relic apm error profiles

[click to enlarge]

For each attribute, the error profile includes:

  • A pie chart showing how the error’s attribute is distributed for values that deviate the most
  • A table comparing the error attribute’s distribution to that of non-erroring transactions

apm error profiles

[click to enlarge]

apm error profiles

[click to enlarge]

Error profiles shows you the distinctive attributes of each error, which can be the key to determining its root cause. Are all the problems coming from one method? From one account or user? You no longer need to manually facet by the attributes you think might be at play. Error profiles will facet by all the attributes and tell you which ones are unusual.

Overall, error profiles is designed to help you take more of the guesswork out of resolving your app errors. You can more easily determine if you can safely ignore the error, or if you should attempt to resolve the error with a new deployment, code edits, customer communications, or other actions.

Early users are already impressed: “The error profiles feature automates my manual process for troubleshooting,” says Adam Gelinas, principal software engineer at Constant Contact. “I routinely switch the grouping of errors so that I can look for patterns in the attributes we are tracking. This feature saves me time.”

Learn more about APM error profiles by joining the discussion about New Relic APM Error Analytics in our New Relic Online Technical Community.

 

Shreyans Parekh is a Product Marketing Manager at New Relic, where his job is to focus on market and industry dynamics in the areas of cloud migration and DevOps. His writing has appeared in publications by Internet Retailer, Intuit, Apttus and IBM Bluewolf. He can be reached on Twitter @ShreyParekh. View posts by .

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