WO2021147481A1 - 监控方法、装置及电子设备 - Google Patents

监控方法、装置及电子设备 Download PDF

Info

Publication number
WO2021147481A1
WO2021147481A1 PCT/CN2020/128819 CN2020128819W WO2021147481A1 WO 2021147481 A1 WO2021147481 A1 WO 2021147481A1 CN 2020128819 W CN2020128819 W CN 2020128819W WO 2021147481 A1 WO2021147481 A1 WO 2021147481A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
service system
interface
dimension
target dimension
Prior art date
Application number
PCT/CN2020/128819
Other languages
English (en)
French (fr)
Inventor
赵鹏昕
陈韬
郝拯华
Original Assignee
北京字节跳动网络技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京字节跳动网络技术有限公司 filed Critical 北京字节跳动网络技术有限公司
Publication of WO2021147481A1 publication Critical patent/WO2021147481A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324—Display of status information
    • G06F11/327—Alarm or error message display
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available

Definitions

  • This application relates to the field of computer application technology, and more specifically, to a monitoring method, device, and electronic equipment.
  • the service system carries access requests from tens of thousands of terminals, and the operating status of the network service system has a huge impact.
  • the purpose of this application is to provide a monitoring method, device and electronic equipment. By determining and selecting a monitoring plan that matches the target dimension to monitor the service system, monitoring of different dimensions of the service system can be realized, the comprehensiveness and accuracy of the service system monitoring can be improved, and the monitoring efficiency of the service system can be improved.
  • this application discloses a monitoring method, including: determining a target dimension to be monitored in a service system, wherein the target dimension includes any of the infrastructure dimension, interface dimension, and user dimension of the service system Choose a monitoring plan that matches the target dimension; execute a monitoring plan that matches the target dimension to obtain a monitoring result corresponding to the target dimension, wherein the monitoring result is either normal or abnormal; When the monitoring result is abnormal, output alarm information that the monitoring result of the target dimension of the service system is abnormal.
  • the monitoring result corresponding to the target dimension is obtained, and the service is output when the monitoring result is abnormal
  • the target dimension is the infrastructure dimension of the service system; the execution of a monitoring solution that matches the target dimension includes: collecting the number of correct return request data of the basic framework and all received data The number of requests; according to a preset algorithm, the number of correctly returned request data and the number of all requests received are used to calculate the monitoring value of the infrastructure stability; if the monitoring value of the infrastructure stability is greater than or If it is equal to the first threshold, it is determined that the monitoring result of the infrastructure stability is normal; if the monitoring value of the infrastructure stability is less than the first threshold, it is determined that the monitoring result of the infrastructure stability is abnormal.
  • the monitoring value of the stability of the infrastructure is calculated by collecting the number of correct return request data of the basic framework and the number of all requests received, and the monitoring value and the first threshold value are used to realize Implement a monitoring plan that matches the dimensions of the infrastructure of the service system to further improve the accuracy of monitoring the operating status of the infrastructure of the service system.
  • the calculation of the monitoring value of the stability of the infrastructure by using the number of correctly returned request data and the number of all requests received according to a preset algorithm includes: calculating the correct return of requested data The ratio of the number of times to the number of all requests received is used as a monitoring value of the stability of the infrastructure.
  • the target dimension is the interface dimension of the service system
  • the execution of a monitoring solution that matches the target dimension includes: collecting interface parameters of the service system; using the interface according to a preset algorithm
  • the parameter calculates the interface monitoring value of the service system; if the interface monitoring value is greater than or equal to the second threshold, it is determined that the monitoring result of the interface of the service system is normal; if the interface monitoring value is less than the second threshold, It is determined that the monitoring result of the interface of the service system is abnormal.
  • the matched monitoring plan further improves the monitoring accuracy of the operation status of the interface dimension of the service system.
  • the monitoring type of the interface dimension includes any one of the interface access rate and the average delay of the interface.
  • the monitoring type of the interface dimension is the interface access rate
  • the collecting the interface parameters of the service system includes: collecting the total access volume of the interface of the service system at the current time
  • the interface parameter calculation of the interface monitoring value of the service system includes: deriving the total access volume at the current time to obtain the interface access rate of the service system.
  • the interface access rate of the service system is obtained, and the interface access rate is used to monitor the interface dimension of the service system
  • the operating status of the service system further improves the monitoring accuracy of the operating status of the interface dimension of the service system.
  • the monitoring type of the interface dimension is the average delay of the interface;
  • the collecting the interface parameters of the service system includes: collecting the request exit time and the request entrance time corresponding to the interface of the service system; the basis
  • the preset algorithm, using the interface parameters to calculate the interface monitoring value of the service system includes: subtracting the request entry time from the request exit time to obtain the average delay of the interface of the service system.
  • the target dimension is the user dimension: the execution of a monitoring solution that matches the target dimension to obtain a monitoring result corresponding to the target dimension includes: collecting a user's access rate according to a unique identifier of the user; if If the access rate of the user is less than or equal to the third threshold, it is determined that the monitoring result of the user dimension is normal; if the access rate of the user is greater than the third threshold, it is determined that the monitoring result of the user dimension is abnormal.
  • the user's access rate is collected based on the user's unique identification, and the user-dimensional monitoring result is determined based on the relationship between the access rate and the third threshold.
  • the access rate of the user is the real-time access rate of the user or the total access rate of the user in a preset time period.
  • the target dimension further includes the computer room cluster dimension of the service system; the executing a monitoring solution that matches the target dimension to obtain the monitoring result corresponding to the target dimension includes: collecting data of the computer room cluster Access rate; if the access rate balance state of the computer room cluster meets the preset requirements, it is determined that the load balance of the computer room cluster of the service system is normal; if the access rate balance state of the computer room cluster does not meet the preset requirements, it is determined The load balance of the computer room cluster of the service system is abnormal.
  • this application discloses a monitoring device.
  • the determining module is used to determine the target dimension to be monitored in the service system, where the target dimension includes any one of the infrastructure dimension, interface dimension, and user dimension of the service system;
  • the selection module is used to select a monitoring plan that matches the target dimension
  • the execution module is configured to execute a monitoring plan that matches the target dimension, and obtain a monitoring result corresponding to the target dimension, wherein the monitoring result is any one of normal and abnormal;
  • the output module is used for outputting alarm information that the monitoring result of the target dimension of the service system is abnormal when the monitoring result is abnormal.
  • the target dimension is the infrastructure dimension of the service system; the execution module is specifically configured to: collect the number of times that the basic framework correctly returns request data and the number of all requests received; Suppose an algorithm is used to calculate the monitoring value of the stability of the infrastructure by using the number of correctly returned request data and the number of all requests received; if the monitoring value of the stability of the infrastructure is greater than or equal to the first threshold, then It is determined that the monitoring result of the stability of the infrastructure is normal; if the monitoring value of the stability of the infrastructure is less than the first threshold, it is determined that the monitoring result of the stability of the infrastructure is abnormal.
  • the execution module is specifically used to calculate the monitoring value of the stability of the infrastructure by using the number of correctly returned request data and the number of all requests received according to a preset algorithm: The ratio of the number of times that the requested data is correctly returned to the number of all requests received is used as a monitoring value of the stability of the infrastructure.
  • the target dimension is the interface dimension of the service system;
  • the execution module is specifically configured to: collect interface parameters of the service system; use the interface parameters to calculate the interface parameters of the service system according to a preset algorithm Interface monitoring value; if the interface monitoring value is greater than or equal to the second threshold value, it is determined that the monitoring result of the interface of the service system is normal; if the interface monitoring value is less than the second threshold value, it is determined that the service system The monitoring result of the interface is abnormal.
  • the monitoring type of the interface dimension includes any one of the interface access rate and the average delay of the interface.
  • the monitoring type of the interface dimension is the interface access rate; when the execution module collects the interface parameters of the service system, it is specifically used to: collect the total interface access volume of the service system at the current time; When the execution module uses the interface parameters to calculate the interface monitoring value of the service system according to a preset algorithm, it is specifically used to: derive the total access volume at the current time to obtain the interface access rate of the service system.
  • the monitoring type of the interface dimension is interface average delay; when the execution module collects the interface parameters of the service system, it is specifically used to: collect the request exit time and request corresponding to the interface of the service system Entry time; when the execution module uses the interface parameters to calculate the interface monitoring value of the service system according to a preset algorithm, it is specifically used to: subtract the request entry time from the request exit time to obtain the interface of the service system Average delay.
  • the target dimension is the user dimension
  • the execution module is specifically configured to: collect the user's access rate according to the user's unique identification; if the user's access rate is less than or equal to a third threshold, determine the The monitoring result of the user dimension is normal; if the access rate of the user is greater than the third threshold, it is determined that the monitoring result of the user dimension is abnormal.
  • the access rate of the user is the real-time access rate of the user or the total access rate of the user in a preset time period.
  • the target dimension also includes the computer room cluster dimension of the service system; the execution module is specifically configured to: collect the access rate of the computer room cluster; if the access rate equilibrium state of the computer room cluster meets a preset requirement , It is determined that the load balance of the computer room cluster of the service system is normal; if the access rate balance state of the computer room cluster does not meet the preset requirement, it is determined that the load balance of the computer room cluster of the service system is abnormal.
  • an embodiment of the present application also provides an electronic device, which includes:
  • At least one processor and a memory communicatively connected with the at least one processor; wherein the memory stores an instruction executable by the at least one processor, and the instruction is executed by the at least one processor so that the at least one processor
  • the processor can execute the foregoing first aspect or the monitoring method in any implementation manner of the first aspect.
  • an embodiment of the present application also provides a computer-readable storage medium that stores computer instructions, and the computer instructions are used to make the computer execute the foregoing first aspect or any implementation of the first aspect The monitoring method in the mode.
  • the embodiments of the present application also provide a computer program product.
  • the computer program product includes a calculation program stored on a computer-readable storage medium.
  • the computer program includes program instructions. When the program instructions are executed by a computer, The computer is caused to execute the monitoring method in the foregoing first aspect or any implementation manner of the first aspect.
  • this application determines the target dimension to be monitored in the service system, and selects a monitoring solution that matches the target dimension for monitoring, obtains the monitoring result corresponding to the target dimension, and outputs the monitoring result when the monitoring result is abnormal. Describes the alarm information of abnormal monitoring results in the target dimension of the service system.
  • the target dimension includes any of the infrastructure dimension, interface dimension, and user dimension of the service system. Therefore, the operation of the service system in different dimensions can be realized. Status monitoring improves the comprehensiveness and accuracy of service system monitoring. Through the solution of this application, a comprehensive and automatic monitoring program for the service system is realized, which improves the monitoring efficiency of the service system and ensures normal operation and timely repair of abnormalities. Function.
  • an embodiment of the present application also provides a service system, which includes the electronic device described in the foregoing third aspect.
  • FIG. 1 is a schematic flowchart of a monitoring method provided by an embodiment of this application.
  • FIG. 2 is a schematic structural diagram of a monitoring device provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram of an electronic device provided by an embodiment of the application.
  • the embodiment of the present application provides a monitoring method.
  • the monitoring method provided in this embodiment can be executed by a computing device, and the computing device can be implemented as software, or as a combination of software and hardware, and the computing device can be integrated in a server, a terminal device, and the like.
  • a monitoring method provided by an embodiment of the present application includes:
  • S101 Determine a target dimension to be monitored in the service system, where the target dimension includes any one of the infrastructure dimension, interface dimension, and user dimension of the service system.
  • the monitoring method provided in this embodiment is used to implement multi-dimensional monitoring of the service system.
  • the method can be applied to a built-in monitoring module of the service system, and can also be applied to an electronic device external to the service system to perform monitoring operations on the service system.
  • the applied service system may be an open account service system. In specific implementation, you can bury points at the key entrances and exits of the service system. Other monitoring parameters can also be counted through statistical tools such as Remote Dictionary Service (Remote Dictionary Server, Redis for short).
  • the final data display can be visualized Tools for data presentation.
  • the monitoring dimensions of the service system can be divided into multiple types, and the monitoring levels are also different. For example, from the infrastructure dimension of the service system to monitor the stability of the overall level of the system, from the interface dimension or user dimension to monitor the stability of the system's local operation level.
  • the electronic device has pre-stored monitoring programs for different dimensions, and each monitoring program may include the initial parameters that need to be collected for the monitoring of the dimension, the calculation rules on which they are based, and the evaluation rules for the calculation results. After determining the current target dimension to be monitored, you can select a monitoring plan that matches the target dimension.
  • S103 Execute a monitoring solution matching the target dimension to obtain a monitoring result corresponding to the target dimension, where the monitoring result is either normal or abnormal.
  • the electronic device After the electronic device selects a monitoring plan that matches the currently monitored target dimension, it can execute the matched monitoring plan, and obtain a monitoring result corresponding to the target dimension, and use the monitoring result to indicate the normal or abnormal operating status of the target dimension.
  • the monitoring result of the target dimension is normal, it can be determined that the operation status of the target dimension is normal, and there is no need for fault repair processing. If the monitoring result of the target dimension is abnormal, it can be determined that the operation status of the target dimension is abnormal, and the electronic device can output an alarm message that the monitoring result of the target dimension of the service system is abnormal to remind the relevant maintenance personnel to perform fault repair processing on the target dimension .
  • the monitoring method provided by the above embodiment of the present invention includes: determining the target dimension to be monitored in the service system, where the target dimension includes any one of the infrastructure dimension, interface dimension, and user dimension of the service system; selecting to match the target dimension Execute the monitoring program that matches the target dimension, and obtain the monitoring result of the corresponding target dimension, where the monitoring result is either normal or abnormal; when the monitoring result is abnormal, output the monitoring of the target dimension of the service system The result is abnormal alarm information.
  • the target dimension is the infrastructure dimension of the service system.
  • the monitoring value of the stability of the infrastructure is calculated by using the number of correctly returned request data and the number of all requests received.
  • the monitoring value of the stability of the infrastructure is greater than or equal to the first threshold, it is determined that the monitoring result of the stability of the infrastructure is normal.
  • the monitoring value of the stability of the infrastructure is less than the first threshold, it is determined that the monitoring result of the stability of the infrastructure is abnormal.
  • the number of times that the requested data is correctly returned and the number of all requests received are used to calculate the monitoring value of the stability of the infrastructure, including:
  • the overall stability index of the service can be used to determine whether the infrastructure has a problem.
  • possible problems include network connection problems, database stability problems, and so on. Once such a problem occurs, the most intuitive manifestation is the decline in service stability. Through this indicator, it can be known for the first time that there is a problem with the infrastructure.
  • the calculation method of service stability is the total number of correct returns of the service framework divided by the total number of requests. If it is the first 10 minutes that the stability has decreased, it can be determined that the stability of a certain type of basic service has decreased in the current state.
  • the target dimension is the interface dimension of the service system
  • the interface parameter is used to calculate the interface monitoring value of the service system.
  • the monitoring type of the interface dimension includes any one of the interface access rate and the average delay of the interface.
  • the monitoring type of the interface dimension is the interface access rate
  • the interface parameters of the collection service system include:
  • the interface access rate of the service system can be used to judge the logical correctness of each interface and the real-time access rate. If the real-time error rate of a single interface is too high, it indicates that there is an error in the service logic. If there is an increase in traffic on an interface, it indicates that there is an inflow of abnormal traffic. If the overall access rate of the service fluctuates, it indicates that there is a disconnection from the upstream service, and it may be an abnormal upstream service.
  • the method for calculating the access rate of each interface is to obtain the derivation of the total access volume at the current time. Of course, other monitoring indicators for the interface can also be set, which is not limited.
  • the monitoring type of the interface dimension is the average delay of the interface
  • the interface parameters of the collection service system include:
  • the average delay of the interface can be used to judge the rationality of the processing logic.
  • the average delay of each interface is calculated by subtracting the request entry time from the request exit time. If the average delay of a certain type of interface is too high, it indicates that the internal processing logic is unreasonable. Many problems were not effectively exposed when the system was just generated because the amount of data was too low. However, as the system usage time increases and the amount of data continues to increase, various slow queries will appear in the database, and the batch acquisition interface will increase delays due to circular calls downstream. If it is not handled in time, it may overwhelm the database or downstream problems, leading to a service avalanche.
  • the target dimension is the user dimension:
  • the access rate of the user is collected.
  • the third threshold If the user's access rate is less than or equal to the third threshold, it is determined that the monitoring result of the user dimension is normal.
  • the user's access rate is the user's real-time access rate or the user's total access rate in a preset time period.
  • the user access rate can be used to determine whether a user has malicious access.
  • the method for calculating the number of visits by a single user is to count and count the unique identification of the user. If the total number of visits of a single user throughout the day exceeds the threshold, it means that the user may have crawled the service. Need to check the current user's access chain to prevent users from crawling unreasonable data. If the real-time access rate of a single user is too high, it means that the user may have maliciously accessed the interface, and maliciously obtained certain resources that need to be competed.
  • the target dimension also includes the computer room cluster dimension of the service system
  • the calculation of the access rate of the computer room cluster is based on the statistics of the geographical location of the computer room. This type of service indicator can be used to judge whether the load balancing is reasonable.
  • a cluster In order to monitor access to a certain area in China, a cluster has been established in this area. There are also overseas clusters overseas. The traffic is not shared with each other, and the destination of the traffic can be visually observed.
  • the monitoring method provided by the above embodiment of the present invention ranges from the overall stability of the service, the access rate of each interface, the access accuracy rate of each interface, the access error rate of each interface, the average delay of each interface, the number of visits of a single user, and the single Dimensions such as user access rate and computer room cluster access rate realize comprehensive monitoring of the service system.
  • the abnormal situation should be notified as soon as possible, the possible cause of the abnormality can be obtained as soon as possible, and the effect after repair should be observed as soon as possible.
  • an embodiment of the present application also provides a monitoring device 20, including:
  • the determining module 201 is used to determine the target dimension to be monitored in the service system, where the target dimension includes any one of the infrastructure dimension, interface dimension, and user dimension of the service system.
  • the selection module 201 is used to select a monitoring solution that matches the target dimension.
  • the execution module 203 is configured to execute a monitoring solution matching the target dimension to obtain a monitoring result corresponding to the target dimension, where the monitoring result is either normal or abnormal.
  • the output module 204 is used for outputting the alarm information of the abnormal monitoring result of the target dimension of the service system when the monitoring result is abnormal.
  • the target dimension is the infrastructure dimension of the service system;
  • the execution module 204 is specifically used to: collect the number of correct return request data of the basic framework and the number of all requests received; use the correct return request according to a preset algorithm The number of data and the number of all requests received are used to calculate the monitoring value of infrastructure stability; if the monitoring value of infrastructure stability is greater than or equal to the first threshold, it is determined that the monitoring result of infrastructure stability is normal; If the monitoring value of the architecture stability is less than the first threshold, it is determined that the monitoring result of the infrastructure stability is abnormal.
  • the execution module 204 calculates the monitoring value of the stability of the infrastructure by using the number of correctly returned request data and the number of all requests received according to a preset algorithm, it is specifically used to: calculate the number of times the requested data is correctly returned The ratio of the number of total requests received is used as a monitoring value for the stability of the infrastructure.
  • the target dimension is the interface dimension of the service system; the execution module 204 is specifically used to: collect interface parameters of the service system; use the interface parameters to calculate the interface monitoring value of the service system according to a preset algorithm; if the interface monitoring value is greater than or equal to The second threshold value determines that the monitoring result of the interface of the service system is normal; if the interface monitoring value is less than the second threshold value, it is determined that the monitoring result of the interface of the service system is abnormal.
  • the monitoring type of the interface dimension includes any one of the interface access rate and the average delay of the interface.
  • the monitoring type of the interface dimension is the interface access rate; when the execution module 204 collects the interface parameters of the service system, it is specifically used to: collect the total interface access volume of the service system at the current time; the execution module 204 is based on a preset algorithm, When the interface parameter is used to calculate the interface monitoring value of the service system, it is specifically used to: derive the total access volume at the current time to obtain the interface access rate of the service system.
  • the monitoring type of the interface dimension is the average delay of the interface; when the execution module 204 collects the interface parameters of the service system, it is specifically used to: collect the request exit time and request entry time corresponding to the interface of the service system; the execution module 204 is in According to the preset algorithm, when the interface parameter is used to calculate the interface monitoring value of the service system, it is specifically used to: subtract the request entry time from the request exit time to obtain the average delay of the interface of the service system.
  • the target dimension is the user dimension
  • the execution module 204 is specifically configured to: collect the user's access rate according to the unique identifier of the user; if the user's access rate is less than or equal to the third threshold, determine that the monitoring result of the user dimension is normal; If the user's access rate is greater than the third threshold, it is determined that the monitoring result of the user dimension is abnormal.
  • the user's access rate is the user's real-time access rate or the user's total access rate in a preset time period.
  • the target dimension also includes the computer room cluster dimension of the service system; the execution module 204 is specifically used to: collect the access rate of the computer room cluster; if the access rate equilibrium state of the computer room cluster meets the preset requirements, determine the computer room cluster of the service system The load balance is normal; if the access rate balance state of the computer room cluster does not meet the preset requirements, it is determined that the load balance of the computer room cluster of the service system is abnormal.
  • the device shown in FIG. 2 can correspondingly execute the content in the foregoing method embodiment.
  • At least one processor and a memory communicatively connected with the at least one processor; wherein the memory stores an instruction executable by the at least one processor, and the instruction is executed by the at least one processor so that the at least one processor
  • the processor can execute the monitoring method in the foregoing method embodiment.
  • the embodiments of the present application also provide a computer-readable storage medium that stores computer instructions, and the computer instructions are used to make the computer execute the monitoring method in the foregoing method embodiments.
  • the embodiments of the present application also provide a computer program product.
  • the computer program product includes a calculation program stored on a computer-readable storage medium.
  • the computer program includes program instructions that, when executed by a computer, cause the computer to execute The monitoring method in the foregoing method embodiment.
  • FIG. 3 shows a schematic structural diagram of an electronic device 30 suitable for implementing the embodiments of the present application.
  • the electronic devices in the embodiments of this application may include, but are not limited to, mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (e.g. Mobile terminals such as car navigation terminals) and fixed terminals such as digital TVs, desktop computers, etc.
  • the electronic device shown in FIG. 3 is only an example, and should not bring any limitation to the function and scope of use of the embodiments of the present application.
  • the electronic device 30 may include a processing device (such as a central processing unit, a graphics processor, etc.) 301, which may be loaded into a random access device according to a program stored in a read-only memory (ROM) 302 or from a storage device 308
  • the program in the memory (RAM) 303 executes various appropriate actions and processing.
  • various programs and data required for the operation of the electronic device 30 are also stored.
  • the processing device 301, the ROM 302, and the RAM 303 are connected to each other through a bus 304.
  • An input/output (I/O) interface 305 is also connected to the bus 304.
  • the following devices can be connected to the I/O interface 305: including input devices 306 such as touch screens, touch pads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; including, for example, liquid crystal displays (LCD), speakers, An output device 307 such as a vibrator; a storage device 308 such as a magnetic tape, a hard disk, etc.; and a communication device 309.
  • the communication device 309 may allow the electronic device 30 to perform wireless or wired communication with other devices to exchange data.
  • the figure shows the electronic device 30 with various devices, it should be understood that it is not required to implement or have all the devices shown. It may be implemented alternatively or provided with more or fewer devices.
  • the process described above with reference to the flowchart can be implemented as a computer software program.
  • the embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program code for executing the method shown in the flowchart.
  • the computer program may be downloaded and installed from the network through the communication device 309, or installed from the storage device 308, or installed from the ROM 302.
  • the processing device 301 the above-mentioned functions defined in the method of the embodiment of the present application are executed.
  • the above-mentioned computer-readable medium in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two.
  • the computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable removable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • the computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium.
  • the computer-readable signal medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device .
  • the program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wire, optical cable, RF (Radio Frequency), etc., or any suitable combination of the above.
  • the above-mentioned computer-readable medium may be included in the above-mentioned electronic device; or it may exist alone without being assembled into the electronic device.
  • the foregoing computer-readable medium carries one or more programs, and when the foregoing one or more programs are executed by the electronic device, the electronic device can implement the solutions provided by the foregoing method embodiments.
  • the aforementioned computer-readable medium carries one or more programs, and when the aforementioned one or more programs are executed by the electronic device, the electronic device can implement the solutions provided by the aforementioned method embodiments.
  • the computer program code used to perform the operations of the present application can be written in one or more programming languages or a combination thereof.
  • the above-mentioned programming languages include object-oriented programming languages—such as Java, Smalltalk, C++, and also conventional Procedural programming language-such as "C" language or similar programming language.
  • the program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server.
  • the remote computer can be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, using an Internet service provider to pass Internet connection).
  • LAN local area network
  • WAN wide area network
  • each block in the flowchart or block diagram may represent a module, program segment, or part of code, and the module, program segment, or part of code contains one or more for realizing the specified logical function Executable instructions.
  • the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown one after another can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved.
  • each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.
  • the units involved in the embodiments described in this application can be implemented in software or hardware. Wherein, the name of the unit does not constitute a limitation on the unit itself under certain circumstances.
  • the first obtaining unit can also be described as "a unit for obtaining at least two Internet Protocol addresses.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种监控方法、装置及电子设备，属于计算机应用技术领域，该方法包括：确定服务系统中待监控的目标维度，其中，所述目标维度包括所述服务系统的基础架构维度、接口维度和用户维度中的任一种（S101）；选择与所述目标维度匹配的监控方案（S102）；执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，其中，所述监控结果为正常和异常中的任一种（S103）；在所述监控结果为异常时，输出所述服务系统的目标维度的监控结果异常的报警信息（S104）。通过该监控方法，实现了针对服务系统的全面、自动的监控方案，提高了服务系统的监控效率，较大程度地保证了正常运行和异常及时修复功能。

