Intranet equipment monitoring method and device, extranet server and monitoring system

Abstract

The invention relates to the field of intranet equipment monitoring, in particular to an intranet equipment monitoring method and device, an extranet server and a monitoring system. The method comprises the following steps: placing at least one device capable of going out of the network in an intranet for deploying an frp client and a monitoring collector, deploying a public network server on the cloud for deploying an frp server and a prometheus, determining a first device capable of going out of the network and a corresponding public network access channel according to an acquisition target identifier after a data acquisition request is obtained, and further utilizing the prometheus to access the public network through the public network access channel, and pulling the target data corresponding to the acquisition target identifier from the expander, wherein the data acquisition mode is simple and the efficiency is high.

Description

Technical Field

[0001] The present application relates to the field of intranet device monitoring, and in particular to an intranet device monitoring method, device, external network server and monitoring system. Background Art

[0002] In the field of managed security services (MSS), operators often perform security operations on customer network security through the cloud security operation center platform. At this time, higher requirements are placed on the availability of the customer's local network alarm collection equipment, so it is necessary to monitor the availability of the customer's intranet security equipment.

[0003] In the related technology, an agent is manually built into each device. When a new device is added, it must be re-implemented locally. The agent of each device pushes data to the cloud so that the external network server can obtain the device data and then analyze the device availability. However, the data needs to be pushed to the cloud, and the data acquisition method is complicated and inefficient.

[0004] Therefore, the above problems have become problems that need to be solved urgently by those skilled in the art. Summary of the invention

[0005] The purpose of this application is to provide an intranet device monitoring method, device, external network server and monitoring system, which have a simple way of obtaining intranet data and high data acquisition efficiency.

[0006] In order to solve the above technical problems, in the first aspect, a method for monitoring an intranet device is provided, which is executed by an external network server, and prometheus and frp server are deployed on the external network server;

[0007] The method comprises:

[0008] Obtaining a data collection request carrying a collection target identifier, wherein the collection target corresponding to the collection target identifier is an intranet device;

[0009] Determine a first networkable device corresponding to the collection target identifier, wherein the first networkable device is set in an intranet, and an exporter and a frp client corresponding to the prometheus are deployed on the first networkable device, and the exporter can collect data of the collection target corresponding to the target identifier;

[0010] Determine a public network access channel corresponding to the first device that can go out of the Internet, the public network access channel is an access channel between the external network server and the first device that can go out of the Internet, and the public network access channel is constructed according to the frp server and the frpclient;

[0011] Prometheus is used to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel.

[0012] In a preferred example, the present application may be further configured as follows: the data collection request also includes a data service type;

[0013] Using prometheus through the public network access channel, the target data corresponding to the collection target identifier is pulled from the exporter, including:

[0014] Sending a data service type authorization request to the target Internet-accessible device through the public network access channel, so that the first Internet-accessible device can determine whether to authorize a service of the data service type;

[0015] After receiving the authorization information sent by the first network-accessible device,

[0016] Prometheus is used to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel, and the target data is the data corresponding to the data service type.

[0017] In a preferred example, the present application can be further configured as follows: the method further includes:

[0018] An adding request is received, wherein the adding request includes: identification information of the intranet device to be added;

[0019] Determine the first public network access channel corresponding to the intranet device to be added according to the identification information of the intranet device to be added;

[0020] Modify the configuration information of the prometheus according to the identification information of the intranet device to be added and the first public network access channel corresponding to the intranet device to be added.

[0021] In a preferred example, the present application can be further configured as follows: the method further includes:

[0022] A deletion request is received, wherein the deletion request includes: identification information of the intranet device to be deleted;

[0023] Determine the second public network access channel corresponding to the intranet device to be deleted according to the identification information of the intranet device to be deleted;

[0024] Modify the configuration information of the prometheus according to the identification information of the intranet device to be deleted and the second public network access channel corresponding to the intranet device to be deleted.

[0025] In a preferred example, the present application may be further configured as follows: before obtaining the data collection request carrying the collection target identifier, the following further includes:

[0026] Construct a public network access channel based on the frp server and frp client;

[0027] Obtain the address of exporte through the public network access channel;

[0028] Based on the exporter's address, modify the prometheus configuration information.

[0029] In a preferred example, the present application may be further configured as follows: after using prometheus through the public network access channel to pull the target data corresponding to the collection target identifier from the exporter, it also includes:

[0030] Performing equipment performance analysis on the target data to obtain analysis results;

