CN111404774A

CN111404774A - Data monitoring method, device, equipment and storage medium

Info

Publication number: CN111404774A
Application number: CN202010164408.8A
Authority: CN
Inventors: 何彬彬
Original assignee: Tencent Cloud Computing Beijing Co Ltd
Current assignee: Tencent Cloud Computing Beijing Co Ltd
Priority date: 2020-03-11
Filing date: 2020-03-11
Publication date: 2020-07-10
Anticipated expiration: 2040-03-11
Also published as: CN111404774B

Abstract

The embodiment of the application provides a data monitoring method, a device, equipment and a storage medium; the method comprises the following steps: determining a mother machine to be monitored in a cloud platform comprising at least one mother machine; determining a steamed stuffed bun delivering sub-machine in a steamed stuffed bun delivering state in a mother machine to be monitored; determining data packets sent from each packet sender to obtain a plurality of data packets; determining a data volume threshold value of each data packet which can be received by a destination gateway of the data packet according to a preset flow control rule; according to the data quantity threshold value of each destination gateway, sending a data packet belonging to the destination gateway in a plurality of data packets to the destination gateway; determining the total data volume of a plurality of data packets and the gateway data volume of the data packets received by each destination gateway; outputting total data volume and gateway data volume of each destination gateway; therefore, the data volume received by a single gateway is controllable, and the data volume is output to the tenant, so that the problem-occurring gateway can be checked and positioned.

Description

Data monitoring method, device, equipment and storage medium

Technical Field

The present application relates to the field of data processing, and in particular, to a data monitoring method, apparatus, device, and storage medium.

Background

In the related technology, a physical gateway device captures a network packet at a network outlet, and analyzes information based on time, Virtual local area network (V L AN), user, application, data flow direction and the like by using a Quality of Service (QoS) control technology and a traffic management policy in AN IP packet header to determine basic information of current traffic, so that, as the physical gateway device captures the network packet at the network outlet, when one gateway type is added, the scheme development, adaptation function and update performance requirements need to be performed once, the workload developed on a new gateway increases with the increase of the gateway type, and as all servers in a local area network share a certain amount of bandwidth, some servers occupy a larger bandwidth according to different services deployed on each server, thereby affecting the bandwidth usage of other servers.

Disclosure of Invention

The embodiment of the application provides a data monitoring method, a data monitoring device, a data monitoring equipment and a storage medium, wherein the data volume of a data packet sent from each submachine is collected, the control on the data volume is accurate to a single gateway, so that the data volume received by the single gateway is controllable, and the data volume is output to tenants, thereby being beneficial to the tenants to check and locate the gateways with problems.

The technical scheme of the embodiment of the application is realized as follows:

in a first aspect, an embodiment of the present application provides a data monitoring method, including: determining a mother machine to be monitored in a cloud platform comprising at least one mother machine; determining a steamed stuffed bun delivering machine in a steamed stuffed bun delivering state in the mother machine to be monitored; determining data packets sent from each packet sender to obtain a plurality of data packets; determining a data volume threshold value of each data packet which can be received by a destination gateway of the data packet according to a preset flow control rule; according to the data quantity threshold value of each destination gateway, sending the data packets belonging to the destination gateway in the plurality of data packets to the destination gateway; determining the total data volume of the plurality of data packets and the gateway data volume of the data packets received by each destination gateway; and outputting the total data volume and the gateway data volume of each destination gateway.

In a second aspect, an embodiment of the present application provides a data monitoring apparatus, including: the system comprises a first determining module, a monitoring module and a second determining module, wherein the first determining module is used for determining a mother machine to be monitored in a cloud platform comprising at least one mother machine; the second determining module is used for determining a steamed stuffed bun delivering machine in a steamed stuffed bun delivering state in the mother machine to be monitored; a first obtaining module, configured to determine a data packet sent from each packet sender to obtain the plurality of data packets; the third determining module is used for determining a data volume threshold value of each data packet, which can be received by the destination gateway of the data packet, according to a preset flow control rule; a first sending module, configured to send, to the destination gateway, a data packet belonging to the destination gateway among the multiple data packets according to a data amount threshold of each destination gateway; a fourth determining module, configured to determine a total data volume of the multiple data packets and a gateway data volume of a data packet received by each of the destination gateways; and the first output module is used for outputting the total data volume and the gateway data volume of each destination gateway.

In a third aspect, an embodiment of the present application provides a data monitoring device, including: a memory for storing executable instructions; and the processor is used for realizing the data monitoring method when executing the executable instructions stored in the memory.

In a fourth aspect, an embodiment of the present application provides a storage medium, which stores executable instructions for causing a processor to execute the method for monitoring data provided in the embodiment of the present application.

The embodiment of the application has the following beneficial effects: collecting the total amount of a plurality of data packets from the outlet of the master machine where each submachine is located; therefore, when a new gateway needs to be added, the data volume of the newly added gateway receiving packets can be counted by identifying different types of destination IP without adding new development workload; then, according to a flow control rule, sending a data packet belonging to each destination gateway in a plurality of data packets which do not exceed a data volume threshold to each destination gateway, so that the control on the data volume is accurate to a single gateway, and the data volume received by the single gateway is controllable; and finally, outputting the total data volume and the gateway data volume received by the target gateway, so that the data volume is output to the tenant, the change condition of the data volume is convenient to monitor, and the tenant is facilitated to investigate and locate the gateway with problems.

Drawings

FIG. 1 is a schematic diagram of an alternative architecture of a data monitoring system provided by an embodiment of the present application;

FIG. 2A is a schematic diagram of an alternative architecture of a data monitoring system according to an embodiment of the present application;

fig. 2B is a schematic structural diagram of a data monitoring system according to an embodiment of the present application;

fig. 3 is a schematic flow chart of an implementation of a data monitoring method provided in an embodiment of the present application;

fig. 4A is a schematic flow chart of another implementation of the data monitoring method according to the embodiment of the present application;

fig. 4B is a schematic flowchart of another implementation of the data monitoring method according to the embodiment of the present application;

FIG. 5 is a schematic diagram of an interface for changing data monitoring details according to an embodiment of the present application;

FIG. 6 is a schematic view of a load state interface provided by an embodiment of the present application;

fig. 7 is a graph illustrating real-time data change of each gateway traffic according to an embodiment of the present application;

FIG. 8 is a system framework diagram of data monitoring in an embodiment of the present application;

FIG. 9 is a display interface diagram of data monitoring details according to an embodiment of the present application;

FIG. 10 is a schematic diagram of an alternative architecture of a data monitoring system provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of an exemplary packet-sending process;

fig. 12 is a schematic diagram illustrating a flow of network card packet receiving according to an embodiment of the present application;

fig. 13 is a detailed schematic diagram of gateway data monitoring according to an embodiment of the present application.

Detailed Description

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the attached drawings, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

In the following description, references to the terms "first \ second \ third" are only to distinguish similar objects and do not denote a particular order, but rather the terms "first \ second \ third" are used to interchange specific orders or sequences, where appropriate, so as to enable the embodiments of the application described herein to be practiced in other than the order shown or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

Before further detailed description of the embodiments of the present application, terms and expressions referred to in the embodiments of the present application will be described, and the terms and expressions referred to in the embodiments of the present application will be used for the following explanation.

1) The Access Control list (Access Control L ist, AC L) is a set of user, group and mode items related to file, this file appoints authority for all possible user Identification (ID) or group ID combinations, AC L is used to limit network flow and improve network performance, and set bandwidth of upstream and downstream flow of port, AC L can customize bandwidth management of multiple applications, and avoid affecting overall performance of network due to waste of bandwidth resources.