Description

监控方法、装置及电子设备
本申请要求于2020年1月22日提交中国专利局、申请号为202010073543.1、申请名称为“监控方法、装置及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机应用技术领域，更为具体地，涉及一种监控方法、装置及电子设备。
背景技术
随着计算机应用技术的发展，终端与服务系统之间的交互构成了主要网络。服务系统承载着数以万计的终端的访问请求，网络服务系统的运行状态影响巨大。
可见，现有亟需一种高效、全面的针对服务系统的监控方案。
发明内容
本申请的目的在于提供一种监控方法、装置及电子设备。通过确定并选择与所述目标维度匹配的监控方案对服务系统进行监测，可以实现对服务系统不同维度的监控，提高服务系统监控的全面性和准确性，提高服务系统的监控效率。
第一方面，本申请公开了一种监控方法，包括：确定服务系统中待监控的目标维度，其中，所述目标维度包括所述服务系统的基础架构维度、接口维度和用户维度中的任一种；选择与所述目标维度匹配的监控方案；执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，其中，所述监控结果为正常和异常中的任一种；在所述监控结果为异常时，输出所述服务系统的目标维度的监控结果异常的报警信息。
基于上述技术内容，通过确定服务系统中待监控的目标维度，并选择与所述目标维度匹配的监控方案进行监测，获得对应所述目标维度的监控结果，在监控结果为异常时输出所述服务系统的目标维度的监控结果异常的报警信息，由于目标维度包括服务系统的基础架构维度、接口维度和用户维度中的任一种，因此，可以实现服务系统不同维度的监控，提高服务系统监控的全面性和准确性，提高了服务系统的监控效率，保证了正常运行和异常及时修复功能。
可选的，所述目标维度为所述服务系统的基础架构维度；所述执行与所述目标维度匹配的监控方案，包括：采集所述基础框架的正确返回请求数据的次数和所接收的全部请求的次数；依据预设算法，利用所述正确返回请求数据的次数和所接收的全部请求的次数，计算所述基础架构稳定性的监控值；若所述基础架构稳定性的监控值大于或者等于第一阈值，则确定所述基础架构稳定性的监控结果为正常；若所述基础架构稳定性的监控值小于所述第一阈值，则确定所述基础架构稳定性的监控结果为异常。
基于上述技术内容，通过采集所述基础框架的正确返回请求数据的次数和所接收的全 部请求的次数，计算所述基础架构稳定性的监控值，并根据监控值与第一阈值的大小，实现执行与服务系统的基础架构维度匹配的监控方案，进一步的提高对服务系统基础架构维度运行状态的监测准确性。
可选的，所述依据预设算法，利用所述正确返回请求数据的次数和所接收的全部请求的次数，计算所述基础架构稳定性的监控值，包括：计算所述正确返回请求数据的次数和所接收的全部请求的次数的比值，作为所述基础架构稳定性的监控值。
可选的，所述目标维度为所述服务系统的接口维度；所述执行与所述目标维度匹配的监控方案，包括：采集所述服务系统的接口参数；依据预设算法，利用所述接口参数计算所述服务系统的接口监控值；若所述接口监控值大于或者等于第二阈值，则确定所述服务系统的接口的监控结果正常；若所述接口监控值小于所述第二阈值，则确定所述服务系统的接口的监控结果异常。
基于上述技术内容，通过采集所述服务系统的接口参数，利用所述接口参数计算所述服务系统的接口监控值，并根据接口监控值与第二阈值的大小，实现执行与服务系统的接口维度匹配的监控方案，进一步的提高对服务系统的接口维度运行状态的监测准确性。
可选的，所述接口维度的监控类型包括接口访问率和接口平均延时中的任一种。
可选的，所述接口维度的监控类型为接口访问率；所述采集所述服务系统的接口参数，包括：采集所述服务系统当前时间的接口总访问量；所述依据预设算法，利用所述接口参数计算所述服务系统的接口监控值，包括：对所述当前时间总访问量求导，得到所述服务系统的接口访问率。
基于上述技术内容，通过采集所述服务系统当前时间的接口总访问量，对所述当前时间总访问量求导，得到所述服务系统的接口访问率，利用接口访问率监测服务系统的接口维度的运行状态，进一步的提高对服务系统的接口维度运行状态的监测准确性。
可选的，所述接口维度的监控类型为接口平均延时；所述采集所述服务系统的接口参数，包括：采集所述服务系统的接口对应的请求出口时间和请求入口时间；所述依据预设算法，利用所述接口参数计算所述服务系统的接口监控值，包括：将请求出口时间减去请求入口时间，得到所述服务系统的接口平均延时。
可选的，所述目标维度为用户维度：所述执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，包括：依据用户的唯一标识，采集用户的访问率；若所述用户的访问率小于或者等于第三阈值，则确定所述用户维度的监控结果正常；若所述用户的访问率大于所述第三阈值，则确定所述用户维度的监控结果异常。
基于上述技术内容，通过依据用户的唯一标识，采集用户的访问率，根据访问率与第三阈值的大小关系，判断用户维度的监控结果。利用用户的访问率监测服务系统用户维度的运行状态，进一步的提高对服务系统用户维度运行状态的监测准确性。
可选的，所述用户的访问率为所述用户的实时访问率或者所述用户在预设时段内的总访问率。
可选的，所述目标维度还包括所述服务系统的机房集群维度；所述执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，包括：采集所述机房集群的访问率；若所述机房集群的访问率均衡状态满足预设要求，则确定所述服务系统的机房集群的负载均衡正常；若所述机房集群的访问率均衡状态不满足预设要求，则确定所述服务系统 的机房集群的负载均衡异常。
基于上述技术内容，通过采集所述机房集群的访问率，并根据机房集群的访问率的均衡状态，判断服务系统的机房集群的负载均衡是否正常，进一步提高监测服务系统在机房集群维度的运行状态的准确性。
第二方面，本申请公开了一种监控装置。
确定模块，用于确定服务系统中待监控的目标维度，其中，所述目标维度包括所述服务系统的基础架构维度、接口维度和用户维度中的任一种；
选择模块，用于选择与所述目标维度匹配的监控方案；
执行模块，用于执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，其中，所述监控结果为正常和异常中的任一种；
输出模块，用于在所述监控结果为异常时，输出所述服务系统的目标维度的监控结果异常的报警信息。
可选的，所述目标维度为所述服务系统的基础架构维度；所述执行模块，具体用于：采集所述基础框架的正确返回请求数据的次数和所接收的全部请求的次数；依据预设算法，利用所述正确返回请求数据的次数和所接收的全部请求的次数，计算所述基础架构稳定性的监控值；若所述基础架构稳定性的监控值大于或者等于第一阈值，则确定所述基础架构稳定性的监控结果为正常；若所述基础架构稳定性的监控值小于所述第一阈值，则确定所述基础架构稳定性的监控结果为异常。
可选的，所述执行模块在依据预设算法，利用所述正确返回请求数据的次数和所接收的全部请求的次数，计算所述基础架构稳定性的监控值时，具体用于：计算所述正确返回请求数据的次数和所接收的全部请求的次数的比值，作为所述基础架构稳定性的监控值。
可选的，所述目标维度为所述服务系统的接口维度；所述执行模块具体用于：采集所述服务系统的接口参数；依据预设算法，利用所述接口参数计算所述服务系统的接口监控值；若所述接口监控值大于或者等于第二阈值，则确定所述服务系统的接口的监控结果正常；若所述接口监控值小于所述第二阈值，则确定所述服务系统的接口的监控结果异常。
可选的，所述接口维度的监控类型包括接口访问率和接口平均延时中的任一种。
可选的，所述接口维度的监控类型为接口访问率；所述执行模块在采集所述服务系统的接口参数时，具体用于：采集所述服务系统当前时间的接口总访问量；所述执行模块在依据预设算法，利用所述接口参数计算所述服务系统的接口监控值时，具体用于：对所述当前时间总访问量求导，得到所述服务系统的接口访问率。
可选的，所述接口维度的监控类型为接口平均延时；所述执行模块在采集所述服务系统的接口参数时，具体用于：采集所述服务系统的接口对应的请求出口时间和请求入口时间；所述执行模块在依据预设算法，利用所述接口参数计算所述服务系统的接口监控值时，具体用于：将请求出口时间减去请求入口时间，得到所述服务系统的接口平均延时。
可选的，所述目标维度为用户维度；所述执行模块具体用于：依据用户的唯一标识，采集用户的访问率；若所述用户的访问率小于或者等于第三阈值，则确定所述用户维度的监控结果正常；若所述用户的访问率大于所述第三阈值，则确定所述用户维度的监控结果异常。
可选的，所述用户的访问率为所述用户的实时访问率或者所述用户在预设时段内的总 访问率。
可选的，所述目标维度还包括所述服务系统的机房集群维度；所述执行模块具体用于：采集所述机房集群的访问率；若所述机房集群的访问率均衡状态满足预设要求，则确定所述服务系统的机房集群的负载均衡正常；若所述机房集群的访问率均衡状态不满足预设要求，则确定所述服务系统的机房集群的负载均衡异常。
第三方面，本申请实施例还提供了一种电子设备，该电子设备包括：
至少一个处理器；以及，与该至少一个处理器通信连接的存储器；其中，该存储器存储有可被该至少一个处理器执行的指令，该指令被该至少一个处理器执行，以使该至少一个处理器能够执行前述第一方面或第一方面的任一实现方式中的监控方法。
第四方面，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储计算机指令，该计算机指令用于使该计算机执行前述第一方面或第一方面的任一实现方式中的监控方法。
第五方面，本申请实施例还提供了一种计算机程序产品，该计算机程序产品包括存储在计算机可读存储介质上的计算程序，该计算机程序包括程序指令，当该程序指令被计算机执行时，使该计算机执行前述第一方面或第一方面的任一实现方式中的监控方法。
结合上述技术方案，本申请通过确定服务系统中待监控的目标维度，并选择与所述目标维度匹配的监控方案进行监测，获得对应所述目标维度的监控结果，在监控结果为异常时输出所述服务系统的目标维度的监控结果异常的报警信息，目标维度包括服务系统的基础架构维度、接口维度、用户维度等多个维度中的任一种，因此，可以实现服务系统对不同维度的运行状态的监控，提高服务系统监控的全面性和准确性，通过本申请的方案，实现了针对服务系统的全面、自动的监控方案，提高了服务系统的监控效率，保证了正常运行和异常及时修复功能。
第六方面，本申请实施例还提供了一种服务系统，该服务系统包括前述第三方面所述的电子设备。
附图说明
图1为本申请实施例提供的一种监控方法的流程示意图；
图2为本申请实施例提供的一种监控装置的结构示意图；
图3为本申请实施例提供的电子设备的示意图。
具体实施方式
下面结合附图对本申请实施例进行详细描述。
以下通过特定的具体实例说明本申请的实施方式，本领域技术人员可由本说明书所揭露的内容轻易地了解本申请的其他优点与功效。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。本申请还可以通过另外不同的具体实施方式加以实施或应用，本说明书中的各项细节也可以基于不同观点与应用，在没有背离本申请的精神下进行各种修饰或改变。需说明的是，在不冲突的情况下，以下实施例及实施例中的特征可以相互组合。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
需要说明的是，下文描述在所附权利要求书的范围内的实施例的各种方面。应显而易见，本文中所描述的方面可体现于广泛多种形式中，且本文中所描述的任何特定结构及/或功能仅为说明性的。基于本申请，所属领域的技术人员应了解，本文中所描述的一个方面可与任何其它方面独立地实施，且可以各种方式组合这些方面中的两者或两者以上。举例来说，可使用本文中所阐述的任何数目个方面来实施设备及/或实践方法。另外，可使用除了本文中所阐述的方面中的一或多者之外的其它结构及/或功能性实施此设备及/或实践此方法。
还需要说明的是，以下实施例中所提供的图示仅以示意方式说明本申请的基本构想，图式中仅显示与本申请中有关的组件而非按照实际实施时的组件数目、形状及尺寸绘制，其实际实施时各组件的型态、数量及比例可为一种随意的改变，且其组件布局型态也可能更为复杂。
另外，在以下描述中，提供具体细节是为了便于透彻理解实例。然而，所属领域的技术人员将理解，可在没有这些特定细节的情况下实践所述方面。
本申请实施例提供一种监控方法。本实施例提供的监控方法可以由一计算装置来执行，该计算装置可以实现为软件，或者实现为软件和硬件的组合，该计算装置可以集成设置在服务器、终端设备等中。
参见图1，本申请实施例提供的一种监控方法，包括：
S101，确定服务系统中待监控的目标维度，其中，目标维度包括服务系统的基础架构维度、接口维度和用户维度中的任一种。
本实施例提供的监控方法，用于实现对服务系统的多维度监控。方法可以应用于服务系统内置的监控模块，也可以应用于服务系统外接的电子设备，以执行对该服务系统的监控操作。所应用的服务系统可以为开放账号服务系统。具体实施时，可以在服务系统的关键性入口和出口进行埋点，其他的一些监控参数还可以通过远程字典服务(Remote Dictionary Server，简称Redis)等统计工具来统计，最终的数据展示可以通过可视化工具进行数据展示。
在具体的监控过程中，服务系统的监控维度可以分为多种，所针对的监控层面也不同。例如，从服务系统的基础架构维度来监控系统整体层面的稳定性，从接口维度或者用户维度来监控系统局部运行层面的稳定性。
S102，选择与目标维度匹配的监控方案。
电子设备内预先存储有针对不同维度的监控方案，每个监控方案都可以包含针对该维度监控所需要采集的初始参数、所依据的计算规则、以及计算结果的评判规则等内容。在确定当前要监控的目标维度后，即可选择与目标维度匹配的监控方案。
S103，执行与目标维度匹配的监控方案，获得对应目标维度的监控结果，其中，监控结果为正常和异常中的任一种。
电子设备在选择与当前监控的目标维度匹配的监控方案之后，即可执行所匹配的监控方案，并获得对应该目标维度的监控结果，通过监控结果来指示该目标维度的运行状态正常或者异常。
S104，在监控结果为异常时，输出服务系统的目标维度的监控结果异常的报警信息。
若该目标维度的监控结果为正常，则可以认定该目标维度运行状态正常，无需进行故 障修复处理。若该目标维度的监控结果为异常，则可以认定该目标维度运行状态异常，电子设备可以输出服务系统的目标维度的监控结果异常的报警信息，以提示相关维护人员对应该目标维度进行故障修复处理。
此外，需要说明的是，本实施方式仅针对单次监控操作来解释，实际监控过程中，可以周期性地针对不同维度均进行监控，每次监控流程同本实施例公开的监控过程，这样可以保证对服务系统持续、全面地监控。
上述本发明实施例提供的监控方法，包括：确定服务系统中待监控的目标维度，其中，目标维度包括服务系统的基础架构维度、接口维度和用户维度中的任一种；选择与目标维度匹配的监控方案；执行与目标维度匹配的监控方案，获得对应目标维度的监控结果，其中，监控结果为正常和异常中的任一种；在监控结果为异常时，输出服务系统的目标维度的监控结果异常的报警信息。通过本申请的方案，实现了针对服务系统的全面、自动的监控方案，提高了服务系统的监控效率，较大程度地保证了正常运行和异常及时修复功能。
下面，将从各维度对应的监控方案来具体解释上述实施例。
根据本申请实施例的一种具体实现方式，目标维度为服务系统的基础架构维度。
执行与目标维度匹配的监控方案，包括：
采集基础框架的正确返回请求数据的次数和所接收的全部请求的次数；
依据预设算法，利用正确返回请求数据的次数和所接收的全部请求的次数，计算基础架构稳定性的监控值。
若基础架构稳定性的监控值大于或者等于第一阈值，则确定基础架构稳定性的监控结果为正常。
若基础架构稳定性的监控值小于第一阈值，则确定基础架构稳定性的监控结果为异常。
进一步地，依据预设算法，利用正确返回请求数据的次数和所接收的全部请求的次数，计算基础架构稳定性的监控值，包括：
计算正确返回请求数据的次数和所接收的全部请求的次数的比值，作为基础架构稳定性的监控值。
服务整体稳定性指标可以用来判断是否是基础架构出了问题。在产品依赖的基础架构中，可能出现问题的情况有网络连接问题、数据库稳定性问题等。这类问题一旦出现最直观的表现是在服务稳定性的下降，通过该指标可以第一时间知晓是基础架构出了问题。服务稳定性的计算方法是服务框架正确返回总数除以总请求数。如果是第一个10分钟内的稳定性下降，可以判定是当前状态下某类基础服务稳定性下降。
根据本申请实施例的另一种具体实现方式，目标维度为服务系统的接口维度；
执行与目标维度匹配的监控方案，包括：
采集服务系统的接口参数。
依据预设算法，利用接口参数计算服务系统的接口监控值。
若接口监控值大于或者等于第二阈值，则确定服务系统的接口的监控结果正常；
若接口监控值小于第二阈值，则确定服务系统的接口的监控结果异常。
根据本申请实施例的一种具体实现方式，接口维度的监控类型包括接口访问率和接口平均延时中的任一种。
根据本申请实施例的一种具体实现方式，接口维度的监控类型为接口访问率；
采集服务系统的接口参数，包括：
采集服务系统当前时间的接口总访问量。
依据预设算法，利用接口参数计算服务系统的接口监控值，包括：
对当前时间总访问量求导，得到服务系统的接口访问率。
服务系统的接口访问率可以用来判断各个接口的逻辑正确性、实时访问率的问题。如果是单一接口的实时错误率过高，说明服务逻辑出现了错误。如果某个接口出现了流量的徒增，说明有异常流量的流入。如果服务整体的访问率抖降，说明与上游服务产生了脱离，可能是上游服务异常。各个接口各类的访问率的计算方法是当前时间总访问量求导，当然也可以设置其他针对接口的监控指标，不作限定。
根据本申请实施例的一种具体实现方式，接口维度的监控类型为接口平均延时；
采集服务系统的接口参数，包括：
采集服务系统的接口对应的请求出口时间和请求入口时间。
依据预设算法，利用接口参数计算服务系统的接口监控值，包括：
将请求出口时间减去请求入口时间，得到服务系统的接口平均延时。
接口的平均延时可以用来判断处理逻辑的合理性。各个接口的平均延时的计算方法是请求出口时间减去请求入口时间。如果是某一类接口的平均延时过高，说明内部处理逻辑存在不合理的地方。很多问题在系统刚刚产生的时候因为数据量过低并不能有效暴露。但是随着系统使用时间的增加，数据量的持续增长，数据库会出现各类慢查询，批量获取接口会因为循环调用下游而出现延迟增加。如果不及时处理可能会导致压垮数据库或者下游的问题，导致服务雪崩。
根据本申请实施例的另一种具体实现方式，目标维度为用户维度：
执行与目标维度匹配的监控方案，获得对应目标维度的监控结果，包括：
依据用户的唯一标识，采集用户的访问率。
若用户的访问率小于或者等于第三阈值，则确定用户维度的监控结果正常。
若用户的访问率大于第三阈值，则确定用户维度的监控结果异常。
可选的，用户的访问率为用户的实时访问率或者用户在预设时段内的总访问率。
用户访问率可以用来判断是否有用户进行恶意访问。单一用户访问次数的计算方法是对用户唯一标识进行计数统计。如果某单一用户全天总访问量超过阈值，说明该用户可能对于服务进行了爬取。需要查看当前用户的访问链，以防止用户爬取不合理的数据。如果是单一用户的实时访问率过高，说明该用户可能进行了恶意刷接口访问，对于某些需要进行竞争的资源恶意获取。
根据本申请实施例的另一种具体实现方式，目标维度还包括服务系统的机房集群维度；
执行与目标维度匹配的监控方案，获得对应目标维度的监控结果，包括：
采集机房集群的访问率。
若机房集群的访问率均衡状态满足预设要求，则确定服务系统的机房集群的负载均衡正常。
若机房集群的访问率均衡状态不满足预设要求，则确定服务系统的机房集群的负载均衡异常。
机房集群的访问率的计算是对于机房的地理位置进行了打点统计。该类服务指标可以 用来判断负载均衡是否合理。为监控针对国内某区域的访问，该地区建立了一个集群，海外还有海外集群，流量互不共享，流量到达地可以直观观察。
上述本发明实施例提供的监控方法从服务的整体稳定性、各接口的访问率、各接口的访问正确率、各接口的访问错误率、各个接口的平均延时、单一用户的访问次数、单一用户的访问率、机房集群的访问率等维度实现对服务系统的全面监控。提供了对服务系统的全局稳定性的可视化监控，再配合设定监控报警机制可以有效的知晓服务的健康状况。对于异常情况做到第一时间告知，第一时间获得可能异常原因，第一时间观察修复后的效果。
与上面的方法实施例相对应，参见图2，本申请实施例还提供了一种监控装置20，包括：
确定模块201，用于确定服务系统中待监控的目标维度，其中，目标维度包括服务系统的基础架构维度、接口维度和用户维度中的任一种。
选择模块201，用于选择与目标维度匹配的监控方案。
执行模块203，用于执行与目标维度匹配的监控方案，获得对应目标维度的监控结果，其中，监控结果为正常和异常中的任一种。
输出模块204，用于在监控结果为异常时，输出服务系统的目标维度的监控结果异常的报警信息。
可选的，目标维度为服务系统的基础架构维度；执行模块204，具体用于：采集基础框架的正确返回请求数据的次数和所接收的全部请求的次数；依据预设算法，利用正确返回请求数据的次数和所接收的全部请求的次数，计算基础架构稳定性的监控值；若基础架构稳定性的监控值大于或者等于第一阈值，则确定基础架构稳定性的监控结果为正常；若基础架构稳定性的监控值小于第一阈值，则确定基础架构稳定性的监控结果为异常。
可选的，执行模块204在依据预设算法，利用正确返回请求数据的次数和所接收的全部请求的次数，计算基础架构稳定性的监控值时，具体用于：计算正确返回请求数据的次数和所接收的全部请求的次数的比值，作为基础架构稳定性的监控值。
可选的，目标维度为服务系统的接口维度；执行模块204具体用于：采集服务系统的接口参数；依据预设算法，利用接口参数计算服务系统的接口监控值；若接口监控值大于或者等于第二阈值，则确定服务系统的接口的监控结果正常；若接口监控值小于第二阈值，则确定服务系统的接口的监控结果异常。
可选的，接口维度的监控类型包括接口访问率和接口平均延时中的任一种。
可选的，接口维度的监控类型为接口访问率；执行模块204在采集服务系统的接口参数时，具体用于：采集服务系统当前时间的接口总访问量；执行模块204在依据预设算法，利用接口参数计算服务系统的接口监控值时，具体用于：对当前时间总访问量求导，得到服务系统的接口访问率。
可选的，接口维度的监控类型为接口平均延时；执行模块204在采集服务系统的接口参数时，具体用于：采集服务系统的接口对应的请求出口时间和请求入口时间；执行模块204在依据预设算法，利用接口参数计算服务系统的接口监控值时，具体用于：将请求出口时间减去请求入口时间，得到服务系统的接口平均延时。
可选的，目标维度为用户维度；执行模块204具体用于：依据用户的唯一标识，采集用户的访问率；若用户的访问率小于或者等于第三阈值，则确定用户维度的监控结果正常； 若用户的访问率大于第三阈值，则确定用户维度的监控结果异常。
可选的，用户的访问率为用户的实时访问率或者用户在预设时段内的总访问率。
可选的，目标维度还包括服务系统的机房集群维度；执行模块204具体用于：采集机房集群的访问率；若机房集群的访问率均衡状态满足预设要求，则确定服务系统的机房集群的负载均衡正常；若机房集群的访问率均衡状态不满足预设要求，则确定服务系统的机房集群的负载均衡异常。
图2所示装置可以对应的执行上述方法实施例中的内容，本实施例未详细描述的部分，参照上述方法实施例中记载的内容，在此不再赘述。
参见图3，本申请实施例还提供了一种电子设备30，该电子设备包括：
至少一个处理器；以及，与该至少一个处理器通信连接的存储器；其中，该存储器存储有可被该至少一个处理器执行的指令，该指令被该至少一个处理器执行，以使该至少一个处理器能够执行前述方法实施例中的监控方法。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储计算机指令，该计算机指令用于使该计算机执行前述方法实施例中的监控方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品包括存储在计算机可读存储介质上的计算程序，该计算机程序包括程序指令，当该程序指令被计算机执行时，使该计算机执行前述方法实施例中的监控方法。
下面参考图3，其示出了适于用来实现本申请实施例的电子设备30的结构示意图。本申请实施例中的电子设备可以包括但不限于诸如移动电话、笔记本电脑、数字广播接收器、PDA(个人数字助理)、PAD(平板电脑)、PMP(便携式多媒体播放器)、车载终端(例如车载导航终端)等等的移动终端以及诸如数字TV、台式计算机等等的固定终端。图3示出的电子设备仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图3所示，电子设备30可以包括处理装置(例如中央处理器、图形处理器等)301，其可以根据存储在只读存储器(ROM)302中的程序或者从存储装置308加载到随机访问存储器(RAM)303中的程序而执行各种适当的动作和处理。在RAM 303中，还存储有电子设备30操作所需的各种程序和数据。处理装置301、ROM 302以及RAM 303通过总线304彼此相连。输入/输出(I/O)接口305也连接至总线304。
通常，以下装置可以连接至I/O接口305：包括例如触摸屏、触摸板、键盘、鼠标、图像传感器、麦克风、加速度计、陀螺仪等的输入装置306；包括例如液晶显示器(LCD)、扬声器、振动器等的输出装置307；包括例如磁带、硬盘等的存储装置308；以及通信装置309。通信装置309可以允许电子设备30与其他设备进行无线或有线通信以交换数据。虽然图中示出了具有各种装置的电子设备30，但是应理解的是，并不要求实施或具备所有示出的装置。可以替代地实施或具备更多或更少的装置。
特别地，根据本申请的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本申请的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信装置309从网络上被下载和安装，或者从存储装置308被安装，或者从ROM302被安装。在该计算机程序被处理装置301执行时，执行本申请实施例的方法中限定的上述功能。
需要说明的是，本申请上述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中，计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读信号介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：电线、光缆、RF(射频)等等，或者上述的任意合适的组合。
上述计算机可读介质可以是上述电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。
上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该电子设备执行时，使得该电子设备能够实现上述方法实施例提供的方案。
或者，上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该电子设备执行时，使得该电子设备能够实现上述方法实施例提供的方案。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请的操作的计算机程序代码，上述程序设计语言包括面向对象的程序设计语言—诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络——包括局域网(LAN)或广域网(WAN)—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的 方式来实现。其中，单元的名称在某种情况下并不构成对该单元本身的限定，例如，第一获取单元还可以被描述为“获取至少两个网际协议地址的单元”。
应当理解，本申请的各部分可以用硬件、软件、固件或它们的组合来实现。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (15)

  1. 一种监控方法的方法，其特征在于，包括：
    确定服务系统中待监控的目标维度，其中，所述目标维度包括所述服务系统的基础架构维度、接口维度和用户维度中的任一种；
    选择与所述目标维度匹配的监控方案；
    执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，其中，所述监控结果为正常和异常中的任一种；
    在所述监控结果为异常时，输出所述服务系统的目标维度的监控结果异常的报警信息。
  2. 根据权利要求1所述的方法，其特征在于，所述目标维度为所述服务系统的基础架构维度；
    所述执行与所述目标维度匹配的监控方案，包括：
    采集基础框架的正确返回请求数据的次数和所接收的全部请求的次数；
    依据预设算法，利用所述正确返回请求数据的次数和所接收的全部请求的次数，计算所述基础架构稳定性的监控值；
    若所述基础架构稳定性的监控值大于或者等于第一阈值，则确定所述基础架构稳定性的监控结果为正常；
    若所述基础架构稳定性的监控值小于所述第一阈值，则确定所述基础架构稳定性的监控结果为异常。
  3. 根据权利要求2所述的方法，其特征在于，所述依据预设算法，利用所述正确返回请求数据的次数和所接收的全部请求的次数，计算所述基础架构稳定性的监控值，包括：
    计算所述正确返回请求数据的次数和所接收的全部请求的次数的比值，作为所述基础架构稳定性的监控值。
  4. 根据权利要求1所述的方法，其特征在于，所述目标维度为所述服务系统的接口维度；
    所述执行与所述目标维度匹配的监控方案，包括：
    采集所述服务系统的接口参数；
    依据预设算法，利用所述接口参数计算所述服务系统的接口监控值；
    若所述接口监控值大于或者等于第二阈值，则确定所述服务系统的接口的监控结果正常；
    若所述接口监控值小于所述第二阈值，则确定所述服务系统的接口的监控结果异常。
  5. 根据权利要求4所述的方法，其特征在于，所述接口维度的监控类型包括接口访问率和接口平均延时中的任一种。
  6. 根据权利要求5所述的方法，其特征在于，所述接口维度的监控类型为接口访问率；
    所述采集所述服务系统的接口参数，包括：
    采集所述服务系统当前时间的接口总访问量；
    所述依据预设算法，利用所述接口参数计算所述服务系统的接口监控值，包括：
    对所述当前时间总访问量求导，得到所述服务系统的接口访问率。
  7. 根据权利要求5所述的方法，其特征在于，所述接口维度的监控类型为接口平均延时；
    所述采集所述服务系统的接口参数，包括：
    采集所述服务系统的接口对应的请求出口时间和请求入口时间；
    所述依据预设算法，利用所述接口参数计算所述服务系统的接口监控值，包括：
    将请求出口时间减去请求入口时间，得到所述服务系统的接口平均延时。
  8. 根据权利要求1所述的方法，其特征在于，所述目标维度为用户维度：
    所述执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，包括：
    依据用户的唯一标识，采集用户的访问率；
    若所述用户的访问率小于或者等于第三阈值，则确定所述用户维度的监控结果正常；
    若所述用户的访问率大于所述第三阈值，则确定所述用户维度的监控结果异常。
  9. 根据权利要求8所述的方法，其特征在于，所述用户的访问率为所述用户的实时访问率或者所述用户在预设时段内的总访问率。
  10. 根据权利要求1所述的方法，其特征在于，所述目标维度还包括所述服务系统的机房集群维度；
    所述执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，包括：
    采集所述机房集群的访问率；
    若所述机房集群的访问率均衡状态满足预设要求，则确定所述服务系统的机房集群的负载均衡正常；
    若所述机房集群的访问率均衡状态不满足预设要求，则确定所述服务系统的机房集群的负载均衡异常。
  11. 一种监控装置，其特征在于，包括：
    确定模块，用于确定服务系统中待监控的目标维度，其中，所述目标维度包括所述服务系统的基础架构维度、接口维度和用户维度中的任一种；
    选择模块，用于选择与所述目标维度匹配的监控方案；
    执行模块，用于执行与所述目标维度匹配的监控方案，获得对应所述目标维度的监控结果，其中，所述监控结果为正常和异常中的任一种；
    输出模块，用于在所述监控结果为异常时，输出所述服务系统的目标维度的监控结果异常的报警信息。
  12. 一种电子设备，其特征在于，所述电子设备包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行前述权利要求1-10中任一项所述的监控方法。
  13. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行权利要求1-10中任一项所述的监控方法。
  14. 一种计算机程序，其特征在于，包括程序代码，当计算机运行所述计算机程序时，所述程序代码执行如权利要求1-10中任一项所述的方法。
  15. 一种服务系统，其特征在于，包括如权利要求12所述的电子设备。