[0031] Early warning confirmation is performed based on the analysis results so that an alert can be issued when it is determined that an early warning is needed.

[0032] In a preferred example, the present application may be further configured as follows: performing device performance analysis on the target data to obtain analysis results includes:

[0033] Obtain multiple historical data corresponding to the collection target identifier stored in the prometheus;

[0034] Determine whether the target data meets the preset safety data threshold and obtain a first result;

[0035] Analyze the data change trend according to multiple historical data and target data to predict whether the data in a future preset period meets the preset safety data threshold, and obtain a second result;

[0036] An analysis result is determined based on the first result and the second result.

[0037] In a second aspect, an intranet device monitoring device is provided, which is arranged on an external network server, and prometheus and frp server are deployed on the external network server;

[0038] The device comprises:

[0039] An acquisition module, used to acquire a data acquisition request carrying an acquisition target identifier, wherein the acquisition target corresponding to the acquisition target identifier is an intranet device;

[0040] A first determination module is used to determine a first networkable device corresponding to the collection target identifier, the first networkable device is set in the intranet, and an exporter and a frp client corresponding to the prometheus are deployed on the first networkable device, and the exporter can collect data of the collection target corresponding to the target identifier;

[0041] A second determining module is used to determine a public network access channel corresponding to the first device that can go out of the Internet, wherein the public network access channel is an access channel between the external network server and the first device that can go out of the Internet, and the public network access channel is constructed according to the frp server and the frp client;

[0042] The pulling module is used to use Prometheus to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel.

[0043] In a third aspect, an external network server is provided, comprising:

[0044] one or more processors;

[0045] Memory;

[0046] One or more applications, wherein one or more applications are stored in a memory and configured to be executed by one or more processors, and one or more programs are configured to: perform operations corresponding to the method shown in any possible implementation of the first aspect.

[0047] In a fourth aspect, an intranet device monitoring system is provided, comprising:

[0048] As in the external network server of the third aspect, prometheus and frpserver are deployed on the external network server;

[0049] At least one networkable device is set in the intranet, and an exporter and a frp client corresponding to the prometheus are deployed on the networkable device, and the exporter can collect data from the intranet device;

[0050] At least one intranet device is provided in the intranet.

[0051] In a fifth aspect, a computer-readable storage medium is provided, wherein the storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, at least one program, a code set or an instruction set is loaded by a processor and executes the steps of the method shown in any possible implementation method of the first aspect.

[0052] In a sixth aspect, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, operations corresponding to the method shown in any possible implementation manner in the first aspect are implemented.

[0053] In summary, the method of the present application includes at least one of the following beneficial technical effects:

[0054] This application places at least one network-capable device in the intranet for deploying the frp client and the monitoring collector exporter, and deploys a public network server on the cloud for deploying the frp server and prometheus. After receiving the data collection request, the first network-capable device and the corresponding public network access channel can be determined according to the collection target identifier, and then, prometheus is used to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel. The data acquisition method is simple and efficient.

[0055] The intranet equipment monitoring device, extranet server and monitoring system provided in this application also have the above-mentioned beneficial technical effects and will not be described in detail. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] In order to more clearly illustrate the embodiments of the present application or the technical solutions of the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0057] Figure 1 A schematic diagram of an application scenario of an intranet device monitoring method provided in an embodiment of the present application;

[0058] Figure 2 This is a flow chart of an intranet device monitoring method provided by an embodiment of the present application;

[0059] Figure 3 A schematic diagram of a connection relationship of a device provided in an embodiment of the present application;

[0060] Figure 4 A schematic diagram of a flow chart of an overall solution provided in an embodiment of the present application;

[0061] Figure 5 It is a structural diagram of an intranet device monitoring device provided in an embodiment of the present application;

[0062] Figure 6 It is a structural diagram of an external network server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] This specific embodiment is merely an explanation of the present application and is not a limitation of the present application. After reading this specification, those skilled in the art may make modifications to the present embodiment without any creative contribution as needed, but such modifications are protected by the patent law as long as they are within the scope of the claims of the present application.

[0064] It should be noted that in the optional embodiments of the present application, the object information and other related data involved, when the embodiments in the present application are applied to specific products or technologies, need to obtain the permission or consent of the object, and the collection, use and processing of the relevant data need to comply with the relevant laws, regulations and standards of the relevant countries and regions. In other words, if the embodiments of the present application involve data related to the object, it needs to be obtained with the authorization and consent of the object, the authorization and consent of the relevant departments, and in compliance with the relevant laws, regulations and standards of the country and region. If personal information is involved in the embodiments, the acquisition of all personal information needs to obtain the consent of the individual. If sensitive information is involved, the separate consent of the information subject needs to be obtained. The embodiments also need to be implemented with the authorization and consent of the object.

