Intent-based distributed alert service
By adopting shareable alarm service technology in the data center, using multiple instances of the alarm rule execution engine to allocate equipment and resources, the complexity of abnormal detection and alarm generation in the data center is solved, and flexible scaling and efficient manage.
Patent Information
- Application Number
- CN202011272347.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-08-24
- Filing Date
- 2020-11-13
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-11-13
AI Technical Summary
In large data centers, the diversity of network equipment and the equipment configuration of different tenants make it difficult to generate data generated by abnormal detection and alarms, and it is difficult to effectively monitor and manage.
Using shareable alarm service technology, the device is allocated through multiple instances of the alarm rule execution engine, the administrator's advanced intent data is received, the administrator is converted into low-level rules, and the resources are allocated across multiple instances to obtain telemetry data, and the exception detection and Alert generation.
It realizes flexible alarm service expansion and reduction, simplifies network administrator operations, and improves data center management efficiency and user satisfaction.
Smart Images

Figure CN114189425B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to computer networks, and more particularly to anomaly detection in computer networks. Background Art
[0002] Virtualized data centers are becoming a core foundation of modern information technology (IT) infrastructure. In particular, modern data centers have extensively utilized virtualized environments, in which virtual hosts such as virtual machines or containers are deployed and executed on underlying computing platforms of physical computing devices.
[0003] Virtualization within large data centers can provide multiple advantages, including efficient use of computing resources and simplified network configuration. Therefore, in addition to the efficiency and higher return on investment (ROI) brought by virtualization, enterprise IT staff also generally prefer virtualized computing clusters in data centers because of their management advantages.
[0004] Supporting virtualization in a large data center may require numerous network devices and host devices that can be coupled together in a data center network. In addition, network devices in a data center may be assigned to different tenants. Given the large number of network devices, different types of network devices, and different tenants that may exist in a data center, it may be difficult to configure the devices to generate data for anomaly detection and alert generation. Summary of the invention
[0005] This disclosure describes techniques for providing a sharable alert service to perform anomaly detection and alert generation for cloud infrastructure monitoring, which can be used by multiple applications and tenants at cloud scale.
[0006] Administrators can express alert rules as "intents" that define rules in a high-level "natural language." An alert rule compiler can receive the intent and convert the high-level intent into one or more lower-level rules that can be programmatically processed by multiple alert rule execution engines. In some aspects, devices in a network system can be associated with an alert rule execution engine in a distributed manner. For example, devices in a network can be associated with different instances of an alert rule execution engine, thereby allocating resource usage across multiple alert rule execution engines to obtain telemetry data about devices in the network and process alerts.
[0007] The techniques described herein may provide one or more technical advantages. For example, the techniques may facilitate the use of an alert rule execution engine that may be implemented as a microservice and may be fault-tolerant and scalable. As a result, the alert service may be easily scaled to meet changes in the number of devices used by a network system. In addition to scalability, the alert service may be easily used by network administrators because the administrator may express intent in a high-level natural language, and the alert service may convert the administrator's intent into lower-level rules that define the devices and metrics that need to be accessed to implement the administrator's intent.
[0008] In one example, a method includes: allocating multiple devices among multiple instances of an alert rule execution engine by one or more processors; receiving data representing an alert intent by the one or more processors; converting the data representing the alert intent into one or more rules by the one or more processors, the one or more rules specifying alert criteria for corresponding alerts of the one or more rules; determining, by the one or more processors, a device set among the multiple devices specified by the one or more rules; assigning, by the one or more processors, the one or more rules to corresponding instances among the multiple instances of the alert rule execution engine to which the device set has been assigned, wherein each corresponding instance of the alert rule execution engine is configured to apply the one or more rules to devices in the device set assigned to the corresponding instance of the alert rule execution engine; registering the device set specified by the one or more rules with a telemetry service, wherein the device set provides telemetry data in response to the registration; subscribing to the telemetry data by the corresponding instance among the multiple instances of the alert rule execution engine to obtain the telemetry data; and outputting an indication of an alert for the rule in response to determining, by the corresponding instance among the multiple instances of the alert rule execution engine based on the one or more rules, that the telemetry data matches the alert criteria of a rule among the one or more rules.
[0009] In another example, an alarm service system includes: an alarm controller, executable by one or more processors and configured to distribute multiple devices among multiple instances of an alarm rule execution engine; an alarm intent compiler, executable by one or more processors and configured to: receive data representing an alarm intent, convert the data representing the alarm intent into one or more rules, the one or more rules specifying alarm criteria for corresponding alarms of the one or more rules, and determining a device set among multiple devices specified by the one or more rules; and an alarm rule programmer, executable by one or more processors and configured to assign the one or more rules to multiple instances of the alarm rule execution engine to which the device set has been assigned. The invention relates to a corresponding instance in the example, wherein each corresponding instance of the alert rule execution engine is configured to apply one or more rules to devices in a device set assigned to the corresponding instance of the alert rule execution engine; wherein the alert rule controller is also configured to register a device set specified by one or more rules with a telemetry service, wherein the device set provides telemetry data in response to the registration; wherein one or more corresponding instances of the multiple instances of the alert rule execution engine are also configured to: subscribe to telemetry data to obtain telemetry data, and in response to the corresponding instance of the multiple instances of the alert rule execution engine determining, based on one or more rules, that the telemetry data matches the alert criteria of a rule in one or more rules, output an indication of an alert of the rule.
[0010] In another example, a computer-readable storage medium includes instructions that, when executed, cause a processing circuit system of a computing system to perform the following operations: distribute multiple devices among multiple instances of an alert rule execution engine; receive data representing an alert intent; convert the data representing the alert intent into one or more rules, wherein the one or more rules specify alert criteria for corresponding alerts of the one or more rules; determine a set of devices among multiple devices specified by the one or more rules; assign the one or more rules to corresponding instances among multiple instances of the alert rule execution engine to which the device set has been assigned, wherein each corresponding instance of the alert rule execution engine is configured to apply the one or more rules to devices in the set of devices assigned to the corresponding instance of the alert rule execution engine; register the set of devices specified by the one or more rules with a telemetry service, wherein the set of devices provides telemetry data in response to the registration; subscribe to the telemetry data by corresponding instances among the multiple instances of the alert rule execution engine to obtain the telemetry data; and output an indication of an alert for the rule in response to determining by corresponding instances among the multiple instances of the alert rule execution engine that the telemetry data matches the alert criteria of a rule in the one or more rules based on the one or more rules.
[0011] The details of one or more techniques of the present disclosure are set forth in the accompanying drawings and the following description. Other features, objects, and advantages of the invention will become apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1 is a conceptual diagram illustrating an example network including an intent-based alert service according to one or more aspects of the present disclosure;
[0013] Figure 2 is a block diagram illustrating an example system including an alert service in a network and / or within a data center according to one or more aspects of the present disclosure;
[0014] Figure 3 is a block diagram showing further details of an alert service according to one or more aspects of the present disclosure;
[0015] Figure 4 is a conceptual diagram illustrating an example of assigning alerts and network devices to an alert rule execution engine according to one or more aspects of the present disclosure;
[0016] Figure 5 is a conceptual diagram illustrating an event pattern alert rule state machine according to one or more aspects of the present disclosure;
[0017] Figure 6 is a conceptual diagram illustrating a warning mode alert rule state machine according to one or more aspects of the present disclosure;
[0018] Figure 7 is a flow chart illustrating operations performed by an example alert service according to one or more aspects of the present disclosure;
[0019] Figure 8 is a conceptual diagram illustrating normalized alert data according to one or more aspects of the present disclosure;
[0020] Fig.9A An API for an alert service controller according to one or more aspects of the present disclosure is shown;
[0021] Fig. 9B According to one or more aspects of the present disclosure, Fig.9A Parameters associated with the API;
[0022] Fig.10 An API for receiving historical and real-time alert notifications according to one or more aspects of the present disclosure is shown; and
[0023] Fig.11 Rules and health metrics are shown that may be used to scale out or scale down various components and services of an alert service in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION
[0024] Data centers that use virtualized environments provide efficiency, cost, and organizational advantages in which virtual hosts, virtual machines, or containers are deployed and executed on underlying computing platforms of physical computing devices. A typical data center employs many network devices and host devices that are used to support the virtualized environment and enable communication between entities within the data center and outside the data center. Monitoring the numerous devices in the data center for anomalies may be useful for effectively managing the data center structure. In addition, monitoring the devices in the data center for anomalies can facilitate early detection and resolution of problems, thereby improving user satisfaction with the data center. Telemetry data from network devices and host devices can facilitate anomaly detection.
[0025] In some cases, collecting enough data from network devices to facilitate anomaly detection can be a challenge, particularly given the number of network devices and host devices in the network and the variety of different network devices and host devices in the network. For network administrators, it can be difficult to master all of the different commands or application programming interfaces (APIs) required to collect telemetry data from devices in the network.
[0026] Described herein are techniques that enable a network administrator to indicate the administrator's intent regarding obtaining telemetry data for devices in the network. The administrator's intent can be translated into one or more lower-level rules that conform to different protocols and metrics that can be obtained from network devices. Furthermore, the techniques described herein can facilitate an alert service that can be easily scaled as the network grows.
[0027] Figure 1 is a conceptual diagram illustrating an example network including anomaly detection service 140 in a network (eg, a network within a data center) according to one or more aspects of the present disclosure. Figure 1 An example implementation of a network system 100 and a data center 101 is shown, with the data center 101 hosting one or more computing networks, computing domains or projects, and / or cloud-based computing networks. The network system 100 may include one or more cloud-based computing clusters, which may coexist in a common overall computing environment, such as in a single data center, or be distributed between environments, such as across different data centers. The cloud-based computing clusters may be, for example, different cloud environments, such as an OpenStack cloud environment, a Kubernetes cloud environment, a collection of bare metal servers, a Contrail or Tungsten cluster, or various combinations of other computing clusters, domains, networks, etc. In other cases, other implementations of the network system 100 and data center 101 may be appropriate. Such implementations may include Figure 1 The examples include a subset of the components, and / or may include Figure 1 Additional components not shown.
[0028] exist Figure 1 In the example of FIG. 1 , data center 101 provides an operating environment for applications and services for customers 104 coupled to data center 101 via service provider network 106 . Figure 1 can be shown as distributed in Figure 1 In other examples, between multiple devices in Figure 1 The features and techniques of one or more devices in the present invention may be performed internally by local components of one or more such devices. Similarly, one or more such devices may include certain components and perform various techniques described herein as being attributed to one or more other devices. In addition, certain operations, techniques, features, and / or functions may be combined with Figure 1 In some embodiments, the present invention relates to an operation, technique, feature, or function that is attributable to one or more components, devices, or modules, or is performed by a specific component, device, and / or module. In other examples, such operations, techniques, features, and / or functions may be performed by other components, devices, or modules. Therefore, some operations, techniques, features, and / or functions attributed to one or more components, devices, or modules may also be attributed to other components, devices, and / or modules, even if not specifically described in this manner herein.
[0029] Data center 101 hosts infrastructure equipment, such as network and storage systems, redundant power supplies, and environmental controls.Service provider network 106 may be coupled to one or more networks managed by other providers, and thus may form part of a large-scale public network infrastructure such as the Internet.
[0030] In some examples, data center 101 may represent one of many geographically distributed network data centers. Figure 1 As shown in the example of FIG. 1 , data center 101 is a facility that provides network services to customers 104. Customers 104 may be collective entities, such as businesses and governments, or individuals. For example, a network data center may host network services for several businesses and end users. Other example services may include data storage, virtual private networks, traffic engineering, file services, data mining, science or supercomputing, etc.
[0031] exist Figure 1 In the example of FIG. 1 , data center 101 includes a group of storage systems, application servers, computing nodes, or other devices, including devices 110A to 110N (collectively referred to as "devices 110", representing any number of network devices). Devices 110 may be interconnected via a high-speed switching fabric 121 provided by one or more layers of physical network switches and routers. In some examples, devices 110 may be included in fabric 121, but are shown separately for ease of illustration.
[0032] Device 110 can be any of many different types of network devices (core switches, spine network devices, branch network devices, edge network devices, or other network devices), but in some examples, one or more devices 110 can be used as physical computing nodes and / or storage nodes in a data center. For example, one or more of devices 110 can provide an operating environment for the execution of one or more customer-specific applications or services. Alternatively or additionally, one or more devices 110 can provide an operating environment for one or more virtual machines or other virtualized instances (such as containers). In some examples, one or more of devices 110 can alternatively be referred to as host computing devices or more simply as hosts. Device 110 can thereby execute one or more virtualized instances, such as virtual machines, containers, or other virtual execution environments for running one or more applications or services (such as virtual network functions (VNFs)).
[0033] In general, each device 110 can be any type of device that can operate on a network and can generate data (e.g., connectivity data, flow data, sFlow data, resource utilization data) that can be accessed through telemetry or other means, which can include any type of computing device, sensor, camera, node, monitoring device, or other device. In addition, some or all of the devices 110 can represent a component of another device, where such a component can generate data that can be collected through telemetry or other means. For example, some or all of the devices 110 can represent physical or virtual network devices, such as switches, routers, hubs, gateways, security devices (such as firewalls, intrusion detection and / or intrusion prevention devices).
[0034] Although not specifically shown, the switch fabric 121 may include a top-of-rack (TOR) switch coupled to a distribution layer of chassis switches, and the data center 101 may include one or more non-edge switches, routers, hubs, gateways, security devices (such as firewalls, intrusion detection and / or intrusion prevention devices), servers, computer terminals, laptops, printers, databases, wireless mobile devices (such as cellular phones or personal digital assistants), wireless access points, bridges, cable modems, application accelerators, or other network devices. The switch fabric 121 may perform layer 3 routing to route network traffic between the data center 101 and the customer 104 through the service provider network 106. The gateway 108 is used to send and receive packets between the switch fabric 121 and the service provider network 106.
[0035] In some examples, orchestration engine 130 manages functions of data center 101, such as computing, storage, networking, and application resources. Orchestration engine 130 can implement security policies across a group of VMs or to the boundaries of a tenant network. Orchestration engine 130 can deploy network services (e.g., load balancers) in a tenant's virtual network.
[0036] According to one or more examples of the present disclosure, a software defined network ("SDN") controller 132 provides a logically and in some cases physically centralized controller to facilitate the operation of one or more virtual networks within a data center 101. In some examples, the SDN controller 132 operates in response to configuration input received from an orchestration engine 130 via a northbound application programming interface (API) 131, which in turn can operate in response to configuration input received from an administrator 128 interacting with and / or operating a user interface device 129. The SDN controller 132 can create virtual networks for tenants within or across data centers 101. The SDN controller 132 can attach virtual machines (VMs) to a tenant's virtual network. The SDN controller 132 can connect a tenant's virtual network to an external network, such as the Internet or a VPN.
[0037] In some examples, the SDN controller 132 manages network and networking services such as load balancing, security, etc., and can allocate resources from the device 110 used as a host device to various applications via the southbound API 133. That is, the southbound API 133 represents a set of communication protocols used by the SDN controller 132 to make the actual state of the network equal to the desired state specified by the orchestration engine 130. For example, the SDN controller 132 can implement the high-level request of the orchestration engine 130 by configuring physical switches, such as top-of-rack (TOR) switches, chassis switches, and switch fabrics 121; physical routers; physical service nodes, such as firewalls and load balancers; and virtual services such as virtual firewalls in VMs. The SDN controller 132 maintains routing, network, and configuration information in a state database. Different cloud computing clusters can have separate instances of the SDN controller 132.
[0038] The alert service 140 may configure the device 110 (and / or other devices) to collect and provide telemetry data related to the operation of the device 110. Such data may include process usage data, memory usage data, network usage data, error counts, etc. The alert service 140 may be configured with rules for determining whether to generate an alert based on the telemetry data. Applications, processes, threads, etc. may subscribe to alerts to be notified when an alert is triggered based on current conditions on one or more devices on the network.
[0039] The user interface device 129 can be implemented as any suitable device for presenting output and / or accepting user input. For example, the user interface device 129 can include a display. The user interface device 129 can be a computing system, such as a mobile or non-mobile computing device operated by a user and / or administrator 128. According to one or more aspects of the present disclosure, the user interface device 129 can, for example, represent a workstation, a laptop or notebook computer, a desktop computer, a tablet computer, or any other computing device that can be operated and / or present a user interface by a user. In some examples, the user interface device 129 can be physically separated from the controller 132 and / or in a position different from the controller 132. In such an example, the user interface device 129 can communicate with the controller 132 via a network or other communication means. In other examples, the user interface device 129 can be a local peripheral device of the controller 132, or can be integrated into the controller 201.
[0040] Additionally, user interface device 129 may communicate with alarm service 140 or components thereof to configure alarm service 140 to configure alarms using high-level intent statements and receive alarms, logs, or other data from devices 110 and other components of data center 101 .
[0041] According to the techniques of this disclosure, the alert service 140 may provide a sharable alert service to perform anomaly detection and alert generation for cloud infrastructure monitoring, which may be used by multiple applications and tenants at cloud scale.
[0042] The administrator 128 can utilize the UI device 129 to input data representing alert rules as "intents" that define rules in terms of a high-level "natural language." The alert service 140 can receive the data representing the intent and convert the high-level intent into one or more lower-level rules that can be programmatically processed by multiple alert rule execution engines of the alert service 140. In some aspects, the devices 110 in the network system can be associated with the alert rule execution engines in a distributed manner. For example, the devices 110 in the network can be associated with different instances of the alert rule execution engines, thereby allocating resource usage across multiple alert rule execution engines to obtain telemetry data about the devices in the network and process alerts.
[0043] Figure 2 is a block diagram illustrating an example system including an alert service in a network and / or within a data center according to one or more aspects of the present disclosure. Figure 2 The network system 200 can be described as Figure 1 Example or alternative implementations of the network system 100. Figure 2 One or more aspects of this document may be Figure 1 described in the context of .
[0044] Although such as Figure 1 and 2 The data centers shown may be operated by any entity, but some data centers may be operated by service providers, where the business model of such service providers may involve providing computing power to customers or clients. Therefore, data centers typically contain a large number of computing nodes or host devices. In order to operate effectively, these hosts must be connected to each other and to the outside world, and this capability is provided by physical network devices, which can be interconnected in a leaf-spine topology. The collection of these physical devices (e.g., network devices and hosts) forms an underlying network.
[0045] Each host device in such a data center can have several virtual machines running on it, which can be called workloads. Clients in the data center can generally access these workloads and can use these workloads to install applications and perform other operations. Workloads running on different host devices but accessible by a specific client are organized into a virtual network. Each client typically has at least one virtual network. These virtual networks are also called overlay networks. In some cases, clients in the data center may experience network problems such as increased latency, packet loss, low network throughput, or slow workload processing. Deploying workloads in large multi-tenant data centers can complicate solving such problems.
[0046] exist Figure 2 In the example of FIG. 1 , network 205 connects alarm service 140, host device 210A, and host devices 210B-210N. Alarm service 140 may correspond to Figure 1 Example or alternative implementations of alert service 140 are shown. Host devices 210A, 210B, through 210N may be collectively referred to as “host devices 210 ,” meaning any number of host devices 210 .
[0047] Each host device 210 may be Figure 1 110, but in Figure 2 In the example of , as opposed to a network device, each host device 210 is implemented as a server or host device that functions as a physical or virtualized computing node or storage node of a virtual data center. As further described herein, one or more host devices 210 (e.g., Figure 2 A host device 210A) may execute multiple virtual computing instances, such as virtual machines 228, and further, one or more host devices 210 (e.g., one or more of host devices 210B to 210N) may execute applications or service modules on non-virtualized single-tenant and / or bare metal servers. Figure 1 middle, Figure 2The examples illustrate a network system that may include a mix of virtual server devices and bare metal server devices.
[0048] Also connected to the network 205 is a user interface device 129 that can be operated by the administrator 128, such as Figure 1 In some examples, user interface device 129 may present one or more user interfaces on a display device associated with user interface device 129 .
[0049] Network 205 may correspond to Figure 1 The switch fabric 121 and / or the service provider network 106 may correspond to any one of the switch fabric 121 and / or the service provider network 106, or alternatively, may correspond to a combination of the switch fabric 121, the service provider network 106, and / or another network. Figure 2 Not shown, but network 205 may also include Figure 1 Some components of include gateway 108, SDN controller 132 and orchestration engine 130.
[0050] Shown in network 205 are spine devices 202A and 202B (collectively referred to as "spine devices 202" and representing any number of spine devices 202), and leaf devices 203A, 203B, and leaf devices 203C (collectively referred to as "leaf devices 203" and also representing any number of leaf devices 203). Although network 205 is shown with spine devices 202 and leaf devices 203, other types of network devices may be included in network 205, including core switches, edge network devices, top-of-rack devices, and other network devices.
[0051] Typically, network 205 may be the Internet, or may include or represent any public or private communications network or other network. For example, network 205 may be a cellular, ZigBee, Bluetooth, near field communication (NFC), satellite, enterprise, service provider, and / or other types of networks capable of data transmission between computing systems, servers, and computing devices. One or more of the client devices, server devices, or other devices may transmit and receive data, commands, control signals, and / or other information on the network 205 using any suitable communication technology. The network 205 may include one or more network hubs, network switches, network routers, satellite antennas, or any other network devices. Such devices or components may be operably coupled to each other to provide information exchange between computers, devices, or other components (e.g., between one or more client devices or systems and one or more server devices or systems). Figure 2Each device or system shown may be operatively coupled to the network 205 using one or more network links. The links coupling such devices or systems to the network 205 may be Ethernet, asynchronous transfer mode (ATM), or other types of network connections, and such connections may be wireless and / or wired connections. Figure 2 One or more of the devices or systems shown on the network 205 may be remotely located relative to one or more of the other shown devices or systems.
[0052] Each host device 210 represents a physical computing device or a computing node or a storage node that provides an execution environment for a virtual host, a virtual machine, a container, and / or other real or virtualized computing resources. In some examples, each host device 210 can be a component of a cloud computing system, a server farm, and / or a server cluster (or a portion thereof) that provides services to client devices and other devices or systems.
[0053] Certain aspects of host device 210 are described herein with respect to host device 210A. Other host devices 210 (e.g., host devices 210B to 210N) may be similarly described and may also include components with the same reference numbers, which may represent the same, similar, or corresponding components, devices, modules, functions, and / or other features. Therefore, the description herein with respect to host device 210A may be applied to one or more other host devices 210 (e.g., host devices 210B to 210N) accordingly.
[0054] exist Figure 2 In the example of FIG. 2 , the host device 210A includes underlying physical computing hardware, including one or more processors 213, one or more communication units 215, one or more input devices 216, one or more output devices 217, and one or more storage devices 220. In the example shown in the figure, the storage device 220 may include a kernel module 222 and a virtual router module 224. The storage device 220 may also include virtual machines 228A to 228N (collectively referred to as "virtual machines 228", and represent any number of virtual machines 228), which, when present, may be executed on top of a hypervisor (not shown), or may be controlled by a hypervisor. One or more devices, modules, storage areas, or other components of the host device 210A may be interconnected to enable inter-component communication (physically, communicatively, and / or operationally). In some examples, such a connection may be provided by a communication channel (e.g., communication channel 212A), a system bus, a network connection, an inter-process communication data structure, or any other method for transmitting data.
[0055] Processor 213A may implement functions associated with host device 210A and / or execute instructions associated with host device 210A. Communication unit 215A may communicate with other devices or systems on behalf of host device 210A. One or more input devices 216 and output devices 217 may represent input and / or output devices associated with host device 210A. Storage device 220 may store information for processing during operation of host device 210A. Each such component may be implemented in a manner similar to that described herein in conjunction with network analysis system 140, etc.
[0056] The virtual router module 224 can be a data center 101 ( Figure 1 ) executes multiple routing instances and can route packets to appropriate virtual machines executing in an operating environment provided by host device 110. Virtual router module 224 can also be responsible for collecting overlay flow data, such as Contrail Flow data when used in an infrastructure using Contrail SDN.
[0057] Virtual machines 228A through 228N (collectively referred to as "virtual machines 228" and representing any number of virtual machines 228) may represent example instances of virtual machines 228. Host device 210A may divide the virtual and / or physical address space provided by storage device 220 into a user space for running user processes. Host device 210A may also divide the virtual and / or physical address space provided by storage device 220 into a kernel space, which is protected and may not be accessible to user processes.
[0058] Each virtual machine 228 can represent a tenant virtual machine that runs a client application, such as a network server, a database server, an enterprise application, or hosts a virtualized service for creating a service chain. In some cases, any one or more of the host device 210 or another computing device directly hosts the client application (i.e., not as a virtual machine) (e.g., one or more of the host devices 210B to 210N, such as host device 210B and host device 210N). Although one or more aspects of the present disclosure are described in terms of a virtual machine or a virtual host, the techniques described herein in accordance with one or more aspects of the present disclosure for such a virtual machine or a virtual host may also be applied to containers, applications, processes, or other execution units (virtualized or non-virtualized) executed on the host device 210.
[0059] exist Figure 2In the example of , the alert service 140 may include one or more processors 243, one or more communication units 245, one or more input devices 246, one or more output devices 247, and one or more storage devices 250. The storage device 250 may include an alert rule intent programming interface 221, an alert rule intent compiler 218, an alert notification subscription service 208, an alert rule execution engine 214, and a data repository 259.
[0060] One or more of the devices, modules, storage areas, or other components of alert service 140 may be interconnected to enable inter-component communication (physically, communicatively, and / or operationally). In some examples, such connectivity may be provided via a communication channel (e.g., communication channel 242), a system bus, a network connection, an inter-process communication data structure, or any other method for transferring data.
[0061] The one or more processors 243 of the alert service 140 may implement functionality and / or execute instructions associated with the network analysis system 240 or associated with one or more modules shown and / or described herein. The one or more processors 243 may be, may be part of, and / or may include processing circuitry that performs operations according to one or more aspects of the present disclosure. Examples of processors 243 include a microprocessor, an application processor, a display controller, an auxiliary processor, one or more sensor hubs, and any other hardware configured to function as a processor, a processing unit, or a processing device.
[0062] One or more communication units 245 of alert service 140 can communicate with devices external to alert service 140 by transmitting and / or receiving data, and can function in some aspects as input devices and output devices. In some examples, communication unit 245 can communicate with other devices over a network. In other examples, communication unit 245 can send and / or receive radio signals over a radio network, such as a cellular radio network. Examples of communication unit 245 include a network interface card (e.g., such as an Ethernet card), an optical transceiver, a radio frequency transceiver, a GPS receiver, or any other type of device that can send and / or receive information. Other examples of communication unit 245 can include a device that can transmit and / or receive information over a network. GPS, NFC, ZigBee, and cellular networks (e.g., 3G, 4G, 5G), as well as those found in mobile devices and Universal Serial Bus (USB) controllers, etc. A device that communicates with a radio. Such communications may follow, implement or comply with appropriate protocols, including Transmission Control Protocol / Internet Protocol (TCP / IP), Ethernet, Bluetooth, NFC or other technologies or protocols.
[0063] The one or more input devices 246 may represent any input device of the alert service 140 not otherwise described herein. The one or more input devices 246 may generate, receive, and / or process input from any type of device capable of detecting input from a person or machine. For example, the one or more input devices 246 may generate, receive, and / or process input in the form of electrical, physical, audio, image, and / or visual input (e.g., peripherals, keyboards, microphones, cameras).
[0064] The one or more output devices 247 may represent any output device of the alert service 140 not otherwise described herein. The one or more output devices 247 may generate, receive, and / or process input from any type of device capable of detecting input from a person or machine. For example, the one or more output devices 247 may generate, receive, and / or process output in the form of electrical and / or physical output (e.g., peripheral devices, actuators).
[0065] One or more storage devices 250 in the alarm service 140 can store information for processing during the operation of the alarm service 140. The storage device 250 can store program instructions and / or data associated with one or more modules described according to one or more aspects of the present disclosure. One or more processors 243 and one or more storage devices 250 can provide an operating environment or platform for such modules, which can be implemented as software, but in some examples can include any combination of hardware, firmware and software. One or more processors 243 can execute instructions, and one or more storage devices 250 can store instructions and / or data for one or more modules. The combination of the processor 243 and the storage device 250 can retrieve, store and / or execute instructions and / or data for one or more applications, modules or software. The processor 243 and / or the storage device 250 can also be operably coupled to one or more other software and / or hardware components, including but not limited to one or more components of the alarm service 140 and / or one or more devices or systems shown as connected to the alarm service 140.
[0066] In some examples, one or more storage devices 250 are implemented as temporary storage, which may indicate that the primary purpose of one or more storage devices is not long-term storage. The storage device 250 of the alarm service 140 can be configured for short-term storage of information as volatile memory, and therefore does not retain the stored content if it is deactivated. Examples of volatile memory include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), and other forms of volatile memory known in the art. In some examples, the storage device 250 also includes one or more computer-readable storage media. The storage device 250 can be configured to store a larger amount of information than volatile memory. The storage device 250 can also be configured for long-term storage of information as non-volatile storage space, and retain information after activation / deactivation cycles. Examples of non-volatile memory include magnetic hard disks, optical disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory.
[0067] The alert rule intent compiler 218 receives an alert intent 230 that represents an alert generation intent at a higher level, and converts the alert intent into one or more lower-level alert rules that implement the alert intent 230. The alert intent 230 may be a natural language. As an example, the alert intent 230 may be "notify if CPU and network usage deviate from normal behavior in the cluster." In this example, the alert rule intent compiler 218 may automatically generate three alert rules from the alert intent 130:
[0068] 1. If for N of the M monitoring windows, / cpu / usage is higher than<baseline_threshold> , an alarm is issued to all hosts in the system
[0069] 2. If for N of the M monitoring windows, / network / ingress / bit_rate is higher than<baseline_threshold> , an alarm is issued for all network devices in the system
[0070] 3. If for N of the M monitoring windows, / network / egress / bit_rate is higher than<baseline_threshold> , an alarm is issued for all network devices in the system
[0071] The alarm rule intent compiler 218 can also perform optimizations in terms of alarm rule generation. For example, if there is an alarm intent that can be expressed in terms of an existing alarm intent, the alarm rule intent compiler 218 can map the new alarm intent to the existing alarm intent. The alarm rule intent compiler 218 can optimize the alarm rules by combining rules. As an example, assume that two alarm intents 230 "Intent1" and "Intent2" have previously been received and processed by the alarm rule intent compiler 218 to generate alarm rules "AlarmRuleSet1" and "AlarmRuleSet2", respectively. Next, assume that a new alarm intent 230 "Intent3" is received after Intent1 and Intent2 have been processed. The alarm rule intent compiler 218 can detect that Intent3 is a combination of Intent1 and Intent2. For example, the alarm rule intent compiler can detect that Intent3=Intent1+Intent2. In response to detecting that Intent3 is a combination of Intent1 and Intent2, alarm rule intent compiler 230 can generate an alarm rule that is a combination of the rules of Intent1 and Intent2, thereby avoiding generating a completely new set of alarm rules for Intent3. In this example, the alarm rule intent compiler can generate AlarmRuleSet3=AlarmRuleSet1+AlarmRuleSet1. The alarm rules generated by the alarm rule intent compiler 218 can be stored in the data repository 259 as alarm rules 232.
[0072] The alert rule intent programmer 221 receives the alert rules and determines one or more alert rule execution engines 214 that will process the alert rules. An alert rule intent instance 221 may program mutually exclusive subsets of alert rules to an alert rule execution engine 214. There may be multiple instances of the alert rule intent programmer 221, where each instance may be assigned a subset of rules. Each alert rule intent programmer 221 may independently determine the resources used by the rule and / or the resources that need to be created for the rule and the alert rule execution engine 214 to which the rule is to be posted for processing. In some aspects, the alert rule intent programmer may use Fig.9A The API shown programs rules into the alert rules execution engine 214 . Fig. 9B The parameters used by various functions of the API are shown in .
[0073] The alarm rule execution engine 214 receives telemetry data from network devices 202 and 203 and from host device 210. The alarm rule execution engine 214 applies the rules that have been programmed for it to the telemetry data and generates a corresponding alarm for the rule if the rule is met. In some aspects, the alarm rule execution engine 214 receives a telemetry data stream from network devices 202, 203 or host device 210 and analyzes a sliding window of telemetry data in the telemetry window data stream. For example, an alarm rule definition can be "If the "average" of "metric_1" is "above" the "threshold" within the "1 minute" monitoring interval in 3 of the past 5 monitoring intervals, then issue an alarm." After the sliding window analysis, if the conditions of the alarm rule are met, an alarm can be generated.
[0074] The alarm notification subscription service 208 provides an interface for an application (e.g., any one of applications 226A, 226B, ..., 226N, etc.) to notify the alarm service 140 that the application wishes to receive notifications of alarms. An application can specify an alarm or alarm type for which the application is interested in receiving notifications. In some aspects, there may be multiple end-user applications, management applications, and services interested in receiving real-time and historical alarm notifications. There may be multiple instances of the subscription service 208 that can serve a large number of applications simultaneously. In the event that an instance of the subscription service 208 fails, subscription requests on the failed instance may be reassigned to other available instances of the subscription service 208. In the event that an existing instance fails, a new instance of the subscription service 208 may be automatically generated.
[0075] The data repository 259 may represent any suitable data structure or storage medium for storing information related to configuring and processing alarms and telemetry, including storage of rules 232 and alarm history 234. The data repository 259 may be responsible for storing data in an indexed format to enable fast data retrieval and query execution. The information stored in the data repository 259 may be stored and / or categorized so that one or more modules in the alarm service 140 may provide input requesting information from the data repository 259 and, in response to the input, receive information stored in the data repository 259. The data repository 259 may be implemented by multiple hardware devices and may achieve fault tolerance and high availability by sharding and replicating data.
[0076] Figure 3 is a block diagram showing more details of an alert service according to one or more aspects of the present disclosure. Figure 3 As shown, the alert service 140 includes the above Figure 2 The components described herein, namely, alert rule intent compiler 218, alert rule programmer 221, alert rule execution engine 214, and alert notification subscription service 208. Figure 3As shown, the alert service 140 includes an inventory service 316 , an alert controller 330 , an alert rule execution service 332 , a publishing platform 314 , an alert data adapter 310 , and an alert notifier 306 .
[0077] The inventory service 316 may provide information about network resources available to the network 205. Such information may include network devices, host devices, services, etc. coupled to the network, as well as the status of such resources.
[0078] The alarm controller 330 can register the device with the network telemetry service to initiate the collection of telemetry data for the device and metrics specified in the alarm rules generated by the alarm rule intent compiler 218. In some aspects, the alarm controller 330 can select an appropriate protocol for collecting telemetry data from the device. For example, the alarm controller 330 can select a protocol based on the network or data management protocol supported by the device using information obtained from the device or from the inventory service 316.
[0079] An application, such as an element management service (EMS) application 302, can provide the alert intent 230 to the alert rule intent compiler 218. For example, a network administrator can provide the alert intent 230 via the EMS application 302.
[0080] After the alarm rule intent compiler 218 compiles the alarm intent 230 into one or more rules, the alarm controller 330 can provide a telemetry collector that can collect the desired telemetry data from the device specified in the rule generated from the alarm intent. In some aspects, the alarm controller can issue a request to the telemetry controller 328 to provide a telemetry collector. In order to supply the telemetry collector, a set of sensors and protocols can be determined that can be used by the telemetry collector to collect the desired telemetry data from the device. In some aspects, the alarm controller 330 can query the telemetry service 327 for its telemetry collection capabilities. Once the capabilities of the telemetry collector are determined, the alarm service 140 can request the appropriate telemetry protocol and (multiple) sensors. In some aspects, when the same metric can be collected using multiple telemetry protocols (such as Simple Network Management Protocol (SNMP), Google Remote Procedure Call (gRPC), Junos Telemetry Interface (JTI), etc.), priority can be given to the streaming-based telemetry protocol through a polling-based protocol.
[0081] In some aspects, telemetry service 327 may use heuristics to select the most appropriate protocol based on the current load on different collectors to collect the desired metrics for alert service 140. For example, the telemetry service may select the telemetry protocol collector with the least current load.
[0082] It is possible that more than one alert rule may specify the same metric. In this case, the telemetry collector will be provisioned only once to collect the desired metric. A single stream of metric data will be received by the alert rule execution engine 214, and rules in the alert rule execution engine that utilize the same metric can be executed simultaneously.
[0083] In certain aspects, when an alert rule is deleted and there are no longer rules interested in receiving data for a desired metric, the telemetry collector that supplied the metric can be decommissioned so that the previously desired metric is not collected.
[0084] More details regarding the telemetry service 327, including the telemetry controller 328 and the telemetry subscription service 326, can be found in commonly filed, co-pending U.S. patent application serial number ____________, entitled “INTENT BASED TELEMETRY COLLECTION SERVICE,” which is incorporated herein by reference.
[0085] In certain aspects, the alarm controller 330 can manage multiple instances of the alarm rule intent compiler 218 and the alarm rule programmer 221. For example, multiple alarm intents can be processed simultaneously and converted into alarm rule sets that are intended to satisfy the alarm intents. If an alarm rule compiler instance 218 fails, a new instance for the alarm rule intent compiler 218 can be generated to satisfy the expected workload. The alarm controller 330 can reassign the current workload of the failed instance to the available pool of alarm rule intent compiler 218 instances that are in good condition.
[0086] The alert rule execution service 332 manages instances of the alert rule execution engine 214. For example, the alert rule execution service 332 can create and delete instances of the alert rule execution engine 214 as needed to maintain performance goals and / or resource usage goals. As described above, each execution engine 214 can be assigned alert rules for a specific set of network devices. Upon receiving a rule to be processed, the alert rule execution engine 214 can subscribe to telemetry data by issuing a subscription request to the telemetry subscription service 326. Instances of the execution engine 214 may crash. The alert rule execution service 332 can reassign the alert rules of the failed service to other available alert rule execution engine instances 214. In the event of a failure of an existing instance, a new instance of the alert rule execution engine 214 can be automatically generated.
[0087] Publishing platform 314 publishes alerts to applications that have subscribed to alerts (eg, applications 304A-304N, collectively referred to as “applications 304”). In some aspects, publishing platform 314 provides alert data to alert notification subscription service 208, alert data adapter 310, and alert notifier 306. Fig.10An example of an API is shown that an application 304 can use to subscribe to alerts, unsubscribe from alerts, obtain alert data, and modify alert subscriptions.
[0088] The alarm data adapter 310 can store the alarm notification persistently in a persistent storage device, such as a time series database (TSDB) 312. In some aspects, the TSDB 312 can be implemented using a ClickHouse database or an InfluxDB database. The same metric data can be collected through different telemetry protocols such as Simple Network Management Protocol (SNMP), Google Remote Procedure Call (gRPC), Junos Telemetry Interface (JTI), etc. However, when an alarm notification is generated, the output result can be converted to a constant standardized representation for use by the application 304. Figure 8 An example of an alert rule notification that has been standardized is shown in FIG.
[0089] In some aspects, there may be multiple instances of the alarm data adapter 310 that receive alarm notifications for rule sets for disjoint sets of network devices. In the event that an instance of the alarm data adapter 310 crashes, other available instances of the service may be the ones to handle the workload of the failed instance. In the event that an older instance crashes, a new instance of the alarm data adapter 310 may be automatically generated.
[0090] The alert notifier 306 can notify the subscribing application 304 of the alert via a notification channel established between the alert notifier 306 and the subscribing application 304. In some aspects, the notification channel can be a gRPC streaming channel, a slack application, an inter-process communication mechanism, etc. The alert notifier 306 can identify the metric and specific resource for which the notification was generated. A set of tags that provide context for the alert notification may be present. Tags can be added dynamically to include metadata information about the metric data that generated the alert rule notification.
[0091] In some aspects, the alarm service 140 can monitor itself to facilitate fault tolerance and dynamic scaling. For example, the alarm service 140 can monitor resource utilization such as processor and memory usage and other metrics such as queue sizes, which can be specific to a particular component of the alarm service. The alarm service can periodically or continuously monitor health metrics that can indicate whether the alarm service 140 is becoming a bottleneck for a given load, resulting in the generation (e.g., creation) of new instances of components that become bottlenecks. In some aspects, a set of rules can be defined to monitor the health metrics of a given service and then used to make decisions for creating new microservice instances to expand the alarm service capabilities. Similarly, the same mechanism is used to determine whether the load conditions are low enough to allow the alarm service capabilities to be reduced. Fig.11Rules and health metrics are shown that may be used to scale out or scale down various components and services of alert service 140 .
[0092] In some aspects, one or more of the services described above as part of the alert service 140 (e.g., alert rule intent compiler 218, alert rule programmer 221, alert rule execution engine 214, alert notification subscription service 208, inventory service 316, alert controller 330, alert rule execution service 332, publishing platform 314, alert data adapter 310, and alert notifier 306) can be implemented as microservices. For example, the microservices that make up the alert service 140 can be loosely coupled with one or more other microservices of the alert service 140, and a lightweight protocol can be implemented to communicate between the microservices.
[0093] In some aspects, one or more of the above services may be implemented as a Kubernetes deployment construct, including pods and containers.
[0094] The alarm service 140 can be implemented as any suitable computing system, such as one or more server computers, workstations, mainframes, devices, cloud computing systems, and / or other computing systems capable of performing operations and / or functions described according to one or more aspects of the present disclosure. In some examples, the alarm service 140 represents a cloud computing system, a server farm, and / or a server cluster (or a portion thereof) that provides services to client devices and other devices or systems. In other examples, the alarm service 140 can represent or be implemented by one or more virtualized computing instances (e.g., virtual machines, containers) of a data center, a cloud computing system, a server farm, and / or a server cluster.
[0095] For ease of explanation, only a limited number of devices (e.g., user interface device 129, spine device 202, leaf device 203, host device 210, alert service 140, etc.) are shown in the figures and / or other descriptions referenced herein. However, the technology according to one or more aspects of the present disclosure can be implemented using more such systems, components, devices, modules, and / or other items, and joint references to these systems, components, devices, modules, and / or other items can represent any number of such systems, components, devices, modules, and / or other items.
[0096] Figure 2 and 3The modules shown (e.g., components of the alarm service 140 and / or the host device 210) and / or the modules and systems shown or described elsewhere in this disclosure can perform the operations described using software, hardware, firmware, or a mixture of hardware, software, and firmware that resides in and / or executes at one or more computing devices. For example, a computing device can execute one or more such modules with multiple processors or multiple devices. A computing device can execute one or more such modules as a virtual machine executing on underlying hardware. One or more of these modules can be executed as one or more services of an operating system or computing platform. One or more such modules can be executed as one or more executable programs at the application layer of a computing platform. In other examples, the functions provided by the modules can be implemented by dedicated hardware devices.
[0097] Figure 4 is a conceptual diagram illustrating an example of assigning alerts and network devices to an alert rule execution engine according to one or more aspects of the present disclosure. Figure 4 In the example shown, the alert execution rule service 332 includes four instances of the alert rule execution engine 214A, 214B, 214C, and 214D. In the example, there are 12 network devices, D1-D12, evenly distributed across the alert rule execution engines 214A-214D. Table 402 shows the allocation of alert rules and network devices to the alert rule execution engines in this example. Alert rule (A1) instances are created for network devices D1, D5, D7, and D8. Figure 4 As shown in table 402, device D1 is assigned to alert rule execution engine 214A, device D5 is assigned to alert rule execution engine 214B, and devices D7 and D8 are assigned to alert rule execution engine 214C. Therefore, alert A1 is assigned to alert rule execution engines 214A, 214B, and 214C for alert rule processing. Alert rule A2 only applies to device D2, so alert rule A2 is only assigned to alert rule execution engine 214A. Alert rule A3 applies to devices D7, D8, D10, and D11, and is assigned to alert rule execution engines 214C and 214D.
[0098] In certain aspects, the alert rule programmer 221 is configured to assign all rules for a given network device to the same instance of the alert rule execution engine 214. Such assignment can facilitate distributing the load of alert rule processing among multiple instances of the alert rule execution engine 214, thereby producing a horizontally stable alert service 140.
[0099] During the lifetime of an alert rule, the rule can transition between different states. These states can depend on the warning mode. In some aspects, the alert service 140 supports two warning modes: event mode and warning mode. In event mode, the alert notification subscription service 208 can send periodic alert notifications as long as the conditions that satisfy the alert rule persist. In warning mode, the alert notification subscription service 208 can send alert notifications when the alert state changes. For example, when the alert rule conditions are met, the alert notification subscription service 208 can send an "active" notification. As long as the alert rule conditions remain unchanged, no more notifications will be sent. If the alert rule conditions are no longer met, the alert notification subscription service 208 can send an "inactive" notification. Therefore, the warning mode may not be as "noisy" as the event mode.
[0100] Figure 5 506. 507. 508. 509. 510. 511. 512. 513. 521. 522. 534. 535. 546. 551. 552. 561. 57. 58. 59. 60. 613. 624. 636. 647. 658. 66. 67. 68. 69. 70. 714. 725. 737. 748. 759. 76. 77. 78. 79. 80. 815. 826. 838. 79. 849. 90. 916. 927. 939. 941. 950. 969. 97. 98. 99. 100. 1011. 1024. 1030. 1041. 1051. 1069. 107. 108. 109. 110. 111. 112. 113. 114. 115. 116. 117. 118. 119. 120. 121. 122. 123. 124. 125. 126. 127. 128. 129. 130. 131. 132. 133. 134. 135. 136. 137. 138. 139. 140. 141. 142. 143. 144. 145. 146. 147. 148. 149
[0101] Figure 6606 . 607 is a conceptual diagram illustrating an alert mode alert rule state machine according to one or more aspects of the present disclosure. When an alert rule is configured, the initial state of the alert rule can be set to learning 602. When the alert rule is explicitly disabled or deleted, the alert rule can be set to disabled state 604. When the alert rule is explicitly enabled, the state of the alert rule can be set to learning 602. While in the learning state 602, if the telemetry data matches the rule criteria, the alert rule state can be set to active state 606, and the output can be logged. In some aspects, the rule can be in active 606 state as long as the telemetry data continues to match the rule criteria. While in active state 606, if the rule continues to match and the metadata changes, other alerts can be logged with the updated metadata, and the alert rule state can remain in active state 606. For example, rule R1 can be in active state because both interfaces Interface1 and Interface2 are down. Later, rule R1 can be in active state because another interface Interface3 in addition to Interface1 and Interface2 is also in down state. In this case, the metadata has changed and additional notifications may be sent to indicate that rule R1 is still active, but the activation reason may have changed. If the telemetry data does not match the rule criteria, the output may be logged with the alert rule state as Inactive 608. The alert rule may remain in the Inactive 608 state until the telemetry data matches the rule criteria. In any state other than Disabled 604, if the alert rule is reset, the state of the alert rule may be set to Learning 602.
[0102] Figure 7 is a flow chart illustrating operations performed by components of an example alert service 140 according to one or more aspects of the present disclosure. Figure 1 , 3 and 3 are described in the context of the alert service 140 Figure 7 In other examples, Figure 7 The operations described in can be performed by one or more other components, modules, systems, or devices. In addition, in other examples, in combination Figure 7 The operations described may be combined, performed in a different order, omitted, or may include additional operations not specifically shown or described. Figure 7 The techniques described in can be used to facilitate an easily configurable and scalable alerting service.
[0103] In some aspects, devices are assigned to instances of an alert rule execution engine (702). The devices may be assigned evenly or by other suitable heuristics.
[0104] Such as EMS application 302 ( Figure 3 ) can provide an alert intent for an alert to be provided by the alert service (704). As described above, the alert intent can be a high-level description of an alert. The alert rule intent compiler of the alert service can convert the alert intent into one or more rules, which can include specific telemetry data, criteria associated with the data, and the device to which the alert will apply (706). The one or more rules can be designed to implement the alert intent received by the alert service.
[0105] The alert service may determine devices associated with or specified by the rule generated at 706 ( 708 ).
[0106] The rules generated by the alert rule intent compiler may be provided to one or more instances of an alert rule programmer. The alert rule programmer may assign the rules to one or more instances of an alert rule execution engine (710). In some aspects, the alert rule programmer assigns the rules based on the device associated with the instance of the alert rule execution engine so that all rules associated with the same device are assigned to the same alert rule execution engine. In addition, the alert rules may be assigned to the alert rule execution engine based on the load currently experienced by the alert rule execution engine. For example, the rules may be assigned to an alert rule execution engine that is relatively lightly loaded.
[0107] Multiple rules can be assigned to the same alert rule execution engine. The same rule can be assigned to different execution engine instances, with each instance focusing on alert processing for a specific subset of network devices for a given rule.
[0108] The alert rules controller may register the device specified in the one or more rules with the telemetry service to begin collecting telemetry data for the metrics specified in the one or more rules (712). In certain aspects, the alert rules controller selects an appropriate protocol to register with the device.
[0109] The alert rule execution engine(s) 214, upon receiving the rule, can subscribe to the telemetry subscription service to receive the desired telemetry for the alert rule assigned to the alert rule execution engine (714). The alert rule execution engine(s) 214 begin receiving telemetry data for the metrics to which the alert rule execution engine has subscribed (716).
[0110] Each instance of the alert rule execution engine 214 processes the rules assigned to that instance (718) and determines whether the telemetry data matches the criteria specified in the one or more rules defining the alert (718). In some aspects, the alert rule execution engine 214 performs a sliding window analysis on the telemetry data and the rule criteria. For example, the alert rule execution engine can determine whether the telemetry data matches the rule criteria over a time window that passes (e.g., slides) over time. If the telemetry data matches the rule criteria within all or a specified portion of the sliding window, an alert associated with the rule can be triggered.
[0111] If the telemetry data matches the criteria specified by the alert rule (the "yes" branch of 720), the alert service outputs an indication of the alert. For example, the alert service may notify the subscribing application of the alert condition. The alert rule execution engine 214 may then wait to receive additional telemetry data to process according to the rule (return to 716).
[0112] If the telemetry data does not match the criteria specified by the alert rule (“No” branch of 720 ), the alert rule execution engine may wait for the arrival of additional telemetry data to process according to the rule (return to 716 ).
[0113] For the processes, devices and other examples or descriptions described herein (including in any flow chart or flowchart), some operations, actions, steps or events included in any technology described herein may be performed in different orders, may be added, merged or omitted completely (e.g., not all described actions or events are necessary for implementing the technology). In addition, in some examples, operations, actions, steps or events may be performed, for example, by multithreading, interrupt processing or multiple processors simultaneously rather than sequentially. Even if not clearly identified as automatically executed, some other operations, actions, steps or events may also be automatically executed. Moreover, some operations, actions, steps or events described as automatically executed may alternatively not be automatically executed, but in some examples, such operations, actions, steps or events may be executed in response to input or another event.
[0114] The drawings included herein each illustrate at least one example implementation of an aspect of the present disclosure. However, the scope of the present disclosure is not limited to such implementations. Therefore, other examples or alternative implementations of the systems, methods, or techniques described herein other than those shown in the drawings may be suitable in other cases. Such implementations may include a subset of the devices and / or components included in the drawings, and / or may include additional devices and / or components not shown in the drawings.
[0115] The detailed description set forth above is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. In order to provide a full understanding of the various concepts, the detailed description includes specific details. However, these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form in the accompanying drawings to avoid obscuring these concepts.
[0116] Thus, although one or more implementations of various systems, devices, and / or components may be described with reference to specific figures, such systems, devices, and / or components may be implemented in a variety of different ways. Figure 1 and / or Figure 2 ) may be alternatively implemented as a single device; for example, one or more components shown as separate components may alternatively be implemented as a single component. Moreover, in some examples, one or more devices generated as a single device in the figures herein may alternatively be implemented as multiple devices; one or more components shown as a single component may alternatively be implemented as multiple components. Each of such multiple devices and / or components may be directly coupled via wired or wireless communications, and / or remotely coupled via one or more networks. In addition, one or more modules may interact with each other and / or operate in conjunction with each other so that, for example, one module serves as a service or extension of another module. Moreover, each module, data repository, component, program, executable file, data item, functional unit or other item shown in the storage device may include multiple components, subcomponents, modules, submodules, data repositories and / or other components or modules or data repositories (not shown) that are not shown. Moreover, one or more devices or components that may be shown in various figures herein may alternatively be implemented as part of another device or component that is not shown in such figures. In this and other ways, some functions described herein may be performed by distributed processing of two or more devices or components.
[0117] Each module, data repository, component, program, executable file, data item, functional unit or other item shown in the storage device can be implemented in various ways. For example, each module, data repository, component, program, executable file, data item, functional unit or other item shown in the storage device can be implemented as a downloadable or pre-installed application or "app / APP". In other examples, each module, data repository, component, program, executable file, data item, functional unit or other item shown in the storage device can be implemented as part of an operating system executed on a computing device.
[0118] In addition, certain operations, techniques, features, and / or functions may be described herein as being performed by specific components, devices, and / or modules. In other examples, such operations, techniques, features, and / or functions may be performed by different components, devices, or modules. Therefore, in other examples, some operations, techniques, features, and / or functions that may be described herein as being attributed to one or more components, devices, or modules may be attributed to other components, devices, and / or modules, even if not specifically described in this manner herein.
[0119] Although specific advantages have been identified in conjunction with the description of some examples, various other examples may include some, all, or none of the enumerated advantages. Other advantages, technical or otherwise, may become apparent to one of ordinary skill in the art from this disclosure. Furthermore, although specific examples have been disclosed herein, various aspects of the disclosure may be implemented using any number of technologies, whether currently known or not, and therefore, the disclosure is not limited to the examples specifically described and / or shown in this disclosure.
[0120] In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium and / or transmitted via a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media (which corresponds to tangible media such as data storage media), or communication media (which includes any media that facilitates the transfer of a computer program from one place to another (e.g., according to a communication protocol)). In this manner, a computer-readable medium may generally correspond to (1) a non-transitory tangible computer-readable storage medium, or (2) a communication medium such as a signal or carrier wave. A data storage medium may be any available medium that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures to implement the techniques described in the present disclosure. A computer program product may include a computer-readable medium.
[0121] As an example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, flash memory, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) is used to send instructions from a website, server or other remote source, the definition of the medium includes coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology (such as infrared, radio and microwave, etc.). However, it should be understood that computer-readable storage media and data storage media do not include connections, carriers, signals or other transient media, but rather relate to non-transient tangible storage media. The disks and optical disks used include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blue-ray disks, wherein the disks usually copy data magnetically, while the optical disks copy data optically by lasers. The above combination should also be included in the scope of computer-readable media.
[0122] Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuit systems. Therefore, the terms "processor" or "processing circuit system" used herein may refer to any of the aforementioned structures or any other structure suitable for implementing the described techniques, respectively. In addition, in some examples, the described functionality may be provided within dedicated hardware and / or software modules. Similarly, the technology may be fully implemented in one or more circuits or logic elements.
[0123] The technology of the present disclosure can be implemented in a variety of devices or apparatuses, including wireless handsets, mobile or non-mobile computing devices, wearable or non-wearable computing devices, integrated circuits (ICs) or a group of ICs (e.g., chipsets). Various components, modules, or units are described in this disclosure to emphasize the functional aspects of devices configured to perform the disclosed technology, but they do not necessarily need to be implemented by different hardware units. Instead, as described above, the various units can be combined in hardware units, or provided by a collection of interoperable hardware units (including one or more processors described above) in combination with appropriate software and / or firmware.
Claims
1. A method for processing alert intent data, include: distributing, by one or more processors, the plurality of devices among the plurality of instances of the alert rule execution engine; receiving, by the one or more processors, data indicative of an alert intent; converting, by the one or more processors, the data representing the alert intent into one or more rules, the one or more rules specifying alert criteria for a corresponding alert for the one or more rules; determining, by the one or more processors, a set of devices among the plurality of devices specified by the one or more rules; assigning, by the one or more processors, the one or more rules to respective instances of the plurality of instances of the alert rule execution engine that have been assigned the set of devices, wherein each respective instance of the alert rule execution engine is configured to apply the one or more rules to devices in the set of devices assigned to the respective instance of the alert rule execution engine; registering, by the one or more processors, the set of devices specified by the one or more rules with a telemetry service, wherein the set of devices provides telemetry data in response to the registration; subscribing, by the corresponding instance of the plurality of instances of the alert rule execution engine, to the telemetry data to obtain the telemetry data; as well as In response to a determination by the corresponding instance of the plurality of instances of the alert rule execution engine that the telemetry data matches alert criteria for a rule of the one or more rules based on the one or more rules, an indication of the alert for the rule is output. 2 . The method of claim 1 , wherein converting the data representing the alert intent comprises determining that the set of devices is to be associated with the one or more rules, and generating the one or more rules to specify the set of devices.
3. The method according to claim 1, wherein allocating the plurality of devices among the plurality of instances of the alert rule execution engine comprises allocating a first subset of the one or more devices to a first instance of the alert rule execution engine and allocating a second subset of the one or more devices to a second instance of the alert rule execution engine, wherein assigning the one or more rules between the respective ones of the plurality of instances of the alert rule execution engine comprises assigning the one or more rules to each of the first instance of the alert rule execution engine and the second instance of the alert rule execution engine, and Wherein subscribing to the telemetry data by the corresponding instance among the multiple instances of the alert rule execution engine to obtain the telemetry data includes subscribing to first telemetry data by the first instance of the alert rule execution engine to obtain the first telemetry data from the first subset of the one or more devices, and subscribing to second telemetry data by the second instance of the alert rule execution engine to obtain the second telemetry data from the second subset of the one or more devices.
4. The method of claim 1, wherein assigning the one or more rules to respective instances of the alert rule execution engine comprises assigning all rules for a same device among the plurality of devices to the same instance of the alert rule execution engine to which the device has been assigned.
5. The method according to claim 1, wherein the data representing the alert intention is converted include: In response to determining that the alert intent is a combination of a first alert intent and a second alert intent, the one or more rules are generated as a combination of one or more first rules converted from the first alert intent and one or more second rules converted from the second alert intent.
6. The method according to any one of claims 1 to 5, further comprising: include: provisioning a telemetry collector for a device in the plurality of devices based at least in part on the one or more rules; as well as The device of the plurality of devices is registered with the telemetry collector based at least in part on the one or more rules. 7 . The method of claim 6 , wherein provisioning the telemetry collector comprises selecting a protocol for receiving telemetry data from the device of the plurality of devices.
8. The method of claim 7, wherein selecting the protocol for receiving the telemetry data comprises selecting the protocol based on a resource load associated with the protocol.
9. The method of claim 7, wherein the device of the plurality of devices implements a streaming protocol and a polling protocol, and wherein selecting the protocol for receiving the telemetry data comprises selecting the streaming protocol.
10. The method of any one of claims 1 to 5, wherein determining that the telemetry data matches the alert criteria based on the one or more rules comprises performing a sliding window analysis on a stream of telemetry data received from a device.
11. The method of any one of claims 1 to 5, wherein a single stream of telemetry data received from the device is provided to multiple instances of the alert rule execution engine that utilize the telemetry data processing rules.
12. The method of any one of claims 1 to 5, further comprising storing telemetry data associated with an alarm and alarm metadata for the alarm in a persistent storage device.
13. The method according to any one of claims 1 to 5, further comprising: include: In response to determining that resource utilization by an instance of the plurality of instances of the alert rule execution engine exceeds a threshold, spawning a new instance of said alert rule execution engine, reassigning one or more devices assigned to the instance of the plurality of instances of the alert rule execution engine that exceeds the threshold to the new instance of the alert rule execution engine, and Rules associated with the one or more devices are assigned to the new instance of the alert rules execution engine.
14. An alarm service system, include: an alert controller executable by one or more processors and configured to distribute a plurality of devices among a plurality of instances of an alert rule execution engine; an alert intent compiler, executable by the one or more processors and configured to: receiving data indicating the intent of an alert, converting the data representing the alert intent into one or more rules, the one or more rules specifying alert criteria for corresponding alerts for the one or more rules, and determining a set of devices among the plurality of devices specified by the one or more rules; an alert rule programmer executable by the one or more processors and configured to assign the one or more rules to respective instances of the plurality of instances of the alert rule execution engine to which the set of devices has been assigned, wherein each respective instance of the alert rule execution engine is configured to apply the one or more rules to the devices in the set of devices to which the respective instance of the alert rule execution engine is assigned; wherein the alert rules controller is further configured to register the set of devices specified by the one or more rules with a telemetry service, wherein the set of devices provides telemetry data in response to the registration; Wherein one or more corresponding instances of the plurality of instances of the alert rule execution engine are further configured to: subscribing to said telemetry data to obtain said telemetry data, and In response to a determination by the corresponding instance of the plurality of instances of the alert rule execution engine that the telemetry data matches alert criteria for a rule of the one or more rules based on the one or more rules, an indication of the alert for the rule is output.
15. The alarm service system according to claim 14, wherein the alarm intent compiler configured to convert the data representing the alarm intent comprises the alarm intent compiler configured to: determining that the set of devices is to be associated with the one or more rules; and The one or more rules are generated to specify the set of devices.
16. The alarm service system according to claim 14, wherein the alarm rule programmer is further configured to: assigning a first subset of the one or more devices to a first instance of the alert rules execution engine and assigning a second subset of the one or more devices to a second instance of the alert rules execution engine, Wherein the assignment of the one or more rules to the respective instances of the plurality of instances of the alert rule execution engine comprises assignment of the one or more rules to each of the first instance of the alert rule execution engine and the second instance of the alert rule execution engine.
17. The alarm service system of claim 14, wherein the assignment of the one or more rules to the corresponding instances of the alarm rule execution engine comprises assignment of all rules for a same device among the plurality of devices to the same instance of the alarm rule execution engine to which the device has been assigned.
18. The alarm service system of claim 14, wherein the alarm rule compiler configured to convert the data representing the alarm intent comprises the alarm rule compiler configured to: In response to a determination that the alert intent is a combination of a first alert intent and a second alert intent, the rule is generated as a combination of one or more first rules converted from the first alert intent and one or more second rules converted from the second alert intent.
19. The alarm service system according to any one of claims 14 to 18, wherein the alarm rule controller is further configured to: provisioning a telemetry collector for a device in the plurality of devices based at least in part on the one or more rules; and The device of the plurality of devices is registered with the telemetry collector based at least in part on the one or more rules.
20. A computer readable storage medium encoded with instructions for causing one or more programmable processors to perform the method according to any one of claims 1 to 13.