PCT/CN2020/128819 2020-01-22 2020-11-13 监控方法、装置及电子设备 WO2021147481A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010073543.1A CN111290924B (zh) 2020-01-22 2020-01-22 监控方法、装置及电子设备
CN202010073543.1 2020-01-22

Publications (1)

Publication Number Publication Date
WO2021147481A1 true WO2021147481A1 (zh) 2021-07-29

Family

ID=71030700

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/128819 WO2021147481A1 (zh) 2020-01-22 2020-11-13 监控方法、装置及电子设备

Country Status (2)

Country Link
CN (1) CN111290924B (zh)
WO (1) WO2021147481A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113472080A (zh) * 2021-07-30 2021-10-01 王雪梅 一种配电自动化监控方法、装置及电子设备
CN113626289A (zh) * 2021-08-27 2021-11-09 中国银行股份有限公司 一种用户活跃度监控方法及装置
CN113904951A (zh) * 2021-09-28 2022-01-07 济南浪潮数据技术有限公司 一种网关设备的数据监控方法、装置及相关设备
CN114760233A (zh) * 2022-03-22 2022-07-15 中国工商银行股份有限公司 业务处理方法、装置、电子设备及存储介质
CN115174358A (zh) * 2022-09-08 2022-10-11 浪潮电子信息产业股份有限公司 存储集群接口的监测处理方法、系统、设备及存储介质
CN116055496A (zh) * 2022-12-30 2023-05-02 广州趣研网络科技有限公司 一种监控数据采集方法、装置、电子设备及存储介质
CN116126521A (zh) * 2022-12-20 2023-05-16 北京海致星图科技有限公司 服务内存信息的负载均衡方法、装置、存储介质和设备
CN116647572A (zh) * 2023-07-26 2023-08-25 腾讯科技（深圳）有限公司 访问端点切换方法、装置、电子设备及存储介质
CN117333981A (zh) * 2023-10-31 2024-01-02 浙江泰源科技有限公司 一种机房集成监控管理方法与系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111290924B (zh) * 2020-01-22 2022-05-10 北京字节跳动网络技术有限公司 监控方法、装置及电子设备
CN113760635A (zh) * 2020-09-21 2021-12-07 北京沃东天骏信息技术有限公司 连接异常的确定方法、装置、电子设备和存储介质
CN113762693A (zh) * 2021-01-18 2021-12-07 北京京东拓先科技有限公司 用于展示信息的方法和装置
CN114461502B (zh) * 2022-02-16 2023-11-14 北京百度网讯科技有限公司 模型的监控方法和装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104750585A (zh) * 2013-12-30 2015-07-01 腾讯科技（深圳）有限公司 终端检测的方法及装置
US20160194666A1 (en) * 2011-09-28 2016-07-07 Rheinkalk Gmbh Process for Production of Biogas
CN106789398A (zh) * 2016-11-25 2017-05-31 中国传媒大学 一种媒体大数据hadoop集群监控的方法
CN107391336A (zh) * 2017-06-21 2017-11-24 华迪计算机集团有限公司 一种用于对服务器的运行状态进行监控的系统及方法
CN108289033A (zh) * 2017-01-10 2018-07-17 湖南易分销电子商务有限公司 一种云计算对监控系统方法
CN111290924A (zh) * 2020-01-22 2020-06-16 北京字节跳动网络技术有限公司 监控方法、装置及电子设备

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8510430B2 (en) * 2006-08-03 2013-08-13 International Business Machines Corporation Intelligent performance monitoring based on resource threshold
CN103391299B (zh) * 2012-05-08 2016-09-28 深圳市腾讯计算机系统有限公司 负载均衡方法和负载均衡系统
CN106547848A (zh) * 2016-10-18 2017-03-29 广州酷狗计算机科技有限公司 数据存储方法及装置
CN106971254A (zh) * 2017-02-13 2017-07-21 上海瀚之友信息技术服务有限公司 一种业务监控系统及方法
US20180241644A1 (en) * 2017-02-21 2018-08-23 Microsoft Technology Licensing, Llc Server performance evaluation through single value server performance index
CN107741955B (zh) * 2017-09-15 2020-06-23 平安科技（深圳）有限公司 业务数据监控方法、装置、终端设备及存储介质
CN108845910B (zh) * 2018-05-31 2024-02-06 康键信息技术（深圳）有限公司 大规模微服务系统的监控方法、装置及存储介质
CN109067780B (zh) * 2018-09-17 2023-02-28 平安科技（深圳）有限公司 爬虫用户的检测方法、装置、计算机设备和存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160194666A1 (en) * 2011-09-28 2016-07-07 Rheinkalk Gmbh Process for Production of Biogas
CN104750585A (zh) * 2013-12-30 2015-07-01 腾讯科技（深圳）有限公司 终端检测的方法及装置
CN106789398A (zh) * 2016-11-25 2017-05-31 中国传媒大学 一种媒体大数据hadoop集群监控的方法
CN108289033A (zh) * 2017-01-10 2018-07-17 湖南易分销电子商务有限公司 一种云计算对监控系统方法
CN107391336A (zh) * 2017-06-21 2017-11-24 华迪计算机集团有限公司 一种用于对服务器的运行状态进行监控的系统及方法
CN111290924A (zh) * 2020-01-22 2020-06-16 北京字节跳动网络技术有限公司 监控方法、装置及电子设备

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113472080A (zh) * 2021-07-30 2021-10-01 王雪梅 一种配电自动化监控方法、装置及电子设备
CN113472080B (zh) * 2021-07-30 2023-10-20 北京中芯标准科技有限公司 一种配电自动化监控方法、装置及电子设备
CN113626289A (zh) * 2021-08-27 2021-11-09 中国银行股份有限公司 一种用户活跃度监控方法及装置
CN113904951B (zh) * 2021-09-28 2023-07-25 济南浪潮数据技术有限公司 一种网关设备的数据监控方法、装置及相关设备
CN113904951A (zh) * 2021-09-28 2022-01-07 济南浪潮数据技术有限公司 一种网关设备的数据监控方法、装置及相关设备
CN114760233A (zh) * 2022-03-22 2022-07-15 中国工商银行股份有限公司 业务处理方法、装置、电子设备及存储介质
CN114760233B (zh) * 2022-03-22 2024-05-28 中国工商银行股份有限公司 业务处理方法、装置、电子设备及存储介质
CN115174358A (zh) * 2022-09-08 2022-10-11 浪潮电子信息产业股份有限公司 存储集群接口的监测处理方法、系统、设备及存储介质
CN115174358B (zh) * 2022-09-08 2023-01-17 浪潮电子信息产业股份有限公司 存储集群接口的监测处理方法、系统、设备及存储介质
CN116126521A (zh) * 2022-12-20 2023-05-16 北京海致星图科技有限公司 服务内存信息的负载均衡方法、装置、存储介质和设备
CN116126521B (zh) * 2022-12-20 2023-10-31 北京海致星图科技有限公司 服务内存信息的负载均衡方法、装置、存储介质和设备
CN116055496A (zh) * 2022-12-30 2023-05-02 广州趣研网络科技有限公司 一种监控数据采集方法、装置、电子设备及存储介质
CN116055496B (zh) * 2022-12-30 2024-04-05 广州趣研网络科技有限公司 一种监控数据采集方法、装置、电子设备及存储介质
CN116647572A (zh) * 2023-07-26 2023-08-25 腾讯科技（深圳）有限公司 访问端点切换方法、装置、电子设备及存储介质
CN116647572B (zh) * 2023-07-26 2023-11-14 腾讯科技（深圳）有限公司 访问端点切换方法、装置、电子设备及存储介质
CN117333981A (zh) * 2023-10-31 2024-01-02 浙江泰源科技有限公司 一种机房集成监控管理方法与系统
CN117333981B (zh) * 2023-10-31 2024-03-22 浙江泰源科技有限公司 一种机房集成监控管理方法与系统