[0065] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0066] In addition, the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article, unless otherwise specified, generally means that the associated objects before and after are in an "or" relationship.

[0067] In order to better understand and illustrate the solutions of the embodiments of the present application, some technical terms involved in the embodiments of the present application are briefly explained below.

[0068] (1) Intranet penetration: Intranet devices can access the public network and actively establish a TCP (Transmission Control Protocol) duplex connection channel to the Internet through the intranet. At this time, they can access the intranet and obtain resources through the corresponding listening IP and port on the public network.

[0069] Frp (Fast Reverse Proxy): A software that implements intranet penetration technology. Through frp, users can expose intranet services to the public network in a safe and convenient way through nodes with public IPs, achieving remote access and management. frp consists of two parts: frpc (client) and frps (server). The server is usually deployed on a machine with a public IP, responsible for receiving and processing requests from the external network, and forwarding requests to the corresponding devices or services in the intranet according to the configuration. The client is deployed on the machine where the intranet service that needs to be penetrated is located, responsible for forwarding the traffic of the intranet service to the server, and receiving the response from the server.

[0070] In the embodiment of the present application, a public network access channel is constructed between the network-accessible device in the intranet and the external network server through the frp service to realize internal and external communication.

[0071] (2) Prometheus: A software for implementing operation and maintenance monitoring. Prometheus periodically captures the status of monitored components through the HTTP (HyperTextTransfer Protocol) protocol. These components need to provide an HTTP interface (exporter) to expose their monitoring data. Prometheus stores this data in a built-in time series database, which is optimized for time series data and supports efficient writing and query operations.

[0072] exporter: collector, where prometheus collects monitoring indicator data from the corresponding service by requesting the exporter program.

[0073] Of course, you can also view monitoring data through the Prometheus interface; when Prometheus triggers an alarm, the alarm information will be sent to the operation and maintenance personnel through the configured notification channel (such as email, SMS, etc.), so that appropriate measures can be taken according to the alarm information to solve the alarm problem.

[0074] In the embodiment of the present application, the information of the intranet device can be collected from the first outbound device through prometheus and exporter.

[0075] An intranet device monitoring method provided in an embodiment of the present application relates to the field of intranet data acquisition, and of course can also be the field of intranet data monitoring.

[0076] In order to better understand the solution provided by the embodiment of the present application, the solution is described below in conjunction with a specific application scenario.

[0077] Please refer to Figure 1 , Figure 1A schematic diagram of an application scenario of an intranet device monitoring method provided in an embodiment of the present application. The intranet device monitoring method can be applied to an intranet device monitoring system.

[0078] In some embodiments, the intranet device monitoring system includes:

[0079] The external network server has prometheus and frp server deployed on it;

[0080] At least one network-capable device is set up in the intranet. The exporter and frp client corresponding to prometheus are deployed on the network-capable device. The exporter can collect data from the intranet device.

[0081] At least one intranet device is provided in the intranet.

[0082] The embodiment of the present application provides a solution for monitoring intranet devices on the cloud based on intranet penetration. The principle of this application is to use frp, prometheus, and applications (applications corresponding to the monitoring method implemented on the external network server and applications deployed on the device that can be put out), place at least one device that can be put out of the network in the intranet, for deploying frpclient and monitoring collector exporter, and deploy a public network server on the cloud for deploying frp server. The collector address of the deployed intranet can be exposed on the public network through frp, so that prometheus can pull data. At this time, the prometheus configuration can be modified by the program on the cloud, and the monitoring information can be pulled from the intranet through the channel exposed by frp in the form of pull. Moreover, when a new device is added, it is only necessary to modify the prometheus configuration on the cloud, without changing the configuration of the intranet device, which greatly reduces the local engineering content.

[0083] The external network server may be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0084] Specifically, the external network server can obtain a data collection request carrying a collection target identifier, and the collection target corresponding to the collection target identifier is an intranet device; determine the first networkable device corresponding to the collection target identifier, the first networkable device is set in the intranet, and the first networkable device is deployed with an exporter and frpclient corresponding to prometheus, and the exporter can collect data of the collection target corresponding to the target identifier; determine the public network access channel corresponding to the first networkable device, the public network access channel is the access channel between the external network server and the first networkable device, and the public network access channel is constructed according to the frp server and the frp client; use prometheus to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel.

