Overview
NetOp can send notifications about incidents and anomalies to email addresses, Slack, PagerDuty, Splunk, and Microsoft Teams. Users enrolled in the platform do not automatically receive notifications — they must be explicitly added to a notification rule.
Notification Channels
| Channel | Use Case |
|---|---|
| Default; supports multiple recipients | |
| Slack | ChatOps teams |
| PagerDuty | On-call escalation |
| Splunk | SIEM integration |
| Microsoft Teams | Enterprise collaboration |
Configuring Email Notifications
- Open Integrations from the left menu
- Click the Notifications tab
- Click Email
- In the New Email Integration dialog:
- Enter one or more recipient email addresses on the left
- Select the incident/anomaly categories you want to send
- Click Save
You can add multiple rows — one per recipient group or per category subset.
Available Notification Topics
- Operations Incident
- Service Performance Incident
- Utilization Performance Incident
- Network Utilization Incident
- Anomalies
Notification Timing
Four events trigger a notification per incident:
| Event | When |
|---|---|
| Creation | Immediately on incident open |
| Update | Once per day while open |
| Severity Change | When severity increases or decreases |
| Closing | When the incident resolves |
All four are enabled by default. You can disable individual events from Settings → Incidents.
Per-Metric Anomaly Notifications
From Settings → Anomalies, you can enable a Notify Admin toggle for each individual metric (CPU, Latency, Packet Loss, etc.). These are disabled by default.
Only enable per-metric notifications for high-priority metrics to avoid notification fatigue.
Best Practices
- Configure at least one email notification recipient before going live.
- Use Slack or Teams for NOC visibility; PagerDuty for after-hours escalation.
- Avoid enabling per-metric anomaly notifications for all metrics simultaneously.
- Review and update recipient lists when team members change.
Comments
0 comments
Please sign in to leave a comment.