2) A Virtual Private Network (VPN) is a Private Network established over a public Network to perform encrypted communication. The method has wide application in enterprise networks. The VPN gateway realizes remote access through encryption of the data packet and conversion of a data packet target address. A VPN may be implemented in a number of ways, including server, hardware, software, etc.

3) Flow control: the data monitoring is short, and the flow control technology is divided into two types: one is a traditional flow control mode, realizes data monitoring based on a source address, a destination address, a source port, a destination port and a protocol type through QoS modules of a router and a switch, and belongs to four-layer flow control; the other is an intelligent flow control mode, which realizes flow control based on an application layer through professional flow control equipment and belongs to seven-layer flow control.

4) The Private network (VPC) on the public Cloud platform is a logic isolation network space which can be defined by a tenant, is similar to a traditional network operated by a user in a data center, is hosted in the Private network of the public Cloud platform and is a service resource of the tenant on the public Cloud platform, comprises Cloud service resources such as a Cloud server, load balance and a Cloud database, and the tenant can completely master the Private network environment comprising definition network segment division, IP addresses, routing strategies and the like and can realize multilayer security protection through a network AC L, security groups and the like.

5) Gateway (Gateway), also called Gateway, protocol converter. The default gateway is on the network layer to realize network interconnection, and is the most complex network interconnection device, and is only used for two network interconnections with different high-level protocols. The gateway is also similar in structure to a router, except for the interconnect layer. The gateway can be used for interconnection of both wide area networks and local area networks.

6) The bandwidth sharing method is that an operator can allocate certain bandwidth resources to each rack by default, and then all servers in the rack share and use the bandwidth without paying attention to the specific bandwidth use condition of each server.

7) The Object Storage (COS) is a highly available, highly stable and highly safe Cloud Storage service provided by a public Cloud platform facing enterprises and individual developers. Tenants may place any number and form of unstructured data into the COS and implement the management and processing of the data therein. The COS supports a standard Restful API interface, so that a user can use the COS quickly, the charging is carried out according to the actual usage amount, and the lowest use limit is not generated.

8) Blockchain (Blockchain): an encrypted, chained transactional memory structure formed of blocks (blocks).

9) Block chain Network (Blockchain Network): the new block is incorporated into the set of a series of nodes of the block chain in a consensus manner.

In the related technology, a physical gateway device is mainly applied to AN internet outlet of AN enterprise or a campus network, and as internet traffic of all users passes through the internet outlet, intelligent traffic management based on conditions such as time, V L AN, users, application and data flow direction can be realized by monitoring network traffic, analyzing traffic behavior and setting a traffic management strategy, but a centralized gateway has the problems of performance bottleneck, single-point failure and the like, and cannot meet the performance pressure and stability requirements of a million-level network platform.

In view of the above technical problems, embodiments of the present application provide a data monitoring method, apparatus, device, and storage medium, where a plurality of data packets are obtained from an exit of a host, and then, according to a rule, a data packet belonging to a destination gateway is counted and sent to each destination gateway, where the data packet does not exceed a data volume threshold, so that each gateway receiving the data packet has a record of data volume coming in and going out, which is convenient for monitoring the destination gateway; and finally, outputting the total data volume and the gateway data volume received by the destination gateway, so that the data volume is output to the tenant, and the change condition of the data volume is conveniently monitored in a visual mode.

An exemplary application of the data monitoring device provided in the embodiments of the present application is described below, and the device provided in the embodiments of the present application may be implemented as various types of user devices such as a notebook computer, a tablet computer, a desktop computer, a set-top box, a mobile device (e.g., a mobile phone, a portable music player, a personal digital assistant, a dedicated messaging device, and a portable game device), and may also be implemented as a server. In the following, an exemplary application will be explained when the device is implemented as a device or a server.

Referring to fig. 1, fig. 1 is an optional architecture schematic diagram of a data monitoring system provided in an embodiment of the present application, and to implement supporting an exemplary application, first, a plurality of data packets sent by a plurality of slave machines are obtained from a master machine 11, then, a destination gateway of each data packet is determined, and then, a data packet that does not exceed a data volume threshold of a destination gateway 12 in data packets belonging to the destination gateway 12 is sent to the destination gateway 12; meanwhile, the data packet which does not exceed the data volume threshold of the destination gateway 13 in the data packets belonging to the destination gateway 13 is sent to the destination gateway 13; sending the data packets which do not exceed the data volume threshold of the destination gateway 14 from the data packets belonging to the destination gateway 14; in this way, the control on the data volume is accurate to a single gateway, so that the data volume received by the single gateway is controllable; finally, the total data volume and the gateway data volume received by the destination gateway are output on a display interface of the terminal 10, so that the data volume is visually presented to the tenant, the change situation of the data volume is conveniently monitored, and the tenant is facilitated to investigate and locate the gateway with problems.

Referring to fig. 2A, fig. 2A is another alternative architecture schematic diagram of the data monitoring system provided in the embodiment of the present application, including a blockchain network 20 (exemplarily showing a server 200 as a native node), a monitoring system 30 (exemplarily showing a device 300 belonging to the monitoring system 30 and a graphical interface 301 thereof), which are described below.

The blockchain network 20 is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block includes information of a batch of network transactions for verifying the validity (anti-counterfeiting) of the information and generating a next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.

The block chain underlying platform can comprise processing modules such as user management, basic service, intelligent contract and operation monitoring. The user management module is responsible for identity information management of all blockchain participants, and comprises public and private key generation maintenance (account management), key management, user real identity and blockchain address corresponding relation maintenance (authority management) and the like, and under the authorization condition, the user management module supervises and audits the transaction condition of certain real identities and provides rule configuration (wind control audit) of risk control; the basic service module is deployed on all block chain node equipment and used for verifying the validity of the service request, recording the service request to storage after consensus on the valid request is completed, for a new service request, the basic service firstly performs interface adaptation analysis and authentication processing (interface adaptation), then encrypts service information (consensus management) through a consensus algorithm, transmits the service information to a shared account (network communication) completely and consistently after encryption, and performs recording and storage; the intelligent contract module is responsible for registering and issuing contracts, triggering the contracts and executing the contracts, developers can define contract logics through a certain programming language, issue the contract logics to a block chain (contract registration), call keys or other event triggering and executing according to the logics of contract clauses, complete the contract logics and simultaneously provide the function of upgrading and canceling the contracts; the operation monitoring module is mainly responsible for deployment, configuration modification, contract setting, cloud adaptation in the product release process and visual output of real-time states in product operation, such as: alarm, monitoring network conditions, monitoring node equipment health status, and the like.

The platform product service layer provides basic capability and an implementation framework of typical application, and developers can complete block chain implementation of business logic based on the basic capability and the characteristics of the superposed business. The application service layer provides the application service based on the block chain scheme for the business participants to use.

The type of blockchain network 20 is flexible and may be, for example, any of a public chain, a private chain, or a federation chain. Taking a public link as an example, electronic devices such as user equipment and servers of any service entity can access the blockchain network 20 without authorization; taking a federation chain as an example, an electronic device (e.g., a device/server) under the jurisdiction of a service entity after obtaining authorization may access the blockchain network 20, and at this time, become a special type of node in the blockchain network 20, i.e., a client node.

Note that the client node may provide only functionality to support the initiation of transactions by the business entity (e.g., for uplink storage of data or querying of data on the chain), and may be implemented by default or selectively (e.g., depending on the specific business requirements of the business entity) for the functions of the native nodes of the blockchain network 20, such as the ranking function, consensus service, ledger function, etc., described below. Therefore, the data and the service processing logic of the service subject can be migrated to the blockchain network 20 to the maximum extent, and the credibility and traceability of the data and service processing process are realized through the blockchain network 20.