[0085] It is understandable that the above is only an example and is not limited to this embodiment.

[0086] The present application embodiment provides a method for monitoring an intranet device. Figure 2 As shown, the method includes:

[0087] S201, obtaining a data collection request carrying a collection target identifier, where the collection target corresponding to the collection target identifier is an intranet device;

[0088] The data collection request can be automatically initiated by an external network client or a spontaneous program set inside the external network server, and is intended to request the collection of data of the collection target corresponding to the collection target identifier.

[0089] The collection target ID is a unique identification ID corresponding to the collection target, which can be a number, a string, a UUID or an IP address. The collection target is an intranet device.

[0090] S202: Determine the first network-accessible device corresponding to the collection target identifier.

[0091] The first networkable device is set in the intranet, and an exporter and a frp client corresponding to prometheus are deployed on the first networkable device, and the exporter can collect data of a collection target corresponding to the target identifier;

[0092] The external network server can correspond to multiple Internet-enabled devices, and each Internet-enabled device can collect data from multiple internal network devices.

[0093] See also Figure 3 , Figure 3 A schematic diagram of the connection relationship of a device provided in an embodiment of the present application.

[0094] The outbound device 1 corresponds to the intranet device 1, intranet device 2, intranet device 3, and intranet device 4. That is, the data of intranet device 1, intranet device 2, intranet device 3, and intranet device 4 can be collected through the exporter corresponding to prometheus; the outbound device 2 corresponds to the intranet device 5, intranet device 6, and intranet device 7.

[0095] The external network server stores the correspondence information between the networkable devices and the internal network devices. Then, after obtaining the acquisition target identifier (a certain internal network device), the first networkable device corresponding to the acquisition target identifier can be determined based on the acquisition target identifier.

[0096] Furthermore, in order to ensure the reliability of the data, in one possible manner, there is redundancy in the intranet devices corresponding to the internet-accessible devices, and some important intranet devices can correspond to at least two internet-accessible devices at the same time. Then, the target data can be pulled for each internet-accessible device, and the consistency of at least two target devices can be verified. If there is inconsistency, it means that the data may be abnormal, and the target data can be further retrieved and verified again.

[0097] S203: Determine a public network access channel corresponding to the first Internet-accessible device.

[0098] The public network access channel is an access channel for the external network server and the first network-accessible device, and the public network access channel is constructed based on the frp server and the frp client;

[0099] The access channel for each network-accessible device is pre-established, and then the correspondence between multiple network-accessible devices and multiple access channels is stored, so that after the first network-accessible device is determined, the corresponding public network access channel can be determined through the correspondence.

[0100] The public network access channel is constructed based on the frp server and frp client, specifically creating the frp public network access channel of the exporter. Then, after the channel configuration is modified on the cloud's external network server, the local frp client configuration file can be modified after the network-accessible device monitors the modification, so that the cloud can add a public network-accessible intranet service channel.

[0101] S204. Use prometheus to access the public network channel and pull the target data corresponding to the collection target identifier from the exporter.

[0102] Since prometheus is set up on the external network server, and exporter is set up on the network-accessible device, after determining the public network access channel, prometheus can be used to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel.

[0103] Moreover, even as the number of devices increases, they only need to be added through the external network server in the cloud. Compared with the low efficiency, high labor cost and maintenance difficulty brought by the traditional agent deployment model, the embodiment of the present application reduces the local labor cost and has very little local engineering content, which greatly reduces the operation and maintenance costs caused by uncontrollable factors in the local environment.

[0104] It can be seen that in the embodiment of the present application, at least one network-capable device is placed in the intranet for deploying frpclient and monitoring collector exporter, and a public network server is deployed on the cloud for deploying frp server and prometheus. After obtaining the data collection request, the first network-capable device and the corresponding public network access channel can be determined according to the collection target identifier, and then, prometheus is used to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel. The data acquisition method is simple and efficient.

[0105] A possible implementation of the embodiment of the present application is that in order to ensure the security of intranet data, the embodiment of the present application can also be open only to a certain type of service. Specifically, the data collection request also includes the data service type;

[0106] S204. Use prometheus to access the public network channel to pull the target data corresponding to the collection target identifier from the exporter, including:

