Overview
Incidents are the primary operational unit in NetOp. An incident aggregates multiple related anomalies into a single ticket, provides automated root cause analysis via Insights, and suggests remediation steps via Recommendations. This significantly reduces Mean Time to Resolution (MTTR).
Incident Structure
Each incident contains:
| Section | Description |
|---|---|
| Header | ID, severity, start/close time, main cause, status |
| Observation Types | Categories of anomalies included |
| Top Clients (MB) | Most active clients during the incident |
| Top Applications (MB) | Most active applications during the incident |
| Incident Subcategories | Detailed breakdown with total observed count and avg duration |
The Four Incident Tabs
1. Observations
All historical anomalies linked to this incident — from creation to resolution. Each observation shows:
- Severity, start/close time
- Affected element and interface
- Anomaly type and full description
2. Insights
Automated root cause analysis. NetOp cross-correlates all related and unrelated metrics to identify the most likely root cause. Examples:
- "WAN ISP interface throughput exceeded 70% of 100Mbps downlink for 14 cumulative minutes"
- "SLA QoE for Office365 was poor for 29 minutes within the past hour"
3. Recommendations
Suggested actions to resolve and prevent recurrence:
- Contact ISP for link investigation
- Adjust SD-WAN policy to route traffic via alternate WAN
- Increase bandwidth limit
- Configure traffic shaping
4. Analysis (AI Chat)
Interactive natural-language interface. Ask questions in plain English:
- "What caused this incident?"
- "How many times has this type of incident occurred this month?"
- "Which devices are involved?"
The AI responds based on the specific incident data and allows follow-up questions.
Viewing Incidents
Incidents can be viewed at three levels:
- Organization — all incidents across all customers
- Customer — all incidents for one customer
- Site — incidents for one specific site
Navigate using the top tabs (Dashboard → Customers → Incidents).
Incident Severity Levels
| Severity | Meaning |
|---|---|
| Critical | Service-affecting; immediate action required |
| High | Significant degradation; investigate urgently |
| Medium | Performance impact; review within the day |
| Minor | Informational; monitor for escalation |
Investigating an Incident
- Open the Incidents tab
- Find the incident by severity or creation time
- Click the → (Go to Incident) arrow
- Review Observations to understand the timeline
- Read Insights for automated root cause
- Follow Recommendations for remediation
- Click the Statistics shortcut to view the metric charts in the relevant time range
Best Practices
- Focus on incidents rather than individual anomalies to reduce noise.
- Use the Analysis tab for unfamiliar incident types.
- Close incidents manually if resolved before NetOp auto-closes them, to keep statistics accurate.
- Track MTTR improvements over time using the Monthly Summary Report.
Comments
0 comments
Please sign in to leave a comment.