In APM, you can make a transaction a key transaction when you want it to have a custom level of monitoring, or when you want it to have its own alert policy.
For most New Relic agents, a key transaction can be any type of transaction. For the PHP, Node.js, and Go agents, only web transactions can be turned into key transactions.
Create key transactions
To create a key transaction:
- Go to one.newrelic.com > More > Key transactions to view the key transactions index.
- Select Add more, then select an application and a transaction.
Rename a key transaction
Here's how to rename:
- Go to one.newrelic.com > More > Key transactions.
- From the index, select the gear icon for the key transaction you want to rename.
- Enter a new name for the transaction, then save.
Change Apdex settings
You can set a custom Apdex threshold for a key transaction if it is a web transaction. (Apdex is not applicable for non-web-transactions.) This is useful if the transaction is expected to be faster or slower than other transactions.
Important
Key transaction Apdex settings override the T value set for that app. This can mean, for example, that a key transaction could be reported as Satisfied but a different transaction in the same app with the same response time could be Frustrated.
To change a key transaction's Apdex threshold:
- Go to one.newrelic.com > More > Key transactions.
- Select the icon for the transaction you want to edit.
- Enter a new value in seconds under the Apdex T heading, then save.
The Apdex threshold affects how key transaction traces are created.
Delete key transactions
To delete a key transaction:
- Go to one.newrelic.com > More > Key transactions.
- Select the gear icon for the key transaction you want to delete.
- Select Stop tracking.
New Relic automatically deletes any associated alerts and events for the deleted key transaction.