NetRoute Policy

Overview

Once you have configured a NetRoute, it can be used to create policies which will utilize severity-based indicators to generate actionable alerts and notify users through default channels. Creating a policy ensure a proactive alert mechanism enabling efficient network management and rapid troubleshooting which further minimized potential disruptions.

Navigation

Go to Menu and select Settings . After that, Go to Policy Settings . Then, select NetRoute Policy.

Create NetRoute Policy

You can create a NetRoute policy by clicking on the Create Policy button. Below-mentioned parameters will be displayed on the next screen to configure the policy.

Field	Description
Policy Name	Provide a descriptive name for policy.
Tag	Provide a Tag for the policy.

Since configurations for different Policy Evaluation Types differ, let's look at them separately:

Source to Destination

If you select Source to Destination as Route Evaluation Type, it can be further divided as:

Field	Description
Threshold Alert	Triggers when the selected metric crosses a fixed value you define.
Baseline Alert	Alerts when current behavior deviates from its usual historical pattern.
Anomaly	Detects unexpected behavior automatically without requiring strict thresholds.
Forecast	Predicts future breaches based on trends and alerts before limits are hit.

Threshold Alert

Use-Case

Suppose you are managing network connectivity between your data center and a cloud-hosted application. You want Motadata ObserveOps to raise an alert whenever the packet loss or latency on the route between the source and destination exceeds a fixed threshold, for example when round-trip time goes above 100ms, indicating potential network degradation. You can create a Source to Destination Threshold Alert NetRoute policy to do the same.

Set Conditions

Field	Description
Route Evaluation Type	Select Source to Destination as Route Evaluation Type and further select the Threshold Alert card.
Counter	Use the dropdown to select a counter.
Source Filter	Use the dropdown to either select a NetRoute or a Tag associated with a configured NetRoute.
Source	List of sources will be available based on the Source Filter selection.
Critical/Major/Warning	Provide a numerical threshold value for each severity level respectively. You can also change the operator suitable to your needs using the dropdown.

Set Alert Message

Field	Description
Subject	Modify the subject-line for the alert message.
Message	Modify the alert message from here.

info

For a list of default supported Macros to modify the default set message, Please visit: Alert Macros

Notification

Field	Description
To	Add every recipient that should receive the alert. Type an entry, then select from the picker or press Enter to add it as a tag. - @User for a registered ObserveOps user (delivered by their profile channels). - @email@example.com for a direct email address. - /Handle for a Microsoft Teams or Slack handle from a saved integration profile. - #UserProfile for a saved user profile that fans out to every user inside it. - !Profile for a Syslog Forwarder or SNMP Trap Forwarder integration profile that forwards the alert to an external destination.
+ Bcc	Select + Bcc at the end of the To field to open a BCC field below it. Recipients you add in the BCC field stay hidden from every other recipient. Applies to email notifications only.
If severity is	Select the severity level using individual checkboxes in the dropdown.You can select multiple, all, or a single option as per your requirement. You can also have different recipients notified at different severity levels. For instance, you can notify johndoe@motadata.com when severity level hits Critical and send an alert notification to janedoe@motadata.com when severity level is Major.
Play Sound	Activate this toggle to enable sound notifications when an alert is triggered.
If Severity is	Choose the severity level at which the sound notification should be triggered. This option becomes visible only when the Play Sound toggle is switched ON.
Renotification	Turning on the toggle will resend the alert at a specific interval defined by the user if the alert severity is not changed for the time specified. If turned off, Motadata ObserveOps will not renotify about the alert.
Renotify	Similar to the To field, enter the username or email address of the recipient. Also choose a preset duration for renotification along with the severity level at which they system will renotify you if the alert severity is not changed.
Do not renotify if acknowledged	If the toggle is turned on, Motadata ObserveOps will not send a renotification to the recipient if they mark the alert as acknowledged.

info

The first recipient in To goes into the email To header and is visible to every other recipient. Set it to a team or distribution address such as noc@company.com for privacy. See Notification for the full BCC behaviour.

Declare Incident

