WO2021164179A1

WO2021164179A1 - Data monitoring method and apparatus

Info

Publication number: WO2021164179A1
Application number: PCT/CN2020/099562
Authority: WO
Inventors: 黄咏康
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-02-17
Filing date: 2020-06-30
Publication date: 2021-08-26
Also published as: CN111371841A; CN111371841B

Abstract

The present application relates to data monitoring and is applied to the field of big data. Disclosed are a data monitoring method and a related apparatus. The method is applied to the technical field of data monitoring, and comprises: searching for a feature value of a monitored device; in the case that the monitored device has the feature value, determining whether the monitored device is a mirror-copied device; in the case that the monitored device is not the mirror-copied device, confirming the monitored device as a registered device; obtaining an account priority corresponding to the monitored device; obtaining, according to a correspondence between the account priority and a data request threshold, a first data request threshold corresponding to the monitored device; and in the case that the number of data requests of the monitored device reaches the first data request threshold, rejecting the data request issued by the monitored device. The implementation of the present application can achieve management of all newly added devices on a platform and enhance the monitoring effect.

Description

Data monitoring method and device

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on February 17, 2020, the application number is 202010098060.7, and the invention title is "a data monitoring method and device", the entire content of which is incorporated into this application by reference .

Technical field

This application relates to the field of big data, and in particular to a data monitoring method and device.

Background technique

With the continuous development of cloud technology, the inventor realized that the cloud monitoring platform is widely used to manage the collected data sent by the monitored device, so as to achieve the purpose of unified management of multiple monitored devices.

In order to ensure the security of cloud monitoring platform products, existing cloud monitoring vendors usually can only manage specific brands of machines in the internal network. However, in actual use, users need to manage machines produced by different manufacturers, not just those produced by that manufacturer. The existing cloud monitoring platform products cannot adapt to the ever-increasing monitoring needs of users. In the process of use, there are problems such as the platform's inability to manage new equipment and the disconnection of equipment monitoring.

technical problem

In view of this, the embodiments of this application provide a data monitoring method and related equipment to solve the problem that the existing cloud monitoring platform products cannot meet the increasing monitoring needs of users. During the use process, there are platforms that cannot perform new equipment. Management, equipment monitoring and other problems.

Technical solutions

The embodiments of the present application provide a data monitoring method and device, which can incorporate different newly-added devices into the management scope of the platform, thereby improving the monitoring effect.

In the first aspect, an embodiment of the present application provides a data monitoring method. The above method includes: searching for the characteristic value of the monitored device; in the case that the monitored device has the above characteristic value, judging whether the monitored device is a mirror copy Device; In the case that the monitored device is not the mirror copy device, confirm that the monitored device is a registered device; obtain the account priority corresponding to the monitored device; according to the corresponding relationship between the account priority and the data request threshold Acquire the first data request threshold corresponding to the monitored device; in the case that the number of data requests of the monitored device reaches the first data request threshold, reject the data request sent by the monitored device.

In a second aspect, an embodiment of the present application provides a data monitoring device, which includes a module for executing the method of the first aspect.

In a third aspect, an embodiment of the present application provides a server, the server includes a processor and a memory, the processor and the memory are connected to each other, wherein the memory is used to store a computer program that supports the server to execute the above method, and The computer program includes program instructions, and the processor is configured to invoke the program instructions to execute the method of the first aspect described above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium that stores a computer program, and the computer program includes program instructions that, when executed by a processor, cause all The processor executes the method of the first aspect described above.

Beneficial effect

In the embodiments of this application, different newly-added devices can be included in the management scope of the platform, which improves the monitoring effect.

Description of the drawings

Fig. 1 is an architecture diagram of a data monitoring system provided by an embodiment of the present application.

Fig. 2 is a flowchart of a data monitoring method provided by an embodiment of the present application.

Fig. 3 is a flowchart of another data monitoring method provided by an embodiment of the present application.

Fig. 4 is a schematic structural diagram of a data monitoring device provided by an embodiment of the present application.

Fig. 5 is a schematic block diagram of a server provided by an embodiment of the present application.

Embodiments of the present invention

It should be understood that the specific embodiments described here are only used to explain the application, and are not used to limit the application.

The technical solution of the present application can be applied to the field of big data technology, and different newly-added devices can be included in the management scope of the platform, which improves the monitoring effect.

Since the monitoring device assigns a characteristic value to each registered monitored device, if you need to confirm the registration of the monitored device, you only need to find the characteristic value corresponding to the monitored device, and use the characteristic value to distinguish the monitored device. The number of data requests for each monitored device is limited. Therefore, a data monitoring method proposed in this application can realize that different newly added devices are included in the management scope of the platform, and the monitoring effect is improved.

