The Tealeaf Alert Service should be reviewed for both SaaS and OnPrem.

Some areas that can be improved:

• Control over alert content and subject line

  • Currently, to change the content and subject lines of alert emails, a very complicated and not well documented process of template development is required. (Editing files like "AlertServiceText.xsl", etc.)

  • The alert name is often more intuitive than the event name, as alerts commonly use dimension values in their criteria.

  • When an alert is based on a dimension value threshold, can the name of the dimension be placed in the subject line?

• Aggregated vs One-Off alerting

  • The current alerting service is built on the concept of aggregated reporting data exceeding a threshold. However, there are use cases when a single session should fire the alert... for example alerting when a VIP visitor (perhaps identified in a dimension) or a hostile visitor arrives at the site.

  • In this case the alert requires detailed context about the particular session that has triggered the alert... event values, IP address , Logon ID, URL visited, etc.. This level of session data is not exposed for alert content building in the current design.