Blockchain network 20 receives a transaction submitted by a client node (e.g., device 300 shown in fig. 2A as belonging to monitoring system 30) from a business entity (e.g., monitoring system 30 shown in fig. 2A), executes the transaction to update or query the ledger, and displays various intermediate or final results of executing the transaction on a user interface of the device (e.g., graphical interface 301 of device 300).

An exemplary application of the blockchain network is described below by taking monitoring system access to the blockchain network to monitor data uplink as an example.

The device 300 of the monitoring system 30 accesses the blockchain network 20 to become a client node of the blockchain network 20. The device 300 acquires the transmitted data packets through the sensor, and then transmits the data packets belonging to each destination gateway among a plurality of data packets not exceeding the data volume threshold to each destination gateway; finally, the total data volume and the gateway data volume received by the single gateway are displayed, and the total data volume and the gateway data volume are transmitted to the server 200 in the block chain network 20 or stored in the device 300; in the case where the upload logic has been deployed to the device 300 or the user has performed an operation, the device 300 generates a transaction corresponding to the update operation/query operation according to the to-be-processed item/synchronization time query request, specifies an intelligent contract to be called to implement the update operation/query operation and parameters transferred to the intelligent contract in the transaction, and the transaction also carries a digital signature signed by the monitoring system 30 (for example, a digest of the transaction is encrypted by using a private key in a digital certificate of the monitoring system 30), and broadcasts the transaction to the blockchain network 20. The digital certificate can be obtained by registering the monitoring system 30 with the certificate authority 31.

A native node in the blockchain network 20, for example, the server 200 verifies a digital signature carried by the transaction when receiving the transaction, and after the verification of the digital signature is successful, it is determined whether the monitoring system 30 has a transaction right according to the identity of the monitoring system 30 carried in the transaction, and any verification judgment of the digital signature and the right verification will result in a transaction failure. After successful verification, the native node signs its own digital signature (e.g., by encrypting a digest of the transaction using the native node's private key) and continues to broadcast in the blockchain network 20.

After the node with the sorting function in the blockchain network 20 receives the transaction successfully verified, the transaction is filled into a new block and broadcasted to the node providing the consensus service in the blockchain network 20.

The nodes in the blockchain network 20 that provide the consensus service perform a consensus process on the new block to reach agreement, the nodes that provide the ledger function append the new block to the end of the blockchain, and perform the transaction in the new block: and displaying the total data volume of the collected sending packets and the gateway data volume of the collected receiving packets to a user in a visual mode. The resulting total data volume and the amount of gateway data and synchronization time for the packet may be displayed in the graphical interface 301 of the device 300.

The native node in the blockchain network 20 may read the target article set from the blockchain, and present the target article set on the monitoring page of the native node, and the native node may also monitor the gateway by using the total data amount stored in the blockchain and the gateway data amount.

In practical applications, different functions may be set for different native nodes of the blockchain network 20, for example, the server 200 is configured to have a data monitoring function and an accounting function, for example, the server monitors the amount of data packets sent by the master and the amount of data packets received by the gateway. For this situation, in the transaction process, the server 200 receives the recommendation request sent by the device 300, the server 200 is adopted to obtain the data packets sent by the master, and according to the flow control rule, the data packets belonging to each destination gateway in the multiple data packets which do not exceed the data volume threshold are sent to each destination gateway, and the total data volume and the gateway data volume received by the destination gateway are output; in this way, the control on the data volume is accurate to a single gateway, so that the data volume received by the single gateway is controllable; and the data volume is output to the tenants, so that the change condition of the data volume is convenient to monitor, and the tenants can conveniently check and locate the gateways with problems.

Referring to fig. 2B, fig. 2B is a schematic structural diagram of a data monitoring system according to an embodiment of the present application, and the apparatus 400 shown in fig. 2B includes: at least one processor 410, memory 450, at least one network interface 420, and a user interface 430. The various components in device 400 are coupled together by a bus system 440. It is understood that the bus system 440 is used to enable communications among the components. The bus system 440 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 440 in FIG. 2B.

The processor 410 may be an integrated circuit chip having signal processing capabilities such as a general purpose processor, a digital signal processor, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, etc., wherein the general purpose processor may be a microprocessor or any conventional processor, etc.

The user interface 430 includes one or more output devices 431, including one or more speakers and/or one or more visual displays, that enable the presentation of media content. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, in some examples, a keyboard, a mouse, a microphone, a touch screen display, a camera, other input buttons and controls.

The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard disk drives, optical disk drives, and the like. Memory 450 optionally includes one or more storage devices physically located remote from processor 410.

The memory 450 includes either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a Random Access Memory (RAM). The memory 450 described in embodiments herein is intended to comprise any suitable type of memory.

In some embodiments, memory 450 is capable of storing data, examples of which include programs, modules, and data structures, or a subset or superset thereof, to support various operations, as exemplified below.

An operating system 451, including system programs for handling various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and handling hardware-based tasks;

a network communication module 452 for communicating to other computing devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: bluetooth, wireless compatibility authentication, and Universal Serial Bus (USB), etc.;

a presentation module 453 for enabling presentation of information (e.g., user interfaces for operating peripherals and displaying content and information) via one or more output devices 431 (e.g., display screens, speakers, etc.) associated with user interface 430;

an input processing module 454 for detecting one or more user inputs or interactions from one of the one or more input devices 432 and translating the detected inputs or interactions.

In some embodiments, the apparatus provided in the embodiments of the present application may be implemented in software, and fig. 2B illustrates a data monitoring server 455 stored in the memory 450, which may be software in the form of programs and plug-ins, and includes the following software modules: a first determining module 4551, a second determining module 4552, a first obtaining module 4553, a third determining module 4554, a first sending module 4555, a fourth determining module 4556, and a first output module 4557; these modules are logical and thus may be combined or further split according to the functionality implemented. The functions of the respective modules will be explained below.

In other embodiments, the apparatus provided in the embodiments of the present Application may be implemented in hardware, and for example, the apparatus provided in the embodiments of the present Application may be a processor in the form of a hardware decoding processor, which is programmed to execute the data monitoring method provided in the embodiments of the present Application, for example, the processor in the form of the hardware decoding processor may employ one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable logic devices (Programmable Device L) devices, P L D), Complex Programmable logic devices (CP L D), Field Programmable Gate Arrays (FPGAs), or other electronic components.

The data monitoring method provided by the embodiment of the present application will be described in conjunction with exemplary applications and implementations of the device provided by the embodiment of the present application.

Referring to fig. 3, fig. 3 is a schematic flow chart of an implementation of a data monitoring method provided in an embodiment of the present application, and is described with reference to the steps shown in fig. 3.

Step S301, a master machine to be monitored is determined in a cloud platform comprising at least one master machine.

Here, the master machine may be a physical machine in the cloud platform, and the master machine includes a plurality of slave machines, for example, virtual machines; some of the plurality of submachine in the master machine to be monitored are in a packet sending state, namely, the submachine sends packets outwards, and some of the submachine are in a non-packet sending state.

Step S302, determining a steamed stuffed bun delivering machine in a steamed stuffed bun delivering state in the mother machine to be monitored.

Here, the master unit includes a plurality of slave units, some of the slave units are in the packet issuing state, and some of the slave units are not in the packet issuing state, that is, some of the slave units issue packets outward, and some of the slave units do not issue packets outward at the present time, and in step S321, the packet issuing slave unit that issues packets outward at the present time is determined.

