Skip to main content
Use the NetBeez webhook integration to send network monitoring alerts and incidents to Flashduty On-call. NetBeez sends every alert and every incident as an open notification followed by a cleared notification: the open notification triggers a Flashduty alert, and the cleared notification recovers the same alert.

​
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, go to Channels and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add an integration
  3. Select NetBeez and click Save
  4. Open the new integration card and copy the push URL

​
Use a shared integration

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

​
Configure NetBeez

1

Enable the webhook integration

  1. Sign in to NetBeez as an administrator (webhooks require BeezKeeper 13.0 or later)
  2. Go to Settings → Integrations → Webhooks and enable the integration
  3. Paste the full Flashduty push URL into the webhook URL field and save
  4. Optionally use the test function on that page to check the URL. Flashduty returns success for a request without an event type (event_type or event) and creates no alert
2

Choose the notification types to send

In the notification settings on the same page, select what to send to the webhook: Agent device alerts, alerts for Agents, Targets, WiFi profiles and scheduled tests, and incidents for Agents, Targets and WiFi profiles. Each type can be sent as single notifications or as aggregate notifications; an aggregate request carries several events, and Flashduty handles them one by one.
Alerts and incidents are separate notifications. If you select both for the same network problem, Flashduty creates two alerts. To respond by incident only, select only the incident notifications.
3

Verify the lifecycle

Make a Target or Agent fail (for example, temporarily disable an Agent), confirm that Flashduty receives an active alert, then restore it and confirm the original alert recovers.

​
Payload fields

NetBeez POSTs application/json with a single data field: an object for a single notification, an array for an aggregate notification. Flashduty parses it directly, so no template is needed. The alert title is “object name: message”. The object name is the first non-empty of target, wifi_profile, agent and destination.

​
Alert Key

  • Alert notifications use alert_dedup_id. NetBeez documents that the open and cleared notifications of one alert share it, so grouping by it is enough.
  • Incident notifications use the object type, the object ID and incident_ts. incident_ts is always the incident start time and is the same in the open and cleared notifications. NetBeez also suggests correlating incidents by incident_id, but the cleared example in its documentation carries a different incident_id from the open one, so Flashduty does not depend on it and keeps incident_id only as a label.
  • Alert and incident Alert Keys never overlap, and changing the object name, message or severity does not change the Alert Key.
If an alert notification has no alert_dedup_id, or an incident notification has no object ID or incident_ts, Flashduty returns a parameter error because the cleared notification could not be matched to its alert reliably.

​
Status and severity

NetBeez documents only that open alerts have a severity of at most 5 with names such as alert and critical, and does not publish a full table, so only 1 and 2 map to Critical. To change a severity, rewrite it with a rule under the channel’s Configuration.

​
FAQ

Flashduty processes the events in alert_ts order, oldest first, so the open event of an alert is handled before its cleared event and the alert ends up recovered.
The NetBeez test sends sample data. Flashduty treats only requests that contain event_type or event as alerts and returns success without creating an alert for anything else. If the sample is recognized as an alert, close it manually in Flashduty.
No. NetBeez retries on non-2xx responses, the Alert Key of an event does not change, and repeated deliveries merge into the same alert.

​
Troubleshooting

  • NetBeez fails to deliver: confirm the webhook URL is the full push URL and includes integration_key
  • Flashduty returns a parameter error: confirm the body has data, alerts carry alert_dedup_id, and incidents carry an object ID and incident_ts
  • An alert does not recover: confirm the matching type is selected in NetBeez so its cleared notification is sent (open and cleared notifications share one notification type)
For the field reference, see the NetBeez documentation NetBeez Webhook Payloads Reference.