search
Home

Rules Type

hashtag
Rules Type

There are two types of Rule a user can configure

  1. Entity Based

    1. Allow a user to create Rules per device

      1. Allow user to include or exclude the devices from the rule

  2. Entity by Property

    1. Allow a user to create Rules by using HwSKU, Role, OS Version across all the managed devices

hashtag
1. Entity Based explained

hashtag
Possible Values & Description

  1. Rule Name: The user can choose any related name

  2. For: The user can choose 2 options

chevron-rightDevice: Once the user chooses the rule for Devices it will show the below Metricshashtag

  • ASIC IPv4 Routes

  • ASIC IPv6 Routes

  • BGP Neighbours Down

  • Device CPU Core Temperature

  • Device CPU Utilization

  • Device Down

  • Device Memory Utilization

  • Device Queue Transmit Counter

  • FAN Speed

  • Failed FANs

  • Failed PSUs

  • PSU Temperature

  • SSD Health

  • SSD Temeperature

  • SSD Used Memory Percent

  • frr CPU Utilization

  • syncd CPU Utilization

chevron-rightInterface: Once the user chooses the rule for Interfaces it will show the below Metricshashtag

  • Interface flap

  • Interface PFC Receive Counters

  • Interface PFC Transmit Counters

  • Interface Queue Transmit Counters

  • Traffic InDiscards

  • Traffic InErrors

  • Traffic OutDiscards

  • Traffic OutErrors

  • Traffic Rx Utilization

  • Traffic Tx Utilization

  • Transceiver Rx Power

  • Transceiver Temperature

  • Transceiver Tx Power

  • Transceiver Voltage

chevron-rightServer: The user will be able to get alerts for IntelGaudy hashtag

  • CPU Core Temperature

  • CPU Utilization

  • Device Down

  • FAN Speed

  • GPU Memory Utilization

  • GPU PSU 1 Power Draw

  • GPU PSU 2 Power Draw

  • GPU Temperature

  • GPU Utilization

  • Memory Utilization

  1. Metrics: Metrics depend on the above (For: Device/Interface) condition

  2. Measure: Metrics are measured in three diff ways

    1. MIN

    2. AVG

    3. MAX

  3. Period: Measured metrics can be verified with a buffer of a timer

    1. 5 min

    2. 10 min

    3. 15 min

    4. 30 min

    5. 1 hour

hashtag
Conditions

  1. When Measured Value is: This option allows a user to choose what condition has to match when the measured value is

    1. EQ: Equal to

    2. NEQ: Not Equal to

    3. GE: Greater than Equal to

    4. LE: Less than Equal to

    5. GT: Greater than

    6. LT: Less than

  2. Critical Threshold: The user can set a Critical value on which push notification will be triggered

  3. Warning Threshold: The user can set a Warning value on which push notification will be triggered

hashtag
Notification

  1. Notify: The user can choose the integrated SLACK Channel

  2. Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket

  3. Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket

  4. Weekly Digest: Slack Users can choose this for Weekly Digest to SLACK Channel

  5. Do not notify if the same alert trigger in: 30min, 1hour, 2hours, 10hours, 24hours

  6. Stop notifying after: The user can choose a value of occurrence then it will not trigger the same in the next 24 hours

hashtag
2. Entity by Property

hashtag
Possible Values & Description

  1. Rule Name: The user can choose any related name

  2. Filter: user can filter the rule for all managed devices by

    1. HWSKU

    2. ROLE

    3. OS Version

  3. For: The user can choose 2 options

chevron-rightDevice: Once the user chooses the rule for Devices it will show the below Metricshashtag

  • ASIC IPv4 Routes

  • ASIC IPv6 Routes

  • BGP Neighbours Down

  • Device CPU Core Temperature

  • Device CPU Utilization

  • Device Down

  • Device Memory Utilization

  • Device Queue Counter

  • FAN Speed

  • Failed FANs

  • Failed PSUs

  • PSU Temperature

  • SSD Health

  • SSD Temeperature

  • SSD Used Memory Percent

  • frr CPU Utilization

  • syncd CPU Utilization

chevron-rightInterface: Once the user chooses the rule for Interfaces it will show the below Metricshashtag

  • Interface Flap

  • Interface PFC Counters

  • Interface Queue Counters

  • Traffic InDiscards

  • Traffic InErrors

  • Traffic OutDiscards

  • Traffic OutErrors

  • Traffic Rx Utilization

  • Traffic Tx Utilization

  • Transceiver Rx Power

  • Transceiver Temperature

  • Transceiver Tx Power

  • Transceiver Voltage

  1. Select: this option depends on the Filter category, possible values are

    1. Select HWSKU :

    2. Select ROLE :

    3. Select OS VERSION :

  2. Metrics: Metrics depend on the above (For: Device/Interface) condition

  3. Measure: Metrics are measured in three diff ways

    1. MIN

    2. AVG

    3. MAX

  4. Period: Measured metrics can be verified with a buffer of a timer

    1. 5 min

    2. 10 min

    3. 15 min

    4. 30 min

    5. 1 hour

hashtag
Conditions

  1. When Measured Value is: This option allows a user to choose what condition has to match when the measured value is

    1. EQ: Equal to

    2. NEQ: Not Equal to

    3. GE: Greater than Equal to

    4. LE: Less than Equal to

    5. GT: Greater than

    6. LT: Less than

  2. Critical Threshold: The user can set a Critical value on which push notification will be triggered

  3. Warning Threshold: The user can set a Warning value on which push notification will be triggered

hashtag
Notification

  1. Notify: The user can choose the integrated SLACK Channel

  2. Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket

  3. Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket

  4. Weekly Digest: Slack Users can choose this for Weekly Digest to SLACK Channel

  5. Do not notify if the same alert trigger in 30min, 1hour, 2hours, 10hours, 24hours

  6. Stop notifying after: The user can choose a value of occurrence then it will not trigger the same in the next 24 hours

PreviousRule EngineNextAdd Rules: Entity

Last updated

Was this helpful?