Overview
NetOp ships with balanced default settings designed to detect real issues without generating excessive noise. After onboarding, review and tune these settings to match your network's behavior and your team's monitoring sensitivity.
Settings are configured at the customer (tenant) level — all sites under a customer share the same thresholds.
Accessing Settings
- Open the Dashboard
- Navigate to the Customers Table
- Click a customer name
- The Settings section opens with 7 tabs
Settings Tabs
| Tab | Purpose |
|---|---|
| Sites | Site names and per-site operational severity |
| Site Management | Device-to-site assignment |
| Network Interfaces | WAN bandwidth, switch port roles |
| Anomalies | Metric thresholds and severities |
| Incidents | Incident triggers and notification events |
| QoE | SD-WAN policy profile traffic types |
| SNMP | Community strings and subnet scanning |
Anomalies Tab
For each metric (Devices, Traffic, Loss, Latency, VPN Status, VPN Traffic, VPN Latency, etc.) you can:
- Enable/Disable the anomaly (all enabled by default)
- Set one or more static thresholds with different severity levels
- Configure how many threshold crossings per hour trigger the anomaly
- Enable Notify Admin for that specific metric
Recommended starting thresholds:
| Metric | High Severity | Critical Severity |
|---|---|---|
| CPU | 70% | 90% |
| Memory | 60% | 80% |
| Packet Loss | 1% | 5% |
| Latency | 100ms | 300ms |
Incidents Tab
Four notification events per incident category:
- Create — notify on incident open
- Close — notify on resolution
- Update — daily update while open
- Severity Change — notify on escalation/de-escalation
Each can be independently enabled or disabled. You can also set severity filters: e.g., only notify for High and Critical incidents.
Sites Tab
Each site has configurable operational anomaly severity behavior per device type:
- SD-WAN/Firewall
- Switch/Router
- Access Point
- VPN tunnel
- VPN third party
You can set the initial severity and escalation times independently per device type. For example, a VPN tunnel may escalate to Critical after 20 minutes; an access point after 1 minute.
Important Notes
- Aggressive thresholds (very low values) generate more anomalies and incidents — useful for critical environments, noisy for general monitoring.
- NetOp's defaults are intentionally balanced — validate against your environment before tightening.
- Changes take effect immediately; no restart required.
Comments
0 comments
Please sign in to leave a comment.