• /
  • Log in
  • Free account

Instrument errors with the C SDK

BETA

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.

Tip

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.

Contents

For an index of documentation available during the private Beta, see the C SDK table of contents.

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 Insights as TransactionError events.

For more help

Beta support for the C SDK is being handled through New Relic's Explorers Hub in a private group. If you need access to the support group, contact Jodee Varney (Product Manager) at jvarney@newrelic.com. Normal support channels will re-route you to the community or the Product Manager.

Create issueEdit page
Copyright © 2021 New Relic Inc.