Please refer to FIG. 1. FIG. 1 is an architecture diagram of a data monitoring system provided by an embodiment of the present application. As shown in Figure 1, the system includes a monitored device 10, a data monitoring device 20, and a monitoring platform 30. In a possible implementation manner, the monitored device 10 may be a portable terminal such as a mobile phone, a tablet computer, or a notebook computer, or a non-portable terminal such as a desktop computer, or other devices capable of uploading data.

It should be noted that in the data monitoring system shown in FIG. 1, the monitored device 10 is used to provide characteristic values to the data monitoring device 20.

The data monitoring device 20 is used to obtain the characteristic value of the monitored device 10; the data monitoring device 20 is also used to confirm whether the above characteristic value exists in the registration database of the monitoring platform 30; the data monitoring device 20 is also used to obtain The account priority of the device 10 and the corresponding first data request threshold; the data monitoring device 20 is also used to reject the request sent by the monitored device 10 when the number of data requests of the monitored device 10 reaches the first data request threshold. Data request.

The monitoring platform 30 is used to provide the data monitoring device 20 with the characteristic values of the registered equipment.

In a possible implementation, the data monitoring device 20 obtains the universally unique identification code generated by the monitoring platform 30 when the monitored device 10 does not have a characteristic value, and uses the universally unique identification code as the above-mentioned monitored device 10 Eigenvalues.

Please refer to FIG. 2. FIG. 2 is a schematic flowchart of a data monitoring method provided by an embodiment of the present application, and the foregoing method includes.

S101. Find the characteristic value of the monitored device.

In the embodiment of the present application, after the monitored device is legally registered in the monitoring platform, it will obtain the specified characteristic value, so that each monitored device can be distinguished by using the characteristic value. After the monitoring device is started or upgraded, it is necessary to first determine whether the corresponding monitored device has been registered in the monitoring platform.

In a possible implementation manner, the aforementioned monitoring platform uses a uniform naming rule to generate different characteristic values for the monitored device.

For example, the first 3 digits of the characteristic value are used to indicate the area where the monitored device is located, the 4th to 6th digits of the characteristic value are used to indicate the model of the monitored device, and the last digit of the characteristic value is used to indicate whether the monitored device is Mirror copy equipment.

Further, it is determined whether the naming information sent by the user is received; in the case of receiving the naming information, the naming information is sent to the monitoring platform.

Further, the above-mentioned data monitoring device receives the named field sent by the user, and randomly selects the numerical value of the specific position of the characteristic value to represent the named field set by the user.

For example, the data monitoring device receives the naming field sent by the user as "model", and the naming field needs to be represented by 3 digits in the characteristic value. The data monitoring device randomly selects the 5th to 7th digits of the characteristic value to indicate the Name the field. It should be understood that the foregoing description is only used as an example, and the embodiment of the present application does not specifically limit the naming rule of the characteristic value.

For another example, in the case where the above-mentioned data monitoring device receives the "A place" input by the user, the randomly generated "02" is used to indicate "A land", and the randomly generated "33" is used to indicate "B land". . Furthermore, the above data monitoring device counts that 55% of the monitored equipment belongs to brand A, 40% of the monitored equipment belongs to brand B, and 5% of the monitored equipment belongs to brand C. The above data monitoring device uses "000" and "001". "And "111" are used to represent the monitored devices of brands A, B and C, respectively.

S102: In the case where the above-mentioned monitored device has the above-mentioned characteristic value, determine whether the above-mentioned monitored device is a mirror copying device.

In the solution of the present application, when multiple monitored devices are mirrored and copied, the copied monitored devices may have duplicate characteristic values, that is, if the characteristic values of the monitored devices are not unique, the above-mentioned monitored devices are mirrored copy devices. In order to ensure the security and stability of the background service, the above-mentioned data monitoring device may further determine whether to register the copied monitored device according to the judgment result.

S103: In the case that the monitored device is not the mirror copy device, confirm that the monitored device is a registered device.

Specifically, in the case where the above-mentioned characteristic value exists in the registration database and the monitored device is not the above-mentioned mirror copying device, it is confirmed that the above-mentioned monitored device is a device that has been legally registered.

In a possible implementation, in the case where the monitored device is the above-mentioned mirror copy device, it is determined whether there are duplicate data with the above characteristic value in the registration database of the monitoring platform; if it exists, the above-mentioned data of the monitored device is cleared. Feature value, and perform the above-mentioned step of finding the feature value of the monitored device. Otherwise, confirm that the above-mentioned monitored device is a registered device.

