In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
- In the Flashduty console, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Select Moesif and click Save
- Open the generated integration card and copy the Push URL
Use a shared integration
- In the Flashduty console, go to Integration Center → Alert Events
- Select Moesif and enter an integration name
- Configure the default route and select a channel. You can add more rules under Routing after creation
- Click Save and copy the generated Push URL
Configure Moesif
1
Create a webhook notification channel in Moesif
Where: Moesif › Account icon › Notification Channels › + Create Channel
Click Save. The account icon is in the account menu in the lower-left corner.
2
Select the channel in your alert rules
Where: Moesif › Alert Rules › + Alert Rule
You can also edit an existing rule, or click Alert on any time series chart to create one. Select the channel in every alert rule that should notify Flashduty.
3
Trigger an alert and confirm
Where: Moesif › Alert RulesThe Moesif channel has no test button, so make an alert rule that uses the channel trigger for real (for example, lower the threshold of a static alert for a while) and check that Flashduty shows an alert titled with the rule name. Moesif sends no recovery notification, so close the alert by hand or with auto-close, as described below.
The Notification Throttle of a channel or rule and Silencing alerts stop Moesif from sending some notifications. Suppressed notifications never reach Flashduty.
Recovery and auto-close
Moesif notifies only when a rule triggers. The request body has no alert ID and no field that marks a recovery, so the alert in Flashduty does not recover on its own. Each Moesif notification is a separate Flashduty alert. Close it by hand, or turn on auto-close in the channel that receives this integration. We suggest twice the rule’s evaluation period, for example 30 minutes for a 15-minute rule.Alert key
The request has no field that identifies the same alert across notifications, so Flashduty generates a random Alert Key for each notification. Different notifications never merge into one alert.Status and severity
Moesif alerts carry no severity. The alert in Flashduty is always Warning; its status equals its severity and it does not recover. A notification whosetype is not alert (for example another kind of notification sent to the same channel) is ignored and creates no alert.
Alert content
- Title: the alert rule name
name. When the notification has a single group value, it is appended, for exampleLatency per user: user-1. Without a rule name the title isMoesif alert - Description: the rule condition
metric, then each group value with its current value and, for dynamic alerts, its direction; up to 20 are listed
Troubleshooting
- Flashduty receives nothing: check that the rule is on and selects the channel in Send To, and that the channel’s Webhook URL is the full push URL including
integration_key. In Moesif Alert History, check that the rule triggered and was not suppressed by a throttle or silencing - Flashduty returns a parameter error: the body is not JSON, or has neither
namenormetric_values. Use Moesif’s built-in webhook channel and do not rewrite the body - Alerts never close: Moesif sends no recovery. Turn on auto-close in the channel, or close the alerts by hand