A data transmission alarm method, apparatus, device, and storage medium

Abstract

This application relates to the field of data processing technology, specifically to a data transmission alarm method, apparatus, device, and storage medium, aiming to achieve real-time monitoring and alarming of cloud dedicated line traffic. The method includes: a resource pool acquisition machine sending port time-series data of a switch to a monitoring platform at preset time intervals; the monitoring platform sending the port time-series data to a data transmission component; the data transmission component associating the port time-series data with corresponding tenant information and service information; the data transmission component sending the port time-series data associated with the tenant information and service information to a cloud monitoring backend; the cloud monitoring backend calculating the value of a preset monitoring indicator based on the port time-series data; and the cloud monitoring backend pushing alarm information to users according to preset alarm rules based on preset thresholds corresponding to the monitoring indicators.

Description

Technical Field

[0001] This application relates to the field of network technology, and more specifically, to a data transmission alarm method, apparatus, device, and storage medium. Background Technology

[0002] Cloud dedicated lines are used to establish high-speed, low-latency, stable, and secure dedicated connection channels between users' local data centers and virtual private clouds (VPCs) in the cloud. This can meet customers' business needs for large data volumes. To ensure stable business operation, real-time monitoring and alerting of the data transmission status of cloud dedicated lines are necessary. In existing technologies, the traffic data status is generally viewed by actively querying the data transmission status.

[0003] Existing technologies cannot analyze and process existing data or generate threshold alarms, nor can they display alarm information to the corresponding users in real time. Summary of the Invention

[0004] This application provides a data transmission alarm method, apparatus, device, and storage medium, aiming to achieve real-time monitoring and alarming of cloud dedicated line traffic.

[0005] A first aspect of this application provides a data transmission alarm method, the method comprising:

[0006] The resource pool acquisition unit sends port timing data of the switch to the monitoring platform at preset time intervals.

[0007] The monitoring platform sends the port timing data to the data transmission component;

[0008] The data transmission component associates the port timing data with the corresponding tenant information and service information;

[0009] The data transmission component sends the port time-series data associated with the tenant information and the business information to the cloud monitoring backend.

[0010] The cloud monitoring backend calculates the values ​​of preset monitoring indicators based on the port time-series data;

[0011] The cloud monitoring backend pushes alarm information to users based on preset thresholds corresponding to the monitoring indicators and preset alarm rules.

[0012] Optionally, the method further includes:

[0013] Upon receiving an information viewing instruction in the cloud monitoring backend, the tenant corresponding to the information viewing instruction is determined.

[0014] The cloud monitoring backend sends the time-series data information corresponding to the tenant to the cloud monitoring console.

[0015] Optionally, the resource pool acquisition unit sends port timing data of the switch to the monitoring platform at preset time intervals, including:

[0016] The resource pool acquisition machine collects port timing data from the switch every preset time interval through a pre-configured gateway monitoring protocol.

[0017] The resource pool acquisition unit sends the port timing data to the monitoring platform.

[0018] Optionally, the data transmission component associates the port timing data with the corresponding tenant information and service information, including: the data transmission component determines the tenant information and service information corresponding to the port timing data based on the port information carried in the port timing data;

[0019] The data transmission component encapsulates the tenant information, the service information, and the port timing data into the same data packet.

[0020] Optionally, before the data transmission component associates the port timing data with the corresponding tenant information and service information, the method further includes:

[0021] The data transmission component establishes a message queue of corresponding length based on the traffic volume of the port timing data;

[0022] The data transmission component creates a corresponding number of coroutines based on the length of the message queue;

[0023] The data transmission component places the port timing data into the message queue.

[0024] Optionally, the cloud monitoring backend calculates the values ​​of preset monitoring indicators based on the port time-series data, including:

[0025] The cloud monitoring backend writes corresponding query statements based on the time-series data;

[0026] The cloud monitoring backend aggregates the time-series data of all time periods corresponding to the tenant based on the query statement;

[0027] The cloud monitoring backend calculates the value of the monitoring metric corresponding to the tenant based on the aggregated time-series data.

[0028] Optionally, the cloud monitoring backend pushes alarm information to users according to preset thresholds corresponding to the monitoring indicators and preset alarm rules, including:

[0029] If the value of the monitored indicator does not meet the preset threshold, a corresponding alarm message is generated;

[0030] If the alarm information conforms to the alarm rules, the alarm information will be sent to the cloud monitoring console.