For example, after mirroring and copying the monitored device A that is successfully registered, the monitored device B is obtained. At this time, the monitored device B and the monitored device A are two different devices. The above data monitoring device needs to clear the characteristic value of the monitored device B first, and register the monitored device B on the monitoring platform to be monitored Device B assigns a new characteristic value, so that two devices are managed with different characteristic values.

Further, when the data monitoring device inquires that the monitored device is a mirrored copy device, the data monitoring device generates the characteristic value of the monitored device according to the characteristic value of the other monitored device copied by the monitored device.

For example, the characteristic value of the monitored device A is "A330", and the registered device A is mirrored and copied to obtain the monitored devices B and C. The above-mentioned data monitoring device regards "A330-1" and "A330-2" as the characteristic values of the monitored equipment B and C, respectively, according to the characteristic value of the monitored equipment A.

For another example, the characteristic value of the monitored device A is "A330", and the successfully registered monitored device A is mirrored and copied to obtain the monitored devices B and C in the first place and the monitored device D in the second place. The aforementioned data monitoring device regards "A330-10" and "A330-11" as the characteristic values of the monitored equipment B and C, respectively, according to the characteristic value of the monitored equipment A, and regards "A330-20" as the characteristic value of the monitored equipment D. Eigenvalues.

In another possible implementation, before confirming that the monitored device is a registered device, the method further includes: in the case that the monitored device does not have a characteristic value, obtaining the universal unique identification generated by the monitoring platform Code; the above universally unique identification code is used as the characteristic value of the above-mentioned monitored device.

For example, the aforementioned universally unique identifier (UUID) can be a globally unique identifier (globally unique identifier). unique identifier (GUID), you can also use a globally unique identifier (GUID) to distinguish the above-mentioned monitored devices. It should be understood that the method for generating the universal unique identification code is not specifically limited in the embodiments of the present application.

Further, the above-mentioned data monitoring device associates and stores the monitored equipment and characteristic values that have an association relationship.

For example, the monitored equipment B and C are mirrored copy equipment of the monitored equipment A, the above data monitoring device associates the monitored equipment A with B, C for storage, and the monitored equipment B and C are displayed as the branch options of the monitored equipment A .

Further, the monitored device A is the upper-level option of the monitored devices B and C. The monitoring interface of the monitored device A can contain abnormal warning information of the monitored devices B and C. The data monitoring device can be monitored through the monitoring interface. The monitoring interface of device A enters the details pages of monitored devices B and C.

S104. Obtain the account priority corresponding to the monitored device.

In a possible implementation, different account priorities correspond to different operation permissions.

For example, the running account corresponding to the monitored device A can only query the running status of the monitored device A, and cannot uninstall the service on the monitored device A; the running account corresponding to the monitored device B can start and stop the monitoring service of the monitored device B , Query the running log and version information of the monitored device B.

For another example, the operating account corresponding to the monitored device A can perform all operations on the monitored device A, but before performing the corresponding operations, the operating account corresponding to the monitored device A needs to obtain the authorization instructions of the monitoring platform.

Further, the above-mentioned data monitoring device configures the operation corresponding to the above-mentioned account priority according to the actual use requirements of the user.

For example, the priority of the running account on the above-mentioned monitored device is a normal account, and it has 3 operation permissions. The above-mentioned data monitoring device can assign these 3 operation permissions to operation A, operation B, and operation according to the actual use needs of the user. C.

S105. Obtain the first data request threshold corresponding to the monitored device according to the corresponding relationship between the account priority and the data request threshold.

Specifically, the above-mentioned data monitoring apparatus uses the acquired characteristic value and the account priority of the monitored device for associated storage, so as to obtain different first data request thresholds of the above-mentioned monitored device.

In a possible implementation manner, the first data request threshold is a query per second (QPS), and the data monitoring device sets the first data request threshold in a gradient according to the user's account priority .

For example, for the monitored device whose account priority is low, the query rate per second is set to 15; for the monitored device whose account priority is ordinary, the query rate per second is set to 20; for the above account priority is high For monitored devices, the query rate per second is set to 30.

For another example, the query rate per second for the monitored devices with a low account priority is set to 15; according to the user's setting, the data monitoring device will specify 100 monitored devices with a low priority to query per second The rate is set to 10.

For another example, for the above-mentioned account priority of ordinary monitored equipment, the query rate per second is set to 20; according to the user's setting, the above-mentioned data monitoring device sets the designated priority of 50 units as the ordinary monitored equipment’s query rate per second Set to 30.

S106: When the number of data requests of the monitored device reaches the first data request threshold, reject the data request sent by the monitored device.

In a possible implementation manner, the above-mentioned data monitoring device can adjust the traffic of the monitored device in real time according to the number of users who are currently sending data requests.

