ONES GA 3.0
Release
  • ONES GA v3.0
    • Open Networking Enterprise Suite (ONES)
      • ONES Application
        • ONES Telemetry Collector(s) and Visibility
        • ONES Time Scale Metric Calculation
        • ONES Rule Engine
        • ONES Orchestration
        • ONE DL
        • ONES Supportability
        • ONES Security
        • ONES 3.0 Multisite
    • What's new?
    • Getting Started
      • Supported Switch Platforms and NOS
      • Scalability
      • Subscription
      • ONES Installation
        • Installation Pre-requisites
        • Download ONES Package
        • Installing ONES Application
        • ONE-DL cloud Deployment
        • Installing ONES Agents 3.0
          • ONES Telemetry Agent Installation
          • ONES Server Agent Installation
          • ONES Orchestration Agent Installation
          • Agent Less Telemetry
            • Cumulus(NVUE API)
            • Arista EOS (OpenConfig)
            • CISCO NXOS (GRPC)
        • Adding New Controller
        • Installing ONES Multisite
      • VM Deployment
        • VMware ONES Deployment
        • KVM ONES Deployment
        • Upgrade VM
    • ONES Web GUI Administration
      • Login Page
      • Adding Devices
      • Monitor
      • Inventory
        • Devices
        • Configurations
      • Rule Engine
        • Slack Channel Integration
        • Zendesk Support Integration
        • Service Now Integration
        • Rules Type
          • Add Rules: Entity
          • Add Rules: Entity by Properties
        • Alerts
      • Analytics
      • Settings
      • Integrations
        • Slack Channel Integration
        • Zendesk Support Integration
        • Service Now Integration
        • Cloud Services
          • Splunk
          • Amazon S3
      • Accounts
      • ONES Orchestration
        • VXLAN-Symmetric
          • VXLAN-Symmetric-SAG-no-mclag-vrf
          • VXLAN-Symmetric-SAG-mclag-vrf
          • VXLAN-Symmetric-SVI-no-mclag-vrf
          • VXLAN-Symmetric-SVI-mclag-vrf
          • VXLAN-Symmetric-SAG-vrf-RoCE
        • VXLAN-SVI
          • VXLAN-SVI-no-mclag-IPv6-ebgp-IPv6-SVI
          • VXLAN-SVI-no-mclag-ibgp-IPv4-Underlay
          • VXLAN-SVI-no-mclag-ebgp-IPv6-SAG
          • VXLAN-SVI-no-mclag-ebgp-IPv4-Underlay
          • VXLAN-svi-no-mclag-ebgp-BGPU-Underlay
        • VXLAN-SAG
          • VXLAN-SAG-no-mclag-ibgp-no-host
          • VXLAN-SAG-no-mclag-ibgp-BGPU-Underlay
          • VXLAN-SAG-no-mclag-ibgp-BGPU-Underlay-HostPO
          • VXLAN-SAG-no-mclag-ebgp-no-host
        • VXLAN-MGLAG
          • VXLAN-MCLAG-ibgp-sag
          • VXLAN-MCLAG-ebgp-svi.yaml
          • VXLAN-MCLAG-ipv6-ibgp-sag
          • VXLAN-MCLAG-ebgp-BGPU-IPv6SAG
          • VXLAN-MCLAG-ibgp-BGPU-IPv6svi
          • VXLAN-MCLAG-ipv4-ibgp-svi
          • VXLAN-MCLAG-ipv6-ebgp-sag
        • VXLAN-Asymmetric
          • VXLAN-Asymmetric-SAG-no-mclag
          • VXLAN-Asymmetric-SAG-mclag
          • VXLAN-Asymmetric-SVI-no-mclag
          • VXLAN-Asymmetric-SVI-mclag
        • MH-VXLAN
          • MH-VXLAN-ibgp-sag
          • MH-VXLAN-ipv6-ibgp-sag
          • MH-VXLAN-Asymmetric-SAG
          • MH-VXLAN-ebgp-BGPU-IPv6SAG
          • MH-VXLAN-ipv6-ebgp-sag
          • MH-VXLAN-Symmetric-2-SAG-vrf
        • MCLAG
          • MCLAG-IPv4-SVI-AccessHosts
          • MCLAG-ibgp-BGPU-Underlay-IPv4SVI-AccessHosts
          • MCLAG-ibgp-IPv6-Underlay-IPv6SVI-AccessHosts
          • MCLAG-IPv4-Underlay-IPv6SVI-AccessHosts
          • MCLAG-IPv6-Underlay-IPv6SVI-AccessHosts
        • L3-MCLAG
          • L3-MCLAG
          • L3-MCLAG-bgpU-combinedLink
          • L3-MCLAG-bgp-combinedLink
        • L2-LS
          • L2LS-EC-L2
          • L2LS-EC-L3-ipv4
          • L2LS-EC-L3-ipv6
        • iBGP
          • i-BGP-IPv6-CLOS-IPv6-host
          • i-BGP-IPv6-CLOS-IPv4-svi
          • i-BGP-IPv4-CLOS-L2PO-host
          • i-BGP-IPv4-CLOS-L2-host
          • i-BGP-IPv4-CLOS-IPv6-svi
          • i-BGP-IPv4-CLOS-IPv4-PO-host
          • i-BGP-BGP-U-CLOS-IPv4-svi
          • i-BGP-BGP-U-CLOS-IPv4-host
        • e-BGP
          • e-BGP-IPv6-CLOS-IPv6-host
          • e-BGP-IPv6-CLOS-IPv4-svi
          • e-BGP-IPv4-CLOS-L2-host
          • e-BGP-IPv4-CLOS-IPv6-svi
          • e-BGP-BGP-U-CLOS-IPv6-svi
          • e-BGP-BGP-U-CLOS-IPv6-host
        • BGP-PO
          • BGP-PO-SFLOW-LeafOnly-EC
          • BGP-PO-SFLOW-LeafOnly-EC-incr1
          • BGP-PO-MCLAG-SFLOW-LeafOnly-EC
        • LeafOnly-EC
        • IPCLOS-1-IPv4-SVI-AccessHosts
        • DHCP-IPCLOS-IPv4-SVI-AccessHosts
        • VXLAN-Symmetric-SAG-vrf-RoCE
    • Common Issues and Troubleshooting Steps
      • ONES Installation
        • Storage issue
      • ONES Uninstallation
        • ONES-Application
        • Telemetry Agent
        • Orchestration Agent
      • Permission Issues
        • Application Installation
      • gNMI Troubleshooting on non-SONiC Switches
    • How to contact Aviz Networks Support?
    • Backup and Recovery
