CA3168289A1 - Method and system for monitoring microservices - Google Patents
Method and system for monitoring microservicesInfo
- Publication number
- CA3168289A1 CA3168289A1 CA3168289A CA3168289A CA3168289A1 CA 3168289 A1 CA3168289 A1 CA 3168289A1 CA 3168289 A CA3168289 A CA 3168289A CA 3168289 A CA3168289 A CA 3168289A CA 3168289 A1 CA3168289 A1 CA 3168289A1
- Authority
- CA
- Canada
- Prior art keywords
- service
- status
- registering
- center
- query result
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 32
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000004891 communication Methods 0.000 claims description 12
- 230000007246 mechanism Effects 0.000 claims description 9
- 230000002159 abnormal effect Effects 0.000 claims description 7
- 238000011045 prefiltration Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000002708 enhancing effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5015—Service provider selection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/508—Monitor
Abstract
Disclosed are a micro-service monitoring method and system, belonging to the technical field of micro-services. The method comprises: a service registration center registering a service instance of a micro-service; a monitoring center sending a state acquisition request to a service gateway; the service gateway receiving the state acquisition request, and acquiring, from the service registration center, a registration record of the service instance indicated by the state acquisition request; the service gateway querying a service state of the indicated service instance according to the registration record, and sending a service state query result to the monitoring center; and the monitoring center receiving the service state query result and performing corresponding processing. The embodiments of the present invention can improve the monitoring convenience and monitoring time effectiveness of a micro-service, and the problem of resources being occupied by a monitoring program does not occur.
Description
METHOD AND SYSTEM FOR MONITORING MICROSERVICES
BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to the technical field of microservices, and more particularly to a method and a system for monitoring microservices.
Description of Related Art
BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to the technical field of microservices, and more particularly to a method and a system for monitoring microservices.
Description of Related Art
[0002] Microservices refer to sets of small services developed from individual applications.
Therein, every application runs in its own process, and communicates with a lightweight mechanism (usually an HTTP resource API). These services are constructed around business functions and can be separately deployed through a fully automatic deployment mechanism. Essentially, microservices are distributed applications. They usually operate on a cluster, and the cluster carries service instances.
Therein, every application runs in its own process, and communicates with a lightweight mechanism (usually an HTTP resource API). These services are constructed around business functions and can be separately deployed through a fully automatic deployment mechanism. Essentially, microservices are distributed applications. They usually operate on a cluster, and the cluster carries service instances.
[0003] Since microservices feature numerous individuals and various deployment ways, problems can raise everywhere, making monitoring of service statuses particularly difficult. In a conventional system for monitoring microservices, whenever a new service instance is added, a monitoring program has to be simultaneously deployed for that service instance, so that the monitoring program can collect monitoring data as scheduled and upload the data to a monitoring center where monitoring is performed.
[0004] However, the conventional system for monitoring microservices have the following shortcomings:
[0005] 1. The system has complicated configuration and is unable to do monitoring automatically:
every time a service instance is added or gets offline, the corresponding monitoring program has to be configured, activated, or destroyed, and the system is unable to sense the need automatically; and
every time a service instance is added or gets offline, the corresponding monitoring program has to be configured, activated, or destroyed, and the system is unable to sense the need automatically; and
[0006] 2. The system takes resources and is less timely: a configuration program is an Date Regue/Date Received 2022-07-18 independent progress, which consumes certain machine resources, and due to a scheduled reporting mechanism it adopts, the system is unable to acquire the latest service statuses of microservices, making the monitoring less timely.
SUMMARY OF THE INVENTION
SUMMARY OF THE INVENTION
[0007] The objective of the present invention is to at least solve one of technical problems of the prior art or related arts. To this end, the present invention provides a method and a system for monitoring microservices.
[0008] Embodiments of the present invention provide the following technical schemes.
[0009] In a first aspect, the present invention provides a method for monitoring microservices, the method comprises:
[0010] registering, by a service registering center, service instances of microservices;
[0011] sending, by a monitoring center, a status acquiring request to a service gateway;
[0012] receiving, by the service gateway, the status acquiring request, and acquiring registering record of the service instance designated by the status acquiring request from the service registering center;
[0013] the service gateway according to the registering record, checking service status of the designated service instance, and sending a query result of the service status to the monitoring center; and
[0014] receiving, by the monitoring center, the query result of the service status and performing a corresponding operation.
[0015] Further, after the step of registering, by a service registering center, service instances of microservices, the method further comprises:
[0016] maintaining, by the service registering center, communication with the service instances using a heartbeat mechanism, and when the communication has been interrupted longer than a predetermined time period, cancelling, by the service registering center, the service instances.
[0017] Further, the service gateway, according to the registering records, queries service status Date Regue/Date Received 2022-07-18 of the designated service instances through:
[0018] retrieving a network address of the designated service instance from the registering record;
and
and
[0019] according to the network address, sending a querying request for the service status to the designated service instance, and receiving the query result of the service status of the designated service instance.
[0020] Further, the service status comprises one or more of a CPU utilization rate, a memory utilization rate, disk reading and writing, network connectivity, heapSize information, and heapUsedSize information.
[0021] Further, the corresponding operation comprises:
[0022] storing the query result of the service status; and/or
[0023] displaying the query result of the service status on a page; and/or
[0024] according to the query result of the service status, warning of the service instance having the abnormal service status.
[0025] In a second aspect, the present invention provides a system for monitoring microservices.
The system comprises a service registering center, a monitoring center, and a service gateway, therein:
The system comprises a service registering center, a monitoring center, and a service gateway, therein:
[0026] the service registering center, for registering service instances of microservices;
[0027] the monitoring center, for sending a status acquiring request to the service gateway;
[0028] the service gateway comprising:
[0029] a pre-filter, for receiving the status acquiring request;
[0030] a route filter, for acquiring registering record of the service instance designated by the status acquiring request from the service registering center, and according to the registering record, checking service status of the designated service instance;
[0031] a post-filter, for sending a query result of the service status to the monitoring center; and
[0032] the monitoring center, further for receiving the query result of the service status and performing a corresponding operation.
[0033] Further, the service registering center is further for:
[0034] maintaining communication with the service instances using a heartbeat mechanism, and Date Regue/Date Received 2022-07-18 when the communication has been interrupted longer than a predetermined time period, cancelling the service instances.
[0035] Further, the route filter comprises:
[0036] a service processor, for retrieving a network address of the designated service instance from the registering record; and
[0037] a broadcasting plug-in, for according to the network address, sending a querying request for the service status to the designated service instance, and receiving the query result of the service status of the designated service instance.
[0038] Further, the service status comprises one or more of a CPU utilization rate, a memory utilization rate, disk reading and writing, network connectivity, heapSize information, and heapUsedSize information.
[0039] Further, the monitoring center is specifically for:
[0040] storing the query result of the service status;
[0041] displaying the query result of the service status on a page;
[0042] according to the query result of the service status, warning of the service instance having the abnormal service status.
[0043] The technical schemes provided in the embodiments of the present invention have the following beneficial effects:
[0044] 1. Scaling-up or scaling-down of microservices requires no manual configuration, and service instances of microservices can be dynamically acquired through a service registering center, thereby accomplishing automatic sensing of service instances and in turn enhancing convenience of microservice monitoring; and
[0045] 2. Different from the conventional approach where service statuses are uploaded in a scheduled manner, embodiments of the present invention allow a monitoring center to acquire the latest service statuses of service instances in a real-time manner through a service gateway, and are therefore more features high timeliness without using any monitoring program that consumes resources.
Date Regue/Date Received 2022-07-18 BRIEF DESCRIPTION OF THE DRAWINGS
Date Regue/Date Received 2022-07-18 BRIEF DESCRIPTION OF THE DRAWINGS
[0046] To better illustrate the technical schemes as disclosed in the embodiments of the present invention, accompanying drawings referred in the description of the embodiments below are introduced briefly. It is apparent that the accompanying drawings as recited in the following description merely provide a part of possible embodiments of the present invention, and people of ordinary skill in the art would be able to obtain more drawings according to those provided herein without paying creative efforts, wherein:
[0047] FIG. 1 is a flowchart of a method for monitoring microservices according to Embodiment 1 of the present invention; and
[0048] FIG. 2 is a block diagram of a system for monitoring microservices according to Embodiment 2 of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
DETAILED DESCRIPTION OF THE INVENTION
[0049] To make the foregoing objectives, features, and advantages of the present invention clearer and more understandable, the following description will be directed to some embodiments as depicted in the accompanying drawings to detail the technical schemes disclosed in these embodiments. It is, however, to be understood that the embodiments referred herein are only a part of all possible embodiments and thus not exhaustive. Based on the embodiments of the present invention, all the other embodiments can be conceived without creative labor by people of ordinary skill in the art, and all these and other embodiments shall be encompassed in the scope of the present invention.
[0050] It is to be understood that, in the disclosure, the terms "first,"
"second," and the like are merely descriptive and not intended to suggest or imply relative importance.
Additionally, in the disclosure, whenever "plural" is used, it means that the described object comes in two or more than two unless the context indicates otherwise.
"second," and the like are merely descriptive and not intended to suggest or imply relative importance.
Additionally, in the disclosure, whenever "plural" is used, it means that the described object comes in two or more than two unless the context indicates otherwise.
[0051] FIG. 1 is a flowchart of a method for monitoring microservices according to Embodiment 1 of the present invention. As shown, the method may comprise the following steps.
Date Regue/Date Received 2022-07-18
Date Regue/Date Received 2022-07-18
[0052] At the step 101, a service registering center registers service instances of microservices.
[0053] Specifically, the service registering center receives registering information of the service instances that sent actively when the microservices are activated, and registers the service instances according to the registering information of the service instances.
[0054] Therein, the registering information includes microservice names, network addresses, ports, and service instances.
[0055] After the service registering center registers the service instances of the microservices, it generates and stores registering records of the service instances, for a service gateway to call and use the registering information of the service instances later.
[0056] In an exemplificative implementation, after the step 101, the method further comprises:
[0057] maintaining, by the service registering center, communication with the service instances using a heartbeat mechanism, and when the communication has been interrupted longer than a predetermined time period, cancelling the service instance.
[0058] Specifically, after the microservices are activated, heartbeats are sent to the service registering center at a predetermined cycle (for example, 30 seconds). If the service registering center has not received the heartbeat of a service instance of the microservice by the end of a predetermined time period (for example, 90 seconds), it cancels that service instance.
[0059] In the embodiment of the present invention, with the service registering center registering the service instances of microservices, the present invention can enhance convenience of monitoring. Particularly, scaling-up or scaling-down of microservices requires no manual configuration, and service instances of microservices can be dynamically acquired through a service registering center, thereby accomplishing automatic sensing of service instances and in turn enhancing convenience of microservice monitoring.
[0060] At the step 102, a monitoring center sends a status acquiring request to a service gateway.
[0061] In the present embodiment, the status acquiring request may be an http request, and the status acquiring request may contain the network address of the designated service instance. The designated service instance may be a single service instance, or may be plural service instances. In addition, when there is not a certain service instance Date Regue/Date Received 2022-07-18 designated, the service instance designated in the status acquiring request includes all service instances that have been registered in the service registering center.
[0062] Therein, the service gateway is a distributed service gateway configured using SpringCloud+Zuul.
[0063] In the embodiment of the present invention, the service gateway employs a distributed, decentralized deployment architecture, thereby eliminating the need of deploying monitoring programs for individual service instances as required in the prior art. This in turn prevent system crashes that might otherwise be caused by monitoring programs and in turn prevents single point problems, thereby providing good availability.
[0064] At the step 103, the service gateway receives the status acquiring request, and acquires registering records of the service instances as designated in the status acquiring request from the service registering center.
[0065] Therein, the service gateway comprises internal components such as pre-filters, route filters, and post-filters. Therein, the route filter further comprises a broadcasting plug-in and a service processor.
[0066] Specifically, the process may comprise the following steps.
[0067] First, the pre-filter in the service gateway receives the status acquiring request, and pre-processes the status acquiring request. Further, before pre-processing the status acquiring request, the pre-filter may verify the status acquiring request.
[0068] Then the service processor in the route filter acquires registering records of the service instances designated by the status acquiring request from the service registering center according to a load balancing strategy, and receives the registering records of the service instances designated by the status acquiring request from the service registering center.
[0069] It is to be noted that if the status acquiring request designates a service instance that is not registered in the service registering center, the service gateway generates a request failure message to indicate that the service instance designated in the status acquiring request has not been registered and send the request failure information to the monitoring center.
[0070] At the step 104, the service gateway queries a service status of the designated service instance according to the registering records, and sends a query result of the service status Date Regue/Date Received 2022-07-18 to the monitoring center.
[0071] Specifically, the process may comprise the following steps.
[0072] First, the broadcasting plug-in in the route filter acquires the network address of the designated service instance from the registering record, and broadcasts the status acquiring request to the service instance designated in the status acquiring request. It subsequently receives the query result of the service status sent back by the designated service instance.
[0073] Then the post-filter in the service gateway packages the query result of the service status and sends it to the monitoring center.
[0074] Therein, the service status comprises one or more of a CPU utilization rate, a memory utilization rate, disk reading and writing, network connectivity, heapSize information, and heapUsedSize information.
[0075] At the step 105, receiving, by the monitoring center, the query result of the service status and performing a corresponding operation.
[0076] Specifically, the corresponding operation the monitoring center performs on the query result of the service status may include:
[0077] storing the query result of the service status; and/or
[0078] displaying the query result of the service status on a page; and/or
[0079] according to the query result of the service status, warning of the service instance having the abnormal service status.
[0080] Specifically, the query result of the service status is analyzed to determine whether the service status of the service instance is normal or not. In the event of abnormality, a warning is given to inform the user timely, thereby allowing the user to take action for the abnormal service instance timely.
[0081] In the embodiment of the present invention, the monitoring center may use the "service broadcasting function" of the service gateway to acquire the service status(es) of the designated service instance or of all the service instances that have been registered in the service registering center in a real-time manner, thereby realizing real-time acquisition of the latest service statuses of the service instances. As compared to the conventional Date Regue/Date Received 2022-07-18 approach where service statuses are uploaded as scheduled, the present invention can significantly enhance monitoring in terms of timeliness.
[0082] FIG. 2 is a block diagram of a system for monitoring microservices according to Embodiment 2 of the present invention. The system comprises a service registering center 21, a monitoring center 22, and a service gateway 23.
[0083] The service registering center 21 is for registering service instances of microservices.
[0084] The monitoring center 22 is for sending a status acquiring request for a target service instance to the service gateway.
[0085] The service gateway 23 comprises:
[0086] a pre-filter 231, for receiving the status acquiring request;
[0087] a route filter 232, for acquiring the registering record of the service instance designated in the status acquiring request from the service registering center, and according to registering records, checking the service status of the designated service instance; and
[0088] a post-filter 233, for sending the query result of the service status of the target service instance to the monitoring center 22; and
[0089] the monitoring center 22, further for receiving the query result of the service status and performing a corresponding operation.
[0090] Further, service registering center 21 is further for:
[0091] maintaining communication with the service instances using a heartbeat mechanism, and when the communication has been interrupted longer than a predetermined time period, cancelling the service instances.
[0092] Further, the route filter 232 comprises:
[0093] a service processor, for acquiring the network address of the designated service instance from the registering record; and
[0094] a broadcasting plug-in, for according to network address, sending a request for checking the service status to the designated service instance, and receiving the query result of the service status from the designated service instance.
[0095] Further, service status comprises one or more of a CPU utilization rate, a memory utilization rate, disk reading and writing, network connectivity, heapSize information, and Date Regue/Date Received 2022-07-18 heapUsedSize information.
[0096] Further, the monitoring center 22 is specifically for:
[0097] storing the query result of the service status;
[0098] displaying the query result of the service status on a page; and
[0099] according to the query result of the service status, warning of the service instance having the abnormal service status.
[0100] It is to be noted that work division among the foregoing functional modules for the system for monitoring microservices of the present embodiment is merely exemplary. In practical implementations, the work division may be made among different functional modules. In other words, the internal architecture of the system for monitoring microservices may be reconfigured with different functional modules to perform all or a part of the functions as described previously. In addition, since the system for monitoring microservices of the present embodiment and the disclosed method for monitoring microservices in the previous embodiment stem from the same conception, the details of its implementation can be learned from the description made to the method of the previous embodiment, and no repetition is made herein.
[0101] People of ordinary skill in the art would appreciate that all or part of the steps as described in the foregoing embodiments may be implemented using hardware, or may alternatively be implemented using a program that instructs relevant hardware. The program may be stored in a computer readable storage medium, and the storage medium may be a read-only storage, a magnetic disk, an optical disk, or the like.
[0102] The present invention has been described with reference to the preferred embodiments and it is understood that the embodiments are not intended to limit the scope of the present invention. Moreover, as the contents disclosed herein should be readily understood and can be implemented by a person skilled in the art, all equivalent changes or modifications which do not depart from the concept of the present invention should be encompassed by the appended claims. Hence, the scope of the present invention shall only be defined by the appended claims.
Date Regue/Date Received 2022-07-18
Date Regue/Date Received 2022-07-18
Claims (10)
1. A method for monitoring microservices, comprising:
registering, by a service registering center, service instances of microservices;
sending, by a monitoring center, a status acquiring request to a service gateway;
receiving, by the service gateway, the status acquiring request, and acquiring registering record of the service instance designated by the status acquiring request from the service registering center;
the service gateway according to the registering record, checking service status of the designated service instance, and sending a query result of the service status to the monitoring center; and receiving, by the monitoring center, the query result of the service status and performing a corresponding operation.
registering, by a service registering center, service instances of microservices;
sending, by a monitoring center, a status acquiring request to a service gateway;
receiving, by the service gateway, the status acquiring request, and acquiring registering record of the service instance designated by the status acquiring request from the service registering center;
the service gateway according to the registering record, checking service status of the designated service instance, and sending a query result of the service status to the monitoring center; and receiving, by the monitoring center, the query result of the service status and performing a corresponding operation.
2. The method of claim 1, wherein after the step of registering, by a service registering center, service instances of microservices, the method further comprises:
maintaining, by the service registering center, communication with the service instances using a heartbeat mechanism, and when the communication has been interrupted longer than a predetermined time period, cancelling, by the service registering center, the service instances.
maintaining, by the service registering center, communication with the service instances using a heartbeat mechanism, and when the communication has been interrupted longer than a predetermined time period, cancelling, by the service registering center, the service instances.
3. The method of claim 1, wherein the service gateway, according to the registering records, queries service status of the designated service instances through:
retrieving a network address of the designated service instance from the registering record; and according to the network address, sending a querying request for the service status to the designated service instance, and receiving the query result of the service status of the designated service instance.
retrieving a network address of the designated service instance from the registering record; and according to the network address, sending a querying request for the service status to the designated service instance, and receiving the query result of the service status of the designated service instance.
4. The method of claim 1, wherein the service status comprises one or more of a CPU utilization Date Regue/Date Received 2022-07-18 rate, a memory utilization rate, disk reading and writing, network connectivity, heapSize information, and heapUsedSize information.
5. The method of any of claims 1 through 4, wherein the corresponding operation comprise:
storing the query result of the service status; and/or displaying the query result of the service status on a page; and/or according to the query result of the service status, warning of the service instance having the abnormal service status.
storing the query result of the service status; and/or displaying the query result of the service status on a page; and/or according to the query result of the service status, warning of the service instance having the abnormal service status.
6. A system for monitoring microservices, comprising a service registering center, a monitoring center, and a service gateway, therein:
the service registering center, for registering service instances of microservices;
the monitoring center, for sending a status acquiring request to the service gateway;
the service gateway comprising:
a pre-filter, for receiving the status acquiring request;
a route filter, for acquiring registering record of the service instance designated by the status acquiring request from the service registering center, and according to the registering record, checking service status of the designated service instance;
a post-filter, for sending a query result of the service status to the monitoring center; and the monitoring center, further for receiving the query result of the service status and performing a corresponding operation.
the service registering center, for registering service instances of microservices;
the monitoring center, for sending a status acquiring request to the service gateway;
the service gateway comprising:
a pre-filter, for receiving the status acquiring request;
a route filter, for acquiring registering record of the service instance designated by the status acquiring request from the service registering center, and according to the registering record, checking service status of the designated service instance;
a post-filter, for sending a query result of the service status to the monitoring center; and the monitoring center, further for receiving the query result of the service status and performing a corresponding operation.
7. The system of claim 6, wherein the service registering center is further for:
maintaining communication with the service instances using a heartbeat mechanism, and when the communication has been interrupted longer than a predetermined time period, cancelling the service instances.
maintaining communication with the service instances using a heartbeat mechanism, and when the communication has been interrupted longer than a predetermined time period, cancelling the service instances.
8. The system of claim 6, wherein the route filter comprises:
a service processor, for retrieving a network address of the designated service instance from the Date Regue/Date Received 2022-07-18 registering record; and a broadcasting plug-in, for according to the network address, sending a querying request for the service status to the designated service instance, and receiving the query result of the service status of the designated service instance.
a service processor, for retrieving a network address of the designated service instance from the Date Regue/Date Received 2022-07-18 registering record; and a broadcasting plug-in, for according to the network address, sending a querying request for the service status to the designated service instance, and receiving the query result of the service status of the designated service instance.
9. The system of claim 6, wherein the service status comprises one or more of a CPU utilization rate, a memory utilization rate, disk reading and writing, network connectivity, heapSize information, and heapUsedSize information.
10. The system of any of claims 6 through 9, wherein the monitoring center is specifically for:
storing the query result of the service status;
displaying the query result of the service status on a page; and according to the query result of the service status, warning of the service instance having the abnormal service status.
Date Regue/Date Received 2022-07-18
storing the query result of the service status;
displaying the query result of the service status on a page; and according to the query result of the service status, warning of the service instance having the abnormal service status.
Date Regue/Date Received 2022-07-18
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910048020.9A CN109873736A (en) | 2019-01-18 | 2019-01-18 | A kind of micro services monitoring method and system |
| CN201910048020.9 | 2019-01-18 | ||
| PCT/CN2019/106781 WO2020147331A1 (en) | 2019-01-18 | 2019-09-19 | Micro-service monitoring method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA3168289A1 true CA3168289A1 (en) | 2020-07-23 |
Family
ID=66917690
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA3168289A Pending CA3168289A1 (en) | 2019-01-18 | 2019-09-19 | Method and system for monitoring microservices |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN109873736A (en) |
| CA (1) | CA3168289A1 (en) |
| WO (1) | WO2020147331A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114640657A (en) * | 2020-12-16 | 2022-06-17 | 北京国双科技有限公司 | Multi-registration center fusion method and device |
| CN117609973A (en) * | 2024-01-23 | 2024-02-27 | 江苏博云科技股份有限公司 | Registration center nano-tube method, system, device and server |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109873736A (en) * | 2019-01-18 | 2019-06-11 | 苏宁易购集团股份有限公司 | A kind of micro services monitoring method and system |
| CN110311900A (en) * | 2019-06-19 | 2019-10-08 | 微梦创科网络科技（中国）有限公司 | A kind of service calling method, device, electronic equipment and storage medium |
| CN110708356B (en) * | 2019-09-06 | 2024-01-05 | 国云科技股份有限公司 | Method and system for managing third party application by registry |
| CN110602208B (en) * | 2019-09-12 | 2022-01-21 | 北京笔新互联网科技有限公司 | Distributed micro-service management system and construction method thereof |
| CN111078688B (en) * | 2019-11-18 | 2022-10-18 | 福建天泉教育科技有限公司 | Method for micro-service health check and storage medium |
| CN112988405B (en) * | 2019-12-02 | 2023-12-26 | 中国移动通信集团浙江有限公司 | Automatic degradation method and device for micro-service and computing equipment |
| CN111198804B (en) * | 2019-12-30 | 2023-09-05 | 中电工业互联网有限公司 | Gateway-based industrial Internet platform third-party micro-service monitoring and early warning method |
| CN111277499A (en) * | 2020-01-14 | 2020-06-12 | 浙江华云信息科技有限公司 | Gateway-based real-time effective dynamic routing method |
| CN112291099B (en) * | 2020-11-02 | 2022-07-29 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | Multi-mode registration center architecture switching method under mobile environment |
| CN112579319B (en) * | 2020-12-07 | 2023-09-08 | 中国民航信息网络股份有限公司 | Service calling method and device based on LRU Cache optimization |
| CN113285836B (en) * | 2021-05-27 | 2022-05-10 | 中国人民解放军陆军工程大学 | System and method for enhancing toughness of software system based on micro-service real-time migration |
| CN113938374B (en) * | 2021-12-20 | 2022-06-03 | 飞狐信息技术（天津）有限公司 | Processing method and device for monitoring instrument panel |
| CN114827277B (en) * | 2022-05-06 | 2023-12-01 | 北京思特奇信息技术股份有限公司 | Micro-service system and method based on multi-machine-room container deployment |
| CN115811458A (en) * | 2022-11-17 | 2023-03-17 | 浪潮云信息技术股份公司 | Monitoring method and system based on springboot micro-service |
| CN116319090B (en) * | 2023-05-18 | 2023-08-11 | 中国电子信息产业集团有限公司第六研究所 | Power and environment monitoring system and method based on micro-service |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104349338B (en) * | 2013-07-25 | 2018-01-19 | 普天信息技术有限公司 | A kind of method and system being monitored to sensor access gateway |
| CN107612955A (en) * | 2016-07-12 | 2018-01-19 | 深圳市远行科技股份有限公司 | Micro services provide method, apparatus and system |
| CN106610836B (en) * | 2016-12-23 | 2019-12-31 | 国网信息通信产业集团有限公司 | Micro-service operation management tool |
| CN108306917A (en) * | 2017-01-13 | 2018-07-20 | 中国移动通信集团江西有限公司 | The register method and device of data processing method and device, micro services module |
| US10411973B2 (en) * | 2017-03-20 | 2019-09-10 | Red Hat, Inc. | Automatic microservice problem detection in enterprise applications |
| CN107566153B (en) * | 2017-07-21 | 2020-09-25 | 哈尔滨工程大学 | Self-management micro-service implementation method |
| CN108512689B (en) * | 2017-12-15 | 2021-08-27 | 中国平安财产保险股份有限公司 | Micro-service monitoring method and server |
| CN108282368A (en) * | 2018-01-24 | 2018-07-13 | 云宏信息科技股份有限公司 | A kind of micro services management system, method and computer storage media |
| CN108845910B (en) * | 2018-05-31 | 2024-02-06 | 康键信息技术（深圳）有限公司 | Monitoring method, device and storage medium of large-scale micro-service system |
| CN109873736A (en) * | 2019-01-18 | 2019-06-11 | 苏宁易购集团股份有限公司 | A kind of micro services monitoring method and system |
-
2019
- 2019-01-18 CN CN201910048020.9A patent/CN109873736A/en active Pending
- 2019-09-19 WO PCT/CN2019/106781 patent/WO2020147331A1/en active Application Filing
- 2019-09-19 CA CA3168289A patent/CA3168289A1/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114640657A (en) * | 2020-12-16 | 2022-06-17 | 北京国双科技有限公司 | Multi-registration center fusion method and device |
| CN117609973A (en) * | 2024-01-23 | 2024-02-27 | 江苏博云科技股份有限公司 | Registration center nano-tube method, system, device and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109873736A (en) | 2019-06-11 |
| WO2020147331A1 (en) | 2020-07-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA3168289A1 (en) | Method and system for monitoring microservices | |
| CN105933444B (en) | Based on the service discovery method that registration center and caching mechanism are cooperateed with | |
| CN104168333B (en) | The working method of PROXZONE service platforms | |
| US20140108533A1 (en) | System and method for supporting out-of-order message processing in a distributed data grid | |
| EP3542272B1 (en) | Systems and methods for providing a notification system architecture | |
| US10652080B2 (en) | Systems and methods for providing a notification system architecture | |
| CN109960634B (en) | Application program monitoring method, device and system | |
| CN107872525A (en) | A kind of micro services call framework | |
| CN110311837B (en) | Online service availability detection method and device and computer equipment | |
| CN112637335B (en) | Main/standby mode service deployment method, device, equipment and storage medium | |
| CN104601702B (en) | Cluster remote procedure calling (PRC) method and system | |
| CN112286776A (en) | Method and system for tracking micro-service link | |
| CN107018159B (en) | Service request processing method and device, and service request method and device | |
| US20080313349A1 (en) | Connecting a client to one of a plurality of servers | |
| CN115150419A (en) | Configuration and access method and system for hybrid cloud object storage | |
| CN110505220B (en) | Method and device for supporting OPC protocol to realize dual-computer hot standby and communication terminal | |
| JP3197279B2 (en) | Business takeover system | |
| CN106375102A (en) | Service registration method, application method and correlation apparatus | |
| CN106034164A (en) | Cloud storage gateway file sharing service method and system | |
| CN112564980B (en) | Service monitoring method and system based on micro-service architecture | |
| CN107959696A (en) | A kind of daily record bill processing method and system | |
| CN115065686B (en) | Configuration method, device and system of distributed load balancing system | |
| CN115102999B (en) | DevOps system, service providing method, storage medium and electronic device | |
| CN112988405B (en) | Automatic degradation method and device for micro-service and computing equipment | |
| CN112463317A (en) | Computer room task scheduling method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |
|
| EEER | Examination request |
Effective date: 20220718 |