In step S303, the data packets sent from each of the sub-transmitters are determined to obtain a plurality of data packets.

The data packets sent by the sub-machine in the packet sending state in the master machine to be monitored are determined to obtain a plurality of data packets, and the IP address of the sub-machine for sending the packets is recorded, so that the corresponding relation between the sub-machine for sending the packets and the sent data packets can be presented when the data volume is counted and analyzed. The data packets sent by each sub-machine for sending the packets and the IP addresses of the sub-machines are counted, the corresponding relation between the data packets and the IP addresses is recorded, the data packets are output on a display interface, the destination gateway of the data packets sent by the sub-machines for sending the packets is counted, therefore, the total amount of a plurality of data packets and the gateway data volume sent to the destination gateway are collected from the outlet of the main machine where each sub-machine is located, when a new gateway needs to be added, new development workload does not need to be added, and the data volume of the newly added gateway for receiving the packets can be counted only by identifying the destination IP of different types.

In the above step S302 and step S303, the packet sending data is collected and the packet sending data volume is counted on the master machine where the child machine sending the packets is located, and the sending and receiving conditions of the data volume are not collected centrally on the gateway, but the sending and receiving conditions of the data volume are collected on the physical machine where the child machine is located by adopting a distributed principle, so that the performance of the gateway is not affected, and the performance bottleneck pressure of a million-level cloud platform can be resisted.

Step S304, determining a data volume threshold value at which the destination gateway of each data packet can receive the data packet according to a preset flow control rule.

Here, the preset flow control rule is used to control the maximum amount of data that each gateway can receive. In some possible implementation manners, first, a destination gateway of each data packet is determined, and in a specific example, a source IP and a destination IP carried by each data packet are determined; wherein, the source IP identification sends the IP of the submachine of the data packet, and then, if the source IP is matched with the IP of the submachine of the data packet, the gateway matched with the target IP is determined as the target gateway; that is, if the IP of the packet transmitter actually sending the data packet is the same as the source IP carried by the data packet, it is reasonable to say that the data packet is sent by the packet transmitter, so that the gateway having the destination IP carried in the data packet can be used as the destination gateway; so that the transmission path of the packet matches the path set in the routing table. Then, setting the data volume threshold value to be less than or equal to the number of the maximum data volume set in the preset flow control rule; therefore, the data volume of the data packet received by the destination gateway can be ensured not to be overloaded, and the fluency of packet receiving of the destination gateway is ensured.

Step S305 is to transmit a packet belonging to the destination gateway among the plurality of packets to the destination gateway according to the data amount threshold for each destination gateway.

Here, before sending the data packet to the destination gateway, first determining whether the data packet carries a routing encapsulation packet, that is, step S305 may be implemented as follows: and if the plurality of data packets carry routing encapsulation messages, sending the data packets belonging to the destination gateway in the plurality of data packets to the destination gateway according to the data volume threshold of each destination gateway. In some possible implementation manners, whether a message field carried in a data packet includes a specific field is judged, and if the message field includes the specific field, it is determined that the data packet carries a routing encapsulation message, and in such a case, it is stated that the data packet can be sent to a gateway; and if the data packet does not carry the routing encapsulation message, the data packet is not sent. Then, a part of the data packets belonging to the destination gateway among the plurality of data packets, which is less than or equal to the data amount threshold of the destination gateway, is transmitted to the destination gateway. For example, if there are 1000 packets belonging to the destination gateway a in the plurality of packets, but the threshold of the data size of the destination gateway a is 800, the 1000 packets are sent to the destination gateway a according to the sending time sequence; thus, the data flow control function of each IP to gateway device is realized.

Step S306, determining the total data volume of the plurality of data packets and the gateway data volume of the data packets received by each destination gateway.

Here, the total data volume of the plurality of packets and the gateway data volume of the packet received by each destination gateway are counted, and at the same time, the IP address of each destination gateway is recorded to obtain the correspondence between the gateway data volume and the IP address of the destination gateway.

Step S307, the total data volume and the gateway data volume of each destination gateway are output.

The total data volume and the gateway data volume of each destination gateway are output on a display interface, so that the packet sending flow of the slave unit and the packet receiving flow of the gateway can be monitored, and the gateway with the problem can be quickly positioned.

In some possible implementation manners, the corresponding relationship between the IP address of the sub-machine for sending the packets and the data volume of the sub-machine for sending the packets, and the corresponding relationship between the IP address of the destination gateway and the gateway data volume of the destination gateway are output on a display interface, so that a tenant can more intuitively monitor the packet receiving condition of each gateway and the packet sending condition of each sub-machine.

In the embodiment of the application, a plurality of data packets which are sent out are obtained from a master computer, and the data packets which do not exceed the data volume threshold value are sent to each destination gateway according to the flow control rule, so that the data volume of a single gateway can be monitored; and finally, outputting the total data volume and the gateway data volume received by the target gateway on a display interface, so that the data volume is visualized, the change condition of the data volume is conveniently monitored, and the gateway with the problem can be quickly determined.

In some embodiments, in order to accurately set the data amount threshold of each gateway, step S304 may be implemented by:

step S331, obtaining an upper limit of a data amount of a packet that can be received by each destination gateway set in the specific flow control rule.

Here, an upper limit of the data amount per destination gateway is set in the specific flow control rule.

In step S332, the number equal to or less than the upper limit of the data amount is set as the data amount threshold.

Here, the data amount threshold may be adjusted at different times according to the gateway data amount of the destination gateway at the current time; for example, the gateway data volume of the destination gateway is large in three consecutive hours, and the data volume threshold value can be appropriately increased; alternatively, the data volume threshold is adjusted based on the type of service received by the destination gateway. For example, if the service type indicates that the amount of packets sent for the service is large, the data amount threshold may be adjusted appropriately.

In the embodiment of the application, a data volume threshold not greater than the upper limit of the data volume of each destination gateway is set, and the data volume threshold is adjusted according to the data volume of the actual packet receiving of the destination gateway, so that the destination gateway can smoothly receive packets, and the problems that the bandwidth is beyond expectation and the critical service bandwidth is preempted are solved.

In some embodiments, in order to implement storing information such as packet sending traffic of a statistical slave machine and packet receiving traffic of a gateway into an object storage product to expand storage capacity in parallel and transfer storage cost to a tenant, after step S306, the method further includes the following steps, as shown in fig. 4A, where fig. 4A is another implementation flow diagram of the data monitoring method provided in this embodiment, and the following description is made with reference to fig. 3:

step S401, determining the sub data amount of the data packet sent by each packet sending slave device to determine the total data amount and the gateway data amount of the data packet received by each destination gateway.

Here, the data volume of each sub-steamed stuffed bun, i.e. the sub-data volume, is counted, and the IP address of the sub-steamed stuffed bun maker is recorded, so as to obtain the corresponding relationship between the sub-data volume and the sub-steamed stuffed bun maker, i.e. the sub-data volume of each sub-steamed stuffed bun maker.

Step S402, storing each gateway data volume, a first corresponding relation between each gateway data volume and a destination gateway for receiving the gateway data volume, sub data volumes and a second corresponding relation between each sub data volume and a packet sending machine for sending the sub data volumes in a distributed manner in the cloud platform.

In some possible implementation manners, the gateway data volume, the corresponding relationship between each gateway data volume and the gateway, the sub-data volume, and the corresponding relationship between each sub-data volume and the steamed stuffed bun maker may be regarded as monitoring details, and the monitoring details are stored in the cloud platform in a distributed storage manner, for example, the monitoring details are stored by using an object storage product in the cloud platform, and certain storage, downloading, and management costs are collected from the object storage product, so that the storage capacity can be expanded in parallel, and the storage cost can be transferred to the tenant.