[0031] A second aspect of this application provides a data transmission alarm device, the device comprising:

[0032] The data acquisition module is used by the resource pool acquisition machine to send port timing data of the switch to the monitoring platform at preset time intervals.

[0033] The first data sending module is used by the monitoring platform to send the port timing data to the data transmission component;

[0034] The data association module is used by the data transmission component to associate the port timing data with the corresponding tenant information and service information;

[0035] The second data sending module is used by the data transmission component to send the port time-series data associated with the tenant information and the business information to the cloud monitoring backend;

[0036] The indicator calculation module is used by the cloud monitoring backend to calculate the value of a preset monitoring indicator based on the port time series data;

[0037] The alarm module is used by the cloud monitoring backend to push alarm information to users according to preset thresholds corresponding to the monitoring indicators and preset alarm rules.

[0038] Optionally, the device further includes:

[0039] The switch determination module is used to determine the tenant corresponding to the information viewing instruction when the cloud monitoring backend receives the information viewing instruction;

[0040] The switch information sending module is used by the cloud monitoring backend to send the time-series data information corresponding to the tenant to the cloud monitoring console.

[0041] Optionally, the data acquisition module includes:

[0042] The data acquisition submodule is used by the resource pool acquisition machine to collect port time-series data from the switch at preset time intervals through a pre-configured gateway monitoring protocol.

[0043] The data sending submodule is used by the resource pool acquisition machine to send the port timing data to the monitoring platform.

[0044] Optionally, the data association module includes: a data determination submodule, used by the data transmission component to determine the tenant information and the service information corresponding to the port time series data based on the port information carried in the port time series data;

[0045] The data encapsulation submodule is used by the data transmission component to encapsulate the tenant information, the service information, and the port timing data into the same data packet.

[0046] Optionally, the device further includes:

[0047] The message queue establishment submodule is used by the data transmission component to establish a message queue of corresponding length according to the traffic volume of the port timing data.

[0048] The coroutine creation submodule is used by the data transmission component to create a corresponding number of coroutines based on the length of the message queue;

[0049] The data entry submodule is used by the data transmission component to put the port timing data into the message queue.

[0050] Optionally, the indicator calculation module includes:

[0051] The statement writing submodule is used by the cloud monitoring backend to write corresponding query statements based on the time-series data.

[0052] The data aggregation submodule is used by the cloud monitoring backend to aggregate the time series data of all time periods corresponding to the time series data of the tenant based on the query statement;

[0053] The indicator calculation submodule is used by the cloud monitoring backend to calculate the value of the monitoring indicator corresponding to the tenant based on the aggregated time-series data.

[0054] Optionally, the alarm module includes:

[0055] The alarm information generation submodule is used to generate corresponding alarm information when the value of the monitored indicator does not meet the preset threshold.

[0056] The alarm information sending submodule is used to send the alarm information to the cloud monitoring console when the alarm information meets the alarm rules.

[0057] A third aspect of this application provides a readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps described in the first aspect of this application.

[0058] A fourth aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the method described in the first aspect of this application.

[0059] Using the data transmission alarm method provided in this application, the resource pool acquisition machine sends port timing data of the switch to the monitoring platform at preset time intervals; the monitoring platform sends the port timing data to the data transmission component; the data transmission component associates the port timing data with corresponding tenant information and service information; the data transmission component sends the port timing data associated with the tenant information and service information to the cloud monitoring backend; the cloud monitoring backend calculates the value of a preset monitoring indicator based on the port timing data; and the cloud monitoring backend pushes alarm information to users according to the preset threshold corresponding to the monitoring indicator and preset alarm rules.

[0060] In this method, real-time port data of the switch is collected through the monitoring platform, and then the real-time port data is associated with tenant information and service information through the transmission component. Then, various monitoring indicators of the switch are calculated through the cloud monitoring backend. Finally, alarm information is pushed to users according to the preset thresholds corresponding to the monitoring indicators and the preset alarm rules, thereby realizing real-time monitoring and alarm of cloud private line traffic. Attached Figure Description

[0061] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0062] Figure 1 This is a schematic diagram of a cloud private line network.

[0063] Figure 2 This is a traffic graph query using HTTP.

[0064] Figure 3 This is a traffic graph for Kafka.

[0065] Figure 4 This is a flowchart of a data transmission alarm method proposed in an embodiment of this application;