[0107] S2041. Sending a data service type authorization request to a target Internet-accessible device through a public network access channel, so that the first Internet-accessible device can determine whether to authorize a service of the data service type;

[0108] In the embodiment of the present application, the access control granularity can be refined to the dimension of IP+PORT, and the authorized data service type can be set for different public network access channels. Therefore, when it is necessary to pull data, an authorization request can be sent to the target network-accessible device to facilitate permission verification.

[0109] In one possible case, a fixed one or some data service types can be set as authorized types. In other cases, whether a data service type is an authorized type can also be determined based on the number and time of access. For example, when a data service type has not been accessed for a period of time exceeding a preset time threshold, it is determined that there is no authorization information and it is necessary to reapply for authorization authority, or when the number of accesses exceeds a preset number threshold, it is determined that there is no authorization information and it is necessary to reapply for authorization authority. Of course, there may be other ways, which are not limited in the embodiments of the present application, as long as they can achieve the purpose of the embodiments of the present application.

[0110] S2042. After receiving the authorization information sent by the first network-accessible device, use prometheus to access the public network channel to pull the target data corresponding to the collection target identifier from the exporter, where the target data is data corresponding to the data service type.

[0111] After receiving the authorization information sent by the first network-accessible device, indicating that it can be accessed, prometheus is used to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel. The target data is the data corresponding to the data service type.

[0112] It is understandable that the port number is a digital identifier of an application on a computer, which is used to distinguish different types of services running on the same computer. Each type of service is bound to a specific port number when it is started, and communication with the specific service can be carried out through the port number.

[0113] Generally, when the open granularity is IP, VPN (Virtual Private Network) can be used to control access rights. However, the access control granularity of the embodiment of the present application can be refined to the dimension of IP+PORT (port number), so VPN can only implement some scenarios. Of course, the firewall can also control the dimension of IP+PORT, but the firewall can manually add rules.

[0114] It can be seen that in the embodiment of the present application, when the data collection request also includes the data service type, it is necessary to first determine whether the target network-accessible device authorizes this type of service. Only after authorization can the target data be pulled from the exporter based on prometheus, and the access control granularity can be refined to the IP+PORT dimension to ensure the security of the intranet data.

[0115] In a possible implementation of the embodiment of the present application, the monitoring method further includes:

[0116] An adding request is received, the adding request including: identification information of the intranet device to be added;

[0117] Determine the first public network access channel corresponding to the intranet device to be added according to the identification information of the intranet device to be added;

[0118] Modify the configuration information of Prometheus according to the identification information of the intranet device to be added and the first public network access channel corresponding to the intranet device to be added.

[0119] Among them, when it is necessary to add an intranet device, it is pre-set that the exporter of the intranet device collects data from which network-accessible device. Therefore, it is only necessary to configure the first public network access channel to prometheus and add the identification information of the intranet device to be added to the prometheus monitoring configuration.

[0120] It can be seen that in the embodiment of the present application, when it is necessary to add an intranet device, the configuration information of prometheus can be modified through the cloud according to the identification information of the intranet device to be added and the first public network access channel corresponding to the intranet device to be added, so as to realize the addition of the device. Compared with the traditional mode of deploying agents, the local labor cost is reduced, and at the same time, the local engineering content is very small, which greatly reduces the operation and maintenance costs caused by uncontrollable factors in the local environment.

[0121] In a possible implementation of the embodiment of the present application, the monitoring method further includes:

[0122] A deletion request is received, the deletion request including: identification information of the intranet device to be deleted;

[0123] Determine the second public network access channel corresponding to the intranet device to be deleted according to the identification information of the intranet device to be deleted;

[0124] Modify the configuration information of Prometheus according to the identification information of the intranet device to be deleted and the second public network access channel corresponding to the intranet device to be deleted.

[0125] It can be seen that in the embodiment of the present application, when it is necessary to delete an intranet device, the configuration information of prometheus can be modified through the cloud according to the identification information of the intranet device to be deleted and the second public network access channel corresponding to the intranet device to be deleted, so as to achieve the deletion of the device, which is simple to operate and has low operation and maintenance costs.

[0126] It is understandable that the present application can also add and delete devices that can go out of the network. The specific process is similar to the addition and deletion of intranet devices, and will not be elaborated in the embodiments of the present application.

[0127] In a possible implementation manner of the embodiment of the present application, before obtaining the data collection request carrying the collection target identifier, the monitoring method further includes:

[0128] Build a public network access channel based on frp server and frp client;

[0129] Obtain the exporter's address through the public network access channel;

[0130] Based on the exporte address, modify the configuration information of prometheus.

[0131] It can be seen that in the embodiment of the present application, a public network access channel is constructed based on the frp server and the frp client; through the public network access channel, the address of exporte is exposed to facilitate the modification of the configuration information of prometheus, thereby realizing the establishment of the channel and the setting of monitoring.

[0132] In a possible implementation of the embodiment of the present application, after using Prometheus to access the channel through the public network to pull the target data corresponding to the collection target identifier from the exporter, the monitoring method further includes:

[0133] Perform equipment performance analysis on target data to obtain analysis results;

[0134] Early warning confirmation is performed based on the analysis results so that an alert can be issued when it is determined that an early warning is needed.

[0135] The target data refers to the specific data set to be analyzed, which comes from various information generated when the device is running, including but not limited to CPU usage, memory usage, disk IO, network traffic, etc., and is used to evaluate the running status and performance of the device. The analysis results include: abnormal and normal, no warning is required when normal, and a warning is required when abnormal.

[0136] It can be seen that in the embodiment of the present application, after obtaining the target data, equipment performance analysis can be performed, and early warning confirmation can be performed based on the analysis results. Once it is determined that an early warning is needed, an alert is immediately issued, ensuring the timely discovery of equipment performance problems, thereby ensuring the stable operation and efficient performance of the equipment.

[0137] Furthermore, in some embodiments, device performance analysis can be implemented in a variety of ways:

[0138] Optionally, based on the current target data and the corresponding threshold data of each dimension, determine whether there is abnormal dimension data. If there is any abnormal dimension data, the analysis result is determined to be abnormal; if all dimension data are normal, the analysis result is determined to be normal. Of course, the target data can also be visualized so that the operation and maintenance personnel can monitor the equipment status at all times.

[0139] Optionally, obtain multiple historical data corresponding to the collection target identifier stored in prometheus; determine whether the target data meets the preset safety data threshold to obtain a first result; analyze the data change trend based on the multiple historical data and the target data to predict whether the data in a preset time period in the future meets the preset safety data threshold to obtain a second result; determine the analysis result based on the first result and the second result, wherein as long as the first result and the second result are both normal, the analysis result is determined to be normal, otherwise they are both abnormal.

[0140] Among them, multiple historical data are historical data within a short period of time. Based on multiple historical data and target data, the data change trend can be determined. The change trend can be in the form of a polynomial, and then based on the polynomial prediction model, the data size of a preset time period in the future can be predicted. If the data of the preset time period in the future does not meet the preset safety data threshold, the second result is determined to be abnormal; otherwise, the second result is determined to be normal.

[0141] It can be seen that in the embodiment of the present application, by comparing the target data with the threshold, the first result of whether the current performance is abnormal is quickly obtained; multiple historical data and target data are used to jointly analyze the data change trend, and it is predicted whether the data in the future preset time period meets the preset safety data threshold, and the historical data is combined to predict the future performance trend to obtain the second result; the double verification method takes into account both the current actual situation and future development trends, making the analysis results more comprehensive.

[0142] Furthermore, an embodiment of the present application provides a computer program product, including a computer program, which implements the corresponding contents of the aforementioned method embodiment when the computer program is executed by a processor.

[0143] For the program product on the external network server, it is recorded as application A, see Figure 4 , Figure 4 A schematic diagram of a flow chart of an overall solution provided in an embodiment of the present application, specifically,

[0144] 1. Add a public network access channel for monitoring and collection on application A, and modify the configuration file of frp client through application B to create the public network access address of the collector;

[0145] 2. When adding an intranet device, configure the public network channel address to prometheus, and add the collection target to the prometheus monitoring configuration

[0146] 3. After prometheus is started, the configured collection job regularly collects corresponding device information through the public network channel, such as CPU, memory, disk and other indicators.

[0147] For example, application A obtains:

[0148] Task 1: target collects target ID 192.168.0.5 and collects target ID 192.168.3.6; determines the public network access channel replacement 10.11.0.4:9116.

[0149] Task 2: target collects the target identifier 172.16.155.3; determines the public network access channel replacement 10.11.0.5:9116.

[0150] Determine that Task 1 corresponds to device A (customer A) that can go online, and Task 2 corresponds to device B (customer B) that can go online;