In some embodiments, in order to visually display the total statistical data amount and the gateway data amount so as to facilitate traffic monitoring and timely locate a gateway with a problem, after step S307, the method further includes the following steps, as shown in fig. 4B, where fig. 4B is a schematic flow chart of another implementation of the data monitoring method provided in this embodiment, and the following description is made with reference to fig. 3:

step S421, according to the gateway data volume of each destination gateway and the first corresponding relationship, drawing a first change curve for representing a change condition of the gateway data volume of the gateway in a preset time period.

Here, a first variation curve for representing the variation of the gateway data volume of the destination gateway within a preset time period is drawn according to the gateway data volume and the corresponding relationship between the gateway data volume and the destination gateway. The preset time period can be any time period, and can be a time period for drawing real-time change situations, change situations within 24 hours, change situations within several months and the like.

Step S422, according to the sub-data volume of each steamed stuffed bun making machine and the second corresponding relation, a second variation curve used for representing the variation condition of the sub-data volume of the steamed stuffed bun making machine in a preset time period is drawn.

And drawing a second variation curve for representing the variation condition of the sub-data quantity of the steamed stuffed bun maker in a preset time period according to the sub-data quantity and the corresponding relation between the sub-data quantity and the steamed stuffed bun maker. For example, the sub-data amount of the steamed stuffed bun maker changes within 24 hours.

Step S423, outputting the first variation curve and the second variation curve in the display interface.

Here, the change situation of the sub-data volume of the packet-sending machine in the preset time period and the change situation of the gateway data volume of the destination gateway in the preset time period are output on the display interface, so that the tenant can visually monitor the gateway data volume of the destination gateway and the sub-data volume of the packet-sending machine, and the gateway with problems can be quickly located.

In some embodiments, after the first variation curve and the second variation curve are presented on the display interface, a user may monitor details by viewing gateway data volume, sub-data volume, and the like at any point on the variation curves, and in some possible implementations, first, in response to a received viewing request, a viewing point to which the viewing request refers is determined on the first variation curve and the second variation curve; for example, when the user moves the mouse to a certain point on the first variation curve or the second variation curve to click, or the time spent at the certain point is longer than a certain time length, it is determined that a viewing request is input, and in response to the viewing request, a viewing point is determined. Then, at least the current gateway data volume and the current total data volume of the viewing point are displayed on the display interface. In a specific example, a user is prompted to click the bubble or pop-up box to view the monitoring details of the point in a manner of a bubble or pop-up box and the like on a display interface; or directly popping up the monitoring detail of the point; therefore, the gateway refined flow data on the public cloud platform is visualized, and the data flow control function from each IP to the gateway is realized.

In some embodiments, a flow control rule of the gateway may be formulated by the collected packet receiving data volume of the gateway and the packet sending data volume of the slave machine in the historical time period, so as to limit the flow rate of the gateway, which may be implemented by the following steps:

in a first step, the historical data volume of the data packets received by the gateway in a plurality of historical time periods is determined.

Here, a plurality of history periods are set, the duration of each history period may be the same or different, and the amount of history data received by the gateway in different periods is determined. In other embodiments, if the history period is 1, which may be a period in which the amount of history data of the packet received by the gateway is large, for example, the amount of history data of the packet received by the gateway is large between 14 and 16 points in a day, then the amount of history data received by the gateway in this period is determined by taking 14 to 16 points as a specific history period.

And secondly, determining a data volume threshold value of the gateway in each history period according to the history data volume in each history period and the upper limit of the data volume of the data packet which can be received by the gateway to which the history data volume belongs.

For example, 3 different history periods are set, and based on the historical data amount and the upper limit of the data amount in the 3 history periods, a data amount threshold of each history period in the 3 history periods is set for the gateway, so as to obtain 3 data amount thresholds, so that when the gateway receives a data packet, the data amount of the received data packet is controlled by using different data amount thresholds according to different periods, thereby ensuring that the gateway a can smoothly receive the data packet, and avoiding preempting the transmission bandwidth of other important services. For example, the historical data amount received by the gateway a from 14 to 16 points and the upper limit of the data amount that the gateway a can receive are determined, and the data amount threshold value that the gateway can receive the data packet is set.

And thirdly, formulating a preset flow control rule according to the data volume threshold value in each historical time interval and the historical time interval in which the data volume threshold value is positioned.

Here, one history period corresponds to one data amount threshold, but the data amount thresholds of different history periods may be the same or different; and formulating the preset flow control rule according to the historical data volume threshold and the historical time period corresponding to the historical data volume threshold, and recording the upper limit of the gateway in the flow control rule.

In some possible implementation manners, after the total data volume and the gateway data volume at the current time are counted, the preset flow control rule set at the previous time can be adjusted based on the total data volume and the gateway data volume at the current time, that is, the preset flow control rule is updated according to the total data volume at the current time and the gateway data volume of each destination gateway at the current time. For example, the total data volume at the current time is large, and the data volume of each destination gateway is small, and the data volume threshold of each gateway set in the preset flow control rule can be updated, so that smooth transmission between the master and the gateway can be ensured.

In the following, an exemplary application of the embodiment of the present application in a practical application scenario will be described, taking as an example that all servers of a gateway share a certain amount of bandwidth and share a shared bandwidth on a public cloud platform in a local area network.

The data monitoring method provided by the embodiment of the application can be applied to display, storage and flow control of refined monitoring data of the gateway equipment in the VPC, so that tenants can be helped to quickly locate and solve the problems of abnormal flow and flow preemption. Moreover, the data monitoring method provided by the embodiment of the application has the following functional characteristics:

a. and displaying refined monitoring data of the gateway equipment.

b. And storing refined monitoring data of the gateway equipment.

c. And fine flow control of the gateway equipment.

The data monitoring method provided by the embodiment of the application can support the display of various fine monitoring data of gateway equipment in a VPC on a public cloud platform; the data monitoring method provided by the embodiment of the application can be applied to products comprising: a peer-to-peer connection Network, a Network Address Translation (NAT) gateway, a private line gateway, a VPN gateway, etc. In the process of visually displaying the total data volume and the gateway data volume, a 'monitoring detail' switch is additionally started on a gateway monitoring detail display page; therefore, refined monitoring data on the gateway/shared bandwidth are displayed, and the problem of the gateway can be rapidly located by the tenant on the public cloud platform.

In some possible implementations, first, the "monitor details" switch may be set to not turn on by default.

Secondly, after the switch of the 'monitoring details' is turned on, the user moves (hover) to prompt in a frame: "monitoring detail display: after the monitoring detail is started, the refined flow control of all the intranet IP bandwidths and flow gateways flowing to the XXX from the start time is shown: the user can flow control data flowing from an IP to the XXX ".