[0066] Figure 5 This is a data display effect diagram that does not use data transmission components for processing;

[0067] Figure 6 This is a diagram showing the effect of data processing by a data transmission component according to an embodiment of this application;

[0068] Figure 7 This is a data transmission traffic interaction diagram proposed in an embodiment of this application;

[0069] Figure 8 This is a cloud network service logic diagram proposed in one embodiment of this application;

[0070] Figure 9 This is a schematic diagram of a data transmission alarm device according to an embodiment of this application;

[0071] Figure 10 This is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0072] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0073] refer to Figure 1 , Figure 1This is a schematic diagram of a cloud private line network. A cloud private line is a network service technology that connects enterprise data centers to cloud vendors' virtual private networks, providing a stable, reliable, and high-speed interconnection channel for enterprises to access the cloud privately. The Overlay network is a virtual network built on top of the Underlay network. Through technologies such as tunneling encapsulation, it virtualizes and abstracts the underlying physical connections to achieve a logical network structure. The Overlay network isolates data traffic between different virtual networks and allows it to span multiple physical networks, achieving flexible network segmentation and secure isolation. The Underlay network is the underlying physical network upon which the Overlay network relies. It mainly consists of physical devices (such as routers and switches) and is responsible for transmitting data in data center, enterprise, or WAN environments. It provides the actual transmission path for data packets and guarantees transmission quality and bandwidth. A cloud gateway mimics a disk array, a block-based device, or a file server. This device is placed at the customer's location, delivering hardware or software installed on that hardware. It translates SCSI or file service requirements into REST protocols for communication with public cloud services. BGP (Border Gateway Protocol) is a protocol implemented on the cloud gateway cluster. BFD (Bidirectional Forwarding Detection) is a network protocol that detects errors between two forwarding engines by connecting them through the data link layer. Bidirectional forwarding detection can detect the entire path, regardless of the number of switches or lines involved, helping end-to-end detect any disconnections. NQA (Network Quality Analyzer) is a real-time network performance monitoring and statistical technology that can statistically analyze network information such as response time, network jitter, and packet loss rate. VXLAN is a network virtualization technology that improves the scalability of large-scale cloud deployments and is an extension of VLANs. VXLAN is a powerful tool that can extend Layer 2 networks by penetrating Layer 3. It can overcome the portability limitations of VMS (Virtual Memory System) by encapsulating traffic and extending it to a Layer 3 gateway, allowing it to access servers on external IP subnets. VM stands for Virtual Machine. VPC (Virtual Private Cloud) is a dynamically configured pool of public cloud computing resources that requires the use of encryption protocols, tunneling protocols, and other security procedures to transmit data between private enterprises and cloud service providers. EIP (Enterprise Information Portal) refers to the unified integration of various application systems, data resources, and Internet resources into an enterprise information portal in an Internet environment. It creates personalized application interfaces based on the different characteristics and roles of each user, and organically connects users through the processing and transmission of events and messages.NAT (Network Address Translation) is a technology used to translate private IP addresses used on a local network into global IP addresses when connecting to the Internet. NAT was actually developed to address the shortage of IPv4 addresses. vSwitch (Virtual Switch) refers to a virtual switch or virtual network switch that operates at Layer 2 in a data network, implementing Layer 2 (and some Layer 3) network functions of a physical switch through software. IDC (Internet Data Center) refers to an Internet data center.

[0074] A single cloud private line supports 100Gbps bandwidth, and through link aggregation technology, it can reach the Tbps level to meet customers' business needs for large data volumes. To ensure the stable operation of large customer businesses, the cloud private line uses primary / backup / load management technology to achieve high availability of multi-access point services, but it is still relatively lacking in performance monitoring and alarms such as traffic and status.

[0075] In existing solutions, traffic data monitoring can be achieved through proactive queries via the HTTP protocol or by consuming data from Kafka.

[0076] refer to Figure 2 , Figure 2 This is a traffic graph query using HTTP, such as... Figure 2 As shown, the resource pool data acquisition unit uses SNMP (Simple Network Management Protocol) to periodically collect port performance data such as traffic and status of the leased line switch and report it to the Prometheus platform. Users can customize query parameters based on a specified physical leased line in the cloud leased line portal interface and trigger the background control component to query the data. The cloud leased line control component uses the HTTP protocol to call the Prometheus interface to query port traffic data, calculates and correlates it with tenant service data, and then returns it to the portal interface to plot inflow and outflow rate curves. This method requires users to specify parameters to query traffic data, only supports traffic curve monitoring, and the cloud leased line control component does not store switch performance data, making it impossible to analyze and process existing data or configure threshold alarms.

