CN111106970A

CN111106970A - Data monitoring method and device, electronic equipment and readable storage medium

Info

Publication number: CN111106970A
Application number: CN201911422003.3A
Authority: CN
Inventors: 许锋
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2020-05-05
Anticipated expiration: 2039-12-31
Also published as: CN111106970B

Abstract

The embodiment of the invention provides a data monitoring method and device, electronic equipment and a readable storage medium. The method comprises the following steps: receiving BGP route monitoring configuration information, wherein the monitoring configuration information comprises an identifier of a target BGP route to be monitored and monitoring parameters; acquiring relevant information of a target BGP route corresponding to the identifier based on the monitoring parameters; and sending the relevant information of the target BGP route to the route monitoring equipment so that the monitoring equipment displays the relevant information of the target BGP route. In the embodiment of the application, the BGP of the BGP control layer can be detected through the BGP route related information displayed by the monitoring equipment, manual detection is not needed, and the problems of manual 'misjudgment' and the like are reduced. Furthermore, because the relevant information of the target BGP route can be automatically acquired and sent to the route monitoring equipment, the time delay caused by manually acquiring data can be effectively reduced, and the processing efficiency is improved.

Description

Data monitoring method and device, electronic equipment and readable storage medium

Technical Field

The invention relates to the technical field of data processing, in particular to a data monitoring method and device, electronic equipment and a readable storage medium.

Background

The backbone network interconnection architecture adopts an IGP (Interior Gateway Protocol) + BGP (Border Gateway Protocol) model, and the IGP is responsible for the accessibility of network equipment and the selection of data transmission paths in a control network. BGP routing is used to distribute IP (Internet Protocol) routing information of network border nodes (endpoints) and to control service traffic border egress selection. For the egress scheduling of internet traffic, a BGP control plane is usually constructed by configuring BGP peers (neighbors) and BGP policies (policies) in all network devices of the whole network to process IP routing information, thereby fulfilling the requirements of service egress scheduling.

At present, OAM (Operations, Administration and Maintenance) of a BGP control plane can only be judged and analyzed by manually detecting BGP Peer and BGP Policy information of each network device in the BGP control plane, and then summarizing relevant information of all devices, so as to judge correctness of IP routing information distribution and control of the entire BGP control plane. However, the OAM manual detection in the BGP control plane may have problems of time delay, long troubleshooting time, and manual "misjudgment" in the detection process.

Disclosure of Invention

The present application aims to solve at least one of the above technical drawbacks.

In a first aspect, an embodiment of the present application provides a data monitoring method, where the method includes:

receiving BGP route monitoring configuration information, wherein the monitoring configuration information comprises an identifier of a target BGP route to be monitored and monitoring parameters;

acquiring relevant information of a target BGP route corresponding to the identifier based on the monitoring parameters;

and sending the relevant information of the target BGP route to the route monitoring equipment so that the monitoring equipment displays the relevant information of the target BGP route.

In an embodiment optional in the first aspect, based on the monitoring parameter, the obtaining, by the monitoring node, related information identifying a corresponding target BGP route includes at least one of:

acquiring relevant information corresponding to the monitoring parameters of the target BGP route in real time;

and when monitoring that the related network event of the target BGP route changes, acquiring related information of the target BGP route corresponding to the monitoring parameters.

In an optional embodiment of the first aspect, sending information related to the target BGP route to the route monitoring device includes:

generating route footprint data information of the target BGP route according to the related information of the target BGP route in a specified data format;

and packaging the routing footprint data information of the target BGP route according to a specified data packaging format and then sending the routing footprint data information to the route monitoring equipment.

In an optional embodiment of the first aspect, generating, according to a specified data format, route footprint data information of the target BGP route from the information related to the target BGP route, includes:

and generating the route footprint data information of the target BGP route according to the specified data format by using the relevant information of the target BGP route and the current timestamp.

In an alternative embodiment of the first aspect, the method is performed by a network device, and the related information includes at least one of the following information:

the information of the network equipment, the BGP Peer information corresponding to the target BGP route and the concrete content and route attribute information of the BGP Policy corresponding to the target BGP route.

In an optional embodiment of the first aspect, the method further comprises:

storing the related information of the target BGP route to a designated storage space;

wherein, if history related information of the target BGP route is stored in the storage space before storing the related information of the target BGP route, storing the related information of the target BGP route in the designated storage space, includes:

updating historical relevant information based on the obtained relevant information of the target BGP route to obtain updated relevant information of the target BGP route;

storing the updated related information of the target BGP route to a specified storage space;

sending the relevant information of the target BGP route to the route monitoring equipment, wherein the process comprises the following steps:

and sending the updated related information of the target BGP route to the route monitoring equipment.

In a second aspect, an embodiment of the present application provides a data monitoring method, where the method includes:

acquiring BGP route monitoring configuration information, wherein the BGP route monitoring configuration information comprises an identifier and monitoring parameters of a target BGP route to be monitored;

determining each network device to be monitored corresponding to the target BGP route according to the identifier of the target BGP route;

respectively sending BGP route monitoring configuration information to each network device to be monitored;

and receiving the relevant information of the target BGP route sent by each network device to be monitored, and displaying the relevant information.

In an alternative embodiment of the second aspect, the displaying the related information includes:

and generating a real-time routing footprint line graph of the target BGP routing according to the relevant information of the target BGP routing sent by each network device to be monitored, and displaying the real-time routing footprint line graph.

In an alternative embodiment of the second aspect, the method further comprises:

and comparing the real-time routing footprint line graph of the target BGP route with a pre-configured routing footprint line graph corresponding to the target BGP route, and sending alarm indication information when the real-time routing footprint line graph is different from the expected routing footprint line graph.

displaying relevant data that differs in the real-time route footprint line graph from the expected route footprint line graph.

In an alternative embodiment of the second aspect, the information related to the target BGP route is route footprint data information generated based on a route footprint data format.

In a third aspect, an embodiment of the present application provides a network device, including: a BGP Route data acquisition module and a RoFT (Route of FootPrinT, BGP Route FootPrinT) northbound interface module, wherein:

the BGP route data acquisition module is used for receiving BGP route monitoring configuration information, and the monitoring configuration information comprises an identifier of a target BGP route to be monitored and monitoring parameters; acquiring relevant information of a target BGP route corresponding to the identifier based on the monitoring parameters;

and the RoFT northbound interface module is used for sending the relevant information of the target BGP route to the route monitoring equipment so that the monitoring equipment can display the relevant information of the target BGP route.

In an optional embodiment of the third aspect, the BGP route data collection module includes a RoFT proxy module and a BGP module,

the RoFT agent module is used for receiving BGP route monitoring configuration information;

the BGP module is used for acquiring relevant information corresponding to the target BGP route and the monitoring parameters in real time;

wherein the RoFT agent module is further configured to:

and when monitoring that the related network event of the target BGP route changes, triggering the BGP module to acquire the related information of the target BGP route corresponding to the monitoring parameters.

In an optional embodiment of the third aspect, the network device further includes a RoFT route footprint database for storing information about the target BGP route.

In an embodiment of the third aspect, when sending the relevant information of the target BGP route to the route monitoring device, the RoFT northbound interface module is specifically configured to:

In an embodiment of the third aspect, when the information related to the target BGP route is generated into the route footprint data information of the target BGP route according to the specified data format, the RoFT northbound interface module is specifically configured to:

In an alternative embodiment of the third aspect, the method is performed by a network device, and the related information includes at least one of the following information:

In an alternative embodiment of the third aspect, the RoFT routing footprint database is further configured to:

before storing the related information of the target BGP route, if the historical related information of the target BGP route is stored in the storage space, updating the historical related information based on the acquired related information of the target BGP route to obtain the updated related information of the target BGP route; storing the updated related information of the target BGP route to a specified storage space;

the method for sending the relevant information of the target BGP route to the route monitoring device by the RoFT northbound interface module is specifically configured to:

In a fourth aspect, an embodiment of the present application provides a monitoring device, including: a configuration module, a RoFT data storage module, and a footprints visualization module, wherein:

the configuration module is used for acquiring BGP route monitoring configuration information, and the BGP route monitoring configuration information comprises an identifier and monitoring parameters of a target BGP route to be monitored; determining each network device to be monitored corresponding to the target BGP route according to the identifier of the target BGP route, and respectively sending BGP route monitoring configuration information to each network device to be monitored;

the RoFT data storage module is used for receiving relevant information of a target BGP route sent by each network device to be monitored;

and the footpath visualization module is used for displaying the relevant information of the target BGP route.

In an embodiment of the fourth optional aspect, when displaying the relevant information of the target BGP route, the footprint visualization module is specifically configured to:

In an optional embodiment of the fourth aspect, the monitoring device further includes a monitoring alarm module, specifically configured to:

In an alternative embodiment of the fourth aspect, the footprints visualization module method is further for:

In a fifth aspect, an embodiment of the present application provides an electronic device, including:

a processor; and a memory configured to store a computer program that, when executed by the processor, causes the processor to perform the method of any one of the first and second aspects.

In a sixth aspect, embodiments of the present application provide a computer-readable storage medium for storing a computer program, which, when run on a computer, enables the computer to perform the method of any one of the first and second aspects.

The technical scheme provided by the embodiment of the application has the following beneficial effects:

in this embodiment of the present application, the network device may automatically acquire relevant information of the target BGP route corresponding to the monitoring parameter based on the identifier of the target BGP route to be monitored and the monitoring parameter, which are sent by the monitoring device, and send the relevant information to the route monitoring device; correspondingly, after receiving the relevant information, the route monitoring device can display the relevant information of the BGP route to be monitored, and further, the worker can detect the BGP of the BGP control layer through the relevant information of the BGP route displayed by the monitoring device, so that the manual detection is not needed any more in the prior art, and the problems of manual 'misjudgment' and the like are reduced. Furthermore, because the network device can automatically acquire the relevant information of the target BGP route corresponding to the monitoring parameters and send the relevant information to the route monitoring device, the time delay caused by manually acquiring data can be effectively reduced, and the processing efficiency is further improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly described below.

Fig. 1 is a schematic flowchart of a data monitoring method according to an embodiment of the present application;

FIG. 2 is a schematic diagram of providing routing footprint data information according to an embodiment of the present application;

FIG. 3 is a schematic diagram of another route footprint data information provided in the embodiment of the present application;

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

fig. 5 is a graph illustrating a footprint of a target BGP route according to an embodiment of the present disclosure;

fig. 6 is a schematic diagram illustrating an architecture of a data monitoring system according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a RoFT controller according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 9 is a graph illustrating a footprint graph of a real-time route of multiple target BGP routes according to an embodiment of the present application;

fig. 10 is a schematic flow chart illustrating a target BGP route change according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a monitoring device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative only and should not be construed as limiting the invention.

As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.

The invention will be described and explained with reference to several terms:

the terms referred to in this application will first be introduced and explained:

DR (Datacenter Router ): data center public network flow convergence equipment.

PR (peer Router, operator interconnection Router): a public network traffic egress device;

TRR (IX Router Reflector, BGP route Reflector): is responsible for the delivery and control of BGP routes.

OAM (Operations, Administration and Maintenance): operation, administration and maintenance.

BGP Policy (BGP Policy): contains many items to match different BGP routes and modify related route attribute information.

RoFT (Route of FootPrinT, BGP routing FootPrinT): BGP route passes through BGP neighbor, BGP route strategy and route attribute change association record information in the transmission of backbone network and related equipment.

RoFT Controller: the route footprint controller is a route footprint information centralized data processing platform, and can restore the network footprint view of the BGP route in real time according to related information, so that end-to-end OAM detection and monitoring of a backbone network BGP control layer are realized.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 1 shows a schematic flow chart of a data monitoring method provided in an embodiment of the present application. The method is performed by a network device, as shown in fig. 1, and includes:

step S101, receiving monitoring configuration information of the BGP route, wherein the monitoring configuration information of the BGP route comprises an identifier of a target BGP route to be monitored and monitoring parameters.

