N
Notification Element
A Notification Element is an object that can be forwarded by a Notification Action.
The following Notification Elements are available:
RealTime Monitoring Check Results |
A notification of a Check Result may occur when a Check Status changes, or when the Check gets confirmed or unconfirmed, or periodically, if it remains in its Check Status for a certain period of time. For certain Checks, like the filesystem or tablespace Checks, a notification will also occur if the Check Status changes for a particular filesystem or tablespace, even if the overall Check Status does not change. |
Daily Checks |
A notification of a Daily Check may occur as soon as the Daily Check execution has finished, and once it gets confirmed or unconfirmed. |
Daily Check Detail |
A notification of a Daily Check Detail may occur as soon as the Daily Check execution has finished. |
CCMS Alerts |
A notification of a CCMS Alert may occur as soon as it is delivered by the corresponding Custom Check. |
Changes |
A notification of a Change may occur as soon as it is created, and whenever the status of the Change record changes. However, this function is most useful for notifications of the System Change Auto Detection. |
Tickets |
A notification of a Ticket may occur as soon as Ticket is created, and whenever the status of Ticket changes, or a new Ticket Log is created. |
Server Events |
A notification occurs once the License is about to expire. |
Notifications
Notification Elements can be escalated to Users having the required permission for the Customer owning the affected System. This process is called a Notification in Avantra.
The escalation via e-mail is supported, and these mails can also be converted to pager notifications or text messages (SMS) by use of third-party applications. In addition, it is also possible to send Notification Elements to virtually any other system monitoring or management application. You can write Check Results into log files or arbitrarily formatted text files, like XML files. Or you can execute any command, write to the Windows Event Log, send XanMobile push notifications, or a browser notification. And finally, you can create Tickets in the ticketing system of Avantra.
The escalation mechanism provided by Avantra is highly customizable by means of, for example, Check selectors and includes powerful Filter rules. These filters allow the precise definition of which content is to be escalated to whom and at which point in time. Common parts of Filters can be shared as the so-called Global Expressions.
The Output Channels and Filters support Macros that are replaced with real-life System and Notification Element data during run-time. You can also define your own Macros and therefore enter third-party data into the Notification process by means of the so-called Custom Resolvers.
The trigger for the different Notification Elements, the selected Output Channel, the Filter Lists , and any custom Resolver form the so-called Notification Action. Whenever a Notification Action is executed the result is kept in a Notification Message. This Notification Message allows you to trace exactly if a notification was sent or if it was blocked by a certain filter, when it was delivered, if it succeeded in the first attempt or needed a retry, etc.
Service Providers may delegate the permissions to generate Notifications to their Customers. In this case not all Output Channels are available.