Trap Policy
Overview
The trap policy feature in Motadata AIOps enables effective monitoring and analysis of SNMP trap data, allowing proactive identification and resolution of network device issues. With trap policies, you can define rules and conditions to generate alerts based on trap data, ensuring smooth network operation and timely response to potential issues.
Use-Case
Network Device Monitoring: Configure trap policies to detect and alert on various SNMP trap events generated by network devices, such as link status changes, hardware failures, or configuration errors.
Performance Monitoring: Create trap policies to monitor network device performance metrics, including CPU utilization, memory usage, or interface bandwidth, enabling you to optimize device performance and prevent bottlenecks.
Fault Detection: Utilize trap policies to identify and alert on critical faults or abnormalities in network device behavior, helping you mitigate risks and maintain network reliability.
Create Trap Policy
Navigation
Go to Menu, Select Settings . After that, Go to Policy Settings . Select Metric/Log/Flow/Trap policy. The list of the created policies is now displayed.
Click on to start creating a policy. From the panel on the left side of the screen, click on the Flow tab to start creating a metric policy. The screen to create a Flow Policy is now displayed.
Enter the details of the following parameters to create a Trap Policy:
Field | Description |
---|---|
Policy Name | Enter a unique name of the policy you want to create. |
Tag | Enter a name to logically categorize the policy. You can quickly and easily identify a policy based on the tag assigned to it. |
Set Conditions
Field | Description |
---|---|
Trigger Condition | Choose the specific trap event you wish to create a policy for by selecting from the available options. This event will be the basis for monitoring and generating alerts. |
Operator | Select the operator that will be applied to the trap event values to define the triggering condition for the alert. Different operators such as equal to, not equal to, greater than, less than, etc., are available to provide flexibility in defining your alert conditions. |
Value | Specify the threshold value against which the trap event values will be compared. Once the trap event value meets the specified condition, an alert will be triggered. |
Source Filter | Source Host will be selected by default. |
Source | Select the specific Source Host for which you want to create the policy. |
Critical/Major/Warning | Kindly use these fields to set the severity under which the alert will be triggered. |
Supress Action | Switch this Toggle button ON to supress the actions and notifications mapped to the policy. Once you switch this button ON and the alert is triggered, the action will be executed once and you will receive a single notification before the actions and notifications configured in the policy are supressed for the time-period specified in the field Supress Window. |
Supress Window | Specify the time-period for which you do not wish to execute the actions and receive the notifications mapped to policy. |
Notify Team
Field | Description |
---|---|
Notify | There are two ways you can populate this field: |
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. |
Take Action
Field | Description |
---|---|
Action to be taken | Select a runbook from the dropdown to be executed when the alert is triggered. |
Create New | Select this button to start creating a new runbook which you might want to assign to the policy you are creating. |
Select the Create Policy button to create the policy based on the details entered.
Select the Reset button to erase all the current field values, if required.