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

  • NAM 2018 alerts changed. Even if you're an alert power user, try to copy and edit one of the example alerts shipped with NAM 2018 as an example which will help you understand the new alerting concepts.
  • Identify a business need for the alert and the metrics that would trigger such an alert.
  • If you intend to send alert notifications via email, a user with administrator privileges needs to configure the NAM server to use an existing SMTP server. See Mailer setup. Make sure that all the email recipients you intend to send alerts to are NAM users with an email address. You won't be able to add a new email recipient using alert management pages.
Create alert from report

Applies to NAM 2019+

If you have switched to NAM 2019, NAM can now take most of the work out of defining an alert. NAM 2019 enables you to open a report, click a tile or table entry (some restrictions apply), and select Create alert with most of the alert settings prefilled based on the report where you started. See Creating alerts from NAM reports for details.

Defining an alert

Defining or editing your alerts is divided into three main steps:

Choose the scope of monitoring data your alert will be based on, name your alert (with no leading or trailing whitespace characters) and optionally describe it. You can also select NAM servers (devices) that will manage and propagate your alert.

Alerts basic settings

Selecting an alert type determines the scope of monitoring data used to trigger an alert and which metrics and dimensions you'll be able to use.

Real user performance (probe)
These alerts monitor traffic between a client and a server. They are based on traffic monitored by NAM Probe, including the elements that are configured on the NAM Server: applications, transactions, tiers, regions, areas and sites.

Sequence transactions
These alerts monitor transactions and track the HTTP-based software service activity of synthetic agents and standard users. They are based on traffic monitored by NAM.

Enterprise synthetic
These alerts monitor transactions and track the HTTP-based software service activity of synthetic agents and standard users. They are based on traffic monitored by Enterprise Synthetic.

Citrix/WTS hardware
These alerts monitor the performance of Citrix servers or Windows Terminal Services (for example, the number of active or open sessions).

Network link
These alerts monitor link utilization.

Internetwork traffic
These alerts monitor traffic coming in and going out of a specific site.

Application user experience
These alerts monitor application user experience for all measurement sources: probe, browser, enterprise, backbone synthetic, last mile, and private last mile synthetic.

NAM Probe driver statistics
These alerts monitor driver-specific dimensions and metrics such as drop rates and overruns.

NAM Probe interface statistics
These alerts monitor interface interface-specific dimensions and metrics such as packet and byte counts.

NAM Probe server statistics
These alerts monitor interface server-specific dimensions and metrics such as session statistics and errors.