Alert configuration wizard

Applies to NAM 2018

This alert configuration wizard is available starting in NAM 2018. For alert definition in earlier releases, see Defining an alert.

Before you begin

  • Make sure you have NAM installed.
  • Identify a business need for the alert and the metrics that would trigger such an alert.
  • Determine the default ports available for communications between the individual NAM components.
  • If you intend to send alert notifications via email, a user with administrator privileges needs to configure the server to use an existing SMTP server.

Defining an alert

  1. On the RUM Console menu, select Monitoring ► Alerts to list alert definitions.

  2. Open the configuration wizard for a new or existing alert.

    • To create a new alert from scratch, click the Add alert button.
    • To modify an existing alert, find it in the list and click in the Edit column for that alert.
    • To clone an existing alert and modify the clone, click in the Duplicate column for the alert you want to copy. The copy will appear under the original in the list with a new ID. You can then edit the copy.

    The configuration wizard opens on the Basic settings page.

  3. Basic settings

    • Alert type
      There are different alert types for different purposes. Choose the type that best suits your needs.

    • Alert name
      Make the name easy to find in searches and sorts.

    • Alert description
      Make the description useful to other people (or to you in the future).

    • Devices
      Select the servers reporting traffic to which the new alert will be applied. By default, all available report servers are selected, so you just need to clear the servers to which this alert does not apply.

  4. Triggering and propagation

    • Dimensions and metrics tab

      • Dimensions
        Select the dimension, select the comparison type, and define the filter contents. (To add another row for another dimension, click the Add dimension button first.)

      • Metrics
        The list shows metrics relevant to the Alert type you selected on the Basic settings tab. Select the metric, select the type, and define the filter. If all of the selected metrics match, the alert is triggered and notifications are sent.

        • Metric
          Your alert definition needs one row for each metric you select for your alert.

          • Click Add metric if you need to add another row (another metric) to your alert definition.
          • Click Add compound metric to define a calculated metric, where you define an expression based on other metrics, such as the sum of two standard metrics.
        • Type and associated Filter parameters

    • Advanced configuration tab
      Select Advanced configuration to add an output filter or to configure propagation settings.

      • Monitoring duration and frequency
        Use these two settings to control Time range (the width of this alert’s sliding window) and Frequency (how often the conditions are checked). Time range must be less than or equal to Frequency.

      • Output filter
        You can set additional conditions on metric alert output fields, so that only alerts satisfying these conditions are raised. In the empty edit box, type the filter expression for the selected element. See Filter syntax for more information on filters.

      • Propagation Settings
        These settings control when the alert is raised and add related information to the notification.

  5. Notifications

    • Message
      This is the message sent in the alert. Type or paste a text message explaining what the problem is. To insert the value of a dimension or metric, type a label such as "The value was " (so you know what the value refers to) and then press Ctrl-Space to list dimensions and alerts available to that alert type. Select one of them to insert the value into your message.
    • Alert recipients
      Use the tabs here to select recipient types (email, trap, script, or Slack) and define recipient details.
  6. Summary
    Review the summary and click Finish to save your changes or click Previous to go back and make changes.

Example: Application performance of an application (front-end)

We want to monitor the performance of front-end applications and send an alert if application performance is less than 80 and if more than 5 users are affected.

  1. Basic settings

    • Alert type = Application user experience
  2. Triggering and propagation

    • Dimensions:

      • Is front-end tier
        Type = Dimension and Filter, Filter = ~(Enterprise Synthetic|Backbone|Private Last Mile|Last Mile)
        Because we are interested in tiers that are NOT Enterprise Synthetic, Backbone, Private Last Mile. or Last Mile.
      • Tier
        Type = Dimension and Filter, Filter = ~(Enterprise Synthetic|Backbone|Private Last Mile|Last Mile)
        Because we are interested in tiers.
      • Application
        Type = Dimension and Filter
        Because we are interested in applications on the front end.
    • Metrics:

      • Performance
        Type = Value, Filter = <80
      • Affected users (performance)
        Type = Value, Filter = >5
  3. Notifications
    The last page of the wizard is where you create the message you want to send and define who you want to send it to.

    • Notification
      This is the message your alert recipients will get].

      • In the box, describe what has happened. What made you want to send out this alert? What do the recipients need to know right now and what should they do about it?
      • To quote a relevant metric in your message, press Ctrl-Shift-Space and select the metric from the list. If you know the exact name of the metric, you can type it manually, enclosed in curly brackets. Here's our basic example:

      Application performance of application {Application} (front-end only) has dropped below 80.
      Current value of application performance: {Performance}.
      Number of affected users: {Affected users (performance)}.

      Things within curly brackets will be replaced by actual values when the alert is generated.

    • Alert recipients
      This is where you decide who should get this notification and how they should get it. For example, you might want this particular alert to go to email for a couple of relevant people and to go out as a Slack message.