• /
  • ログイン
  • 無料アカウント

Create and update key transactions

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

There are two ways to create a key transaction:

Rename a key transaction

Here's how to rename:

  1. Go to one.newrelic.com > More > Key transactions.
  2. From the index, select the gear icon for the key transaction you want to rename.
  3. 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.

重要

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:

  1. Go to one.newrelic.com > More > Key transactions.
  2. Select the icon for the transaction you want to edit.
  3. 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:

  1. Go to one.newrelic.com > More > Key transactions.
  2. Select the gear icon for the key transaction you want to delete.
  3. Select Stop tracking.

New Relic automatically deletes any associated alerts and events for the deleted key transaction.

その他のヘルプ

さらに支援が必要な場合は、これらのサポートと学習リソースを確認してください:

問題を作成する
Copyright © 2020 New Relic Inc.