WO2021008031A1 - 基于微服务实现监控智能化的处理方法及电子装置 - Google Patents
基于微服务实现监控智能化的处理方法及电子装置 Download PDFInfo
- Publication number
- WO2021008031A1 WO2021008031A1 PCT/CN2019/117559 CN2019117559W WO2021008031A1 WO 2021008031 A1 WO2021008031 A1 WO 2021008031A1 CN 2019117559 W CN2019117559 W CN 2019117559W WO 2021008031 A1 WO2021008031 A1 WO 2021008031A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- microservice
- module
- monitoring
- modules
- micro
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Definitions
- This application relates to the technical field of microservice architecture, and in particular to a processing method, electronic device, computer equipment, and storage medium for realizing monitoring intelligence based on microservices.
- this application proposes a processing method based on microservices to realize monitoring intelligence, which allows monitoring information to be managed more effectively, and can also provide more convenient and effective services to the business based on this, and improve positioning efficiency.
- the function quickly solves the health problem of the microservice module.
- this application proposes a processing method based on microservices to realize monitoring intelligence, which is applied to an electronic device.
- the method includes the steps of: sending a request; receiving and real-time monitoring of multiple microservice modules returned according to the request The micro-service module communication information; monitor the micro-service module health status of the multiple micro-service modules, and determine the micro-service module health status of the micro-service module according to the micro-service module communication information; when the multiple micro-service modules At least one of the first microservice modules sends an email notification when an abnormal state occurs; executes a preset emergency response mechanism according to the abnormal state of the first microservice module; and visually monitors and visually analyzes the first microservice module Communication information.
- this application also proposes an electronic device, including an information monitoring and collection module, a health status monitoring module, an exception handling module, and a visualization monitoring module.
- Information monitoring and collection module for receiving and real-time monitoring of micro-service module communication information of multiple micro-service modules returned according to the request
- the health status monitoring module is used to monitor the health status of the micro service modules of the multiple micro service modules, determine the health status of the micro service modules of the micro service modules according to the communication information of the micro service modules, and act as Send an email notification when at least one of the microservice modules in an abnormal state occurs;
- the exception handling module is used to execute a preset emergency handling mechanism according to the abnormal state of the microservice module.
- the visual monitoring module is used to visually monitor and visually analyze the communication information of the microservice module.
- this application also provides a computer device, including a memory, a processor, and computer-readable instructions stored in the memory and running on the processor, and the processor executes the computer-readable instructions
- a computer device including a memory, a processor, and computer-readable instructions stored in the memory and running on the processor, and the processor executes the computer-readable instructions
- the present application also provides a non-volatile computer-readable storage medium on which computer-readable instructions are stored.
- the computer-readable instructions are executed by a processor, the following steps are implemented based on the microservice implementation described above:
- the processing method of this application based on the microservices to realize the intelligent monitoring of the monitoring information can be more effective management of the monitoring information, and it can also provide more convenient and effective services to the business based on this, improve the positioning efficiency, and the intelligent functions can quickly solve the microservices Module health issues.
- the intelligent processing of business exceptions is added.
- the business components are independent and do not affect each other. When the obstruction or abnormality of related business processes is monitored , Will activate the resolution mechanism according to the situation, and quickly locate and resolve the business disconnection to ensure smooth business processes.
- FIG. 1 is a schematic diagram of the hardware architecture of an electronic device according to an embodiment of the present application.
- FIG. 2 is a functional block diagram of an electronic device according to an embodiment of the present application.
- FIG. 3 is a flow chart of the steps of a processing method for implementing intelligent monitoring based on microservices in an embodiment of the present application
- FIG. 4 is a detailed flowchart of step 301 in an embodiment of the present application.
- FIG. 5 is a detailed flowchart of step 302 in an embodiment of the present application.
- Fig. 6 is a detailed flowchart of step 303 in an embodiment of the present application.
- FIG. 1 is a schematic diagram of the hardware architecture of an electronic device according to an embodiment of the present application.
- the electronic device 10 includes, but is not limited to, a memory 110, a processor 120, and a processing system 130 that can realize intelligent monitoring based on microservices through a system bus.
- FIG. 1 only shows the electronic device 10 with the components 110-130, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.
- the memory 110 includes at least one type of readable storage medium, the readable storage medium includes flash memory, hard disk, multimedia card, card type memory (for example, SD or DX memory, etc.), random access memory (RAM), static Random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disks, optical disks, etc.
- the memory 110 may be an internal storage unit of the electronic device 10, such as a hard disk or a memory of the electronic device 10.
- the memory may also be an external storage device of the electronic device 10, such as a plug-in hard disk equipped on the electronic device 10, a smart media card (SMC), a secure digital ( Secure Digital, SD card, Flash Card, etc.
- the memory 110 may also include both an internal storage unit of the electronic device 100 and an external storage device thereof.
- the memory 110 is generally used to store the operating system and various application software installed in the electronic device 10, such as the program code of the processing system 130 that implements monitoring intelligence based on microservices.
- the memory 110 may also be used to temporarily store various types of data that have been output or will be output.
- the processor 120 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or other data processing chips.
- the processor 120 is generally used to control the overall operation of the electronic device 10.
- the processor 120 is configured to run the program code or process data stored in the memory 110, for example, to run the microservice-based processing system 130 for intelligent monitoring and the like.
- Fig. 2 is a functional block diagram of an electronic device according to an embodiment of the present application.
- the electronic device 10 (for example, the main server) in the embodiment of the present application includes an information monitoring and collection module 210, a health status monitoring module 220, an exception handling module 230, and a visualization monitoring module 240.
- the information monitoring and collection module 210 monitors and collects the microservice module communication information of the microservice module in real time; the health status monitoring module 220 monitors the health status of the microservice module of the microservice module, and automatically sends an email notification when an abnormal state occurs; When the abnormal state occurs in the microservice module, the abnormality processing module 230 executes an intelligent emergency handling mechanism; and the visualization monitoring module 240 visually monitors the communication information of the microservice module, and performs Heuristics Analysis.
- Skywalking is a domestic open source application performance monitoring tool that supports monitoring, tracking and diagnosis of distributed systems.
- Skywalking can be divided into four parts as a whole: 1.
- Skywalking Agent Use Javaagent for bytecode implantation, non-intrusive collection, and send data to Skywalking Collector through HTTP or gRPC.
- Skywalking Collector Link data collector, which integrates, analyzes and processes the data passed by the agent and stores it in related data storage.
- Storage Skywalking storage uses ElasticSearch, Mysql, TiDB, H2 as storage media for data storage.
- UI Web visualization platform, used to display the landing data.
- Information gathering tasks can be performed by Mixer and Sidecar tools.
- Sidecar will collect relevant information from each request, such as the requested path, time, source IP, destination service, tracing header, log, etc., and request these attributes to be reported to Mixer.
- Mixer and the back-end service are connected through an adapter, and Mixer sends the content reported by Sidecar to the back-end service through the adapter.
- the intelligent emergency handling mechanism at least includes, but is not limited to: fuse mechanism, load balancing...
- microservice In the microservice architecture, the microservice is to complete a single business function. The advantage of this is that it can be decoupled and each microservice can evolve independently.
- an application may consist of multiple microservices, and the data interaction between the microservices is completed through remote procedure calls. This brings about a problem.
- microservice A calls microservice B and microservice C, and microservice B and microservice C call other microservices. This is called "fan-out”. If the call response time of a microservice on the fan-out link is too long or unavailable, the call to microservice A will occupy more and more system resources, which will cause the system to crash, the so-called "avalanche effect.”
- the fuse mechanism is a microservice link protection mechanism to deal with the avalanche effect. In a high-voltage circuit, if the voltage in a certain place is too high, the fuse will blow out to protect the circuit. In stock trading, if the stock index is too high, a circuit breaker mechanism will be used to suspend stock trading. Similarly, in the microservice architecture, the fuse mechanism also plays a similar role. When a certain microservice of the fan-out link is unavailable or the response time is too long, the service will be degraded, and the call of the microservice of the node will be fuse, and the wrong response information will be returned quickly. When it is detected that the microservice call response of the node is normal, the call link is restored.
- Random algorithm randomly select one from the node list for access, and the access of each node is roughly equal. Reference implementation code.
- Polling algorithm According to a fixed order, the available service nodes are visited one by one. A circular array is used to achieve this, the node with sequence number 0 is visited this time, the node with sequence number 1 is visited next time, and so on.
- Weighted round-robin algorithm The round-robin algorithm guarantees that all nodes have the same probability of being visited. Based on this, the weighted round-robin algorithm gives each node a weight, so that each node has a different probability of being visited, and the node with a higher weight is visited The probability is high.
- the number of occurrences of each node in the sequence is its weight value. For example, there are three nodes: a, b, c, and the weights are 3, 2, and 1, respectively. Then the generated sequence is ⁇ a, a, b, c, b, a ⁇ . It is necessary to make the generated sequence as uniform as possible. If the above sequence is a for the first three times, it will cause the nodes visited for the first three times to be a.
- the least active link algorithm each visit selects the node with the least number of connections. Different nodes have different processing speeds. It can be considered that the node with the largest number of nodes has the slowest access speed.
- Consistent hash algorithm Through a hash function, all requests from the same source are mapped to the same node. Only when this node is unavailable can it be allocated to other nodes.
- the information monitoring and collection module 210 sends requests to the microservice modules of the second server (for example, other servers, not shown) in real time, for example, microservices, not shown, in which one management center can manage many microservices.
- the above requests refer to HTTP requests, including GET, HEAD, POST, PUT, DELETE, etc.
- the information monitoring and collection module 210 collects the micro-service module communication information between the first system and the micro-service module obtained through HTTP requests, and displays it on the monitoring interface of the first system (management center).
- the microservice module communication information refers to an information header (Server Header) containing an HTTP status code to respond to a request from a browser.
- the HTTP status code is composed of three decimal numbers. The first decimal number defines the type of the status code, and the latter two numbers have no classification function. There are 5 types of HTTP status codes, as shown in Table 1:
- the microservice module communication information also includes the connection status between the first system (management center) and the microservice module (microservice), including: connected, disconnected, blocked, and down. Connected means that the request arrives normally; Disconnected means that the request can be received but an error is returned; Blocked means that the call is timed out; Down means that the call returns the "Bad Gateway” error message.
- the health status monitoring module 220 monitors the health status of the microservice module (microservice) of the second server via a monitoring interface, and determines whether the microservice module has an abnormal state.
- Monitoring methods include: (2) Monitoring of hosts includes infrastructure layer monitoring and system layer monitoring; (2) Microservice monitoring includes application layer monitoring, business monitoring, and partial end user experience monitoring; (3) End user experience monitoring Need to bury the point method to collect information to supplement and improve.
- the abnormal state is the aforementioned disconnection, blocking and downtime.
- the health status monitoring module 220 sends an HTTP request to the microservice module (microservice) to determine the health status (whether it is still alive) of the microservice module (microservice):
- microservice module returns the microservice module communication information within 60 seconds and it is still alive, the return value is 200 or OK.
- microservice module returns the communication information of the microservice module after 60 seconds, it means that the network may be blocked.
- microservice module does not receive any response, it means that the microservice module (microservice) may be down, network congestion or system downtime.
- the second server When an abnormal state is found (for example, the host is abnormal or the microservice module is abnormal), the second server automatically sends an email notification to the configured email address.
- the system will default to an abnormal mail group.
- an abnormal state When an abnormal state is found, it will automatically send a warning email to this abnormal mail group.
- the exception handling module 230 determines the connection status between the first system (management center) and the microservice module (microservice); if a disconnection occurs, the exception handling module 230 makes the first system (management center) automatically Reconnect with the microservice module (microservice); and if there is a blocking state, send alarm information to the manager.
- the abnormal processing module 230 automatically sends a restart command to the first server via the monitoring interface; if the aforementioned automatic processing fails, it will perform manual processing, and After the manual processing is completed, the operation instruction is recorded on the first server; and the processing strategy is dynamically adjusted according to the processing frequency. The higher the number of manual processes for the same problem, the machine will give priority to the problem next time. Each downtime information will be recorded, and the downtime, timeout, etc. caused by any reason will be displayed in a unified report.
- Fig. 3 is a flow chart of the steps of a processing method for implementing intelligent monitoring based on microservices in an embodiment of the present application.
- the processing method for implementing intelligent monitoring based on microservices in the embodiments of the present application includes the following four main processing steps: step 301, real-time monitoring and collecting microservice module communication information of the microservice module; step 302, monitoring the microservice module The health status of the micro-service module automatically sends an email notification when an abnormal state occurs; step 303, executes a preset intelligent emergency response mechanism according to the abnormal state of the micro-service module; and step 304, visually monitors and visually analyzes the Microservice module communication information.
- FIG. 4 is a detailed flowchart of step 301 in an embodiment of the present application.
- Step 401 the first system (for example, the management center, not shown) of the first server (for example, the main server, not shown) sends a request in real time to the microservice module (for example, other servers, not shown) of the second server (for example, other servers, not shown) , Microservices, not shown), where one management center can manage many microservices.
- the first system for example, the management center, not shown
- the microservice module for example, other servers, not shown
- the second server for example, other servers, not shown
- Microservices not shown
- HTTP requests including GET, HEAD, POST, PUT, DELETE, etc.
- Step 402 The first system (such as the management center) obtains the microservice module communication information between the first system and the microservice module (such as microservice) through HTTP request, and displays it in the first system ( Management center) monitoring interface.
- the first system such as the management center
- the microservice module communication information refers to an information header (Server Header) containing an HTTP status code to respond to a request from a browser.
- the HTTP status code is composed of three decimal numbers. The first decimal number defines the type of the status code, and the latter two numbers have no classification function. There are 5 types of HTTP status codes, as shown in Table 1:
- the micro-service module communication information also includes the connection status between the first system (management center) and the micro-service module, including: connected, disconnected, blocked, and down. Connected means that the request arrives normally; Disconnected means that the request can be received but an error is returned; Blocked means that the call is timed out; Down means that the call returns the "Bad Gateway” error message.
- FIG. 5 is a detailed flowchart of step 302 in an embodiment of the present application.
- Step 501 The manager monitors the health status of the microservice module (microservice) of the second server via a monitoring interface.
- Step 502 Determine whether the microservice module has an abnormal state.
- the abnormal state is the aforementioned disconnection, blocking and downtime.
- the first system sends an HTTP request to the microservice module (microservice) to determine the health status (whether it is still alive) of the microservice module (microservice):
- microservice module returns microservice module communication information within 60 seconds, indicating that it is still alive, the return value is 200 or OK.
- microservice module returns the communication information of the microservice module after 60 seconds, it means that the network may be blocked.
- microservice module does not receive any response, it means that the microservice module (microservice) may be down, network congestion or system downtime.
- Step 503 When an abnormal state is found (such as a host abnormality or a microservice module abnormality), the second server automatically sends an email notification to the configured email address.
- the system will default to an abnormal mail group.
- a warning email When an abnormal state occurs, a warning email will be automatically sent to this abnormal mail group.
- Fig. 6 is a detailed flowchart of step 303 in an embodiment of the present application.
- Step 601 Determine the connection state between the first system (management center) and the microservice module (microservice).
- Step 602 if a disconnected state occurs, the first system (management center) will automatically reconnect with the microservice module (microservice).
- step 603 if a blocking state occurs, an alarm message is sent to the manager.
- Step 604 If the first system (management center) is down, automatically send a restart command to the first server via the monitoring interface.
- the aforementioned automatic processing fails, manual processing is performed, and the operation instruction is recorded on the first server after the manual processing is completed.
- Step 605 The first system (management center) dynamically adjusts the processing strategy according to the processing frequency. The higher the number of manual processes for the same problem, the machine will give priority to the problem next time. Each downtime information will be recorded, and the downtime, timeout, etc. caused by any reason will be displayed in a unified report.
- the intelligent processing solution for monitoring based on microservices in this application provides more effective management of monitoring information, and can also provide more convenient and effective services to the business based on this, improve positioning efficiency, and intelligent functions to quickly solve the health of microservice modules problem.
- the intelligent processing of business exceptions is added.
- the business components are independent and do not affect each other.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims (20)
- 一种基于微服务实现监控智能化的处理方法,应用于电子装置中,所述方法包括步骤:发送请求;接收并实时监控根据所述请求返回的多个微服务模块的微服务模块通信信息;监控所述多个微服务模块的微服务模块健康状态,根据所述微服务模块通信信息判断微服务模块的微服务模块健康状态;当所述多个微服务模块中至少其中一个第一微服务模块发生异常状态时发送邮件通知;根据所述第一微服务模块发生的异常状态执行预设的应急处理机制;及视图化监控并直观分析所述第一微服务模块通信信息。
- 如权利要求1所述的基于微服务实现监控智能化的处理方法,所述方法还包括步骤:自第一服务器之第一系统实时发送请求给第二服务器之第二微服务模块;及通过所述请求获取所述第一系统与所述第二微服务模块间的第二微服务模块通信信息,并显示在所述第一系统的监控界面。
- 如权利要求1所述的基于微服务实现监控智能化的处理方法,所述应急处理机包括制熔断机制,还包括步骤:当扇出链路的微服务不可用或者响应时间太长时,进行服务的降级,进而熔断该节点微服务的调用,快速返回错误的响应信息;及当检测到该节点微服务调用响应正常后,恢复调用链路。
- 如权利要求2所述的基于微服务实现监控智能化的处理方法,所述方法还包括步骤:经由所述监控界面监控所述第二服务器之所述第二微服务模块的健康状态;判断所述第二微服务模块是否发生异常状态;及当所述第二微服务模块是否发生异常状态,通过所述第二服务器自动发送警告邮件给已经配置好的邮件地址邮件。
- 如权利要求4所述的基于微服务实现监控智能化的处理方法,所述方法还包括步骤:发送所述请求给所述第二微服务模块,判断所述第二微服务模块的健康状态;若所述第二微服务模块在预设时间内返回微服务模块通信信息,表示所述第二微服务模块状态正常,则返回预设值或预设信息;若所述第二微服务模块在预设时间后返回所述第二微服务模块通信信息,表示发生网络阻塞;及若所述第二微服务模块没有任何回复,表示所述第二微服务模块已断开、网络阻塞或系统宕机。
- 如权利要求4所述的基于微服务实现监控智能化的处理方法,所述方法还包括步骤:判断所述第一系统与所述第二微服务模块间的连接状态;若出现断开状态,自动进行所述第一系统与所述微服务模块;若出现阻塞状态,发送告警信息给管理人员;及若所述第一系统出现宕机状态,则经由所述监控界面自动发送重启命令给所述第一服务器。
- 一种电子装置,包括:信息监控与收集模块,用于接收并实时监控根据请求返回的多个微服务模块的微服务模块通信信息;健康状态监控模块,用于监控所述多个微服务模块的微服务模块健康状态,根据所述微服务模块通信信息判断微服务模块的微服务模块健康状态,并当所述多个微服务模块中至少其中一个微服务模块发生异常状态时发送邮件通知;异常处理模块,用于根据所述微服务模块发生的异常状态执行预设的应急处理机制;及视图化监控模块,用于视图化监控并直观分析所述微服务模块通信信息。
- 如权利要求7所述的电子装置,应急所述处理机包括制熔断机制,所述应急处理机包括制熔断机制,还包括步骤:当扇出链路的微服务不可用或者响应时间太长时,进行服务的降级,进而熔断该节点微服务的调用,快速返回错误的响应信息;及当检测到该节点微服务调用响应正常后,恢复调用链路。
- 一种计算机设备,包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机可读指令,所述处理器执行所述计算机可读指令时实现如下步骤:发送请求;接收并实时监控根据所述请求返回的多个微服务模块的微服务模块通信信息;监控所述多个微服务模块的微服务模块健康状态,根据所述微服务模块通信信息判断微服务模块的微服务模块健康状态;当所述多个微服务模块中至少其中一个第一微服务模块发生异常状态时发送邮件通知;根据所述第一微服务模块发生的异常状态执行预设的应急处理机制;及视图化监控并直观分析所述第一微服务模块通信信息。
- 如权利要求9所述的计算机设备,所述计算机可读指令被所述处理器执行时还实现以下步骤:自第一服务器之第一系统实时发送请求给第二服务器之第二微服务模块;及通过所述请求获取所述第一系统与所述第二微服务模块间的第二微服务模块通信信息,并显示在所述第一系统的监控界面。
- 如权利要求9所述的计算机设备,所述计算机可读指令被所述处理器 执行时还实现以下步骤:当扇出链路的微服务不可用或者响应时间太长时,进行服务的降级,进而熔断该节点微服务的调用,快速返回错误的响应信息;及当检测到该节点微服务调用响应正常后,恢复调用链路。
- 如权利要求10所述的计算机设备,所述计算机可读指令被所述处理器执行时还实现以下步骤:经由所述监控界面监控所述第二服务器之所述第二微服务模块的健康状态;判断所述第二微服务模块是否发生异常状态;及当所述第二微服务模块是否发生异常状态,通过所述第二服务器自动发送警告邮件给已经配置好的邮件地址邮件。
- 如权利要求12所述的计算机设备,所述计算机可读指令被所述处理器执行时还实现以下步骤:发送所述请求给所述第二微服务模块,判断所述第二微服务模块的健康状态;若所述第二微服务模块在预设时间内返回微服务模块通信信息,表示所述第二微服务模块状态正常,则返回预设值或预设信息;若所述第二微服务模块在预设时间后返回所述第二微服务模块通信信息,表示发生网络阻塞;及若所述第二微服务模块没有任何回复,表示所述第二微服务模块已断开、网络阻塞或系统宕机。
- 如权利要求12所述的计算机设备,所述计算机可读指令被所述处理器执行时还实现以下步骤:判断所述第一系统与所述第二微服务模块间的连接状态;若出现断开状态,自动进行所述第一系统与所述微服务模块;若出现阻塞状态,发送告警信息给管理人员;及若所述第一系统出现宕机状态,则经由所述监控界面自动发送重启命令给 所述第一服务器。
- 一种非易失性计算机可读存储介质,其上存储有计算机可读指令,所述计算机可读指令被处理器执行时实现如下步骤:发送请求;接收并实时监控根据所述请求返回的多个微服务模块的微服务模块通信信息;监控所述多个微服务模块的微服务模块健康状态,根据所述微服务模块通信信息判断微服务模块的微服务模块健康状态;当所述多个微服务模块中至少其中一个第一微服务模块发生异常状态时发送邮件通知;根据所述第一微服务模块发生的异常状态执行预设的应急处理机制;及视图化监控并直观分析所述第一微服务模块通信信息。
- 如权利要求15所述的非易失性计算机可读存储介质,所述计算机可读指令被所述处理器执行时还实现以下步骤:自第一服务器之第一系统实时发送请求给第二服务器之第二微服务模块;及通过所述请求获取所述第一系统与所述第二微服务模块间的第二微服务模块通信信息,并显示在所述第一系统的监控界面。
- 如权利要求15所述的非易失性计算机可读存储介质,所述计算机可读指令被所述处理器执行时还实现以下步骤:当扇出链路的微服务不可用或者响应时间太长时,进行服务的降级,进而熔断该节点微服务的调用,快速返回错误的响应信息;及当检测到该节点微服务调用响应正常后,恢复调用链路。
- 如权利要求16所述的非易失性计算机可读存储介质,所述计算机可读指令被所述处理器执行时还实现以下步骤:经由所述监控界面监控所述第二服务器之所述第二微服务模块的健康状态;判断所述第二微服务模块是否发生异常状态;及当所述第二微服务模块是否发生异常状态,通过所述第二服务器自动发送警告邮件给已经配置好的邮件地址邮件。
- 如权利要求18所述的非易失性计算机可读存储介质,所述计算机可读指令被所述处理器执行时还实现以下步骤:发送所述请求给所述第二微服务模块,判断所述第二微服务模块的健康状态;若所述第二微服务模块在预设时间内返回微服务模块通信信息,表示所述第二微服务模块状态正常,则返回预设值或预设信息;若所述第二微服务模块在预设时间后返回所述第二微服务模块通信信息,表示发生网络阻塞;及若所述第二微服务模块没有任何回复,表示所述第二微服务模块已断开、网络阻塞或系统宕机。
- 如权利要求18所述的非易失性计算机可读存储介质,所述计算机可读指令被所述处理器执行时还实现以下步骤:判断所述第一系统与所述第二微服务模块间的连接状态;若出现断开状态,自动进行所述第一系统与所述微服务模块;若出现阻塞状态,发送告警信息给管理人员;及若所述第一系统出现宕机状态,则经由所述监控界面自动发送重启命令给所述第一服务器。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910639556.8A CN110535902A (zh) | 2019-07-16 | 2019-07-16 | 基于微服务实现监控智能化的处理方法及电子装置 |
CN201910639556.8 | 2019-07-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021008031A1 true WO2021008031A1 (zh) | 2021-01-21 |
Family
ID=68660261
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/117559 WO2021008031A1 (zh) | 2019-07-16 | 2019-11-12 | 基于微服务实现监控智能化的处理方法及电子装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110535902A (zh) |
WO (1) | WO2021008031A1 (zh) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112817727A (zh) * | 2021-02-08 | 2021-05-18 | 上海百胜软件股份有限公司 | 基于微服务架构的任务管理方法、系统、设备和存储介质 |
CN113162799A (zh) * | 2021-03-09 | 2021-07-23 | 北京字跳网络技术有限公司 | 故障定位方法、装置、电子设备、定位系统及存储介质 |
CN113419852A (zh) * | 2021-06-22 | 2021-09-21 | 康键信息技术(深圳)有限公司 | 微服务的请求响应方法、装置、设备及存储介质 |
CN113810379A (zh) * | 2021-08-23 | 2021-12-17 | 深圳价值在线信息科技股份有限公司 | 一种异常处理方法及多服务系统 |
CN113938374A (zh) * | 2021-12-20 | 2022-01-14 | 飞狐信息技术(天津)有限公司 | 一种监控仪表盘的处理方法及装置 |
CN114205422A (zh) * | 2021-12-13 | 2022-03-18 | 平安养老保险股份有限公司 | 一种无侵入式业务处理方法、装置、设备及存储介质 |
CN114697192A (zh) * | 2022-03-16 | 2022-07-01 | 浪潮云信息技术股份公司 | 一种基于Skywalking的应用性能指标告警系统 |
CN114706733A (zh) * | 2022-05-30 | 2022-07-05 | 支付宝(杭州)信息技术有限公司 | 切面程序异常的监控方法和装置 |
CN114745295A (zh) * | 2022-04-19 | 2022-07-12 | 京东科技控股股份有限公司 | 数据采集方法、装置、设备和可读存储介质 |
CN114866606A (zh) * | 2022-04-21 | 2022-08-05 | 彩讯科技股份有限公司 | 一种微服务管理系统 |
CN115037653A (zh) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | 业务流量监控方法、装置、电子设备和存储介质 |
CN115277475A (zh) * | 2022-07-05 | 2022-11-01 | 浪潮云信息技术股份公司 | 一种api网关实现链路跟踪的方法及系统 |
CN115296980A (zh) * | 2022-08-02 | 2022-11-04 | 国家电网有限公司客户服务中心 | 基于Skywalking的告警方法及相关设备 |
CN115314559A (zh) * | 2022-08-03 | 2022-11-08 | 苏州创意云网络科技有限公司 | 网络服务系统及其异常响应方法 |
CN115766786A (zh) * | 2022-11-11 | 2023-03-07 | 四川启睿克科技有限公司 | 一种智能家电终端业务异常的排查系统及方法 |
CN116302862A (zh) * | 2023-05-18 | 2023-06-23 | 浙江华东工程数字技术有限公司 | 一种微服务架构下监控告警方法和系统 |
WO2023125773A1 (zh) * | 2021-12-30 | 2023-07-06 | 网络通信与安全紫金山实验室 | 大规模微服务集群场景下的全局异常处理方法和平台 |
CN116611749A (zh) * | 2023-02-13 | 2023-08-18 | 国家电投集团数字科技有限公司 | 一种基于微服务架构的电力数据智能录入方法及系统 |
CN116737515A (zh) * | 2023-05-10 | 2023-09-12 | 珠海妙存科技有限公司 | 闪存参数可视化方法、系统及存储介质 |
US11870858B2 (en) | 2022-02-01 | 2024-01-09 | International Business Machines Corporation | Intelligent, fast-forwarded health checks within service mesh |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111262898B (zh) * | 2018-12-01 | 2022-06-14 | 阿里巴巴集团控股有限公司 | 服务降级处理方法、装置及电子设备 |
CN111045648B (zh) * | 2019-12-11 | 2024-03-15 | 盈佳云创科技(深圳)有限公司 | 一种微服务开发装置 |
CN111181777B (zh) * | 2019-12-17 | 2022-09-20 | 深圳前海环融联易信息科技服务有限公司 | 一种服务降级的方法、装置、计算机设备及存储介质 |
CN111130939B (zh) * | 2019-12-26 | 2021-09-10 | 深圳前海环融联易信息科技服务有限公司 | 一种流量控制方法、装置、计算机设备及存储介质 |
CN111158987B (zh) * | 2019-12-31 | 2023-09-19 | 中国银行股份有限公司 | 微服务架构的健康检查方法及装置 |
CN111176955A (zh) * | 2020-01-07 | 2020-05-19 | 深圳壹账通智能科技有限公司 | 微服务的监控方法、装置、设备及计算机可读存储介质 |
CN111427557A (zh) * | 2020-04-06 | 2020-07-17 | 中信银行股份有限公司 | 应用微服务化方法、装置、电子设备及可读存储介质 |
CN111581576B (zh) * | 2020-05-08 | 2024-04-02 | 湖南蚁坊软件股份有限公司 | 基于微服务的开发处理方法、装置及存储介质 |
CN111756601B (zh) * | 2020-06-24 | 2023-02-03 | 中国平安财产保险股份有限公司 | 微服务架构监控方法、装置、计算机设备及可读存储介质 |
CN111541590B (zh) * | 2020-07-08 | 2020-11-06 | 广州市玄武无线科技股份有限公司 | 链路监控方法、告警方法、系统、终端及存储介质 |
CN114915647B (zh) * | 2021-01-28 | 2023-08-29 | 复旦大学 | 基于微服务的前沿装备远程互动体验系统 |
CN113704052B (zh) * | 2021-07-21 | 2023-09-22 | 郑州云海信息技术有限公司 | 一种微服务架构的运维系统、方法、设备及介质 |
CN114363091B (zh) * | 2022-03-02 | 2022-11-15 | 工业互联网创新中心(上海)有限公司 | 一种基于apisix实现平台应用统一登录的方法及系统 |
CN115174422A (zh) * | 2022-06-29 | 2022-10-11 | 深圳市华宇讯科技有限公司 | 微服务治理方法及装置 |
CN117251337B (zh) * | 2023-09-07 | 2024-05-28 | 广州宇中网络科技有限公司 | 微服务健康拨测方法、装置、设备及存储介质 |
CN116980480B (zh) * | 2023-09-25 | 2024-02-27 | 上海伊邦医药信息科技股份有限公司 | 基于微服务网络模型的熔断信息的处理方法及系统 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108512689A (zh) * | 2017-12-15 | 2018-09-07 | 中国平安财产保险股份有限公司 | 微服务业务监控方法及服务器 |
CN108712309A (zh) * | 2018-06-11 | 2018-10-26 | 郑州云海信息技术有限公司 | 一种微服务架构下的微服务节点防护方法和系统 |
CN108845910A (zh) * | 2018-05-31 | 2018-11-20 | 康键信息技术(深圳)有限公司 | 大规模微服务系统的监控方法、装置及存储介质 |
CN109818776A (zh) * | 2018-12-17 | 2019-05-28 | 视联动力信息技术股份有限公司 | 微服务模块异常定位方法和装置 |
US20190207954A1 (en) * | 2018-01-02 | 2019-07-04 | ShieldX Networks, Inc. | Systems and methods for evaluating encrypted data packets in a networked environment |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10484410B2 (en) * | 2017-07-19 | 2019-11-19 | Cisco Technology, Inc. | Anomaly detection for micro-service communications |
CN109976935B (zh) * | 2019-03-14 | 2020-09-04 | 北京三快在线科技有限公司 | 微服务架构、微服务节点及其熔断恢复方法、装置 |
-
2019
- 2019-07-16 CN CN201910639556.8A patent/CN110535902A/zh active Pending
- 2019-11-12 WO PCT/CN2019/117559 patent/WO2021008031A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108512689A (zh) * | 2017-12-15 | 2018-09-07 | 中国平安财产保险股份有限公司 | 微服务业务监控方法及服务器 |
US20190207954A1 (en) * | 2018-01-02 | 2019-07-04 | ShieldX Networks, Inc. | Systems and methods for evaluating encrypted data packets in a networked environment |
CN108845910A (zh) * | 2018-05-31 | 2018-11-20 | 康键信息技术(深圳)有限公司 | 大规模微服务系统的监控方法、装置及存储介质 |
CN108712309A (zh) * | 2018-06-11 | 2018-10-26 | 郑州云海信息技术有限公司 | 一种微服务架构下的微服务节点防护方法和系统 |
CN109818776A (zh) * | 2018-12-17 | 2019-05-28 | 视联动力信息技术股份有限公司 | 微服务模块异常定位方法和装置 |
Non-Patent Citations (2)
Title |
---|
DING XUE-YING, LIU DI, QIU ZHEN: "Design and Implementation of Application Monitoring System Based on Micro Service Architecture", ELECTRIC POWER INFORMATION AND COMMUNICATION TECHNOLOGY, vol. 16, no. 7, 15 July 2018 (2018-07-15), pages 75 - 79, XP055773352, ISSN: 2095-641X, DOI: 10.16543/j.2095-641x.electric.power.ict.2018.07.013 * |
MAYER BENJAMIN; WEINREICH RAINER: "A Dashboard for Microservice Monitoring and Management", 2017 IEEE INTERNATIONAL CONFERENCE ON SOFTWARE ARCHITECTURE WORKSHOPS (ICSAW), 5 April 2017 (2017-04-05), pages 66 - 69, XP033107990, DOI: 10.1109/ICSAW.2017.44 * |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112817727A (zh) * | 2021-02-08 | 2021-05-18 | 上海百胜软件股份有限公司 | 基于微服务架构的任务管理方法、系统、设备和存储介质 |
CN113162799A (zh) * | 2021-03-09 | 2021-07-23 | 北京字跳网络技术有限公司 | 故障定位方法、装置、电子设备、定位系统及存储介质 |
CN113162799B (zh) * | 2021-03-09 | 2023-01-24 | 北京字跳网络技术有限公司 | 故障定位方法、装置、电子设备、定位系统及存储介质 |
CN113419852B (zh) * | 2021-06-22 | 2023-10-20 | 康键信息技术(深圳)有限公司 | 微服务的请求响应方法、装置、设备及存储介质 |
CN113419852A (zh) * | 2021-06-22 | 2021-09-21 | 康键信息技术(深圳)有限公司 | 微服务的请求响应方法、装置、设备及存储介质 |
CN113810379A (zh) * | 2021-08-23 | 2021-12-17 | 深圳价值在线信息科技股份有限公司 | 一种异常处理方法及多服务系统 |
CN114205422A (zh) * | 2021-12-13 | 2022-03-18 | 平安养老保险股份有限公司 | 一种无侵入式业务处理方法、装置、设备及存储介质 |
CN114205422B (zh) * | 2021-12-13 | 2023-07-25 | 平安养老保险股份有限公司 | 一种无侵入式业务处理方法、装置、设备及存储介质 |
CN113938374A (zh) * | 2021-12-20 | 2022-01-14 | 飞狐信息技术(天津)有限公司 | 一种监控仪表盘的处理方法及装置 |
WO2023125773A1 (zh) * | 2021-12-30 | 2023-07-06 | 网络通信与安全紫金山实验室 | 大规模微服务集群场景下的全局异常处理方法和平台 |
US11870858B2 (en) | 2022-02-01 | 2024-01-09 | International Business Machines Corporation | Intelligent, fast-forwarded health checks within service mesh |
CN114697192A (zh) * | 2022-03-16 | 2022-07-01 | 浪潮云信息技术股份公司 | 一种基于Skywalking的应用性能指标告警系统 |
CN114745295A (zh) * | 2022-04-19 | 2022-07-12 | 京东科技控股股份有限公司 | 数据采集方法、装置、设备和可读存储介质 |
CN114866606A (zh) * | 2022-04-21 | 2022-08-05 | 彩讯科技股份有限公司 | 一种微服务管理系统 |
CN114706733A (zh) * | 2022-05-30 | 2022-07-05 | 支付宝(杭州)信息技术有限公司 | 切面程序异常的监控方法和装置 |
CN115037653B (zh) * | 2022-06-28 | 2023-10-13 | 北京奇艺世纪科技有限公司 | 业务流量监控方法、装置、电子设备和存储介质 |
CN115037653A (zh) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | 业务流量监控方法、装置、电子设备和存储介质 |
CN115277475A (zh) * | 2022-07-05 | 2022-11-01 | 浪潮云信息技术股份公司 | 一种api网关实现链路跟踪的方法及系统 |
CN115296980A (zh) * | 2022-08-02 | 2022-11-04 | 国家电网有限公司客户服务中心 | 基于Skywalking的告警方法及相关设备 |
CN115314559B (zh) * | 2022-08-03 | 2023-09-29 | 苏州创意云网络科技有限公司 | 网络服务系统及其异常响应方法、服务单元、调度处理单元、电子设备及计算机存储介质 |
CN115314559A (zh) * | 2022-08-03 | 2022-11-08 | 苏州创意云网络科技有限公司 | 网络服务系统及其异常响应方法 |
CN115766786A (zh) * | 2022-11-11 | 2023-03-07 | 四川启睿克科技有限公司 | 一种智能家电终端业务异常的排查系统及方法 |
CN115766786B (zh) * | 2022-11-11 | 2024-05-14 | 四川启睿克科技有限公司 | 一种智能家电终端业务异常的排查系统及方法 |
CN116611749A (zh) * | 2023-02-13 | 2023-08-18 | 国家电投集团数字科技有限公司 | 一种基于微服务架构的电力数据智能录入方法及系统 |
CN116611749B (zh) * | 2023-02-13 | 2023-10-20 | 国家电投集团数字科技有限公司 | 一种基于微服务架构的电力数据智能录入方法及系统 |
CN116737515A (zh) * | 2023-05-10 | 2023-09-12 | 珠海妙存科技有限公司 | 闪存参数可视化方法、系统及存储介质 |
CN116737515B (zh) * | 2023-05-10 | 2024-02-23 | 珠海妙存科技有限公司 | 闪存参数可视化方法、系统及存储介质 |
CN116302862B (zh) * | 2023-05-18 | 2023-08-11 | 浙江华东工程数字技术有限公司 | 一种微服务架构下监控告警方法和系统 |
CN116302862A (zh) * | 2023-05-18 | 2023-06-23 | 浙江华东工程数字技术有限公司 | 一种微服务架构下监控告警方法和系统 |
Also Published As
Publication number | Publication date |
---|---|
CN110535902A (zh) | 2019-12-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021008031A1 (zh) | 基于微服务实现监控智能化的处理方法及电子装置 | |
US10348809B2 (en) | Naming of distributed business transactions | |
CN108039964B (zh) | 基于网络功能虚拟化的故障处理方法及装置、系统 | |
US7685269B1 (en) | Service-level monitoring for storage applications | |
US9413597B2 (en) | Method and system for providing aggregated network alarms | |
US10868709B2 (en) | Determining the health of other nodes in a same cluster based on physical link information | |
US8443078B2 (en) | Method of determining equivalent subsets of agents to gather information for a fabric | |
CN109039787A (zh) | 日志处理方法、装置及大数据集群 | |
CN112596975A (zh) | 对网络设备进行监控处理的方法、系统、设备和存储介质 | |
CN113067875A (zh) | 基于微服务网关动态流控的访问方法和装置以及设备 | |
JP2013222313A (ja) | 障害連絡効率化システム | |
CN112910733A (zh) | 一种基于大数据的全链路监控系统及方法 | |
CN110569238B (zh) | 一种基于大数据的数据治理方法、系统、存储介质和服务端 | |
US20060053021A1 (en) | Method for monitoring and managing an information system | |
CN117370053A (zh) | 一种面向信息系统业务运行全景监测方法及系统 | |
CN113760634A (zh) | 一种数据处理方法和装置 | |
CN110569178A (zh) | 基于大数据平台的接口预警方法和系统 | |
CN112214437B (zh) | 一种存储设备及通信方法、装置、计算机可读存储介质 | |
KR20230055575A (ko) | 사설망과 공용망을 위한 범용 대규모 멀티 클라우드 환경 모니터링 시스템 및 방법 | |
CN114090293A (zh) | 一种服务提供方法及电子设备 | |
JP2018169643A (ja) | セキュリティ運用システム、セキュリティ運用管理装置およびセキュリティ運用方法 | |
CN115987827B (zh) | 一种设备监测方法、装置、电子设备及可读介质 | |
CN113722142B (zh) | 内存不足的原因分析方法、装置、电子设备及存储介质 | |
CN110752939A (zh) | 一种业务进程故障处理方法、通知方法和装置 | |
EP4270183A1 (en) | Public cloud tenant service management method and device |
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: 19937717 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: 19937717 Country of ref document: EP Kind code of ref document: A1 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19937717 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 21/09/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19937717 Country of ref document: EP Kind code of ref document: A1 |