Alerts are not firing in a new view
Originally Published: 2007-09-11
Article Number
Applies To
alert
does not fire
Issue
Alerts are not firing in a view, although the events are seen coming in to the enVision server
Resolution
This can be caused when there are variations of an event. When selecting events for a view, users may use the IN or LIKE operators to find an event when searching by vendor message id. In some instances though, there are multiple instances of a single message id, as the message has been updated over time. In this instance, these newer messages will be identified in enVision with a :01 or :02 designation.
To be sure you are shown all the possible instances of a message id, use REGEX instead of IN or LIKE when searching for events to add to a view. This will result in all the versions of a message being displayed, and then you can select all possible version to ensure the event you want will be alerted upon.
Related Articles
How to create a new ActiveMQ KahaDB for use with AFX in RSA Identity Governance & Lifecycle 347Number of Views RSA Authentication Manager services failed to start after activating a new console certificate 513Number of Views When replacing an RSA SecurID software token with a new software token the token PIN is not carried over to the new token 593Number of Views Installing a new license on RSA Authentication Manager 855Number of Views Creating an alert view 3Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?