The target BGP route refers to a BGP route to be monitored, the identifier of the BGP route is used to uniquely identify one BGP route, and the monitoring parameters refer to parameters that specifically need to monitor the BGP route, such as BGP peers that the monitoring BGP route passes through in each network device, specific contents of matched BGP Policy, and route attribute information.

In practical application, after determining which BGP route is to be specifically monitored, the monitoring device may determine a network device corresponding to the BGP route to be monitored (i.e., a target BGP route), and then may send an identifier of the BGP route to be monitored and monitoring parameters (i.e., BGP route monitoring configuration information) to each network device corresponding to the BGP route to be monitored.

Step S102, based on the monitoring parameters, obtaining the relevant information of the target BGP route corresponding to the identifier.

Correspondingly, for each network device, after the BGP route monitoring configuration information is obtained, it is known which BGP route needs to be monitored specifically according to the identifier of the BGP route to be monitored in the BGP route monitoring configuration information, and then, based on the monitoring parameter, relevant information of the target BGP route (i.e., the BGP route to be monitored) corresponding to the identifier is obtained.

In an embodiment of the present application, the related information may include at least one of the following information:

The information of the network device is used to identify which network device the currently passing network device is set as, for example, the information may be an identifier of the current network device; the BGP Peer information of the target BGP route corresponding to the network equipment is used for representing the BGP Peer information passed by the target BGP route when passing through the current network equipment; the specific content of the BGP Policy corresponding to the target BGP route refers to specific information included in the BGP Policy when the target BGP route passes through the current network device.

Step S103, sending the relevant information of the target BGP route to the route monitoring device, so that the monitoring device displays the relevant information of the target BGP route.

That is to say, after acquiring the BGP route monitoring configuration information, each network device may acquire, based on the monitoring parameters in the BGP route monitoring configuration information, information of the current network device, BGP Peer information of the target BGP route corresponding to the current network device, specific content of BGP Policy corresponding to the target BGP route, route attribute information, and other relevant information, and then send the acquired relevant information to the monitoring device, so that the monitoring device may display the relevant information of the target BGP route after receiving the relevant information sent by the network device.

In the embodiment of the application, the network device may automatically acquire the relevant information of the target BGP route corresponding to the monitoring parameter and send the information to the route monitoring device based on the identifier of the target BGP route to be monitored and the monitoring parameter, which are sent by the monitoring device, and thus, the problems of manual "misjudgment" and the like are reduced, unlike the case where manual detection is required in the prior art. Furthermore, because the network device can automatically acquire the relevant information of the target BGP route corresponding to the monitoring parameters and send the relevant information to the route monitoring device, the time delay caused by manually acquiring data can be effectively reduced, and the processing efficiency is further improved.

In the embodiment of the present application, based on the monitoring parameter, the information related to the target BGP route corresponding to the identifier is acquired, where the information includes at least one of the following:

In practical application, there are multiple ways for each network device to obtain the relevant information of the target BGP route corresponding to the identifier based on the monitoring parameter, and the embodiment of the present application is not limited. For example, the relevant information of the target BGP route corresponding to the monitoring parameter may be obtained in real time, or the relevant information of the target BGP route corresponding to the monitoring parameter may be obtained when a change of a relevant network event of the target BGP route is monitored.

When the manner of obtaining the relevant information is to obtain the relevant information in real time, it means that the network device needs to obtain the relevant information corresponding to the target BGP route and the monitoring parameter in real time, and at this time, the network device may be set to periodically obtain the relevant information based on a preset time interval. For example, the time interval may be set to be 1 hour, and after receiving the monitoring BGP route configuration information, the network device obtains the relevant information of the target BGP route corresponding to the monitoring parameter once every 1 hour interval.

Correspondingly, when the manner of acquiring the related information is to monitor that the related network event of the target BGP route changes, it means that the network device needs to constantly detect whether the related network event of the target BGP route changes, and when the related network event of the target BGP route changes, the related information of the target BGP route corresponding to the monitoring parameter is acquired. The network event related to the target BGP route may refer to a specific value or content of the monitoring parameter of the target BGP route. For example, when the monitoring parameter is BGP Policy, the network event associated with the target BGP route may refer to the specific content of the target BGP route relative to BGP Policy at the current network device. That is to say, the network device needs to constantly detect whether the specific content of the target BGP route changes relative to the BGP Policy of the current network device, and when detecting that the specific content of the BGP Policy changes, obtain the relevant information of the target BGP route corresponding to the monitoring parameter.

In this embodiment of the present application, sending information related to a target BGP route to a route monitoring device includes:

The route monitoring device here is the route monitoring device that sends the monitoring configuration information of the BGP route to the network device, and the specified data format may be configured in advance, which is not limited in this embodiment of the present application. For example, the specified data format may be a RoFT route data footprint format, and at this time, after acquiring the relevant information of the target BGP route, the network device may associate the relevant information according to the RoFT route data footprint format to obtain the route footprint data information of the target BGP route. At this time, the RoFT route footprint data information may clearly record the detailed processing process of the target BGP route in the BGP route control plane, such as which network devices the target BGP route passes through, which BGP peers exist when the target BGP route passes through each network device, the specific BGP Policy content, whether the route attribute has changed, and the like.

As an example, as shown in FIG. 2, the embodiment of the present application provides a schematic diagram of route footprint data information (i.e., route footprint in the diagram). The monitored BGP route in fig. 2 is the target BGP route in the embodiment of the present application, and the generated route footprint data represents network device information (i.e., node footprint information in the graph) in the related information by using Router-ID (Router identifier), which may specifically include one of a device ID, a device AS (Autonomous System) number, and a timestamp; representing BGP Peer information (namely device footprint information in a graph) of a target BGP route corresponding to current network equipment in the related information by using Peer ID (neighbor identification), wherein the BGP Peer information specifically comprises one of a device Peer-IP, an ID, a Peer-AS and a strategy type; and characterizing the concrete content of the BGP Policy corresponding to the target BGP route by adopting two items of Policy classification and Policy-ID. The device policy type in the policy classification may include one of an ingress direction policy, an egress direction policy, an ingress direction policy VPN (Virtual Private Network), an egress direction policy VPN, and a policy local import; the route attribute information in the generated route footprint data information represents the strong association route attribute before or after the policy, and may include: community, Local-Preference, Next-hop, and As-Path (Autonomous Syst Path, an Autonomous System dynamically interpreted programming language).

