Table of Contents

  • Overview
  • In depth



Overview


Notification Management screen tells CloudMonix who should get what notifications and with what minimum severities. In a nutshell, Notification Management screen acts as a central router that directs where notifications go and how these notifications look.  Each entry on the Notification Management screen is a delivery rule.  Users can configure that notifications only from certain resources or resource categories, of certain minimum severities, using specific notification templates, are delivered to specific users or integration points.




In depth


CloudMonix internally features a publish/subscribe notification system.  Notifications in CloudMonix are raised from Alerts, Actions, or Scaling actions of a resource.  Setup of what specific notifications are raised is done thru resource configuration dialog via Alerts, Actions, Scaling Ranges and Adjustment tabs. Each notification has a severity (Debug, Information, Warning, Error, Critical). 


It's also possible to control what notifications are sent on the Notification Rule level by configuring CloudMonix to not send certain type of notifications (e.g. when alert is turned off). That option is especially useful when configuring rules for integrations. Users can then decide what kind of infromation should be posted to a particular integration channel.


When specifying rules for delivery of notifications, administrators can define delivery rules for a specific resource, resource category or the overall account.

Minimum severity will filter out any notifications of lower severity.  Target destination defines who or what should receive a particular notification. Targets of notifications can be User's Email (when Alert Email is specified), User's SMS (when Alert Phone number is specified and Twilio integration is configured), later on user's Twitter (feature not yet available), PagerDuty service, and forthcoming: Webhook integration point, and Hipchat and Slack chat channels, etc.


For example, a company may choose to send all of its Critical notifications coming from all resources to its CEO, while, sending Information or higher notifications to support engineers on the team; notifications from resources in the Database resource category can be delivered to database administrators, and notifications of Error or higher severity can be sent to a Pager Duty integration service.


Delivery rules can also be further customized with specific text-based templates that users can use when sending notifications.  For example, it maybe important to change text or provide specific instructions in the alert email to certain members on the team for alerts of certain severity or source.


notifications%20screen.png