Also Published As

Publication number Publication date
CN111290924A (zh) 2020-06-16
CN111290924B (zh) 2022-05-10

Similar Documents

Publication Publication Date Title
WO2021147481A1 (zh) 监控方法、装置及电子设备
WO2020140649A1 (zh) 区块链智能合约管理方法与装置、电子设备、存储介质
CN111459783B (zh) 应用程序优化方法、装置、电子设备及存储介质
CN109241343A (zh) 一种刷量用户识别系统、方法及装置
CN106844165A (zh) 告警方法及装置
WO2017083022A1 (en) Performance monitoring in a distributed storage system
CN111767202A (zh) 异常检测方法、装置、电子设备和介质
CN102298542A (zh) 一种应用程序的质量确定方法和系统
CN110059939A (zh) 一种风险检测方法及装置
CN112270998A (zh) 区域内感染人员分布的评估方法及装置
WO2020135886A1 (zh) 空气污染物预报方法、装置及电子设备
CN113986564A (zh) 应用数据的流量监控方法、装置、计算机设备及介质
CN115409283A (zh) 设备故障预测方法、设备故障预测装置、设备及存储介质
CN113420935A (zh) 故障定位方法、装置、设备和介质
CN112150033A (zh) 一种快递柜系统管理方法、装置及电子设备
CN115174353B (zh) 故障根因确定方法、装置、设备及介质
WO2023273539A1 (zh) 航班查询系统业务监控方法、装置、设备及存储介质
CN110727558A (zh) 信息提示方法、装置、存储介质及电子设备
CN112019406B (zh) 流量监控方法、装置、电子设备和计算机可读介质
CN113132431B (zh) 服务监控方法、服务监控装置、电子设备及介质
CN115033456A (zh) 一种内网前端性能监控方法、装置、计算机设备及存储介质
CN114443663A (zh) 数据表处理方法、装置、设备及介质
CN113946493A (zh) 一种监控阈值确定及监控报警方法、装置、设备和介质
CN109522133B (zh) 一种数据拼接方法、装置、电子设备及存储介质
WO2023138572A1 (zh) 用户标签检测方法、装置、电子设备及可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20914826

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20914826

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 06.02.2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20914826

Country of ref document: EP

Kind code of ref document: A1