In APM, transaction traces record in-depth details about your application's transactions and database calls. You can edit the default settings for transaction traces.
You can customize your transaction trace settings via New Relic agent configuration files and other "local" configuration methods such as environment variables. For more information about transaction trace configuration options, see the specific New Relic language agent's documentation:
The ability to configure transaction traces using server-side configuration depends on the New Relic agent. If server-side configuration is not supported, the transaction trace settings will be visible in the UI but not editable.
If server-side configuration settings are available for your New Relic agent, you can see them at the following: one.newrelic.com > APM & services > (select an app) > Settings > Application > Server-side agent configuration.
Transaction trace settings available using server-side configuration will differ depending on the New Relic agent you use. The UI includes descriptions of each. Settings in the UI may include:
- Transaction tracing and threshold
- Record SQL, including recording level and input fields
- Log SQL and stack trace threshold
- SQL query plans and threshold
- Error collection, including HTTP code and error class
- Slow query tracing
- Thread profiler
- Cross application tracing
If you want to monitor or alert on a transaction differently than other transactions, make it a key transaction. This is useful, for example, when you want to set a transaction-specific Apdex that is different from your general Apdex T threshold.
Changing a key transaction's Apdex changes the likelihood that it creates a transaction trace. For example:
- If you want to make it more likely a key transaction would generate transaction traces, lower its Apdex T value.
- If you want to make a key transaction less likely to be traced, raise its Apdex T value.
If you have the transaction trace threshold set to a number of seconds, and not to the default Apdex setting, the number-of-seconds threshold will act as the threshold for all transactions, even for key transactions that have custom Apdex settings.
You can also 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. You can also see logs in context of your infrastructure data, such as Kubernetes clusters. No need to switch to another UI page.
You can create custom transactions for app activity that isn't being automatically captured as a transaction by the New Relic agent. For more information, see Custom instrumentation.
For data security reasons, transaction traces do not collect potentially sensitive HTTP request attributes, sometimes called parameters. Traces do collect some basic HTTP request attributes, which New Relic calls agent attributes. To edit attribute collection settings, see the specific New Relic agent:
For more information, see Collect custom attributes.
When you delete a transaction trace, it is deleted permanently.