As of mPulse 56, you benefit from the new Alerts feature, which allows you to have a newer, scalable, and lightweight alert.
The previous version was heavy-weight because of the requirement to render a full dashboard for an image. It had tight limits on how many alerts an user could set up.
You have the following benefits for the new Alerts:
Uses a simple chart instead of a true dashboard image, so it requires fewer resources on the system.
Includes a streamlined user interface (UI).
Supports Slack and expanded Webhook support.
If users want a full dashboard, then they can set up a report instead.
Caution: If you want to use your previously created alerts, which are now under the Alerts (Legacy) folder, you must recreate them by using this new Alerts feature.
Create an Alert
Go to Central > Alerts.
Click New (plus sign).
The Basics: Give the alert a name, optional description, severity, and location.
Choose a data event as follows:
App – Select the domain or app to which this rule applies. The app or domain must already exist in the tenant.
Apply – All or Any.
When – Select Timer, Metric, or Dimensions attribute. When – Select Timer, Metric attribute. If you select Timer, enter a Timer Attribute, a percentile, operator, and value. If you select Metric, enter a Metric Attribute, an operator, and metric value.
Add a dimension filter. You can select more than one dimension filter.
Specify time options for when to monitor the event. Choose the time zone, days(s), and time of day.
Choose an action type(s)
Note: You can add more than one action type.
Notify user(s) Sends an email to an user. You have the following fields: To, Subject, and Message. Dashboards can be dragged and dropped into the message. Attributes can be dragged and dropped into the Subject and Message. For attributes, you have further options once it is inside the message, such as selecting text or image.
Call Webhook Builds an URL for your web service call. You have the following methods to call the Webhook URL: GET, POST, PUT, DELETE, or HEAD. You can specify the headers for the Webhook URL. For POST and PUT methods, you have an additional option to specify the request body. Attributes and Dashboards can be dragged and dropped into the URL field and body.
PagerDuty Notifies the PagerDuty service. You have the following fields: Service API Key, Description, and Details. Attributes and Dashboards can be dragged and dropped into the Description field. The pager will have a short description, and the additional information can be found in the Details section. To get the PagerDuty Service API key, follow steps described in the Getting Started section under PagerDuty integration API and PagerDuty integration guide.
Slack Notifies user by using Slack, which is a real-time messaging app. You have the following fields: Slack Webhook URL, Channel, and Message. Attributes and Dashboards can be dragged and dropped into the Message. For information on how to get the Slack Webhook URL, see https://.slack.com/services/new/incoming-webhook. Note that you need to add your Slack domain to this link.
Firing an Alert via a Webhook
Coming soon, you can trigger an mPulse alert from external sources. For example, if an anomaly is detected via Data Science Workbench, it can trigger an alert by calling a webhook URL.
For information about the mPulse Alert API, see the Alert API page.
How to Configure Webhook for an Alert
1. Go to Central > Alerts, and create a new alert.
2. After you fill out the Basics step, choose the Externally Invoked button.
3. Click on the webhook URL to have the link copied to your clipboard. You have two URL options: trigger and clear.
4. Fill out the information on the Choose an action type(s) step.
5. Save your alert, and provide this webhook URL to the external tool.