For example, if the number of users currently requesting is small, the monitoring platform sends the currently allowed increase range to the data monitoring device, that is, the data monitoring device can increase the traffic limit of the monitored device accordingly.

For another example, there are currently a large number of users. In order to ensure the operation process of the monitored device, the monitoring platform will give priority to increasing the traffic limit of the monitored device with a higher account priority in order from high to low.

In another possible implementation manner, the above-mentioned data monitoring device increases and/or decreases the number of work units corresponding to the above-mentioned monitored equipment according to the above-mentioned account priority; the above-mentioned number of work units is the same as the number of data requests of the above-mentioned monitored equipment Directly proportional.

For example, when the number of data requests of the monitored device increases, for users with high account priority, the above data monitoring device increases the number of work units from 2 to 6 by calling back the Kubernetes interface; for accounts For users with low priority, the above-mentioned data monitoring device increases the number of working units from one to two.

For another example, when the number of data requests of the monitored device decreases, for users with high account priority, the above data monitoring device reduces the number of work units from the original 6 to 4 through the callback Kubernetes interface; For users with low account priority, the above-mentioned data monitoring device reduces the number of working units from the original four to one.

For another example, when the number of data requests of the monitored device increases, and the number of work units that can be added by the data monitoring device is limited, the data monitoring device preferentially increases the number of work units of the monitored device with a higher account priority. Further, the above-mentioned data monitoring device sends prompt information to the monitored equipment according to the current number of data requests. The above-mentioned prompt information can be the estimated time of the task calculated by the above-mentioned monitoring platform, can also suggest the waiting time for the user, and can also be the information of the idle running time period. The above-mentioned data monitoring device can send idle running time period information to users with low account priority, suggesting users with low account priority to change the upload task time, and select a relatively idle time period to perform the data upload task.

In another possible implementation manner, the data monitoring device determines whether any of the following conditions is met: whether the device information of the monitored device is updated, or whether the version information of the data monitoring device is updated; when any of the above conditions is met Send update information to the monitoring platform, where the update information includes the device information of the monitored device and/or the version information of the data monitoring device, and the device information includes name information and/or network information.

In the embodiment of this application, by obtaining the characteristic value of the monitored device and detecting the characteristic value based on the registration database of the monitoring platform, the registration status of each monitored device can be confirmed, thereby realizing the monitoring of all newly added devices on the platform. Management improves the monitoring effect.

Please refer to FIG. 3, which is a schematic flowchart of another data monitoring method provided by an embodiment of the present application, and the foregoing method includes.

S201. Search for the characteristic value of the monitored device.

For the specific implementation of this step, reference may be made to step S101 of the above-mentioned embodiment in FIG. 3, which will not be repeated here.

S202: In the case where the above-mentioned monitored device has the above-mentioned characteristic value, determine whether the above-mentioned monitored device is a mirror copying device.

For the specific implementation of this step, reference may be made to step S102 of the above-mentioned embodiment in FIG. 3, which will not be repeated here.

S203: In the case that the monitored device is not the mirror copy device, confirm that the monitored device is a registered device.

For the specific implementation of this step, reference may be made to step S103 of the above-mentioned embodiment in FIG. 3, which will not be repeated here.

S204. Obtain the account priority corresponding to the monitored device.

For the specific implementation of this step, reference may be made to step S104 of the above-mentioned embodiment in FIG. 3, which will not be repeated here.

S205. Obtain the first data request threshold corresponding to the monitored device according to the corresponding relationship between the account priority and the data request threshold.

For the specific implementation of this step, reference may be made to step S105 of the above-mentioned embodiment in FIG. 3, which will not be repeated here.

S206: When the number of data requests of the monitored device reaches the first data request threshold, reject the data request sent by the monitored device.

For the specific implementation of this step, reference may be made to step S106 of the above-mentioned embodiment in FIG. 3, which will not be repeated here.

S207: After confirming that the monitored device meets the alarm condition, send interface alarm information to the monitoring platform.

Specifically, the aforementioned interface alarm information includes one or more of the following information: alarm information about the number of data requests, alarm information about the hypertext transfer protocol status code, and alarm information about the total number of calls.

In a possible implementation manner, the above confirming that the monitored device meets the alarm condition includes: obtaining the number of data requests, the total number of calls, and the hypertext transfer protocol status code currently corresponding to the monitored device; determining whether any of the following conditions Satisfaction: Whether the number of data requests currently corresponding to the monitored device exceeds the second data request threshold, or whether the total number of calls exceeds the number corresponding to the account priority, or whether the hypertext transfer protocol status code is the same as the preset value; When any of the above conditions are met, confirm that the above-mentioned monitored equipment meets the alarm conditions.

