NetAlertX
NetAlertX scans your network for devices. Point its Webhook publisher at InfraInbox and each report is split into one event per device, on the destinations you choose, with routing, quiet hours and re-notify on top.
Tested with: NetAlertX 26.x’s own sample report; not yet run against a live NetAlertX.
What you get
Section titled “What you get”| NetAlertX reports | In InfraInbox |
|---|---|
| A device is down | An ERROR incident for that device, keyed by its MAC address |
| That device reconnected | The same incident resolves |
| A new device joined the network | A WARNING incident for that device |
| Only other events or plugin changes | One info event in the inbox, with the counts |
The built-in rule keeps a down device’s incident open until it reconnects, so it never closes just because a day went by. A new-device incident closes after 24 hours of quiet.
Prerequisites
Section titled “Prerequisites”- A NetAlertX instance that can reach your InfraInbox server.
- Devices you care about marked in NetAlertX to alert when down: it only reports those.
-
Go to Add source → NetAlertX and name it. InfraInbox issues a key for the URL, shown once, with the webhook URL filled in.
-
In NetAlertX, open Settings → Publishers → Webhook and fill it in:
Field Value URL https://infrainbox.example.com/hooks/netalertx/iik_src_…Payload type jsonRequest method POST -
Enable the Webhook publisher, and in the notification settings choose which sections to send: new devices, down devices and reconnected devices.
The URL, with a placeholder where the key goes, stays on the source’s Connect tab.
Check it works
Section titled “Check it works”Unplug a device that’s set to alert when down and wait for NetAlertX’s next scan. An incident opens; plug it back in and the incident resolves.
Limitations
Section titled “Limitations”- Payload type must be
json. Withhtmlortext, InfraInbox can’t read the devices: the report is kept as an unparsed event you can open. - NetAlertX’s webhook signature (
WEBHOOK_SECRET) isn’t checked: the key in the URL already proves who sent it.
- Routing rules — send new-device alerts somewhere different from down devices
- Built-in rules — edit or override the default rule