An alert profile is a set of thresholds used to evaluate continuous monitoring results. They can be applied to an entire transaction and/or its individual milestones. Anytime a threshold is crossed, APM marks the event on the time axis and logs it in the event log. You can receive emails if your notification profile has ‘path violation events’ enabled, and snmp traps if that’s enabled.

APM has several system-defined profiles or you can create your own. Navigate to > manage alerts > web alerts. From there, click each template to see the conditions it contains. Alert profiles are comprised of one or more conditions which generally follow the format ‘condition A violates if B is present for C tests, and clears if B is not present for D tests.’ You can see that the basic components are a violation clause, a clear clause, and an evaluation period. The violation clause describes poor performance, the clear clause describes acceptable performance, and the evaluation period confirms that the condition is persistent before declaring violation or clear event. If you’d like to create your own custom alert profile.

APM cannot obtain any http status from the target.
HTTP status
The target returns an http status code other than the value specified.
HTTP errors
The target returns an http status code between 400 and 505, inclusive.
Script errors
APM returned an error because a scripted transaction did not run to completion.
Total time
The entire test or specific milestone takes longer than the specified amount of time.
The minimum tolerable apdex score for the test, not the web app.

Setting good alert thresholds: What should your total time/threshold be? Let APM run for a bit to establish a baseline and then set your thresholds around that. Read more…

Applying a profile

Alert profiles are applied to scripts rather than the web app itself. From Experience > web applications, click ‘configure’ for the web app you want to edit, and then select the script that you want to apply the alert profile against. You can apply a profile to the entire transaction, and/or one to each milestone:

A violation event occurs if any milestone violates any condition in either its profile or the overall profile, with one exception: a total time condition in the overall profile applies only to the to the sum of all milestones.
Milestone X
A violation event occurs if a milestone violates any condition in its profile, including a total time condition if one is included.

If an alert profile is applied, status icons are used to tell you at a glance something about the current state of the web path, including when it is currently in violation. is OK and is violation. Alert threshold violations and clears are also logged as events on the test timeline page and in the event log.

  • Events are marked on the time axis of the end user experience chart: a red diamond indicates a condition violated; a green diamond indicates the condition cleared.
  • Events are logged. Navigate to Experience > events to display all web path events for all web paths in an organization; click on the events tab on the test timeline page to display events for a particular web path.
  • Events trigger notifications based on your notification profile.

Overloaded monitoring points: Missing data, grey charts, or purple diamonds could be symptomatic of an overloaded monitoring point. Read more…