• /
  • Log in
  • Free account

Instrument errors with the C SDK

New Relic defines a web or non-web transaction as one logical unit of work in a software application. Once you instrument a transaction, you can also instrument errors in the transaction so you can monitor them in the New Relic UI. In order to use the C SDK to monitor errors, you must manually instrument your source code by adding the New Relic function newrelic_notice_error() to it.


To include function calls in error traces, use GNU's -rdynamic linker flag to link your apps when compiling. The -rdynamic linker flag gives you more meaningful error traces.

Instrument errors in transactions

To instrument errors in transactions:

  1. Start a transaction.
  2. Record an error with newrelic_notice_error(), supplying the required parameters.
  3. End the transaction.

View errors

Transaction errors and error traces appear on the Error analytics page in the New Relic UI. The C SDK reports the total number of errors and up to 100 error traces per minute on the Error analytics page.

You can also view, query, and visualize transaction errors in New Relic One as TransactionError events.

Examine logs for error details

You can bring your logs and application's data together to make troubleshooting easier and faster. With logs in context, you can see log messages related to your errors and traces directly in your app's UI.

  1. From the Errors page, click on a trace to go to the Error details page.
  2. From the error details page, click See logs.
  3. To view details related to an individual log message, click directly on the message.

Logs in context of APM error details

With logs in context, you can examine log data directly within your error details.

You can also see logs in context of your infrastructure data, such as Kubernetes clusters. No need to switch to another UI page in New Relic One.

For more help

If you need more help, check out these support and learning resources:

Create issueEdit page
Copyright © 2021 New Relic Inc.