Further, after generating the route footprint data information of the target BGP route, the network device may package the route footprint data information of the target BGP route according to a specified data packaging format and send the package result to the route monitoring device through the data transmission interface. The specific format of the specified data encapsulation format may be configured in advance, and the embodiment of the present application is not limited.

In addition, in practical application, when the network device encapsulates the route footprint data information and sends the route footprint data information to the Monitoring device, the network device may support multiple internet data transmission protocols, for example, the internet data transmission protocols may include a BMP (BGP Monitoring Protocol), a gNMI telemeasuring (BGP-gNMI Telemetry) mode, a BGP-LS (BGP Link-state, BGP network topology collection) Protocol extension, and the like. In the embodiment of the present application, because each network device processes the associated information according to the standard RoFT routing footprint data format and encapsulates and transmits the associated information according to the uniform data encapsulation format, the processing differentiation of different vendor devices of the BGP routing control plane can be eliminated.

In the embodiment of the present application, generating route footprint data information of a target BGP route according to a specified data format from information related to the target BGP route, including:

In practical application, for the same monitoring parameter, the target BGP route may sometimes generate the same data at different times, and the obtained route footprint data information is also the same at this time. In order to distinguish such route footprint data information, in the embodiment of the present application, route footprint data information of the target BGP route may be generated according to a specified data format together with the current timestamp and the relevant information of the target BGP route, at this time, even though the relevant information of the target BGP route in the route footprint data information is the same, the timestamps are different, and at this time, different route footprint data information may be distinguished according to the timestamp of the route footprint data information.

As an example, as shown in fig. 3, the embodiment of the present application provides a specific example graph in the route footprint data information. Based on fig. 3, the route footprint data information is route footprint data information of BGP route a (10.0.0.0/16 in the backbone network), which includes Router-ID of 1.1.1.1, Peer ID of 192.1689.1.2, Policy classification of ingress direction, timestamp of Time-a, Policy ID of Policy-a/tem-B, and route attribute of a. It is understood that when BGP routes are of different types, there are different logical BGP control planes, the resulting route footprint lines are also different, and the different route footprint information may be distinguished by Router-ID, Peer ID, and policy classification (i.e., route footprint data unique identification). When the unique identifiers of the route footprint data are the same, the old and the new of the data can be distinguished through the timestamp, the strategy ID and the route attribute are the route attribute data strong association records before the BGP strategy and the BGP strategy are processed, and the specific process of the BGP equipment can be rapidly positioned.

In an embodiment of the present application, the method further includes:

wherein, if history related information of the target BGP route is stored in the storage space before the related information of the target BGP route is stored, storing the related information of the target BGP route in the designated storage space, including:

The specified storage space may refer to one storage space separately allocated to each target BGP route in the data repository (that is, each target BGP route corresponds to one storage space), or may refer to one storage space separately allocated to all target BGP routes in the data repository (that is, all target BGP routes correspond to one storage space), which is not limited in the embodiment of the present application.

In practical application, when the relevant information of the target BGP route is acquired, the relevant information of the target BGP route may be stored in the designated storage space, and before the relevant information of the target BGP route is stored in the designated storage space, it may be determined whether history relevant information of the target BGP route is stored in the storage space, and if the history relevant information of the BGP route is stored, the relevant information of the target BGP route is stored in the designated storage space and updated based on the acquired relevant information of the target BGP route to obtain updated relevant information of the target BGP route, and then the updated relevant information of the target BGP route is stored in the designated storage space.

The embodiment of the present application is not limited to the specific implementation manner of updating the history relevant information based on the obtained relevant information of the target BGP route. For example, the obtained relevant information of the target BGP route may be compared with historical relevant information, and different information in the historical relevant information and the relevant information to be currently stored is replaced with information in the relevant information to be currently stored, so as to obtain updated relevant information of the target BGP route; or deleting the history related information and directly storing the acquired related information of the target BGP route. Further, when the network device sends the relevant information of the target BGP route to the route monitoring device, the updated relevant information of the target BGP route may be sent to the route monitoring device.

Fig. 4 shows a flow chart of a data monitoring method provided in an embodiment of the present application. The method is executed by a monitoring device, as shown in fig. 4, and includes:

step S401, acquiring BGP route monitoring configuration information, where the BGP route monitoring configuration information includes an identifier and a monitoring parameter of a target BGP route to be monitored.

For the description of each information included in the BGP route monitoring configuration information, reference may be made to the description above, and details thereof are omitted here. The manner of obtaining BGP route monitoring configuration information may be configured in advance, and the embodiment of the present application is not limited, for example, the identifier and the monitoring parameter of the target BGP route may be configured in a preset storage location in advance, and when BGP route monitoring configuration information needs to be obtained, the BGP route monitoring configuration information is directly obtained.

Step S402, determining each network device to be monitored corresponding to the target BGP route according to the identification of the target BGP route.

Step S403, sending the BGP route monitoring configuration information to each network device to be monitored.

In practical applications, since the identifier of the target BGP route is used to uniquely identify one BGP route, it is known which BGP route (i.e., target BG route) needs to be monitored specifically when the identifier is known. Furthermore, because multiple network devices may exist on the footprint line of the same BGP route, after determining which BGP route needs to be monitored specifically, each network device that specifically exists on the target BGP route footprint line may be determined, and then BGP route monitoring configuration information is sent to each network device to be monitored, respectively. Correspondingly, after each network device receives the BGP route monitoring configuration information, each network device may obtain relevant information of the target BGP route based on the monitoring parameters in the BGP route monitoring configuration information, and send the relevant information to the route monitoring device.

Step S403, receiving the relevant information of the target BGP route sent by each network device to be monitored, and displaying the relevant information.

In practical application, the monitoring device may receive relevant information for the target BGP route, which is sent by each network device to be monitored, and then may display the relevant information for the target BGP route, so as to achieve a visual effect.

