Instrument transactions using the C SDK so you can monitor any application on Linux that uses a language that can import C libraries. After you manually instrument transactions in your source code by adding New Relic functions, you can view the data on the Transactions page in the New Relic UI.
For an index of documentation during the private Beta, see the C SDK table of contents.
To instrument a transaction so you can monitor it in the New Relic UI, wrap the New Relic functions that start and stop instrumentation around the transaction. The function that you use depends on whether you want to instrument a web or non-web transaction.
Add the following code immediately before the transaction that you want to monitor:
For web transactions:
For non-web transactions:
newrelic_txn_t *txn; /* ... */ txn = newrelic_start_non_web_transaction(app, "NAME_YOUR_TRANSACTION");
Add the following code immediately after the web or non-web transaction that you want to monitor:newrelic_end_transaction(&txn);
Segments are the functions and calls that make up a transaction. After you instrument transactions, you can:
- Instrument segments of a transaction if you want more data about functions called during that transaction.
- Instrument errors so that you can use the New Relic UI to monitor errors that occur during your transactions.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.