Here, as shown in fig. 5, in the display interface 51, the range to which the data monitoring method is applicable is displayed: a private network 501, a subnet 502, a routing table 503, and an Internet connection 504, wherein the Internet connection 504 comprises: a public network gateway 541, a NAT gateway 542, a VPN connection 543, a peer connection 544, a private line gateway 545, etc. When the traffic condition of the NAT gateway needs to be checked, the NAT gateway 542 is clicked, a change curve of the NAT gateway 542 within a certain period of time is displayed on the display interface, for example, a change condition of 24 hours (real time, near 7 days, near 30 days, self-selection time, or the like may also be selected) is selected at the selection window 52 on the display interface 51, and a curve 505 is displayed, where the curve 505 indicates that, in the case where the gateway receiving the packet is the NAT gateway within 24 hours, the change conditions of the outgoing bandwidth 506, the incoming bandwidth 507, the outgoing traffic 508, the outgoing packet 509, the incoming packet 510, and the connection number 511 in the network are changed. When any point 521 is clicked to view the flow monitoring detail of the point, the monitoring detail 522 is displayed on the display interface, and the method comprises the following steps: IP address 523, instance ID524, instance name 525, egress bandwidth 526, ingress bandwidth 527, egress traffic 528, egress volume 529, ingress volume 530, number of connections 531, and upper bandwidth limit 532. In the display interface 51, the monitoring details may be searched by inputting "query IP, instance ID, instance name" query monitoring details, such as an input address IP, an instance ID, an instance name, etc., in the search box 53, for example, the obtained search result is: the IP address 523, the instance ID524, the instance name 525, the egress bandwidth 526, the ingress bandwidth 527, the egress traffic 528, the egress amount 529, the ingress amount 530, and the connection number 531 are respectively: 10.0.0.2, ins-0 o6k0zt2, dongyuan-cvm-01, 2.50, 0.16, 1088.20, 291, 263, 2404 and 100.

Again, after the "monitor details" switch is turned on, the table shown in table 1 is displayed in the display interface 51, and table 1 shows the data of the latest time by default.

TABLE 1 monitoring detail parameter table

Again, a loading state is shown, a loading interface 601 shown in fig. 6 is shown in the display interface 51, fig. 6 is a loading state interface schematic diagram provided in the embodiment of the present application, and as shown in fig. 6, in the loading interface 601, "loading data" 607 is displayed, and an IP address 602, an instance ID603, an instance name 604, an outgoing bandwidth 605, and an incoming bandwidth 606 of data to be loaded are displayed.

And thirdly, in a search box of the display interface, the monitoring detail search can be carried out by inputting an IP address, an instance ID, an instance name and the like.

Here, "none" is presented if the search has no results.

Again, the display results may be linked with user-selected metrics.

For example, when the user clicks a button corresponding to the bandwidth input, the bandwidth output, or the traffic output, corresponding content is displayed in the table shown in table 1.

And thirdly, when the mouse moves to a certain point on the curve, the mouse is prompted to click to check the monitoring detail, the time, the current index value and the like of the point in the form of bubbles.

Here, "click to view the monitoring details" is clicked to view, and the following table shows the real-time index data of each IP currently flowing to the gateway in a linked manner.

Finally, clicking the instance ID shows the history data of the IP stream to the gateway data, and shows some key information, such as: mean, peak, mean, selectable time window.

As shown in fig. 7, fig. 7 is a graph of real-time data change of traffic of each gateway in the embodiment of the present application, as can be seen from fig. 7, an abscissa of a curve 701 represents time, an ordinate represents data amount, the curve 701 represents real-time index data of each IP currently flowing to the gateway, and a time to be queried input by a user is: 2017-09-0910: 25-2017-09-0910: 25, as can be seen from the curve 701, in this period, the change situation of the inflow rate is as follows: latest value 590.00 kbit, average: 135.52M bits, Peak: 1.61G (arrival time 04-1821: 40); the change situation of the output flow is as follows: the latest value is as follows: 38.00 kbit, average, 135.58 mbit, and peak: if 1.61 gbit (time of arrival is 04-1821: 40), i.e. at time point 702 (around 19 days 1 month), the traffic reaches the peak, which indicates that the gateway's traffic access is maximum at this time, and reaches 1.61 giga (G), then the data volume threshold of the gateway at time point 702 can be adjusted appropriately by monitoring the curve 701. At block 703, it may be selected to view changes in data volume at different time granularities, such as selecting real-time, approximately 24 hours, approximately 7 days, approximately 15 days, approximately 30 days, or autonomously setting time.

Fig. 8 is a system framework diagram of data monitoring according to an embodiment of the present application, and as shown in fig. 8, refined monitoring data of a gateway device 801 is stored in an object storage 802 on a public cloud platform. The object store 802 charges for data storage, and the object storage service product performs operations such as charging 803, managing 804, and downloading 805 for data. The gateway device 801 may be one of the following: NAT gateway 811, VPN gateway 812, private line gateway 813, and the like; therefore, the monitoring detail data on each gateway/shared bandwidth is stored in the object storage commodity, and the monitoring data storage cost and the convenient tenant management historical data can be transferred.

Fig. 9 is a display interface diagram of a data monitoring detail according to an embodiment of the present application, and as shown in fig. 9, the monitoring detail 900 includes: the method comprises the following steps of IP address 901, instance ID902, instance name 903, outgoing bandwidth 904, incoming bandwidth 905, outgoing flow 906, outgoing packet amount 907, incoming packet amount 908, connection number 909 and bandwidth upper limit 910, wherein the default bandwidth upper limit is the maximum value of the gateway bandwidth, the bandwidth upper limit can be adjusted, the maximum value of the bandwidth (such as the data volume threshold of the gateway) can be modified by clicking a button 911, and as can be seen from FIG. 9, the monitoring of the flow is accurate to the flow control capability of the IP to the gateway device.

Fig. 10 is an alternative architecture schematic diagram of the data monitoring system according to the embodiment of the present application, and as shown in fig. 10, a plurality of mother machines, that is, mother machine 1 to mother machine N, are included on a public cloud platform. And the master machine 1 to the master machine N are used for outputting the service flow outwards.

The gateway service module 1001 is configured to receive normal traffic flows transmitted by the master 1 to the master N.

The gateway service module 1001 includes: NAT gateway 1002, VPN gateway 1003, public network gateway 1004, private line gateway 1005, cloud gateway 1006, and the like.

The flow statistic analysis module 1007 is configured to perform statistical analysis on the flow output by the master, for example, perform flow processing in multiple aspects as follows: IP flow statistics 1008, traffic aggregation 1009, and statistics dump 1010.

In some possible implementation manners, a process of the master machine outputting the service traffic is shown in fig. 11, where fig. 11 is a schematic diagram of a sub-machine packet sending flow according to the embodiment of the present application, and the following description is performed with reference to the steps shown in fig. 11:

in step S1201, the plurality of slave units in the master unit perform a distribution.

Here, the master machine is understood to be a physical machine, the slave machine is a virtual machine on the master machine, and a plurality of virtual machines in the master machine send out data packets, for example, 4 virtual machines in 6 virtual machines on the master machine send out data packets to a plurality of gateways.

Step S1202, a message of the sent data packet is acquired.

Step S1203, determining whether the message is encapsulated with a routing encapsulation message.

Here, if the sent packet is a routing encapsulation message, the process proceeds to step S1205, otherwise, the process proceeds to step S1204.

Step S1204, the data packet is not sent out.

Step S1205 determines whether the IP of the remotely connected network and the destination IP match the routing table.

Here, the destination IP denotes an IP of a destination gateway that receives the packet. If the IP of the remotely connected network and the destination IP match the routing table, step S1206 is entered, otherwise, flow statistics and control are not performed.

Step S1206, counting and controlling the data volume of the data packet sent by the subset.

Here, the packet sending flow of the slave units is counted and controlled, and it is counted which slave units send the data packets to which destination gateways.

In the embodiment of the application, centralized collection is not performed on the gateway, but a distributed principle is adopted, and collection is performed on a physical machine where the submachine is located, so that the flow of the submachine of the million-level network platform reaching a specific gateway N (VPN, private line, NAT gateway or other) through a subnet route is counted, a distributed collection mode is adopted, and the gateway centralized collection is not adopted, so that the performance bottleneck pressure of the million-level cloud platform can be resisted, and the system performance is not influenced.