[0151] For Task 1, access snmp_exporter through the public network access channel replacement10.11.0.4:9116 to obtain the target data of NGFAW192.168.0.5 and the target data of EDR 192.168.3.6.

[0152] For Task 2, access snmp_exporter through the public network access channel replacement10.11.0.5:9116 to obtain the target data of NGFAW172.16.155.3.

[0153] The following is an introduction to a device provided in an embodiment of the present application. The device described below and the method described above can be referenced to each other. The device 500 of this embodiment is set on an external network server, and prometheus and frp server are deployed on the external network server. Figure 5 , Figure 5 : is a structural diagram of an intranet device monitoring device provided in an embodiment of the present application, comprising:

[0154] An acquisition module 510 is used to acquire a data acquisition request carrying an acquisition target identifier, where the acquisition target corresponding to the acquisition target identifier is an intranet device;

[0155] The first determination module 520 is used to determine the first networkable device corresponding to the collection target identifier, the first networkable device is set in the intranet, and the first networkable device is deployed with an exporter and frpclient corresponding to prometheus, and the exporter can collect data of the collection target corresponding to the target identifier;

[0156] The second determining module 530 is used to determine a public network access channel corresponding to the first device that can go out of the Internet, where the public network access channel is an access channel between the external network server and the first device that can go out of the Internet, and the public network access channel is constructed according to the frp server and the frpclient;

[0157] The pulling module 540 is used to use Prometheus to access the public network channel and pull the target data corresponding to the collection target identifier from the exporter.

[0158] In one practicable manner, the data collection request further includes a data service type;

[0159] The pulling module 540 is used for:

[0160] Sending a data service type authorization request to a target Internet-accessible device through a public network access channel, so that the first Internet-accessible device can determine whether to authorize a service of the data service type;

[0161] After receiving the authorization information sent by the first network-accessible device, the target data corresponding to the collection target identifier is pulled from the exporter through the public network access channel using prometheus, where the target data is data corresponding to the data service type.

[0162] In one achievable manner, the apparatus 500 further includes:

[0163] Add modules for:

[0164] An adding request is received, the adding request including: identification information of the intranet device to be added;

[0165] Determine the first public network access channel corresponding to the intranet device to be added according to the identification information of the intranet device to be added;

[0166] Modify the configuration information of Prometheus according to the identification information of the intranet device to be added and the first public network access channel corresponding to the intranet device to be added.

[0167] In one achievable manner, the apparatus 500 further includes:

[0168] Remove modules for:

[0169] A deletion request is received, the deletion request including: identification information of the intranet device to be deleted;

[0170] Determine the second public network access channel corresponding to the intranet device to be deleted according to the identification information of the intranet device to be deleted;

[0171] Modify the configuration information of Prometheus according to the identification information of the intranet device to be deleted and the second public network access channel corresponding to the intranet device to be deleted.

[0172] In one achievable manner, the apparatus 500 further includes:

[0173] Pre-built module, used to: build public network access channel based on frp server and frp client;

[0174] Obtain the exporter's address through the public network access channel;

[0175] Based on the exporte address, modify the configuration information of prometheus.

[0176] In one achievable manner, the present invention further includes:

[0177] An analysis module is used to perform equipment performance analysis on target data and obtain analysis results;

[0178] The warning module is used to confirm the warning based on the analysis results, so as to issue a warning when it is determined that a warning is needed.

[0179] In one achievable manner, the analysis module is used to:

[0180] Get multiple historical data corresponding to the collection target identifier stored in prometheus;

[0181] Determine whether the target data meets the preset safety data threshold and obtain a first result;

[0182] Analyze the data change trend according to multiple historical data and target data to predict whether the data in a future preset period meets the preset safety data threshold, and obtain a second result;

[0183] An analysis result is determined based on the first result and the second result.

[0184] In the embodiment of the present application, an external network server is provided, such as Figure 6 As shown, Figure 6 The external network server 600 shown includes: a processor 601 and a memory 603. The processor 601 and the memory 603 are connected, such as through a bus 602. Optionally, the external network server 600 may also include a transceiver 604. It should be noted that in actual applications, the transceiver 604 is not limited to one, and the structure of the external network server 600 does not constitute a limitation on the embodiments of the present application.

[0185] Processor 601 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 601 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0186] The bus 602 may include a path to transmit information between the above components. The bus 602 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 602 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0187] The memory 603 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0188] The memory 603 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 601. The processor 601 is used to execute the application code stored in the memory 603 to implement the contents shown in the above method embodiment.