For example, when the data monitoring device receives the "500" hypertext transfer protocol status code sent by the monitored device, the data monitoring device confirms that the monitored device meets the alarm condition.

In this embodiment of the application, the monitored device and the data monitoring device are connected by HTTPS short connection, that is, the data monitoring device can calculate and control the QPS of a specific user by counting the number of interfaces called by the monitored device. While using the encrypted channel of HTTPS to ensure data security, through the feature of short connection that is ready to use and close, it reduces the consumption of connection resources of the monitored device, and at the same time achieves a good monitoring effect.

Further, the aforementioned data monitoring device counts the number of interfaces called by the monitored device, and combines the statistical result with the package corresponding to the user to obtain the usage fee corresponding to the monitored device.

For example, the above-mentioned user’s package includes 1000 free calls, and the part that exceeds 1000 but does not exceed 5000 will be charged at 0.05 yuan per time for the number of calls to the monitored device. The monitored device corresponding to the user has made 2000 calls, that is, the user also needs to pay a fee of 50 yuan for the use.

In another possible implementation manner, the above-mentioned data monitoring apparatus collects statistics on the usage expenses of the monitored equipment corresponding to the time period according to the usage time period of the monitored equipment.

For example, the above-mentioned user’s package does not include the number of free calls, and billing is entirely based on the actual number of calls. The above-mentioned monitoring platform stipulates that during busy periods, the number of calls to monitored equipment is charged at 0.1 yuan/time; in normal time periods, the number of calls to monitored equipment is charged at 0.05 yuan/time; during idle time periods , The number of invocations of the monitored equipment is charged at 0.03 yuan/time. The monitored device corresponding to the user made 1000 calls during busy time, 2000 calls during normal time, and 1000 calls during idle time, that is, the user needs to pay 230 yuan.

In another possible implementation manner, the above-mentioned data monitoring device obtains the usage fee corresponding to the monitored device according to the number of monitored devices and the number of calls.

For example, the above-mentioned data monitoring device charges the monitored device with a small number of calls according to the actual number of calls of the monitored device; for the monitored device with a large number of calls, it charges according to the package corresponding to the whole machine.

In the embodiment of this application, the characteristic value of the monitored device is detected based on the registration database of the monitoring platform, and the condition of the monitored device that meets the alarm conditions is sent to the monitoring platform, and the registration and usage status of each monitored device can be confirmed, thereby The management of all new equipment on the platform is realized, and the monitoring effect is improved.

The embodiment of the present application also provides a data monitoring device. The device includes a module for executing the method described in FIG. 1 or FIG. 2, and is configured on a server. Specifically, refer to FIG. 4, which is a schematic block diagram of a data monitoring device provided in an embodiment of the present application. The data monitoring device of this embodiment may include: a feature unit 301, a judgment unit 302, a determination unit 303, an acquisition unit 304, a control unit 305, and a sending unit 306.

The characteristic unit 301 is used to find the characteristic value of the monitored device.

The judging unit 302 is configured to judge whether the monitored device is a mirror copying device when the above-mentioned characteristic value exists in the above-mentioned monitored device.

The determining unit 303 is configured to confirm that the monitored device is a registered device when the monitored device is not the mirror copy device.

The obtaining unit 304 is configured to obtain the account priority corresponding to the above-mentioned monitored device.

The acquiring unit 304 is further configured to acquire the first data request threshold corresponding to the monitored device according to the corresponding relationship between the account priority and the data request threshold.

The control unit 305 is configured to reject the data request sent by the monitored device when the number of data requests of the monitored device reaches the first data request threshold.

In a possible implementation manner, the judgment unit 302 is further configured to judge whether there is data that is duplicated with the characteristic value in the registration database of the monitoring platform when the monitored device is the mirror copy device.

In another possible implementation manner, the determination unit 303 is specifically configured to, if it exists, clear the characteristic value of the monitored device, and execute the step of finding the characteristic value of the monitored device; otherwise, confirm the monitored device The device is a registered device.

In another possible implementation manner, the feature unit 301 is also used to obtain the universal unique identification code generated by the monitoring platform in the case that the monitored device does not have a feature value; As the characteristic value of the above-mentioned monitored device.

In another possible implementation manner, the control unit 305 is further configured to increase and/or decrease the number of work units corresponding to the monitored device according to the account priority; the number of work units is the same as that of the monitored device. Is directly proportional to the number of data requests.

In another possible implementation manner, the above-mentioned device further includes: a sending unit 306, configured to send interface alarm information to the above-mentioned monitoring platform when it is confirmed that the above-mentioned monitored equipment meets the alarm condition; the above-mentioned interface alarm information includes the following: One or more types of information: alarm information about the number of data requests, alarm information about the hypertext transfer protocol status code, and alarm information about the total number of calls.