In some possible implementation manners, a process of a network card receiving a service flow is shown in fig. 12, where fig. 12 is a schematic diagram of a network card receiving flow in an embodiment of the present application, and the following description is performed with reference to the steps shown in fig. 12:

step S1211, the network card receives the data packet sent by the slave device.

Step S1212, obtains the packet of the received data packet.

Step S1213, determine whether the message is encapsulated with a routing encapsulation message.

Here, if the outgoing packet is equipped with a routing encapsulation message, the process proceeds to step S1215, otherwise, the process proceeds to step S1214.

In step S1214, the packet is not received.

In step S1215, it is determined whether the outer source IP and the source IP match the routing table.

Here, the outer layer source IP is the IP of the previous gateway of the destination gateway in the process of sending the data packet from the slave machine to the destination gateway; if the outer layer source IP and the source IP match the routing table, step S1106 is entered, otherwise, the flow statistics and control are not performed.

Step S1216, counting and controlling the data amount of the data packet received by the network card.

Here, the packet receiving flow of the network card may be counted and controlled, and the data amount of the packet received by the gateway of the single IP or the gateway of the bulk IP may be counted.

In the embodiment of the application, by decoupling from the gateway type, although the performance of different gateway functions is complex, the capability does not need to be developed on a new gateway along with the increase of the gateway type, so that the flow control function on each gateway is refined, and the problems that the bandwidth of the gateway (or the shared bandwidth) is beyond expectation, the key service bandwidth is preempted and the like can be solved for tenants.

In the embodiment of the application, the statistics of the gateway N flow is performed in the submachine flow control module, and the statistics of the flow belonging to the gateway N is performed according to VPCIP, with the submachine IP and rmote IP as granularity, including an out latitude and an in latitude. By searching a special route (the function of the route comprises the acquisition of VPCIP, remote IP, CIDR, the access direction and a flow control rule), if the outer layer source IP and the source IP of a data packet received by the gateway match the matching rule of the outer layer source IP and the source IP set in a routing table, the packet receiving flow of the gateway is counted, if the gateway is set with bandwidth limitation, the gateway is monitored, and the counted data volume needs to be collected and analyzed through a monitor (monitor); when data volume statistics and control are carried out, whether a message needs to pass through the gateway or not is judged by an agent (agent) on the host; and when the message indicates that the data needs to pass through the gateway, carrying out data volume statistics and control. The judgment method is as follows: and judging whether the obtained remote IP and the remote IP are matched with a special route, if so, the message needs to pass through the gateway.

In the embodiment of the present application, details of monitoring gateway traffic are shown in fig. 13, and fig. 13 is a schematic diagram of gateway data monitoring details in the embodiment of the present application, and the following description is made:

gateway flow control detail 1300 includes: monitoring 1301, speed limit 1302 and performance 1303; wherein:

the monitoring 1301 includes: source 1311, destination gateway 1312, monitoring metrics 1313, and monitoring time 1314;

here, the source 1311 includes: a master 1315 and a VPC Gateway 1351(VPC Gateway, VPCGW), wherein the master 1315 includes: a core master 1316, a Data Plane Development Kit (DPDK) master 1317, a bare metal master 1318, and a low pass version master 1319; VPCGW1351 includes: a relational database 1320, and the like.

The destination gateway 1312 includes: NAT gateway 1321, peer gateway 1322, leased line gateway 1323, VPN gateway 1324, and Cloud Connect Network (CCN) gateway 1325.

The monitoring metrics 1313 include: an access bandwidth 1326 and an access packet volume 1327.

The monitoring time 1314 includes: granularity (e.g., 1 minute) 1328, latency (e.g., 1 second) 1329, and storage (e.g., 3 months) 1330.

The speed limit 1302 includes: a single IP speed limit 1331 and a bulk IP speed limit 1332.

Performance 1303 includes: capabilities of the 100W handset platform 1333 and capabilities of multiple types of gateways 1334 (e.g., more than 10 types of gateways).

In some embodiments, when gateway data monitoring is turned on, the interface design is as shown in table 2:

for example, an instruction to open the interface is given to the interface (for example, input parameters shown in table 2 and a code (EnableGatewayMonitor) to open the gateway monitoring).

Table 2 interface parameter design under open gateway data monitoring

In some embodiments, when the gateway data monitoring is turned off, the interface design is as shown in table 3, for example, an instruction to turn off the interface is given to the interface (for example, the parameters shown in table 3 and a code to turn off the gateway monitoring (DisableGatewayMonitor)) are input.

Table 3 interface parameter design under gateway data monitoring shutdown

In some embodiments, when querying whether the gateway enables data monitoring, the interface is designed as shown in table 4, for example, the interface is given an instruction to query whether the gateway enables data monitoring (for example, the parameters shown in table 4 and the code to query whether the gateway enables data monitoring are input).

Table 4 interface parameter design for inquiring whether gateway enables data monitoring

In the embodiment of the application, the variation situation of the acquired sent data volume and the received data volume is decoupled from the gateway type, and even if the functional performance of different gateways is complex, in the embodiment of the application, centralized acquisition is not performed on the gateway, but distributed principle is adopted, and the data is acquired on a physical machine where a sub machine is located, so that the performance bottleneck pressure of a million-level cloud platform can be resisted, and the performance of the gateway is not influenced; the acquired data volume is displayed on a million-level public cloud platform, so that the problem of a tenant on the public cloud platform on a gateway can be rapidly positioned; and the monitoring detail data on each gateway or shared bandwidth is stored in the object storage product, so that the monitoring data storage cost is transferred and the tenant management of historical data is facilitated. Therefore, the flow control function refined to each IP is provided, and the problems that the bandwidth of a gateway (or shared bandwidth) is beyond expectation, the bandwidth of a key service is preempted and the like can be solved.

Continuing with the exemplary structure of the data monitoring server 455 provided by the embodiments of the present application implemented as software modules, in some embodiments, as shown in fig. 2, the software modules stored in the data monitoring server 455 of the memory 440 may include:

a first determining module 4551, configured to determine a mother machine to be monitored in a cloud platform including at least one mother machine;

a second determining module 4552, configured to determine a steamed stuffed bun making machine in a steamed stuffed bun making state in the to-be-monitored mother machine;

a first obtaining module 4553, configured to determine the data packets sent from each of the sub-transmitters, so as to obtain the plurality of data packets;

a third determining module 4554, configured to determine, according to a preset flow control rule, a data amount threshold that a destination gateway of each data packet can receive the data packet;

a first sending module 4555, configured to send, to the destination gateway, a packet belonging to the destination gateway from the multiple packets according to a data amount threshold of each destination gateway;

a fourth determining module 4556, configured to determine a total data amount of the multiple packets, and a gateway data amount of a packet received by each of the destination gateways;

a first output module 4557, configured to output the total data volume and the gateway data volume of each of the destination gateways.

In some embodiments, the third determining module 4554 is further configured to: acquiring an upper limit of the data volume of the data packet which can be received by each destination gateway and is set in the preset flow control rule; the number equal to or less than the upper limit of the data amount is set as the data amount threshold.

In some embodiments, the third determining module 4554 is further configured to: determining a source internet protocol address and a destination internet protocol address carried by each of the plurality of data packets; and if the source internet protocol address is matched with the internet protocol address of the packet transmitter, determining the gateway matched with the target internet protocol address as a target gateway for receiving the data packet.

In some embodiments, the first sending module 4555 is further configured to: and if each data packet in the plurality of data packets carries a routing encapsulation message, sending the data packet belonging to the destination gateway in the plurality of data packets to the destination gateway according to the data volume threshold of each destination gateway.