[0077] refer to Figure 3 , Figure 3 This is a traffic graph using Kafka, such as... Figure 3As shown, the resource pool data acquisition machine uses the SNMP protocol to periodically collect port performance data such as traffic and status of the leased line switch and reports it to the central service. The intelligent maintenance platform uses the Kafka protocol to consume the switch port performance data from the central service and store it in the database, supporting maintenance personnel to configure port-level threshold monitoring and alarms. This method supports real-time data consumption and storage, and maintenance personnel can customize thresholds to configure monitoring alarms and view traffic curves. However, the current data is not associated with tenant and business information, so it is not possible to display monitoring data and push alarm information to the corresponding users in real time.

[0078] refer to Figure 4 , Figure 4 This is a flowchart of a data transmission alarm method proposed in an embodiment of this application. Figure 4 As shown, the method includes the following steps:

[0079] S11: The resource pool acquisition unit sends port timing data of the switch to the monitoring platform every preset time interval.

[0080] In this embodiment, the resource pool acquisition unit is a data acquisition device deployed in the resource pool. The monitoring platform is used to monitor the equipment in the cloud private line. Port time-series data is the traffic data and status data of the switch arranged in chronological order over a period of time.

[0081] For example, the monitoring platform is Prometheus: Prometheus is an open-source system developed in Go that supports monitoring, alerting, and time-series data transmission. It uses the RemoteWrite protocol, which allows server-side data to be pushed to remote storage within Prometheus.

[0082] In this embodiment, the resource pool acquisition unit sends port timing data of the switch to the monitoring platform at preset time intervals. The specific steps include:

[0083] S11-1: The resource pool acquisition machine collects port timing data from the switch every preset time period through a pre-configured gateway monitoring protocol.

[0084] In this embodiment, the Gateway Monitoring Protocol (SNMP, Simple Network Management Protocol) is an application layer protocol specifically designed for managing network nodes (such as servers, workstations, routers, switches, and hubs) in IP networks. SNMP, through its standardized information structure and Management Information Base (MIB), enables network administrators to remotely monitor and manage the status and configuration of network devices, and to promptly identify and resolve network problems.

[0085] In this embodiment, the resource pool acquisition unit collects port timing data from a dedicated line switch at preset time intervals using a pre-configured network management monitoring protocol. The preset time interval can be set according to actual needs.

[0086] S11-2: The resource pool acquisition machine sends the port timing data to the monitoring platform.

[0087] In this embodiment, the resource pool acquisition unit sends port timing data to the monitoring platform. The monitoring platform receives the data and prepares to forward it.

[0088] S12: The monitoring platform sends the port timing data to the data transmission component.

[0089] In this embodiment, the data transfer component (Transfer) is used to process time-series data and associate the time-series data with the corresponding tenants and services.

[0090] In this embodiment, the monitoring platform sends port timing data to the data transmission component.

[0091] S13: The data transmission component associates the port timing data with the corresponding tenant information and service information.

[0092] In this embodiment, tenant information includes tenant ID, tenant email, tenant port name, etc., and service information includes switch IP, physical leased line number, leased line gateway, resource pool identifier, etc.

[0093] In this embodiment, after receiving the port timing data, the data transmission component queries the corresponding tenant information and service information in the cloud server based on the port information contained in the port timing data, and then encapsulates the tenant information and service information with the port timing data.

[0094] In this embodiment, the specific steps by which the data transmission component associates the port timing data with the corresponding tenant information and service information include:

[0095] S13-1: The data transmission component determines the tenant information and the service information corresponding to the port timing data based on the port information carried in the port timing data.

[0096] In this embodiment, the port information includes the port identifier and the identifier of the tenant corresponding to the port.

[0097] In this embodiment, the data transmission component determines the tenant identifier corresponding to the switch based on the port information carried in the port timing data, and then queries the tenant information and service information corresponding to the tenant in the cloud server.

[0098] S13-2: The data transmission component encapsulates the tenant information, the service information, and the port timing data into the same data packet.

[0099] In this embodiment, the data transmission component encapsulates tenant information, service information, and port timing data into the same data packet, thereby completing the association between port timing data, tenant information, and service information.