In an alternative embodiment of the present application, the information related to the target BGP route is route footprint data information generated based on a route footprint data format. That is to say, the monitoring device may receive route footprint data information of the target BGP route sent by each network device to be monitored, and the relationship between the relevant information about the target BGP route and the route footprint data information of the target BGP route may refer to the description above, which is not described herein again.

In an alternative embodiment of the present application, the displaying of the related information includes:

In practical application, in order to more conveniently and intuitively know the condition of each target BGP route, after obtaining the relevant information (i.e., route footprint data information) for the target BGP route sent by each network device to be monitored, a real-time route footprint line graph of the target BGP route may be generated according to the relevant information of the target BGP route, and the real-time route footprint line graph is displayed.

It should be noted that "real time" herein is a relative concept, because there is a corresponding time delay in the data transmission process, so "real time" in this embodiment of the present application refers to a period of time after receiving the relevant information for the target BGP route sent by each current network device to be monitored, and before receiving the next channel relevant information for the target BGP route sent by each network device to be monitored.

Because the relevant information of the target BGP route includes the identifier of the network device (i.e., Router-ID), the network device through which the target BGP route passes can be known according to the included identifier of the network device; correspondingly, when the real-time route footprint line graph of the target BGP route is determined, the relevant information of the target BGP route may be acquired, then the network device through which the target BGP route passes may be determined according to the identifier of the network device in the relevant information, and since the relevant information also carries the acquisition timestamp, the sequence of the network devices through which the target BGP route passes may be known according to the timestamp.