In some embodiments, the first sending module 4555 is further configured to: determining the sub-data volume of the data packet sent by each packet sending machine so as to determine the total data volume; and storing each gateway data volume, each gateway data volume and a first corresponding relation of a destination gateway for receiving the gateway data volume, each sub data volume and a second corresponding relation of each sub data volume and a packet sending machine for sending the sub data volumes in a distributed manner in the cloud platform.

In some embodiments, the first output module 4557 is further configured to: according to the gateway data volume of each target gateway and the first corresponding relation, drawing a first change curve for representing the change condition of the gateway data volume of the gateway in a preset time period; drawing a second variation curve for representing the variation condition of the sub-data volume of the steamed stuffed bun making machine in the preset time period according to the sub-data volume of each steamed stuffed bun making machine and the second corresponding relation; and outputting the first variation curve and the second variation curve in a display interface.

In some embodiments, the first output module 4557 is further configured to: in response to a received viewing request, determining a viewing point pointed by the viewing request on the first variation curve and the second variation curve; and displaying at least the current gateway data volume and the current total data volume of the inspection point on the display interface.

In some embodiments, the third determining module 4554 is further configured to: determining the historical data volume of the data packets received by the gateway in a plurality of historical time periods; determining a data volume threshold value of the gateway in each historical time period according to the historical data volume in each historical time period and the upper limit of the data volume of the gateway to which the historical data volume belongs and capable of receiving data packets; and formulating the preset flow control rule according to the data volume threshold value in each historical time period and the historical time period in which the data volume threshold value is positioned.

In some embodiments, the first output module 4557 is further configured to: and updating the preset flow control rule according to the total data volume of the current moment and the gateway data volume of each target gateway of the current moment.

Embodiments of the present application provide a storage medium storing executable instructions, which when executed by a processor, will cause the processor to execute the method provided by the embodiments of the present application.

In some embodiments, the storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

In some embodiments, executable instructions may be written in any form of programming language (including compiled or interpreted languages), in the form of programs, software modules, scripts or code, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

By way of example, executable instructions may correspond, but do not necessarily correspond, to files in a file system, may be stored in a portion of a file that holds other programs or data, such as in one or more scripts stored in a hypertext Markup language (HTM L) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).

By way of example, executable instructions may be deployed to be executed on one in-vehicle computing device or on multiple computing devices located at one site or distributed across multiple sites and interconnected by a communication network.

To sum up, in the embodiment of the present application, a plurality of data packets sent out are obtained from a master, and then, according to a flow control rule, a data packet belonging to a destination gateway is sent to each destination gateway from among the plurality of data packets that do not exceed a data volume threshold, so that the control on the data volume is accurate to a single gateway, and the data volume received by the single gateway is controllable; and finally, outputting the total data volume and the gateway data volume received by the target gateway, so that the data volume is output to the tenant, the change condition of the data volume is convenient to monitor, and the tenant is facilitated to investigate and locate the gateway with problems.

The above description is only an example of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method for monitoring data, the method comprising:

determining a mother machine to be monitored in a cloud platform comprising at least one mother machine;

determining a steamed stuffed bun delivering machine in a steamed stuffed bun delivering state in the mother machine to be monitored;

determining data packets sent from each packet sender to obtain a plurality of data packets;

determining a data volume threshold value of each data packet which can be received by a destination gateway of the data packet according to a preset flow control rule;

according to the data quantity threshold value of each destination gateway, sending the data packets belonging to the destination gateway in the plurality of data packets to the destination gateway;

determining the total data volume of the plurality of data packets and the gateway data volume of the data packets received by each destination gateway;

and outputting the total data volume and the gateway data volume of each destination gateway.

2. The method according to claim 1, wherein the determining, according to a preset flow control rule, a threshold of a data amount that a destination gateway of each packet can receive the packet comprises:

acquiring the upper limit of the data volume of the data packet which can be received by each target gateway and is set in the preset flow control rule;

the number equal to or less than the upper limit of the data amount is set as the data amount threshold.

3. The method according to claim 1, wherein before the determining, according to the preset flow control rule, a threshold of a data amount that a destination gateway of each packet can receive the packet, the method further comprises:

determining a source internet protocol address and a destination internet protocol address carried by each of the plurality of data packets;

and if the source internet protocol address is matched with the internet protocol address of the packet transmitter, determining the gateway matched with the target internet protocol address as a target gateway for receiving the data packet.

4. The method of claim 1, wherein said sending the data packets belonging to the destination gateway among the plurality of data packets to the destination gateway according to the data amount threshold of each destination gateway comprises:

and if each data packet in the plurality of data packets carries a routing encapsulation message, sending the data packet belonging to the destination gateway in the plurality of data packets to the destination gateway according to the data volume threshold of each destination gateway.

5. The method of claim 1, wherein determining the total amount of data of the plurality of packets comprises: determining the sub-data volume of the data packet sent by each packet sending machine so as to determine the total data volume;

correspondingly, after the determining the total data amount of the plurality of data packets, the method further comprises:

and storing each gateway data volume, each gateway data volume and a first corresponding relation of a destination gateway for receiving the gateway data volume, each sub data volume and a second corresponding relation of each sub data volume and a packet sending machine for sending the sub data volumes in a distributed manner in the cloud platform.

6. The method of claim 5, wherein after said outputting the total data volume and the gateway data volume for each of the destination gateways, the method further comprises:

according to the gateway data volume of each target gateway and the first corresponding relation, drawing a first change curve for representing the change condition of the gateway data volume of the gateway in a preset time period;

drawing a second variation curve for representing the variation condition of the sub-data volume of the steamed stuffed bun making machine in the preset time period according to the sub-data volume of each steamed stuffed bun making machine and the second corresponding relation;

and outputting the first variation curve and the second variation curve in a display interface.

7. The method according to claim 1, wherein before the determining, according to the preset flow control rule, a threshold of a data amount that a destination gateway of each packet can receive the packet, the method further comprises:

determining the historical data volume of the data packets received by the gateway in a plurality of historical time periods;

determining a data volume threshold value of the gateway in each historical time period according to the historical data volume in each historical time period and the upper limit of the data volume of the gateway to which the historical data volume belongs and capable of receiving data packets;

and formulating the preset flow control rule according to the data volume threshold value in each historical time period and the historical time period in which the data volume threshold value is positioned.

8. A data monitoring apparatus, the apparatus comprising:

the system comprises a first determining module, a monitoring module and a second determining module, wherein the first determining module is used for determining a mother machine to be monitored in a cloud platform comprising at least one mother machine;

the second determining module is used for determining a steamed stuffed bun delivering machine in a steamed stuffed bun delivering state in the mother machine to be monitored;

a first obtaining module, configured to determine a data packet sent from each packet sender to obtain the plurality of data packets;

the third determining module is used for determining a data volume threshold value of each data packet, which can be received by the destination gateway of the data packet, according to a preset flow control rule;

a first sending module, configured to send, to the destination gateway, a data packet belonging to the destination gateway among the multiple data packets according to a data amount threshold of each destination gateway;

a fourth determining module, configured to determine a total data volume of the multiple data packets and a gateway data volume of a data packet received by each of the destination gateways;

and the first output module is used for outputting the total data volume and the gateway data volume of each destination gateway.

9. An apparatus for data monitoring, comprising:

a memory for storing executable instructions;

a processor for implementing the method of any one of claims 1 to 7 when executing executable instructions stored in the memory.

10. A storage medium having stored thereon executable instructions for causing a processor to perform the method of any one of claims 1 to 7 when executed.