Field	Description
Select Integration Profile to Trigger	Choose an Integration profile to be executed from the dropdown when the chosen alert severity is triggered.
When Alert Severity is	Select an Alert severity from the dropdown.
Create Integration Profile	Select this button to start creating a new Integration profile that you might want to assign to the policy you are creating.

You can click on to define a new Alert severity and Integration Profile combination. You can have separate Integration profile triggered at different levels of Alert severity.

Baseline Alert

The Baseline Alert for Source to Destination routes is a powerful feature within Motadata ObserveOps that enables proactive monitoring of network path performance by comparing real-time route metrics to a dynamically generated baseline. By analyzing historical data and establishing a baseline range, this alerting mechanism helps identify deviations in network behavior, allowing organizations to detect potential connectivity issues and take preventive action.

With the Baseline Alert, organizations gain deeper insights into the normal behavior of their network routes by leveraging historical data from the past 15 days. By dynamically adjusting the baseline range using advanced statistical techniques, the alerting mechanism adapts to changes in network behavior, ensuring accurate detection of deviations in real-time.

Use-Case

Suppose you are monitoring the network path between your headquarters and a remote branch office. The route normally maintains a round-trip time of around 20ms based on historical patterns. Rather than setting a rigid threshold, you want Motadata ObserveOps to alert you whenever the latency deviates significantly from this established baseline, for example if it suddenly increases 50% above the expected range, indicating potential network congestion or path changes. You can create a Source to Destination Baseline Alert NetRoute policy to do the same.

Baseline NetRoute Policy Mechanism

• Policy Evaluation

The Baseline policy evaluations start as soon as the policy is created. During each evaluation, the system considers the route metric data from the last 15 days to create a baseline range.

• Baseline Calculation

To generate the baseline range, the system utilizes advanced statistical methods. These techniques analyze the historical data points within the last 15 days and produce a dynamically adjusted baseline.

• Baseline Threshold Violation

Baseline threshold violation occurs when a route metric's data point deviates from the expected behavior, surpassing the predefined acceptable range known as the baseline threshold. This violation triggers an alert based on the configured parameters within the baseline policy.

In the baseline policy configuration, users set the criteria for triggering an alert by specifying the number of times a data point can deviate from the baseline threshold within a defined time window, as configured in the Abnormality Occurrence and Notify if the Threshold value breach within fields, respectively.

• Actions on Baseline Policy Triggering

Once the baseline alert is triggered, you can define specific actions to be taken, such as sending notifications to relevant stakeholders.

By leveraging the Baseline Alert, organizations can proactively monitor critical network routes, detect unusual path behavior, and take prompt action to ensure smooth connectivity and optimal network performance.

Set Conditions

Field	Description
Route Evaluation Type	Select Source to Destination as Route Evaluation Type and further select the Baseline Alert card.
Counter	Use the dropdown to select a counter.
Source Filter	Use the dropdown to either select a NetRoute or a Tag associated with a configured NetRoute.
Source	List of sources will be available based on the Source Filter selection.
Absolute/Relative	- Select Absolute to define specific numerical values. When selecting this option, users specify the exact values that metrics should deviate from the baseline to trigger an alert. - Select Relative to set thresholds based on percentages. This option allows users to define deviations from the baseline as a percentage, triggering alerts when metrics deviate by the specified percentage.
Critical/Major/Warning	Provide a numerical threshold value for each severity level respectively. You can also change the operator suitable to your needs using the dropdown.
Notify if threshold value breach within	Use the dropdown to select the duration for repeat notification.
Abnormality occurrence	Select the number of occurrences you wish to be notified for when threshold value has been breached.
Auto clear	Select the time duration to auto clear the abnormality alert. This does not clear the base alert.

Set Alert Message

Field	Description
Subject	Modify the subject-line for the alert message.
Message	Modify the alert message from here.

info

For a list of default supported Macros to modify the default set message, Please visit: Alert Macros

Notification

