Skip to main content
Send alerts raised by JumpCloud Insights rules to Flashduty On-call through a JumpCloud webhook notification channel. Each JumpCloud alert maps to one Flashduty alert: it triggers when the alert is raised and recovers when the alert is marked Resolved or becomes Auto-Resolved in JumpCloud.

In Flashduty On-call

You can get the integration push URL in either of the following ways.

Use a dedicated integration

  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select JumpCloud, then click Save
  4. Open the generated integration card and copy the Push URL

Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select JumpCloud and enter an integration name
  3. Configure the default route and select a channel; you can add more rules under Route after creation
  4. Click Save and copy the generated Push URL

Configure JumpCloud

1

Create a webhook notification channel in JumpCloud

Where: JumpCloud Admin Portal › Settings › Notification Channels › Webhooks › +AddBefore saving, you can click Test Webhook in the form: JumpCloud uses it to check the channel configuration and shows a simulated request and response in a dialog (JumpCloud does not document the request body, and it creates no real alert). Then click Save. Sign in as an administrator.If you set Webhook Status to Disabled when saving, open the Webhooks page, click the ellipsis (overflow menu) next to the channel, and choose Enable; the channel sends nothing until then.
2

Select the channel in an Insights rule

Where: JumpCloud Admin Portal › Monitoring › Alerts › Rules › +Rule › Insights › Directory Insights Event Monitoring (or open an existing rule)Alert Resolution and Alert Acknowledgement appear only when both Generate Alerts and Send Notifications are on. Save the rule.
3

Trigger an alert in JumpCloud and verify

Where: JumpCloud Admin Portal › Monitoring › AlertsWhen the rule condition is met, JumpCloud raises an alert and sends it to the channel. Confirm an active alert appears in Flashduty, then find the fired alert on the Alerts page above and mark it Resolved, then confirm the Flashduty alert recovers.The Test Webhook button in the channel form only checks the channel configuration and is not a real alert; verify with a real alert. Flashduty parses requests in the real alert format and returns 400 for a request without alert_id. If a test request fails for that reason, real alerts are not affected.

Alert key

Flashduty builds the Alert Key from alert_id, the ID of the JumpCloud alert. JumpCloud sends the same alert_id on every status change of one alert (Open, Acknowledged, Resolved, Auto-Resolved), so the trigger and the recovery land on the same Flashduty alert. Changes to the title, priority, description or update time do not change the Alert Key. A request without alert_id is rejected. JumpCloud documents that a new event after the threshold is reached updates the existing alert; those updates all fold into the same Flashduty alert.

Status and severity

A recovery keeps the severity of the last payload.

Labels

The alert title comes from alert_title and the description from description.

Troubleshooting

  • Flashduty returns an invalid-parameter error: check that the URL is complete and includes integration_key, and that the request body is JSON
  • An alert does not recover: check that Alert Resolution is on in the rule and that the channel is enabled
  • No notifications arrive: check that the Insights rule selects this webhook channel and that the triggering event falls inside the rule’s monitoring window
For the field definitions, see JumpCloud webhook channels and Create an Insights rule.