[0100] S14: The data transmission component sends the port time-series data associated with the tenant information and the business information to the cloud monitoring backend.

[0101] In this embodiment, the cloud monitoring backend is a platform for monitoring various devices in the private cloud network. It can uniformly monitor multiple nodes in the private cloud network and monitor tenant traffic usage, etc.

[0102] In this embodiment, the data transmission component sends port time-series data associated with tenant information and business information to the cloud monitoring backend.

[0103] In this embodiment, the data transmission method can be RemoteWrite or Push Gateway. Push Gateway is a standalone tool that passively pushes monitoring data. It allows users to push monitoring data to Push Gateway via custom scripts, and then Prometheus pulls this data from Push Gateway, thereby achieving centralized management and monitoring. This method is particularly suitable for scenarios where monitoring metrics cannot be directly obtained through Prometheus xporter, such as monitoring sources behind firewalls or instantaneously generated data.

[0104] S15: The cloud monitoring backend calculates the value of the preset monitoring indicator based on the port time series data.

[0105] In this embodiment, the monitoring metrics include physical leased line rate, number of bytes flowing in / out of the leased line gateway, etc.

[0106] In this embodiment, the cloud monitoring backend determines the tenant information corresponding to the received time-series data, and then writes a query statement to query all port time-series data corresponding to the tenant information. This includes not only the port time-series data received this time, but also the port time-series data received in previous time periods. These port time-series data are aggregated to calculate the values ​​of monitoring indicators corresponding to the switch, such as physical leased line rate and number of bytes flowing in / out of leased line gateway.

[0107] In this embodiment, the specific steps for the cloud monitoring backend to calculate the value of the preset monitoring indicator based on the port time-series data include:

[0108] S15-1: The cloud monitoring backend writes the corresponding query statement based on the time series data.

[0109] In this embodiment, the query statement is used to retrieve data from the database of the cloud platform.

[0110] In this embodiment, the cloud monitoring backend determines the tenant information corresponding to the received time-series data based on the time-series data, and then writes the corresponding query statement to query all the time-series data stored by the tenant in the cloud platform.

[0111] For example, the query statement is a PromQL statement. PromQL (Prometheus Query Language) is a powerful expression language built into the Prometheus system, used for real-time querying and aggregation of time-series data. PromQL supports various data types and operations, allowing users to flexibly query and manipulate monitoring data.

[0112] S15-2: The cloud monitoring backend aggregates the time series data of all time periods corresponding to the tenant based on the query statement.

[0113] In this embodiment, after the corresponding query statement is written in the cloud monitoring backend, the query statement is used to aggregate the time series data of all time periods of the tenant corresponding to the time series data.

[0114] S15-3: The cloud monitoring backend calculates the value of the monitoring indicator corresponding to the tenant based on the aggregated time-series data.

[0115] In this embodiment, the cloud monitoring backend calculates the values ​​of all monitoring metrics for the tenant based on the aggregated time-series data.

[0116] For example, the cloud platform calculates the physical leased line rate of the corresponding tenant based on the aggregated time-series data, and calculates the values ​​of indicators such as the number of bytes flowing in / out of the leased line gateway.

[0117] S16: The cloud monitoring backend pushes alarm information to users according to the preset threshold corresponding to the monitoring indicators and the preset alarm rules.

[0118] In this embodiment, the preset thresholds are pre-set critical values ​​for each monitoring indicator; values ​​below or above certain thresholds are considered abnormal. Alarm information is used to notify the user that the performance of a particular port has become abnormal.

[0119] In this embodiment, the cloud monitoring backend pushes alarm information to users based on preset thresholds corresponding to monitoring metrics and preset alarm rules. Specific steps include:

[0120] S16-1: If the value of the monitored indicator does not meet the preset threshold, generate the corresponding alarm information.

[0121] In this embodiment, if the value of the monitoring indicator does not meet the preset threshold, it indicates that the monitoring indicator has become abnormal, and a corresponding alarm message is generated.

[0122] For example, if the calculated physical leased line rate is lower than the preset minimum physical leased line rate, it indicates that the physical leased line rate is abnormal, and an alarm message "Legacy line rate too low" will be generated.

[0123] S16-2: If the alarm information conforms to the alarm rules, send the alarm information to the cloud monitoring console.

[0124] In this embodiment, the cloud monitoring console is a platform for managing the cloud platform. It can support viewing data from the cloud monitoring backend and viewing and managing the operating status of each device in the cloud network.