[0189] Figure 6 The external network server shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0190] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer can execute the corresponding content in the aforementioned method embodiment.

[0191] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0192] The above are only some implementation methods of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for monitoring intranet equipment, characterized in that: Executed by an external network server, on which prometheus and frp server are deployed; The method comprises: Obtaining a data collection request carrying a collection target identifier, wherein the collection target corresponding to the collection target identifier is an intranet device; Determine a first networkable device corresponding to the collection target identifier, wherein the first networkable device is set in an intranet, and an exporter and a frp client corresponding to the prometheus are deployed on the first networkable device, and the exporter can collect data of the collection target corresponding to the target identifier; Determine a public network access channel corresponding to the first Internet-accessible device, wherein the public network access channel is an access channel between the external network server and the first Internet-accessible device, and the public network access channel is constructed according to the frp server and the frpclient; Prometheus is used to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel.

2. The method according to claim 1, characterized in that The data collection request also includes a data service type; Using prometheus through the public network access channel, the target data corresponding to the collection target identifier is pulled from the exporter, including: Sending a data service type authorization request to the target Internet-accessible device through the public network access channel, so that the first Internet-accessible device can determine whether to authorize a service of the data service type; After receiving the authorization information sent by the first network-accessible device, the target data corresponding to the collection target identifier is pulled from the exporter using Prometheus through the public network access channel, where the target data is data corresponding to the data service type.

3. The method according to claim 1, characterized in that Also includes: An adding request is received, wherein the adding request includes: identification information of the intranet device to be added; Determine the first public network access channel corresponding to the intranet device to be added according to the identification information of the intranet device to be added; Modify the configuration information of the prometheus according to the identification information of the intranet device to be added and the first public network access channel corresponding to the intranet device to be added.

4. The method according to claim 1, characterized in that: Also includes: A deletion request is received, wherein the deletion request includes: identification information of the intranet device to be deleted; Determine the second public network access channel corresponding to the intranet device to be deleted according to the identification information of the intranet device to be deleted; Modify the configuration information of the prometheus according to the identification information of the intranet device to be deleted and the second public network access channel corresponding to the intranet device to be deleted.

5. The method according to claim 1, characterized in that Before obtaining the data collection request carrying the collection target identifier, it also includes: Construct a public network access channel based on the frp server and frp client; Obtain the address of exporte through the public network access channel; Based on the exporter's address, modify the prometheus configuration information.

6. The method according to claim 1, characterized in that After using prometheus to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel, it also includes: Performing equipment performance analysis on the target data to obtain analysis results; Early warning confirmation is performed based on the analysis results so that an alert can be issued when it is determined that an early warning is needed.

7. The method according to claim 6, characterized in that The performing of equipment performance analysis on the target data to obtain analysis results includes: Obtain multiple historical data corresponding to the collection target identifier stored in the prometheus; Determine whether the target data meets the preset safety data threshold and obtain a first result; Analyze the data change trend according to multiple historical data and target data to predict whether the data in a future preset period meets the preset safety data threshold, and obtain a second result; An analysis result is determined based on the first result and the second result.

8. An intranet device monitoring device, characterized in that: Set up on the external network server, on which prometheus and frp server are deployed; The device comprises: An acquisition module, used to acquire a data acquisition request carrying an acquisition target identifier, wherein the acquisition target corresponding to the acquisition target identifier is an intranet device; A first determination module is used to determine a first networkable device corresponding to the collection target identifier, the first networkable device is set in the intranet, and an exporter and a frp client corresponding to the prometheus are deployed on the first networkable device, and the exporter can collect data of the collection target corresponding to the target identifier; A second determining module is used to determine a public network access channel corresponding to the first device that can go out of the Internet, wherein the public network access channel is an access channel between the external network server and the first device that can go out of the Internet, and the public network access channel is constructed according to the frp server and the frp client; The pulling module is used to use Prometheus to pull the target data corresponding to the collection target identifier from the exporter through the public network access channel.

9. An external network server, characterized in that: include: one or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to: perform the steps of the method according to any one of claims 1 to 7.

10. An intranet device monitoring system, characterized in that: include: The external network server according to claim 9, wherein prometheus and frp server are deployed on the external network server; At least one networkable device is set in the intranet, and an exporter and a frp client corresponding to the prometheus are deployed on the networkable device, and the exporter can collect data from the intranet device; At least one intranet device is provided in the intranet.

Images