In another possible implementation manner, the sending unit 306 is specifically configured to obtain the number of data requests, the total number of calls, and the hypertext transfer protocol status code currently corresponding to the monitored device; and to determine whether any of the following conditions is met: the above Whether the number of data requests currently corresponding to the monitored device exceeds the second data request threshold, or whether the above-mentioned total number of calls exceeds the number of times corresponding to the above-mentioned account priority, or whether the above-mentioned hypertext transfer protocol status code is the same as the preset value; When a condition is met, confirm that the above-mentioned monitored equipment meets the alarm condition.

In another possible implementation manner, the above-mentioned feature unit 301 is further configured to determine whether the naming information sent by the user is received before obtaining the universally unique identification code generated for the monitored device in the registration database of the monitoring platform ; In the case of receiving the naming information, send the naming information to the monitoring platform.

It should be noted that the functions of each functional module of the data monitoring device described in the embodiment of the present application can be specifically implemented according to the method in the method embodiment described in FIG. 2 or FIG. 3, and the specific implementation process may refer to FIG. 2 or FIG. The relevant description of the method embodiment of 3 will not be repeated here.

Please refer to FIG. 5. FIG. 5 is a schematic block diagram of a server provided by an embodiment of the present application. As shown in FIG. 5, the server includes a processor 401, an input device 402, an output device 403, and a memory 404. The aforementioned processor 401, input device 402, output device 403, and memory 404 may be connected to each other through a bus. In FIG. 5 shown in the embodiment of the present application, the connection through a bus is taken as an example. The input device 402 is used to input data and/or signals, and the output device 403 is used to output data and/or signals. The output device and the input device may be independent devices or an integrated device. The memory 404 is used to store a computer program, and the computer program includes program instructions. The processor 401 is used to execute the program instructions stored in the memory 404. Wherein, the processor 401 is configured to call the program instructions to execute: find the characteristic value of the monitored device; in the case that the monitored device has the characteristic value, determine whether the monitored device is a mirror copy device In the case that the monitored device is not the mirror copy device, confirm that the monitored device is a registered device; obtain the account priority corresponding to the monitored device; according to the account priority and data request The corresponding relationship of the threshold value, the first data request threshold corresponding to the monitored device is obtained; when the number of data requests of the monitored device reaches the first data request threshold, the data sent by the monitored device is rejected ask.

In a possible implementation manner, the processor 401 is further configured to: in the case that the monitored device is the mirror copy device, determine whether there is a duplicate of the characteristic value in the registration database of the monitoring platform. Data; if it exists, clear the characteristic value of the monitored device, and execute the step of finding the characteristic value of the monitored device; otherwise, confirm that the monitored device is a registered device.

In a possible implementation manner, the processor 401 is further configured to: before confirming that the monitored device is a registered device, if the monitored device does not have the characteristic value, obtain The universal unique identification code generated for the monitored device in the registration database of the monitoring platform; the universal unique identification code is used as the characteristic value of the monitored device.

In a possible implementation manner, the processor 401 is further configured to: increase and/or decrease the number of work units corresponding to the monitored device according to the account priority; The number of data requests from the monitored device is directly proportional.

In a possible implementation manner, the processor 401 is further configured to: upon confirming that the monitored device meets the alarm condition, send interface alarm information to the monitoring platform; the interface alarm information includes the following: One or more types of information: alarm information about the number of data requests, alarm information about the hypertext transfer protocol status code, and alarm information about the total number of calls.

In a possible implementation manner, the processor 401 is specifically configured to: obtain the current number of data requests, the total number of calls, and the hypertext transfer protocol status code corresponding to the monitored device; and determine whether any of the following conditions is met: Whether the number of data requests currently corresponding to the monitored device exceeds the second data request threshold, or whether the total number of calls exceeds the number corresponding to the account priority, or whether the hypertext transfer protocol status code is consistent with a preset value Same; when any one of the conditions is met, confirm that the monitored device meets the alarm condition.

In a possible implementation manner, the processor 401 is further configured to: before obtaining the universal unique identification code generated for the monitored device in the registration database of the monitoring platform, determine whether the name sent by the user is received Information; in the case of receiving the naming information, send the naming information to the monitoring platform.

It should be understood that, in the embodiment of the present application, the so-called processor 401 may be a central processing unit (Central Processing Unit, CPU). The processor 401 may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), and application-specific integrated circuits (Application Specific Integrated Circuits). Specific Integrated Circuit, ASIC), ready-made programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

The memory 404 may include a read-only memory and a random access memory, and provides instructions and data to the processor 401. A part of the memory 404 may also include a non-volatile random access memory. For example, the memory 404 may also store device type information.