[0125] In this embodiment, if the alarm information conforms to the alarm rules, the alarm information is sent to the cloud monitoring console.

[0126] For example, if the alarm rule stipulates that the alarm information is sent immediately after it is generated, then the alarm information conforms to the alarm rule and is sent directly to the cloud monitoring console. If the alarm rule stipulates that the alarm is only triggered within a specified time, then check the current time. If it is within the specified time, then trigger the alarm; otherwise, do not trigger the alarm.

[0127] In this embodiment, the RemoteWrite protocol is used to retrieve, encapsulate, and push time-series data, enabling tenant-level monitoring and alarms. Alarm information can be pushed to users in real time, providing early warnings and timely detection of device faults within the private cloud network, facilitating management and maintenance.

[0128] In another embodiment of this application, the user can log in to the cloud monitoring console and create alarm rules on the alarm rules page. The list of alarm rules is shown below:

[0129] Table 1

[0130]

[0131] Users can flexibly set various alarm rules. After setting them, they can click to confirm and create alarm rules, which will then be applied to the cloud monitoring backend.

[0132] In another embodiment of this application, the method further includes:

[0133] S21: When the cloud monitoring backend receives an information viewing instruction, determine the tenant corresponding to the information viewing instruction.

[0134] In this embodiment, the information viewing command is a command issued by the user on the cloud monitoring console to view tenant information. The tenant information to be viewed includes information such as the physical leased line inflow / outflow rate, the number of bytes flowing in / out of the leased line gateway, and the port status of the tenant's switch.

[0135] In this embodiment, when the cloud monitoring backend receives an information viewing instruction, the corresponding tenant is determined based on the tenant information included in the information viewing instruction.

[0136] S22: The cloud monitoring backend sends the time-series data information corresponding to the tenant to the cloud monitoring console.

[0137] In this embodiment, after determining the switch corresponding to the tenant, the cloud monitoring backend sends the switch information corresponding to the switch to the cloud monitoring console. The user can view the physical leased line inflow / outflow rate, leased line gateway inflow / outflow byte count, and switch port status information corresponding to the switch on the cloud monitoring console.

[0138] In this embodiment, users can query the switch information corresponding to the tenant on the cloud monitoring console and observe the data transmission status on the cloud private line. This ensures that users can promptly identify the fault location when a fault occurs in the cloud private line data transmission, which is beneficial to the stable operation of the entire cloud network.

[0139] In another embodiment of this application, before the data transmission component associates the port timing data with the corresponding tenant information and service information, the method further includes:

[0140] S31: The data transmission component establishes a message queue of corresponding length according to the traffic volume of the port timing data.

[0141] In this embodiment, the message queue is a container for storing messages during message transmission.

[0142] In this embodiment, when the data transmission component receives port timing data, it can establish a message queue of corresponding length according to the traffic volume of the port timing data. When the traffic volume of the port timing data received by the data transmission component is large, a longer message queue can be established to store the port timing data and wait for processing of the port timing data. When the traffic volume of the port timing data received by the data transmission component is small, a shorter message queue can be established, thereby saving computing resources.

[0143] S32: The data transmission component creates a corresponding number of coroutines based on the length of the message queue.

[0144] In this embodiment, coroutines are similar to threads, but coroutines run in user space, which can greatly reduce the overhead of context switching. At the same time, the coroutine scheduler gradually schedules runnable coroutines into threads for execution and promptly schedules blocked coroutines out of threads, which can avoid frequent thread switching and achieve high concurrency with fewer threads. Multiple coroutines can run simultaneously to process data.

[0145] In this embodiment, the data transmission component creates a corresponding number of coroutines based on the length of the message queue. When the message queue is long, more coroutines are created, and when the message queue is short, fewer coroutines are created.

[0146] S33: The data transmission component puts the port timing data into the message queue.

[0147] In this embodiment, after the data transmission component has created the message queue and coroutine, it puts the port timing data into the message queue.

[0148] In this embodiment, Transfer supports custom message queue length and the number of coroutines, allowing for flexible scheduling based on the size of time-series traffic data. All components are deployed in a cluster, achieving overall high availability, improving data processing and transmission speed, and enhancing system operating efficiency.

[0149] refer to Figure 5 , Figure 5 This is a data display diagram that does not use data transmission components for processing. This diagram can only display traffic data on dedicated lines in chronological order. Figure 6 This is a diagram showing the effect of data processing by a data transmission component according to an embodiment of this application. Figure 6 As shown, after processing by the data transmission component, the trend of traffic rate change can be clearly understood.

