Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Alert definition example: operation attributes

We do not have any out-of-the-box alerts for detecting application responses or errors based on responses, but we can define a new metric-based alert to detect when the metric Operation attributes(1) is greater than 0 and break down by URL to inform the operator which page caused the error.

  1. Open the Alert management screen.

  2. On the Alerts tab, click User-defined.

  3. Click Add Alert to access the alert configuration wizard.

Specify basic settings

On the Alert basic settings page of the wizard, in the Alert type list, select Generic performance .

Type an Alert name for your alert.

You need to give your alert a simple but descriptive name. If you are creating a number of alerts, you should name them consistently and with sorting in mind (so that similar alerts appear together in tables of alerts).

Optional: Type an Alert description for your alert.

A good practice is to give your alert a short, simple description that will remind you why you created the alert and what it does. This description is displayed on the Alert Management screen when you select an alert in the list.

In the Report servers selected for the alert list, specify the report server installations to which your alert should be applied.

All active report servers in your console device list appear in this table, and by default, the new alert is enabled on all of them.

Click Next.

Define triggering and propagation conditions

On the Triggering and propagation settings page of the wizard, on the Detection settings tab, specify the conditions under which the alert will be raised.

  1. In the Monitored dimensions section, click Add dimension and select Operation from the dimension list.

  2. In the Dimension filters section, click Add filter and select Server IP address from the list.

  3. In the Server IP address text box, type your server's IP address.

  4. In the Monitored metric section, open the list of metrics and select Operation attributes(1) from the list.

  5. Click Add condition and select Value condition.
    The default values (greater than and 0) are correct for this example.

Click Next.

Configure alert notifications

On the Alert notifications page of the wizard, define a notification message template.


For the notification to be sent, there needs to be at least one recipient configured in the RUM Console. For more information, see Managing Alert Notification Recipients.

In the template, use generic textual information and elements selected from the list hidden under the Filter syntax guidelines icon. For this alert, you could specify the simple message:

Alert: {0}
Operation: {8} 
Operation attributes: {17}

When a notification is sent, it will contain the name of the alert, the name of the operation and the number of the detected operation attributes for each operation.

For a selected user, go to Actions  ► Enable notifications.

Click Next.

Review summary

  1. On the Review summary page of the wizard, verify your alert settings before you apply them to the report servers.

    If you need to change anything, click Previous to go back to the appropriate page of the wizard.

  2. Click Apply.

    On the pop-up window you can select the option to save your changes as a draft, if you intend to make more changes now, or to immediately publish the changes if you want to make your changes live now.