In specific implementation, the processor 401, input device 402, output device 403, and memory 404 described in the embodiment of the present application can execute the implementation described in the method embodiment described in FIG. 2 or FIG. 3 provided by the embodiment of the present application. , The implementation of the data monitoring device described in the embodiment of the present application can also be implemented, which will not be repeated here.

In another embodiment of the present application, a computer-readable storage medium is provided. Optionally, the computer-readable storage medium may be non-volatile or volatile. The computer-readable storage medium stores a computer program, and the computer program includes program instructions that are implemented when executed by a processor: to find a characteristic value of a monitored device; the characteristic value exists in the monitored device In the case of, determine whether the monitored device is a mirror copy device; in the case that the monitored device is not the mirror copy device, confirm that the monitored device is a registered device; obtain the monitored device Corresponding account priority; obtain the first data request threshold corresponding to the monitored device according to the corresponding relationship between the account priority and the data request threshold; the number of data requests on the monitored device reaches the first data In the case of requesting the threshold, the data request sent by the monitored device is rejected.

The computer-readable storage medium may be the internal storage unit of the server described in any of the foregoing embodiments, such as the hard disk or memory of the server. The computer-readable storage medium may also be an external storage device of the server, such as a plug-in hard disk equipped on the server, a smart memory card (Smart Media Card, SMC), and a secure digital (Secure Digital). Digital, SD) card, flash memory card (Flash Card) and so on. Further, the computer-readable storage medium may also include both an internal storage unit of the server and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the server. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing relevant hardware through a computer program. The program can be stored in a computer readable storage medium. During execution, it may include the procedures of the above-mentioned method embodiments. Wherein, the storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM) or a random storage memory (Random Access Memory, RAM) etc.

The above-disclosed are only part of the embodiments of this application. Of course, it cannot be used to limit the scope of rights of this application. Those of ordinary skill in the art can understand all or part of the procedures for implementing the above-mentioned embodiments and make them in accordance with the claims of this application. The equivalent change of is still within the scope of this application.

Claims

A data monitoring method, which includes:

Find the characteristic value of the monitored device;

In the case that the monitored device has the characteristic value, determine whether the monitored device is a mirror copy device;

In the case that the monitored device is not the mirror copy device, confirm that the monitored device is a registered device;

Acquiring the account priority corresponding to the monitored device;

Acquiring the first data request threshold corresponding to the monitored device according to the correspondence between the account priority and the data request threshold;

When the number of data requests of the monitored device reaches the first data request threshold, reject the data request sent by the monitored device.
The method according to claim 1, wherein the method further comprises:

In the case that the monitored device is the mirror copy device, determine whether there is data that is duplicated with the characteristic value in the registration database of the monitoring platform;

If it exists, clear the characteristic value of the monitored device, and execute the step of finding the characteristic value of the monitored device;

Otherwise, confirm that the monitored device is a registered device.
The method according to claim 1 or 2, wherein, before the confirming that the monitored device is a registered device, the method further comprises:

In the case that the monitored device does not have the characteristic value, obtain a universal unique identification code generated for the monitored device in the registration database of the monitoring platform;

The universal unique identification code is used as the characteristic value of the monitored device.
The method according to claim 3, wherein the method further comprises:

Increase and/or decrease the number of work units corresponding to the monitored device according to the account priority;

The number of working units is proportional to the number of data requests of the monitored device.
The method according to claim 4, wherein the method further comprises:

When it is confirmed that the monitored device meets the alarm condition, send interface alarm information to the monitoring platform;

The interface alarm information includes one or more of the following information: alarm information about the number of data requests, alarm information about the hypertext transfer protocol status code, and alarm information about the total number of calls.
The method according to claim 5, wherein the confirming that the monitored device meets an alarm condition comprises:

Acquiring the number of data requests, the total number of calls, and the hypertext transfer protocol status code currently corresponding to the monitored device;

Determine whether any of the following conditions is met: whether the number of data requests currently corresponding to the monitored device exceeds the second data request threshold, or whether the total number of calls exceeds the number corresponding to the account priority, or the hypertext transmission Whether the protocol status code is the same as the preset value;

When any one of the conditions is met, it is confirmed that the monitored device meets the alarm condition.
The method according to claim 3, wherein before the obtaining the universal unique identification code generated for the monitored device in the registration database of the monitoring platform, the method further comprises:

Determine whether the naming information sent by the user is received;

In the case of receiving the naming information, sending the naming information to the monitoring platform.
A data monitoring device, which includes:

Characteristic unit, used to find the characteristic value of the monitored device;

A judging unit, configured to judge whether the monitored device is a mirror copying device in the case that the monitored device has the characteristic value;