As an example, as shown in fig. 5, the embodiment of the present application provides a real-time routing footprint line graph of the target BGP route, where there are real-time routing footprint line graphs of the target BGP route (specifically, as shown in Prefix-a (40.1.0.0/16) and Aspath4809 in the graph, respectively shown by solid arrows and dashed arrows, and a start end and an end of each real-time routing footprint line graph are respectively network devices (e.g., DR, TRR, PR, etc. in the graph). Each real-time routing footprint line graph is generated based on the received related information of the target BGP route, for example, when the real-time routing footprint line graph represented by a solid arrow in the graph is determined, 4 pieces of related information 1 to 4 included in the target BGP route after passing through the operator network device (for example, the mobile trunk in fig. 5) may be acquired. Wherein the identifier of the network device included in the related information 1 is the identifier of the network device PR1, the identifier of the network device included in the related information 2 is the identifier of the network device TRR, the identifier of the network device included in the related information 3 is the identifier of the network device DR1, the identifier of the network device included in the related information 4 is the identifier of the network device DR2, and as is apparent from the time stamps included in the related information 1 to 4, the time at which the target BGP route passes through the network device PR1 is before the network device TRR, the time at which the target BGP route passes through the network device DR1 and the network device DR2 is after the network device TRR, the real-time route footprint of the target BGP route may now be determined to first pass through network device PR1 and network device TRR, and then by network device TRR to network device DR1 and network device DR2 (as particularly illustrated by the solid arrows implemented in fig. 5). In addition, in practical applications, when the real-time routing foot trace of the target BGP route is displayed, information included in the relevant information of the target BGP route may also be displayed, for example, information included in one of the relevant information is specifically MP-IPGP, PD:45090:4001, Policy: PE-out Node, and routing attribute D.

In an alternative embodiment of the present application, the method further comprises:

In practical application, the BGP control plane of the backbone network is a dynamic iterative system, and all BGP peers and BGP policies have relevance. Due to various scene requirements such as service requirements, network failures, network optimization, etc., the content of the BGP control layer needs to be adjusted frequently. At this time, it is necessary to determine whether the adjustment meets design expectations and to quickly locate the cause of the failure. At present, the BGP control health state is required to be inspected manually to judge whether the adjustment meets design expectations or not, and the fault cause is positioned quickly. However, this method takes a long time, resulting in low efficiency, and an erroneous determination may occur due to manual positioning of a location where a failure occurs.

Based on this, in the embodiment of the present application, after the BGP control layer adjusts the target BGP route, a route footprint line graph corresponding to the adjusted target BGP route may be configured in advance, then, relevant information corresponding to the adjusted target BGP route is obtained in real time, a real-time route footprint line graph is determined according to the obtained real-time relevant information, the real-time route footprint line graph is compared with an expected route footprint line graph, and when a difference is found, alarm indication information may be sent to inform a worker that a fault may exist in the current adjusted target BGP route. When the real-time routing footprint line graph and the expected routing footprint line graph are compared, the real-time routing footprint line graph and the expected routing footprint line graph can be subjected to Snapshot storage and then compared.

The specific representation form of the alarm indication sending information may be configured in advance, and the embodiment of the present application is not limited. For example, alarm indication information may be displayed or voice information may be transmitted, etc.

In practical application, in order to enable workers to better know specific fault reasons, different related data in the real-time routing footprint line graph and the pre-configured expected routing footprint line graph can be displayed, and the workers can further analyze the specific fault reasons according to the different related data displayed between the real-time routing footprint line graph and the pre-configured expected routing footprint line graph. Wherein, different related data can be shown by various modes such as diagrams.

In the embodiment of the application, the related information of different target BGP networks can be monitored, so that the change of the BGP routing caused by the network change can be rapidly monitored and managed.

In practical application, footprints of different types of BGP routes in an IP backbone network BGP control plane are different, and the RoFT SDN controller may present a corresponding BGP control plane view for each target BGP route.

The scheme provided by the embodiment of the application can be applied to various data monitoring scenes of the IP backbone network, such as a data monitoring scene of an operator backbone network, a data monitoring scene of an internet network backbone network, a data monitoring scene of an enterprise backbone network and the like. It can be understood that various IP backbone networks to which the scheme provided by the embodiment of the present application can be applied adopt IP routes of a BGP protocol bearer service, and BGP Peer and BGP policy are configured in all network devices of the entire network to build a BGP control layer to process IP routing information.

As shown in fig. 6, when the method provided in this embodiment is applied to a data monitoring scenario of the IP backbone network 200, each network device may form a RoFT data source layer C2 in fig. 6, and as can be seen from fig. 6, in this scenario, the network device may include an IGP (kind of Router), a DR, a TRR, a BR (Back Router), a PR, an ISP (internet service Provider), and the like, and data communication may be implemented based on a physical connection (specifically, as shown in fig. 6) among some network devices. In addition, the monitoring device in the embodiment of the present application may correspond to the RoFT data presentation layer C1 in fig. 6, and the monitoring device may specifically be a RoFT SDN controller 100. And as can be seen from fig. 6, roffsn controller 100 may include a configuration module 11, a footprints view module 12, and a monitoring alarm module 13 (and a RoFT data Storage module 14 (Storage 14 in the figure).

In practical application, the configuration module 11 may send monitoring configuration information of a BGP route to be monitored to each network device, and after each network device in the RoFT data source layer receives the monitoring configuration information of the BGP route, for each network device, route footprint data information of a target BGP route (for example, may include BGP Peer and BGP Policy in fig. 6) may be obtained and stored in a local RoFT route footprint database based on a monitoring parameter in the monitoring configuration information of the BGP route, and then the route footprint data information may be transmitted to the RoFT SDN controller in real time through a northbound API interface (for example, in fig. 6, a manner of automatically triggering and sending a packet in a standard RoFT route footprint format is used). Further, the RoFT data storage module 14 in the RoFT SDN controller receives and stores the route footprint data information sent by each network device, and the footprint view module 12 may obtain the route footprint data information of the target BGP route from the RoFT data storage module 14 (as shown in an area a in fig. 6), and generate a corresponding route footprint line graph display (as shown in an area B in fig. 6).

In addition, in practical applications, when the footprint view module 12 displays the route footprint line graph corresponding to the target BGP route, only the route footprint line graph of the selected target BGP route may be displayed through the footprint view module 12, or the route footprint line graphs of a plurality of target BGP routes may be simultaneously displayed through the footprint view module 12. For example, a route footprint line graph of multiple target BGP routes is presented within and concurrently with region B in FIG. 6.

Of course, in practical applications, in order to better know the state of the target BGP route, the information about the target BGP route may also be queried and displayed to the user through the foot trace view module 12. When the relevant information of the target BGP route is displayed to the user, the relevant information of the target BGP route and the corresponding route footprint line graph can be displayed in a correlated mode, and at the moment, the relation between the relevant information of the target BGP route and the corresponding route footprint line graph can be known more intuitively. For example, while the dashed arrow in fig. 6 represents the route footprint line graph of the target BGP route, the relevant information for generating the route footprint line graph is also simultaneously presented.

In order to better understand the method provided by the embodiments of the present application, the method is described in detail below with reference to specific implementation scenarios. In this example, as shown in fig. 7, the monitoring device may be a RoFT controller that includes a configuration module 31, a footprints visualizable module 33, a monitoring alert module 34, and a RoFT data storage module 32; as shown in fig. 8, each network device may include a northbound API interface module 45 (northbound API 45 in fig. 8), a RoFT proxy module 42 (RoFT Agent 42 in fig. 8), a management module 41, and a RoFT routing footprint database 44.

In practical application, as shown in ① in fig. 7, the configuration module 31 in the RoFT controller functions to send the BGP routes and the monitoring parameters (i.e., the monitoring configuration information of the BGP routes) to be monitored to each network device, accordingly, as shown in ① in fig. 8, the management module 41 included in each network device receives the BGP route monitoring configuration information sent by the RoFT controller (the RoFT controller management module 31 in fig. 8);

further, as shown in ② in fig. 8, the management module 41 transfers the monitoring configuration information of the BGP route to the roftfactor module 42, and the RoFT Agent module 42 allocates relevant resources to the target BGP route (i.e., the BGP route to be monitored) corresponding to the identifier in the monitoring configuration information of the BGP route and associates the relevant resources with the BGP module 43, the RoFT route footprint database 44, and the roftfothboudn API 45 to implement data synchronization of the memory resources.

Then, as shown in ③ in fig. 8, the raft Agent module 42 monitors relevant network events of the target BGP Route in real time, such as BGP Peer Up/Down, BGP Policy Add/Delete/modify, Route Update/Withdraw of the target BGP Route, and triggers the BGP module 43 to obtain relevant information of the target BGP Route when monitoring that the relevant events change.

Then, as shown in ④ in fig. 8, the BGP module 43 associates the relevant information of the target BGP route according to the format of the RoFT route footprint data, obtains the route footprint data information of the target BGP route, and stores the route footprint data information in the RoFT route footprint database 44.

Then, as shown in ⑤ in fig. 8, the RoFT route footprint database 44 stores the RoFT route footprint data information of all the target BGP routes, updates the RoFT route footprint data information of the target BGP routes according to the relevant network events, and pushes the updated RoFT route footprint data information to the RoFT NorthBound API 45 for transmission and encapsulation to the RoFT data storage module 32 (fig. 8 is the RoFT controller data collection module 32) in the RoFT controller.

The information of the network devices through which the monitored target BGP routes pass can be included in the RoFT route footprint data information, the target BGP routes correspond to BGP Peer information of the network devices, and the target BGP routes correspond to specific content of BGP Policy and route attribute information before and after Policy processing. In practical applications, the RoFT route footprint data information for different target BGP routes may be distinguished by the included data, and the BGP control plane of each target BGP route has its own view of the route footprint.

The RoFT route footprint data information of the same target BGP route in different network devices can be distinguished through Router-ID information; the same network equipment can generate a plurality of pieces of RoFT route footprint data information for the same target PBG route, and can realize the distinction through Peer-ID, strategy classification and strategy ID; in addition, the time stamp parameter is also defined in the RoFT routing footprint data information, and the time of each piece of RoFT routing footprint data information can be clearly recorded.

Finally, as shown at ⑥ in FIG. 8, the RoFT Northbound API 45 encapsulates the RoFT route footprint data information for the target BGP route and pushes it to the RoFT controller in real time.

Further, as shown in ② in fig. 7, the RoFT data storage module 32 in the RoFT controller receives the RoFT route footprint data information of the target BGP route received and transmitted by each network device.

Further, the RoFT data storage module 32 may store all the collected RoFT route footprint data information in a serialized manner in the included real-time data storage module, delete the currently received RoFT route footprint data information from the real-time data storage module after receiving the RoFT route footprint data information next time, and store the deleted information in the history data storage module. The historical data storage module stores all the RoFT routing footprint data information of the target BGP routing.

Still further, as shown at ③ in fig. 7, the footprint visualization module 33 may obtain the RoFT route footprint data information of the target BGP route from the RoFT data storage module 32, and draw and display a real-time route footprint graph of the target BGP route according to the RoFT route footprint data information, and may also display the information about the BGP Policy content and the route attribute included in each RoFT route footprint data information in real time, for example, as shown in fig. 9, it simultaneously displays the real-time route footprint graphs (as shown by the arrows and the dashed arrows in fig. 9) of a plurality of target BGP routes (the area a in fig. 9 is the specific information about the plurality of target BGP routes included), and also simultaneously displays the data content (as shown by the solid arrows or the solid arrows in fig. 9) specifically included in each relevant information about each target BGP route, so that the status of the target routes can be more intuitively known.

Further, in practical applications, the footprint visualization module 33 may further separately obtain relevant data of the BGP route that needs to be monitored from the RoFT data storage module 32, and when the RoFT data storage module 32 receives the latest relevant information of the BGP route that needs to be monitored, the footprint visualization module 33 may further perform real-time update and display on the currently displayed route footprint line graph, that is, display the latest route footprint line graph of the BGP route that needs to be monitored.

Further, in practical application, information of some BGP routes may be updated, and at this time, the monitoring alarm module 34 may be started, so that the fault location may be better located, which may be specifically shown in fig. 10.

Firstly, preparation before change can be made, as shown in a first stage in fig. 10, a V1.0 policy specification change, specifically, preparation before change, a real-time route footprint line graph of a target BGP route before change is collected, at this time, V2 change can be performed on partial information of the target BGP route, as shown in a second stage in fig. 10, 2.0 policy specification change, specifically, if a commu-attribute is newly added, a changed network device is changed into a matching policy entry (new and old matching conditions), the number of the matching policy entries is not changed, further, BGP routing monitoring configuration information of the target BGP route can be sent to a network device (in the figure) related to the target BGP route, RoFT routing data information sent by each network device is received, a real-time routing footprint line graph (in the figure, a real-time routing footprint view is generated) is generated, the real-time routing footprint line graph is compared with a set V2 changed expected routing line graph (in the figure, if the graph is a graph of the V2 change expected routing footprint line graph, and a change of the graph is generated, and if the graph shows that a change of the routing trace is identical to a change of the set route is correct, and a change of the target BGP route routing monitoring configuration information is correctly displayed, and if the change of the route trace of the route is not identical to a change route trace graph (a change route trace), a change route alarm module is correctly set), and if the change trace of the route is not correct route), a change route is set, the route trace of the route is set as a change route trace of the route is set when a change route trace of the route is correct route trace of the route, the route is correctly, the route is set when the route is not shown in the route, the route is correct route.

Further, a V3 change may be made to part of the information for the target BGP route, as shown in phase three in fig. 10: the specific implementation process of the change of the V3.0 policy specification may be the same as that of the V2 change of the partial information of the target BGP route, and specifically refer to the description of the V2 change of the partial information of the target BGP route, which is not described herein again.

An embodiment of the present application provides a network device, and as shown in fig. 11, the network device 60 may include: a BGP route data collection module 601 and a RoFT northbound interface module 602, wherein,

the BGP route data acquisition module 601 is configured to receive BGP route monitoring configuration information, where the monitoring configuration information includes an identifier of a target BGP route to be monitored and a monitoring parameter; acquiring relevant information of a target BGP route corresponding to the identifier based on the monitoring parameters;

the RoFT northbound interface module 602 is configured to send the relevant information of the target BGP route to the route monitoring device, so that the monitoring device displays the relevant information of the target BGP route.

In an alternative embodiment of the present application, the BGP route data collection module includes a RoFT proxy module and a BGP module,

wherein the RoFT agent module is further configured to:

In an optional embodiment of the present application, the network device further includes a RoFT route footprint database, configured to store information related to the target BGP route.

In an optional embodiment of the present application, when sending the relevant information of the target BGP route to the route monitoring device, the RoFT northbound interface module is specifically configured to:

In an optional embodiment of the present application, when the information related to the target BGP route is generated into the route footprint data information of the target BGP route according to the specified data format, the RoFT northbound interface module is specifically configured to:

In an optional embodiment of the present application, the method is performed by a network device, and the related information includes at least one of the following information:

the information of the network equipment, the BGP neighbor Peer information of the target BGP route corresponding to the network equipment, the concrete content of the BGP Policy corresponding to the target BGP route, and the route attribute information.

In an optional embodiment of the present application, the RoFT routing footprint database is further configured to:

The network device of the embodiment of the present application may execute the monitoring method provided by the embodiment of the present application, and the implementation principles thereof are similar, and are not described herein again.

An embodiment of the present application provides a monitoring device, as shown in fig. 12, where the monitoring device 70 may include: a configuration module 701, a RoFT data storage module 702, and a footprints visualization module 703, wherein,

a configuration module 701, configured to obtain BGP route monitoring configuration information, where the BGP route monitoring configuration information includes an identifier and a monitoring parameter of a target BGP route to be monitored; determining each network device to be monitored corresponding to the target BGP route according to the identifier of the target BGP route, and respectively sending BGP route monitoring configuration information to each network device to be monitored;

a RoFT data storage module 702, configured to receive relevant information of a target BGP route sent by each network device to be monitored;

and a footprint visualization module 703 for displaying information related to the target BGP route.

In an optional embodiment of the present application, when displaying the relevant information of the target BGP route, the footprint visualization module is specifically configured to:

In an optional embodiment of the present application, the monitoring device further includes an alarm module, specifically configured to:

In an alternative embodiment of the present application, the footprints visualization module method is further configured to:

The monitoring device of the embodiment of the present application can execute the monitoring method provided by the embodiment of the present application, and the implementation principles thereof are similar, and are not described herein again.

An embodiment of the present application provides an electronic device, as shown in fig. 13, an electronic device 2000 shown in fig. 13 includes: a processor 2001 and a memory 2003. Wherein the processor 2001 is coupled to a memory 2003, such as via a bus 2002. Optionally, the electronic device 2000 may also include a transceiver 2004. It should be noted that the transceiver 2004 is not limited to one in practical applications, and the structure of the electronic device 2000 is not limited to the embodiment of the present application.

The processor 2001 is applied to the embodiment of the present application, and is used to implement the functions of the modules shown in fig. 11 and 12.

The processor 2001 may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 2001 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs and microprocessors, and the like.

Bus 2002 may include a path that conveys information between the aforementioned components. The bus 2002 may be a PCI bus or an EISA bus, etc. The bus 2002 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 13, but this is not intended to represent only one bus or type of bus.

The memory 2003 may be, but is not limited to, ROM or other types of static storage devices that can store static information and computer programs, RAM or other types of dynamic storage devices that can store information and computer programs, EEPROM, CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store a desired computer program or in the form of a data structure and that can be accessed by a computer.

The memory 2003 is used for storing computer programs for executing the application programs of the present scheme and is controlled in execution by the processor 2001. The processor 2001 is used to execute a computer program of an application program stored in the memory 2003 to implement the actions of the network device and the monitoring device provided by the embodiments shown in fig. 11 and 12.

An embodiment of the present application provides an electronic device, where the electronic device includes: a processor; and a memory configured to store a machine computer program that, when executed by the processor, causes the processor to perform a data monitoring method.

Embodiments of the present application provide a computer-readable storage medium for storing a computer program thereon, which, when the computer program runs on a computer, enables the computer to execute a method for implementing data monitoring.

The terms and implementation principles related to a computer-readable storage medium in the present application may specifically refer to a data monitoring method in the embodiments of the present application, and are not described herein again.

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, several modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.

Claims

1. A method for monitoring data, comprising:

receiving monitoring configuration information of a Border Gateway Protocol (BGP) route, wherein the monitoring configuration information comprises an identifier of a target BGP route to be monitored and monitoring parameters;

based on the monitoring parameters, acquiring relevant information of a target BGP route corresponding to the identifier;

and sending the relevant information of the target BGP route to a route monitoring device so that the monitoring device displays the relevant information of the target BGP route.

2. The method according to claim 1, wherein said obtaining information about the target BGP route corresponding to the identifier based on the monitoring parameter includes at least one of:

and when monitoring that the relevant network event of the target BGP route changes, acquiring relevant information of the target BGP route corresponding to the monitoring parameters.

3. The method of claim 1, wherein sending information related to the target BGP route to a route monitoring device comprises:

generating route footprint data information of the target BGP route according to the related information of the target BGP route and a specified data format;

4. The method of claim 3, wherein the generating the route footprint data information of the target BGP route from the information related to the target BGP route according to a specified data format comprises:

and generating the routing footprint data information of the target BGP route according to the relevant information of the target BGP route and the current timestamp and a specified data format.

5. The method according to any of claims 1-4, wherein the method is performed by a network device, and wherein the related information comprises at least one of:

the information of the network equipment, the BGP neighbor Peer information of the target BGP route corresponding to the network equipment, the concrete content of BGP Policy corresponding to the target BGP route, and the route attribute information.

6. The method according to any one of claims 1-5, further comprising:

storing the relevant information of the target BGP route to a specified storage space;

wherein, if the history related information of the target BGP route is already stored in the storage space before storing the related information of the target BGP route, the storing the related information of the target BGP route in a specified storage space includes:

updating the historical relevant information based on the obtained relevant information of the target BGP route to obtain the updated relevant information of the target BGP route;

the sending the relevant information of the target BGP route to the route monitoring equipment comprises:

and sending the updated related information of the target BGP route to a route monitoring device.

7. A method for monitoring data, comprising:

respectively sending the BGP route monitoring configuration information to each network device to be monitored;

8. The method of claim 7, wherein the displaying of the related information comprises:

9. The method of claim 8, further comprising:

and comparing the real-time routing footprint line graph of the target BGP route with a pre-configured routing footprint line graph corresponding to the target BGP route, and sending alarm indication information when the real-time routing footprint line graph is determined to be different from the expected routing footprint line graph.

10. A network device comprising a border gateway protocol BGP route data collection module and a BGP route footprint RoFT northbound interface module, wherein:

and the RoFT northbound interface module is used for sending the relevant information of the target BGP route to route monitoring equipment so that the monitoring equipment can display the relevant information of the target BGP route.

11. The network device of claim 10, wherein the BGP route data collection module comprises a RoFT agent module and a BGP module,

the RoFT agent module is used for receiving the BGP route monitoring configuration information;

the BGP module is used for acquiring relevant information corresponding to the monitoring parameters of the target BGP route in real time;

wherein the RoFT agent module is further configured to:

and when monitoring that the relevant network event of the target BGP route changes, triggering the BGP module to acquire relevant information of the target BGP route corresponding to the monitoring parameters.

12. A monitoring device comprising a configuration module, a border gateway protocol BGP route footprint RoFT data storage module, and a footprint visualization module, wherein:

the configuration module is configured to obtain BGP route monitoring configuration information, where the BGP route monitoring configuration information includes an identifier and a monitoring parameter of a target BGP route to be monitored; determining each network device to be monitored corresponding to the target BGP route according to the identifier of the target BGP route, and respectively sending the BGP route monitoring configuration information to each network device to be monitored;

the RoFT data storage module is used for receiving the relevant information of the target BGP route sent by each network device to be monitored;

13. The monitoring device according to claim 12, further comprising a monitoring alarm module, specifically configured to:

14. An electronic device, comprising a processor and a memory:

the memory is configured to store a computer program which, when executed by the processor, causes the processor to perform the method of any of claims 1-9.

15. A computer-readable storage medium, for storing a computer program which, when run on a computer, causes the computer to perform the method of any of claims 1-9.