Powered by GitBook
LogoLogo

Copyright © 2025 Aviz Networks, Inc. All Rights Reserved.

On this page
  • Overview
  • Push Notification
Export as PDF
  1. ONES GA v3.0
  2. ONES Web GUI Administration

Rule Engine

Overview

In data centre operations, a rule engine with alerts for various metrics is essential for proactive monitoring and management of critical components and services. Let's see the different types of rule engine alerts for specific metrics in a data centre environment

  1. CPU and Memory Alerts

  2. Fan and Power Supply Unit Alerts

  3. Traffic Bandwidth

  4. ASIC IPv4 & IPv6 Routes

  5. BGP Neighbour Alerts

  6. Health Services

  7. Device Down Alerts

  8. SSD Health, temperature and memory usage alert

  9. Device Queue counters

  10. PFC counters

  11. Traffic Errors and Discard Counters

  12. frr and syncd services CPU utilization status

  13. Server Agent based metrics

    1. CPU Temperature and Utilization

    2. Down status

    3. FAN Speed

    4. Memory Utilization

    5. GPU

      1. Memory Utilization

      2. PSU Power Draw

      3. Temperature

      4. Utilization

Push Notification

Rule Engine pushes the configured rule notification in case any device breaches the threshold value configured under the rule to

  1. Slack channel

  2. Zendesk Support ticket

  3. Service Now ticket

To use Rule Engine Alert feature User needs to setup first Slack channel integration, Zendesk Support integration or Service-Now integration

PreviousConfigurationsNextSlack Channel Integration