A determining unit, configured to confirm that the monitored device is a registered device when the monitored device is not the mirror copy device;

An obtaining unit, configured to obtain the account priority corresponding to the monitored device;

The obtaining unit is further configured to obtain the first data request threshold corresponding to the monitored device according to the corresponding relationship between the account priority and the data request threshold;

The control unit is configured to reject the data request sent by the monitored device when the number of data requests of the monitored device reaches the first data request threshold.
A server, including a processor and a memory, the processor and the memory are connected to each other, wherein the memory is used to store a computer program, the computer program includes program instructions, the processor is configured to call the The program instructions are used to find the characteristic value of the monitored device; in the case that the monitored device has the characteristic value, determine whether the monitored device is a mirroring copy device; when the monitored device is not owned by In the case of the mirror copy device, confirm that the monitored device is a registered device; obtain the account priority corresponding to the monitored device; obtain the monitored device according to the correspondence between the account priority and the data request threshold The first data request threshold corresponding to the device; when the number of data requests of the monitored device reaches the first data request threshold, the data request sent by the monitored device is rejected.
The server according to claim 9, wherein the processor is further configured to: in the case that the monitored device is the mirror copy device, determine whether there is a duplicate of the characteristic value in the registration database of the monitoring platform If it exists, clear the characteristic value of the monitored device and execute the step of finding the characteristic value of the monitored device; otherwise, confirm that the monitored device is a registered device.
The server according to claim 9 or 10, wherein the processor is further configured to: before confirming that the monitored device is a registered device, when the monitored device does not have the characteristic value Next, obtain the universal unique identification code generated for the monitored device in the registration database of the monitoring platform;

The universal unique identification code is used as the characteristic value of the monitored device.
The server according to claim 11, wherein the processor is further configured to: increase and/or decrease the number of work units corresponding to the monitored device according to the account priority; the number of work units is equal to The number of data requests of the monitored device is directly proportional.
The server according to claim 12, wherein the processor is further configured to: upon confirming that the monitored device meets the alarm condition, send interface alarm information to the monitoring platform; the interface alarm information includes the following One or more types of information: alarm information about the number of data requests, alarm information about the hypertext transfer protocol status code, and alarm information about the total number of calls.
The server according to claim 13, wherein the processor is specifically configured to: obtain the number of data requests, the total number of calls, and the hypertext transfer protocol status code currently corresponding to the monitored device; and determine whether any of the following conditions is satisfied : Whether the number of data requests currently corresponding to the monitored device exceeds the second data request threshold, or whether the total number of calls exceeds the number corresponding to the account priority, or whether the hypertext transfer protocol status code is consistent with a preset The value is the same; when any one of the conditions is met, it is confirmed that the monitored device meets the alarm condition.
The server according to claim 11, wherein the processor is further configured to: before obtaining the universal unique identification code generated for the monitored device in the registration database of the monitoring platform, determine whether a user is received The sent naming information; when the naming information is received, the naming information is sent to the monitoring platform.
A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the following steps:

Find the characteristic value of the monitored device; in the case that the monitored device has the characteristic value, determine whether the monitored device is a mirroring copy device;

In the case that the monitored device is not the mirror copy device, confirm that the monitored device is a registered device;

Acquiring the account priority corresponding to the monitored device; acquiring the first data request threshold corresponding to the monitored device according to the correspondence between the account priority and the data request threshold;

When the number of data requests of the monitored device reaches the first data request threshold, reject the data request sent by the monitored device.
The computer-readable storage medium according to claim 16, wherein the following steps are further implemented:

In the case that the monitored device is the mirror copy device, determine whether there is data that is duplicated with the characteristic value in the registration database of the monitoring platform;

If it exists, clear the characteristic value of the monitored device, and execute the step of finding the characteristic value of the monitored device;

Otherwise, confirm that the monitored device is a registered device.
The computer-readable storage medium according to claim 16 or 17, wherein the following steps are further implemented:

Before confirming that the monitored device is a registered device, in the case that the monitored device does not have the characteristic value, obtain the universal unique value generated for the monitored device in the registration database of the monitoring platform Identifier;

The universal unique identification code is used as the characteristic value of the monitored device.
The computer-readable storage medium according to claim 18, wherein the following steps are further implemented:

Increase and/or decrease the number of work units corresponding to the monitored device according to the account priority;

The number of working units is proportional to the number of data requests of the monitored device.
The computer-readable storage medium according to claim 19, wherein the following steps are further implemented:

When it is confirmed that the monitored device meets the alarm condition, send interface alarm information to the monitoring platform;

The interface alarm information includes one or more of the following information: alarm information about the number of data requests, alarm information about the hypertext transfer protocol status code, and alarm information about the total number of calls.