The Hudu admin area is accessible ONLY to admins and super admin users within your organization.
Hudu Radar alerts let your team know when something needs attention on a Radar-scanned network, such as a device going offline, a new device appearing, a Radar agent that stops checking in, or a scan that fails or falls behind. Radar alerts are created in the same place as other Hudu alerts and can be sent by email, webhook, or both.
Visit Alerts for additional information on general alert settings, and About Hudu Radar for additional information on Hudu Radar.
Creating a Radar alert
- Navigate to the Hudu admin area → Alerts.
- Click + New Alert.
- Enter a Name for the alert.
- Choose a Radar option from Alert type (see Radar alert types below).
- For Radar agent check-in and Radar scan overdue alerts, select a wait time.
- Select All Radar companies, or select specific companies. Only companies with Hudu Radar enabled can be selected.
- Enter the email address to receive the alert in Send alert to.
- Optionally, under Configure Webhook, enter a Webhook URL. Radar webhooks must use a publicly reachable URL, and the Radar webhook payload is not configurable (see Sending Radar alerts to a webhook below).
- Click Create Alert to save.
You can't create two alerts of the same Radar type that send to the same email address and cover the same company.
Radar alert emails are sent from donotreply@hudu.com. We recommend adding this address to your email allow list so alerts aren't filtered as spam.
Radar alert types
Radar new device, Radar scan failed, and Radar agent check-in alerts require Radar collector v2.1.2 or later. Radar device offline and Radar scan overdue work with all collector versions.
Sends an alert when a device discovered by Hudu Radar changes from online to offline. This alert sends once per outage and doesn't repeat.
Sends an alert when Hudu Radar discovers a new device on a network.
This alert only fires after a network's first scan has completed, so the devices found during the initial scan won't trigger it. Devices added by a Radar Agent check-in always send a new device alert.
Sends an alert when a Hudu Radar Agent hasn't checked in within the selected wait time.
- Wait time options: 30 minutes, 1 hour (default), 2 hours, or 4 hours.
- Agents check in every 15 minutes.
- This alert repeats once per wait time until the agent checks in again, for up to about 5 hours. After that, the agent is treated as removed and the alert stops.
Sends an alert when a Radar collector hasn't run a full scan within the selected wait time.
- Wait time options: 2 hours (default), 4 hours, 8 hours, or 24 hours.
- Hudu Radar scans every 35 minutes.
- This alert is checked per collector.
- A collector that has never started a scan won't trigger it. A collector whose scan started but never finished will.
- Paused or uninstalled collectors don't trigger scan overdue alerts.
- Single-network Scan now scans don't count toward this alert.
- This alert repeats once per wait time until a full scan completes.
Sends an alert when a Hudu Radar scan fails.
How repeat alerts work
Radar agent check-in and Radar scan overdue alerts repeat once per wait time until the problem is fixed. For example, a scan overdue alert with a 4 hour wait time sends again every 4 hours until the collector completes a full scan.
Agent check-in alerts repeat for up to about 5 hours. After that, the agent is treated as removed and the alert stops, even if the agent never checks in again.
Once the problem is fixed, the repeat cycle resets. If the same problem happens again, the alert sends as soon as it passes the selected wait time, without waiting for the previous repeat cycle to finish.
Selecting companies
- All Radar companies: the alert covers every company that has Hudu Radar enabled.
- Specific companies: the alert covers only the companies you select. Each company must have Hudu Radar enabled.
When Hudu Radar is turned off
When Hudu Radar is turned off, your Radar alerts are paused rather than deleted. Paused Radar alerts don't appear in the Hudu admin area → Alerts list. How they come back depends on how Radar was turned off:
- Limited mode: alerts are hidden and return on their own when limited mode ends.
- Radar turned off for the account, or the license revoked: alerts return only after Hudu Radar is activated again for each company from Networks. Turning the setting back on doesn't restore them automatically.
- Radar revoked for specific companies: only alerts whose companies are all revoked are hidden. An alert that still covers another active company stays in the list.
Sending Radar alerts to a webhook
Radar webhooks must use a publicly reachable URL.
The Radar webhook payload is not configurable. Hudu sends it automatically in a fixed JSON format, and custom payloads and Hudu webhook variables (such as $HUDU_URL) are not supported.
To send Radar alerts to a webhook provider, route the webhook through an automation tool such as Zapier or Microsoft Power Automate. The tool receives the Radar payload, then reformats it into a message the destination service accepts.
Visit Zapier - WebHooks for additional information on receiving Hudu webhooks in Zapier.
Radar webhook payload
Every Radar alert includes the following fields:
| Field | Description |
| event_type | The type of alert. One of device_offline, new_device, agent_stale, scan_stale, or scan_failed. |
| deployment_name | The name of the Radar collector/deployment. |
| company_name | The name of the Hudu company. |
| occurred_at | When the event occurred, in UTC (ISO 8601). |
Each alert type maps to an event_type as follows:
| Alert type | event_type | Includes |
| Radar device offline | device_offline | device |
| Radar new device | new_device | device |
| Radar agent check-in | agent_stale | device |
| Radar scan overdue | scan_stale | scan |
| Radar scan failed | scan_failed | scan |
Included in Radar device offline, Radar new device, and Radar agent check-in alerts.
- id: the device ID.
- name: the device name.
- ip_address: the device's IP address.
- device_type: the type of device.
- is_up: whether the device is up (true or false).
- last_agent_check_in_time: when the agent last checked in, in UTC. Can be null.
- network_cidr_address: the CIDR address of the device's network.
- hudu_asset_url: a link to the device's Hudu asset. Can be null.
Included in Radar scan overdue and Radar scan failed alerts.
- id: the scan ID.
- status: the scan status.
- started_at: when the scan started, in UTC.
- ended_at: when the scan ended, in UTC. Can be null.
- network_cidr_address: the CIDR address of the scanned network. Null for a scan that isn't tied to one network.
FAQ
Radar new device alerts only fire after a network's first scan has completed. Devices found during the initial scan don't trigger the alert. Devices added by a Radar Agent check-in are the exception and always send a new device alert.
Scan overdue alerts are checked per collector. A collector that has never started a scan won't trigger one, and paused or uninstalled collectors don't trigger them either. Single-network Scan now scans don't count, so the alert is based on the collector's last full scan.
Once per wait time until the problem is fixed. For example, an agent check-in alert with a 1 hour wait time repeats every hour until the agent checks in again. Agent check-in alerts stop after about 5 hours, when the agent is treated as removed.
Only companies with Hudu Radar enabled can be selected on Radar alerts.
You can't have two alerts of the same Radar type that send to the same email address and cover the same company. Edit the existing alert, or change the alert type, email address, or companies.
Radar alerts are paused and hidden from the Alerts list when Hudu Radar is turned off. They aren't deleted. Alerts hidden by limited mode return on their own. If Radar was turned off for the account or the license was revoked, activate Hudu Radar again for each company from Networks to restore them.
No. The Radar webhook payload is not configurable and is sent automatically. Custom payloads and Hudu webhook variables are not supported for Radar alerts. To send Radar alerts to a webhook provider, route them through an automation tool such as Zapier or Microsoft Power Automate.
Troubleshooting
Most webhook providers, including Slack, Microsoft Teams, and Discord, only accept messages in their own format, and the Radar payload can't be changed. Route the webhook through an automation tool such as Zapier or Microsoft Power Automate to reformat the payload before it reaches the provider.
Radar webhooks must use a publicly reachable URL. Webhooks sent to private or local network addresses aren't delivered. Use a public URL, such as one provided by Zapier or Microsoft Power Automate.
Radar alert emails are sent from donotreply@hudu.com. Check your spam or quarantine folder, and add this address to your email allow list.