Hands-on tutorial

Tutorials · Monitoring

How to Set Up Network Alerts by Email and Webhook

Get told about offline devices, failed links and security events before users call: choose what to alert on, send alerts to email and to your ticketing or chat tool by webhook, and avoid alert fatigue.

Beginner8 min6 steps

Before you start

  • A monitoring or management platform (for example NavCloud, a gateway, or an SNMP/syslog tool)
  • An email address or distribution list for the network team
  • A webhook URL from your ticketing or chat system

Step by step

  1. Decide what deserves an alert

    Start with a short list: device offline for more than 5 minutes, WAN down or failed over, PoE overload, high CPU or temperature, configuration changes, and security events. Everything else goes to logs and reports.

  2. Set severities

    Critical: the site or a core device is down. Warning: something needs attention today. Information: for reports only. Send only critical and warning alerts immediately.

  3. Add email notifications

    Use a team mailbox or distribution list, not one person's address, so alerts are not lost during holidays.

  4. Add a webhook

    Create an incoming webhook in your ticketing or chat tool and paste its URL in the alert settings. Most tools accept JSON with the device, site, severity and message.

    POST https://tickets.example.com/hooks/network
    {"site":"HQ","device":"Core-SW1","severity":"critical","message":"Device offline"}
    
  5. Test

    Unplug a test access point or trigger a test alert, and confirm it reaches email and the ticketing tool with the right severity.

  6. Review monthly

    Look at the alerts from the last month. Remove or tune any alert that nobody acted on, and add alerts for problems that users reported first.

Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.

Pro tips

  • Acknowledge alerts when you start working on them so the team does not duplicate effort.
  • Keep the webhook URL secret: treat it like a password.
  • Send a monthly availability report to management, not individual alerts.