[0150] refer to Figure 7 , Figure 7 This is a data transmission traffic interaction diagram proposed in an embodiment of this application, such as... Figure 7 As shown, each resource pool has one resource pool acquisition machine, which periodically reports data to the monitoring platform. The monitoring platform sends the data to the data forwarding component, which processes the data and then sends it to the cloud monitoring backend. After the cloud monitoring backend performs calculations on the data, the data can be queried through the cloud monitoring console, and alarms can also be configured through the cloud monitoring console.

[0151] refer to Figure 8 , Figure 8 This is a cloud network service logic diagram proposed in one embodiment of this application, such as... Figure 8 As shown, the resource pool in the business push layer sends monitoring data to the monitoring sub-resource pool. The monitoring sub-resource pool sets up tenant monitoring on the tenant side and operation and maintenance monitoring on the operation and maintenance side. Both are implemented based on the Prometheus system. After processing the port time series data of each tenant, it is sent to the cloud management layer by the data forwarding component. The cloud management layer stores it in the database. Users can view the corresponding data in the cloud management layer through monitoring requests.

[0152] In another embodiment of this application, the method can also be extended to support data consumption via Kafka. After associating tenant business data, a Kafka message subscription mechanism is provided to achieve protocol diversification. Users can subscribe to the information they need, obtain the corresponding information through the data transmission component, and view it on the cloud platform. By providing users with access to various information through diversified protocols, the user experience is enhanced.

[0153] Based on the same inventive concept, one embodiment of this application provides a data transmission alarm device. (Reference) Figure 9 , Figure 9 This is a schematic diagram of a data transmission alarm device 900 according to an embodiment of this application. Figure 9 As shown, the device includes:

[0154] The data acquisition module 901 is used by the resource pool acquisition machine to send port timing data of the switch to the monitoring platform at preset time intervals.

[0155] The first data sending module 902 is used by the monitoring platform to send the port timing data to the data transmission component;

[0156] The data association module 903 is used by the data transmission component to associate the port timing data with the corresponding tenant information and service information;

[0157] The second data sending module 904 is used by the data transmission component to send the port time-series data associated with the tenant information and the business information to the cloud monitoring backend.

[0158] The indicator calculation module 905 is used by the cloud monitoring backend to calculate the value of a preset monitoring indicator based on the port time series data;

[0159] The alarm module 906 is used by the cloud monitoring backend to push alarm information to users according to the preset threshold corresponding to the monitoring indicators and the preset alarm rules.

[0160] Optionally, the device further includes:

[0161] The switch determination module is used to determine the tenant corresponding to the information viewing instruction when the cloud monitoring backend receives the information viewing instruction;

[0162] The switch information sending module is used by the cloud monitoring backend to send the time-series data information corresponding to the tenant to the cloud monitoring console.

[0163] Optionally, the data acquisition module includes:

[0164] The data acquisition submodule is used by the resource pool acquisition machine to collect port time-series data from the switch at preset time intervals through a pre-configured gateway monitoring protocol.

[0165] The data sending submodule is used by the resource pool acquisition machine to send the port timing data to the monitoring platform.

[0166] Optionally, the data association module includes: a data determination submodule, used by the data transmission component to determine the tenant information and the service information corresponding to the port time series data based on the port information carried in the port time series data;

[0167] The data encapsulation submodule is used by the data transmission component to encapsulate the tenant information, the service information, and the port timing data into the same data packet.

[0168] Optionally, the device further includes:

[0169] The message queue establishment submodule is used by the data transmission component to establish a message queue of corresponding length according to the traffic volume of the port timing data.

[0170] The coroutine creation submodule is used by the data transmission component to create a corresponding number of coroutines based on the length of the message queue;

[0171] The data entry submodule is used by the data transmission component to put the port timing data into the message queue.

[0172] Optionally, the indicator calculation module includes:

[0173] The statement writing submodule is used by the cloud monitoring backend to write corresponding query statements based on the time-series data.

[0174] The data aggregation submodule is used by the cloud monitoring backend to aggregate the time series data of all time periods corresponding to the time series data of the tenant based on the query statement;

[0175] The indicator calculation submodule is used by the cloud monitoring backend to calculate the value of the monitoring indicator corresponding to the tenant based on the aggregated time-series data.