Field	Description
To	Add every recipient that should receive the alert. Type an entry, then select from the picker or press Enter to add it as a tag. - @User for a registered ObserveOps user (delivered by their profile channels). - @email@example.com for a direct email address. - /Handle for a Microsoft Teams or Slack handle from a saved integration profile. - #UserProfile for a saved user profile that fans out to every user inside it. - !Profile for a Syslog Forwarder or SNMP Trap Forwarder integration profile that forwards the alert to an external destination.
+ Bcc	Select + Bcc at the end of the To field to open a BCC field below it. Recipients you add in the BCC field stay hidden from every other recipient. Applies to email notifications only.
If severity is	Select the severity level using individual checkboxes in the dropdown.You can select multiple, all, or a single option as per your requirement. You can also have different recipients notified at different severity levels. For instance, you can notify johndoe@motadata.com when severity level hits Critical and send an alert notification to janedoe@motadata.com when severity level is Major.
Play Sound	Activate this toggle to enable sound notifications when an alert is triggered.
If Severity is	Choose the severity level at which the sound notification should be triggered. This option becomes visible only when the Play Sound toggle is switched ON.
Renotification	Turning on the toggle will resend the alert at a specific interval defined by the user if the alert severity is not changed for the time specified. If turned off, Motadata ObserveOps will not renotify about the alert.
Renotify	Similar to the To field, enter the username or email address of the recipient. Also choose a preset duration for renotification along with the severity level at which they system will renotify you if the alert severity is not changed.
Do not renotify if acknowledged	If the toggle is turned on, Motadata ObserveOps will not send a renotification to the recipient if they mark the alert as acknowledged.

info

The first recipient in To goes into the email To header and is visible to every other recipient. Set it to a team or distribution address such as noc@company.com for privacy. See Notification for the full BCC behaviour.

Declare Incident

Field	Description
Select Integration Profile to Trigger	Choose an Integration profile to be executed from the dropdown when the chosen alert severity is triggered.
When Alert Severity is	Select an Alert severity from the dropdown.
Create Integration Profile	Select this button to start creating a new Integration profile that you might want to assign to the policy you are creating.

You can click on to define a new Alert severity and Integration Profile combination. You can have separate Integration profile triggered at different levels of Alert severity.

Hop-to-Hop

Set Conditions

Field	Description
Path Evaluation Type	Select Hop-to-Hop as Path Evaluation Type.
Counter	Use the dropdown to select a counter.
Source Filter	Use the dropdown to either select a NetRoute or a Tag associated with a configured NetRoute.
Source	List of sources will be available based on the Source Filter selection.
Operator	Use the dropdown menu to select an operator best suitable for your requirements.
Value	Provide a numerical threshold value for the severity level.
Severity	Select a severity level to associate with the configured threshold value. You can only select single severity level.

note

To address different severity levels for Hop-to-Hop Path Evaluation, multiple policies can be created.

Set Alert Message

Field	Description
Subject	Modify the subject-line for the alert message.
Message	Modify the alert message from here.

info

For a list of default supported Macros to modify the default set message, Please visit: Alert Macros

Notification

Field	Description
To	Add every recipient that should receive the alert. Type an entry, then select from the picker or press Enter to add it as a tag. - @User for a registered ObserveOps user (delivered by their profile channels). - @email@example.com for a direct email address. - /Handle for a Microsoft Teams or Slack handle from a saved integration profile. - #UserProfile for a saved user profile that fans out to every user inside it. - !Profile for a Syslog Forwarder or SNMP Trap Forwarder integration profile that forwards the alert to an external destination.
+ Bcc	Select + Bcc at the end of the To field to open a BCC field below it. Recipients you add in the BCC field stay hidden from every other recipient. Applies to email notifications only.
Play Sound	Activate this toggle to enable sound notifications when an alert is triggered.

info

The first recipient in To goes into the email To header and is visible to every other recipient. Set it to a team or distribution address such as noc@company.com for privacy. See Notification for the full BCC behaviour.

Declare Incident

Field	Description
Select Integration Profile to Trigger	Choose an Integration profile to be executed from the dropdown when the chosen alert severity is triggered.
When Alert Severity is	Select an Alert severity from the dropdown.
Create Integration Profile	Select this button to start creating a new Integration profile that you might want to assign to the policy you are creating.

You can click on to define a new Alert severity and Integration Profile combination. You can have separate Integration profile triggered at different levels of Alert severity.