NetRoute Performance SLO in ObserveOps
ObserveOps (formerly known as AIOps) lets you create Service Level Objectives for NetRoute routes you already monitor in the NetRoute module. Use NetRoute Performance SLOs to measure route performance compliance using NetRoute metrics and track achievement through the same SLO framework you use for infrastructure.
Prerequisites
Before you create a NetRoute Performance SLO, confirm the following:
- At least one NetRoute route is active and monitored in ObserveOps.
- NetRoute data appears under the NetRoute module with metrics available.
- You have permissions to create SLO profiles in Settings.
How It Works
ObserveOps evaluates NetRoute SLOs against counters collected from monitored routes. You define one or more conditions using a counter, an operator, and a threshold value. ObserveOps evaluates each condition at the frequency you set — Daily, Weekly, Monthly, or Quarterly — and calculates an achieved percentage against your target.
When you add multiple conditions to a single NetRoute SLO, ObserveOps evaluates them using the same multi-condition logic it applies to infrastructure Performance SLOs. This lets you define complex route compliance rules in a single profile.
Configure a NetRoute Performance SLO
- Go to Settings from the main menu.
- Select Service Level Objectives, then click SLO Profile.
- Click Create SLO Profile.
- Set SLO Type to Performance.
- Select the NetRoute tab that appears in the performance SLO configuration area.
- Fill in the NetRoute condition fields:
| Field | Description |
|---|---|
| Counter | Select a NetRoute metric to evaluate — e.g., latency, packet loss, jitter. |
| Operator | Choose the comparison direction: >, <, >=, <=, or =. |
| Value | Enter the threshold number. Units update automatically based on the selected counter. |
| Source Filter | Filter by a specific dimension of the route or tag. |
| Source | Select the specific NetRoute route or NetRoute tag to evaluate. |
- To add more conditions, click Add Condition and repeat step 6 for each metric.
- Fill in the remaining SLO fields:
| Field | Description |
|---|---|
| SLO Name | A unique name for this SLO profile. |
| SLO Description | A short explanation of what this SLO measures. |
| Target (%) | The minimum compliance percentage required to meet the SLO. |
| Warning (%) | An early-alert threshold above the target. Must be higher than the target. |
| Frequency | Evaluation window: Daily, Weekly, Monthly, or Quarterly. |
| Start Date | The date ObserveOps begins collecting data for this SLO. Only future dates are supported. |
| Tags | Custom tags for grouping and filtering SLO profiles. |
| Notify Team | Teams or individuals to notify when the SLO breaches a threshold. |
- Click Create SLO Profile.
Your NetRoute SLO appears in the SLO Profile list with Status: ON.
You can edit only SLO Description, Tags, and Notify Team after you create the profile.
View NetRoute SLO Results
NetRoute SLOs appear across all existing SLO views without extra configuration.
SLO Visualization
Open SLO > Visualization to see your NetRoute SLO alongside infrastructure and APM SLOs. Each card shows Target, Achieved %, Violation %, and a trend chart for the selected frequency window.
SLO History
Open SLO > History to review historical evaluations for your NetRoute SLOs. Filter and drill down the same way you do for other SLO types.
Reporting and Dashboards
NetRoute SLOs appear in SLO dashboards, SLO reports, and SLO widgets with no additional configuration. Existing dashboard and reporting capabilities work without modification.
Example
Your network team monitors three WAN routes for a retail chain using NetRoute. You create a NetRoute Performance SLO with a packet_loss < 1% condition and a latency < 50ms condition, using a Weekly frequency and a 99.5% target. At the weekly review, the SLO dashboard shows which routes stayed within the target and which routes triggered the warning threshold — giving you clear data for your WAN performance report.
Troubleshooting
NetRoute tab does not appear in the Performance SLO form
Cause: No NetRoute routes are active in the NetRoute module, or the NetRoute module is not licensed. Fix: Verify that at least one route appears in the NetRoute module with live data. If NetRoute is not in your navigation, contact your ObserveOps administrator to check licensing.
SLO shows 0% achieved immediately after creation
Cause: SLO evaluation starts at the beginning of the next evaluation window. Fix: Wait for the first evaluation window to complete. A Daily SLO starts at midnight; a Weekly SLO starts at the beginning of the configured week.