[0176] Optionally, the alarm module includes:

[0177] The alarm information generation submodule is used to generate corresponding alarm information when the value of the monitored indicator does not meet the preset threshold.

[0178] The alarm information sending submodule is used to send the alarm information to the cloud monitoring console when the alarm information meets the alarm rules.

[0179] Based on the same inventive concept, another embodiment of this application provides a readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the data transmission alarm method as described in any of the above embodiments of this application.

[0180] Based on the same inventive concept, another embodiment of this application provides an electronic device. Figure 10 This is a schematic diagram of an electronic device 1000 according to an embodiment of this application, including a memory 1002, a processor 1001, and a computer program stored in the memory and executable on the processor. When executed by the processor, the program implements the steps in the data transmission alarm method described in any of the above embodiments of this application.

[0181] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0182] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0183] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0184] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0185] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0186] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0187] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0188] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0189] The data transmission alarm method, apparatus, device, and storage medium provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A data transmission alarm method, characterized in that, The method includes: The resource pool acquisition unit sends port timing data of the switch to the monitoring platform at preset time intervals. The monitoring platform sends the port timing data to the data transmission component; The data transmission component associates the port timing data with the corresponding tenant information and service information; The data transmission component sends the port time-series data associated with the tenant information and the business information to the cloud monitoring backend. The cloud monitoring backend calculates the values ​​of preset monitoring indicators based on the port time-series data; The cloud monitoring backend pushes alarm information to users based on preset thresholds corresponding to the monitoring indicators and preset alarm rules.

2. The data transmission alarm method according to claim 1, characterized in that, The method further includes: Upon receiving an information viewing instruction in the cloud monitoring backend, the tenant corresponding to the information viewing instruction is determined. The cloud monitoring backend sends the time-series data information corresponding to the tenant to the cloud monitoring console.

3. The data transmission alarm method according to claim 1, characterized in that, The resource pool acquisition unit sends port timing data of the switch to the monitoring platform at preset time intervals, including: The resource pool acquisition machine collects port timing data from the switch every preset time interval through a pre-configured gateway monitoring protocol. The resource pool acquisition unit sends the port timing data to the monitoring platform.

4. The data transmission alarm method according to claim 1, characterized in that, The data transmission component associates the port timing data with the corresponding tenant information and service information, including: the data transmission component determines the tenant information and service information corresponding to the port timing data based on the port information carried in the port timing data; The data transmission component encapsulates the tenant information, the service information, and the port timing data into the same data packet.

5. The data transmission alarm method according to claim 1, characterized in that, Before the data transmission component associates the port timing data with the corresponding tenant information and service information, the method further includes: The data transmission component establishes a message queue of corresponding length based on the traffic volume of the port timing data; The data transmission component creates a corresponding number of coroutines based on the length of the message queue; The data transmission component places the port timing data into the message queue.

6. The data transmission alarm method according to claim 1, characterized in that, The cloud monitoring backend calculates the values ​​of preset monitoring metrics based on the port time-series data, including: The cloud monitoring backend writes corresponding query statements based on the time-series data; The cloud monitoring backend aggregates the time-series data of all time periods corresponding to the tenant based on the query statement; The cloud monitoring backend calculates the value of the monitoring metric corresponding to the tenant based on the aggregated time-series data.

7. The data transmission alarm method according to claim 1, characterized in that, The cloud monitoring backend pushes alarm information to users according to preset thresholds corresponding to the monitoring metrics and preset alarm rules, including: If the value of the monitored indicator does not meet the preset threshold, a corresponding alarm message is generated; If the alarm information conforms to the alarm rules, the alarm information will be sent to the cloud monitoring console.

8. A data transmission alarm device, characterized in that, The device includes: The data acquisition module is used by the resource pool acquisition machine to send port timing data of the switch to the monitoring platform at preset time intervals. The first data sending module is used by the monitoring platform to send the port timing data to the data transmission component; The data association module is used by the data transmission component to associate the port timing data with the corresponding tenant information and service information; The second data sending module is used by the data transmission component to send the port time-series data associated with the tenant information and the business information to the cloud monitoring backend; The indicator calculation module is used by the cloud monitoring backend to calculate the value of a preset monitoring indicator based on the port time series data; The alarm module is used by the cloud monitoring backend to push alarm information to users according to preset thresholds corresponding to the monitoring indicators and preset alarm rules.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 7.

Images