In New Relic APM, transaction traces record in-depth details about your application's transactions and database calls. If transaction traces are included as part of your subscription level, they are enabled by default in New Relic APM. You can also edit the default settings for transaction traces.
Access to this feature depends on your subscription level.
Configure transaction trace settings via agent
You can customize your transaction trace settings via New Relic agent configuration files and other "local" configuration methods such as environment variables.
Select a New Relic language agent to see its transaction trace configuration options:
Configure transaction traces using server-side configuration
The ability to configure transaction traces using server-side configuration depends on the New Relic agent. For example, the New Relic Go and PHP agents do not support server-side configuration. If you are using these agents, the transaction trace settings will be visible in the UI but not editable.
To access server-side configuration settings for transaction traces if available for your New Relic agent:
Go to rpm.newrelic.com/apm > (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
Configure traces for specific (key) transactions
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.
Create custom transactions
You can create custom transactions for app activity that isn't being automatically captured as a transaction by the New Relic agent. See Custom instrumentation for more information.
Collect HTTP request attributes, parameters
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 information on how to capture custom attributes, see Collect custom attributes.
Delete a transaction trace
When you delete a transaction trace, it is deleted permanently.
- Delete a single transaction trace
To delete a transaction trace record permanently:
- In New Relic APM, select a transaction trace.
- Below the transaction trace's title, select Delete this trace.
- Delete all transaction traces
To delete all traces for the selected app permanently:
- In New Relic APM, go to the Transactions page.
- At the bottom of the list of transactions, select Delete all traces.
It may take fifteen minutes or more for all transaction trace records to disappear from the UI.
To delete all traces for your account, get support at support.newrelic.com.