CN108512689B - Micro-service monitoring method and server - Google Patents
Micro-service monitoring method and server Download PDFInfo
- Publication number
- CN108512689B CN108512689B CN201711348482.XA CN201711348482A CN108512689B CN 108512689 B CN108512689 B CN 108512689B CN 201711348482 A CN201711348482 A CN 201711348482A CN 108512689 B CN108512689 B CN 108512689B
- Authority
- CN
- China
- Prior art keywords
- service
- micro
- log
- monitoring
- request information
- 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.)
- Active
Links
Images
Classifications
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- 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
- 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/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- 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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention is suitable for the technical field of micro-services, and provides a micro-service monitoring method and a server, wherein the method comprises the following steps: generating a plurality of calling request information, wherein each calling request information corresponds to a plurality of micro services, and sending each calling request information to the corresponding micro service; each piece of calling request information is used for enabling the corresponding micro service to generate a monitoring data identifier corresponding to the calling request information; acquiring monitoring data identifiers generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identifier; and monitoring the service data of each micro service according to the acquired service log of each micro service. The method and the server can quickly find the online fault, reduce the time required by fault positioning and enable the monitoring of the micro-service business to be easier.
Description
Technical Field
The invention belongs to the technical field of micro services, and particularly relates to a micro service monitoring method and a server.
Background
The micro-service is an emerging software architecture, a large complex application program is decomposed into a plurality of micro-services, each micro-service can be independently deployed, and the micro-services are loosely coupled. Each microservice is only concerned with completing one task and well completing the task.
At present, the monitoring of a micro-service system and an application level is mature, but because an on-line fault cannot be found quickly under a distributed system, the time required for fault positioning is long, and the monitoring of the micro-service is difficult.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and a server for monitoring a micro-service, so as to solve the problem in the prior art that it is difficult to monitor a micro-service.
The first aspect of the embodiments of the present invention provides a method for monitoring a micro-service, including:
generating a plurality of calling request information, wherein each calling request information corresponds to a plurality of micro services, and sending each calling request information to the corresponding micro service; each piece of calling request information is used for enabling the corresponding micro service to generate a monitoring data identifier corresponding to the calling request information;
acquiring monitoring data identifiers generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identifier;
and monitoring the service data of each micro service according to the acquired service log of each micro service.
Optionally, the call request information includes a micro-service identifier corresponding to each micro-service; the sending each piece of the calling request information to the corresponding micro-service comprises:
and sending each piece of calling request information to a corresponding micro service according to each micro service identifier in each piece of calling request information.
Optionally, a log identifier is corresponding to a service log of each micro service, and the log identifier corresponds to a monitoring data identifier of the micro service; the obtaining the service log of each microservice according to each monitoring data identifier includes:
and acquiring the service logs of the micro-services corresponding to the monitoring data identifications according to the log identifications corresponding to the monitoring data identifications.
Optionally, the monitoring the service data of each microservice according to the obtained service log of each microservice includes:
determining the average time consumption and the service success rate of the service data of each micro service according to the acquired service log of each micro service;
and monitoring the average time consumption and the service success rate of the service data of each micro service according to preset conditions.
Optionally, the determining the service success rate of the service data of each micro service includes:
and sending the acquired service log to a service party for configuration, and determining the service success rate of the service data according to the key in the return code configured by the service party and the value indicating successful configuration.
A second aspect of the embodiments of the present invention provides a server, including a memory and a processor, where the memory stores a computer program operable on the processor, and the processor executes the computer program to implement the following steps:
generating a plurality of calling request information, wherein each calling request information corresponds to a plurality of micro services, and sending each calling request information to the corresponding micro service; each piece of calling request information is used for enabling the corresponding micro service to generate a monitoring data identifier corresponding to the calling request information;
acquiring monitoring data identifiers generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identifier;
and monitoring the service data of each micro service according to the acquired service log of each micro service.
Optionally, the call request information includes a micro-service identifier corresponding to each micro-service; the sending each piece of the calling request information to the corresponding micro-service comprises:
and sending each piece of calling request information to a corresponding micro service according to each micro service identifier in each piece of calling request information.
Optionally, a log identifier is corresponding to a service log of each micro service, and the log identifier corresponds to a monitoring data identifier of the micro service; the obtaining the service log of each microservice according to each monitoring data identifier includes:
and acquiring the service logs of the micro-services corresponding to the monitoring data identifications according to the log identifications corresponding to the monitoring data identifications.
Optionally, the monitoring the service data of each microservice according to the obtained service log of each microservice includes:
determining the average time consumption and the service success rate of the service data of each micro service according to the acquired service log of each micro service;
and monitoring the average time consumption and the service success rate of the service data of each micro service according to preset conditions.
Optionally, the determining the service success rate of the service data of each micro service includes:
and sending the acquired service log to a service party for configuration, and determining the service success rate of the service data according to the key in the return code configured by the service party and the value indicating successful configuration.
A third aspect of embodiments of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the task execution control method described above.
Compared with the prior art, the embodiment of the invention has the following beneficial effects: in the embodiment of the invention, a plurality of pieces of calling request information are generated, each piece of calling request information corresponds to a plurality of micro services, and each piece of calling request information is sent to the corresponding micro service; acquiring monitoring data identifiers generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identifier; and monitoring the service data of each micro service according to the acquired service log of each micro service, thereby being capable of rapidly finding out the on-line fault, reducing the time required by fault positioning and enabling the monitoring of the service of the micro service to be easier.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a flowchart of a micro-service monitoring method provided by an embodiment of the present invention;
FIG. 2 is a monitoring system architecture for microservice services provided by an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a monitoring data identifier provided by an embodiment of the present invention;
FIG. 4 is a flowchart of an implementation of step S103 in FIG. 1;
FIG. 5 is a schematic diagram of an operating environment of a microservice service monitor provided by an embodiment of the present invention;
fig. 6 is a program module diagram of a microservice service monitor provided in an embodiment of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.
In order to explain the technical means of the present invention, the following description will be given by way of specific examples.
Example one
Fig. 1 shows an implementation flow of a task execution control method provided in an embodiment of the present invention, which is detailed as follows:
step S101, generating a plurality of calling request information, wherein each calling request information corresponds to a plurality of micro services, and sending each calling request information to the corresponding micro service; and each piece of calling request information is used for enabling the corresponding micro service to generate a monitoring data identifier corresponding to the calling request information.
The embodiment of the invention monitors the micro-service by setting a special micro-service monitoring system. In one example, fig. 2 shows a micro-service monitoring system architecture exemplified by a good owner micro-service. Kafka is a high throughput distributed publish-subscribe messaging system that can handle all the action flow data in a consumer-scale website; logstash is a tool to receive, process and forward logs; the ElasticSearch is a search server based on Lucene; MySQL is a relational database management system; the Alert server is an alarm server; the Accio Server is a Server of an Accio application program which is developed safely.
The calling request information comprises micro-service identifications corresponding to the micro-services; the sending each piece of the calling request information to the corresponding micro-service comprises: and sending each piece of calling request information to a corresponding micro service according to each micro service identifier in each piece of calling request information.
Specifically, if a call request initiates multi-layer micro-service call, each micro-service provides a monitoring data identifier, and the structure of the monitoring data identifier is shown in fig. 3. The traceId of each monitoring data identity is the same and is used for concatenating the whole call request, and in addition, the spanld is used as the unique identity of each micro-service in one request chain. For the service side of the http and the dubbo service, the status of the service side can be independently constructed, the sql call cannot construct the monitoring data identifier from the sql service side, and only the call condition of the sql service can be obtained from the calling side, so the childstatus records the service call condition from the calling side, and simultaneously can record the condition that the http and the dubbo call do not reach the service side.
In this embodiment, the traceId is a unique id of the request chain, and includes time and a memory address; the spanId is the unique id of each service different on the request chain; a monitoring data identifier can be uniquely confirmed through the traceId and the spanId; project is the request chain root service name, project is the current service name, each service provider constructs its status; the child status is a child service of the current service call, and is an array structure, and each element of the array records the call and return conditions of the child service.
As an implementation manner, the monitoring data identifier may be constructed based on interceptors such as SpringBoot, Mybatis, and Dubbo, the monitoring data identifier is bound with the current thread through threadlocal, and the request chain id is transmitted through http header and dubborpcontext, but not limited thereto.
Step S102, acquiring monitoring data identifications generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identification.
And the service log of each micro service corresponds to a log identifier, and the log identifier corresponds to the monitoring data identifier of the micro service. The obtaining the service log of each microservice according to each monitoring data identifier includes: and acquiring the service logs of the micro-services corresponding to the monitoring data identifications according to the log identifications corresponding to the monitoring data identifications.
In this embodiment, a request id is uniformly added to each service Log based on Log4j2MDC, so that the service Log is associated with monitoring data Status, but the present invention is not limited thereto. In other embodiments, the request id may also be uniformly added to each service log in other manners, so that the service log is associated with the monitoring data Status.
And step S103, monitoring the service data of each micro service according to the acquired service log of each micro service.
Referring to fig. 4, in an embodiment, the implementation process of step S103 may be:
step S201, according to the acquired service log of each micro service, determining the average time consumption and the service success rate of the service data of each micro service.
With reference to fig. 2, in this embodiment, data obtained from the elastic search statistics in the latest preset time period (for example, in the latest five minutes) is stored in the db database, where the data includes time consumption statistics, exception statistics, service return code distribution, service success rate, and the like of each interface of each micro service. Then, the data of each micro-service is counted from the db database according to time units such as hours, days, weeks, months and the like, and the information such as average time consumption, service success rate and the like of the service data of each micro-service is determined.
In one embodiment, the determining the service success rate of the service data of each microservice includes: and sending the acquired service log to a service party for configuration, and determining the service success rate of the service data according to the key in the return code configured by the service party and the value indicating successful configuration.
It can be understood that, since most services perform abnormal interception on the interface, the return codes are diversified, and thus, if the service success rate of the service data of each micro service is determined directly according to the received return codes, the determined service success rate of the service data of each micro service is seriously deviated from the true situation.
In this embodiment, the returned log information is collected without any processing, a configuration interface is provided for the service party to configure, and finally, statistics of the success rate is performed according to the key of the return code configured by the service party and the value indicating success. The method of the embodiment can ensure that the statistics of the service success rate and the data extraction are not coupled, the statistics of the service success rate is accurate and reliable, all original data of the return code can be reserved so as to be convenient to check, in addition, a uniform front-end interface is provided for configuration and query, and the maintenance and management are also convenient.
Step S202, monitoring the average consumed time and the service success rate of the service data of each micro service according to preset conditions.
In this step, the preset condition is a preset value range, and when the average consumed time of the service data and/or the service success rate exceeds the corresponding preset value range, alarm information is generated and sent to the corresponding intelligent terminal in a short message, a WeChat, an email or the like, so that the related personnel can timely know the alarm abnormality. In addition, the total number of requests and the error rate can be monitored in the step.
For example, it may be set to one period every 5 minutes, and two adjacent periods may be alarmed if the statistical data is over-limited or fluctuates greatly, and the default threshold is shown in table 1.
TABLE 1
| Index (I) | Threshold value | Positive and negative fluctuation | Remarks for note |
| Average time consumption | >10s | >500% (total number of requests greater than 100) | Filtering low frequency requests |
| Success rate of service | <50％ | >50% (total number of requests greater than 100) | Filtering low frequency requests |
| Total number of requests | [avg-2δ,avg+2δ]Outer cover | >90％ | Outside of 95% confidence interval |
| Error rate | >10％ | >60% (difference between two periods is greater than 1000) |
In addition, the acquired micro-service monitoring data identification, the service log and the monitoring alarm information can be generated into a report, so that developers can visually and quickly know the application condition, and the optimization and improvement of the application program are facilitated.
The micro-service monitoring method generates a plurality of calling request information, each calling request information corresponds to a plurality of micro-services, and sends each calling request information to the corresponding micro-service; acquiring monitoring data identifiers generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identifier; and monitoring the service data of each micro service according to the acquired service log of each micro service, thereby being capable of rapidly finding out the on-line fault, reducing the time required by fault positioning and enabling the monitoring of the service of the micro service to be easier.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Example two
Corresponding to the micro-service monitoring method described in the foregoing embodiment, fig. 5 shows a schematic view of an operating environment of a micro-service monitoring program provided in an embodiment of the present invention. For convenience of explanation, only the portions related to the present embodiment are shown.
In the present embodiment, the microservice service monitor 500 is installed and run in the server 50. The server 50 may include, but is not limited to, a memory 501 and a processor 502. FIG. 5 only shows server 50 with components 501-502, but it is to be understood that not all of the shown components are required and that more or fewer components can alternatively be implemented.
The storage 501 may in some embodiments be an internal storage unit of the server 50, such as a hard disk or a memory of the server 50. The memory 501 may also be an external storage device of the server 50 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the server 50. Further, the memory 501 may also include both an internal storage unit and an external storage device of the terminal device 50. The memory 501 is used for storing application software installed in the server 50 and various data, such as program codes of the micro service monitoring program 500. The memory 501 may also be used to temporarily store data that has been output or is to be output.
The processor 502 may be a Central Processing Unit (CPU), microprocessor or other data Processing chip in some embodiments, and is used to run program codes stored in the memory 501 or process data, such as executing the micro service monitoring program 500.
The server 50 may also include a display, which in some embodiments may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch, and the like.
Please refer to fig. 6, which is a block diagram of a microservice service monitor 500 according to an embodiment of the present invention. In this embodiment, the micro-service business monitoring program 500 may be divided into one or more modules, and the one or more modules are stored in the memory 501 and executed by one or more processors (in this embodiment, the processor 502) to complete the present invention. For example, in fig. 6, the microservice service monitoring program 500 may be divided into a call information generating module 601, an obtaining module 602, and a monitoring module 603. The module referred to in the present invention refers to a series of computer program instruction segments capable of performing specific functions, and is more suitable than a program for describing the execution process of the microservice service monitoring program 500 in the server 50. The following description will specifically describe the functions of the module 601 and 603.
The calling information generating module 601 is configured to generate multiple pieces of calling request information, where each piece of calling request information corresponds to multiple micro services, and send each piece of calling request information to a corresponding micro service; and each piece of calling request information is used for enabling the corresponding micro service to generate a monitoring data identifier corresponding to the calling request information.
The obtaining module 602 is configured to obtain a monitoring data identifier generated by each micro service, and obtain a service log of each micro service according to each monitoring data identifier.
And the monitoring module 603 is configured to monitor the service data of each microservice according to the obtained service log of each microservice.
As an implementation manner, the calling request information includes a micro service identifier corresponding to each micro service; the calling information generating module 601 is configured to: and sending each piece of calling request information to a corresponding micro service according to each micro service identifier in each piece of calling request information.
As another implementable manner, a log identifier is corresponding to a service log of each micro service, and the log identifier corresponds to a monitoring data identifier of the micro service; the obtaining module 602 is configured to: and acquiring the service logs of the micro-services corresponding to the monitoring data identifications according to the log identifications corresponding to the monitoring data identifications.
Optionally, the monitoring module 603 is configured to:
determining the average time consumption and the service success rate of the service data of each micro service according to the acquired service log of each micro service;
and monitoring the average time consumption and the service success rate of the service data of each micro service according to preset conditions.
Further, the monitoring module 603 is configured to: and sending the acquired service log to a service party for configuration, and determining the service success rate of the service data according to the key in the return code configured by the service party and the value indicating successful configuration.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (9)
1. A micro-service monitoring method is characterized by comprising the following steps:
generating a plurality of calling request information, wherein each calling request information corresponds to a plurality of micro services, and sending each calling request information to the corresponding micro service; each piece of calling request information is used for enabling the corresponding micro service to generate a monitoring data identifier corresponding to the calling request information;
acquiring monitoring data identifiers generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identifier;
monitoring the service data of each micro service according to the acquired service log of each micro service;
the monitoring the service data of each micro service according to the acquired service log of each micro service includes:
determining the service success rate of the service data of each micro service according to the acquired service log of each micro service;
monitoring the service success rate of the service data of each micro service according to a preset condition;
the determining the service success rate of the service data of each micro service according to the acquired service log of each micro service includes:
collecting the returned service log, and not processing the service log;
and sending the service log to a service party for configuration, and determining the service success rate of the service data according to the key in the return code configured by the service party and the value indicating successful configuration.
2. The micro-service business monitoring method of claim 1, wherein the invocation request information includes a micro-service identification corresponding to each of the micro-services; the sending each piece of the calling request information to the corresponding micro-service comprises:
and sending each piece of calling request information to a corresponding micro service according to each micro service identifier in each piece of calling request information.
3. The micro-service business monitoring method of claim 1, wherein a log identifier is associated with the business log of each micro-service, and the log identifier corresponds to the monitoring data identifier of the micro-service; the obtaining the service log of each microservice according to each monitoring data identifier includes:
and acquiring the service logs of the micro-services corresponding to the monitoring data identifications according to the log identifications corresponding to the monitoring data identifications.
4. The micro-service business monitoring method according to any one of claims 1 to 3, wherein the monitoring the business data of each micro-service according to the obtained business log of each micro-service comprises:
determining the average consumed time of the service data of each micro service according to the acquired service log of each micro service;
and monitoring the average consumed time of the service data of each micro service according to preset conditions.
5. A server, comprising a memory and a processor, wherein the memory stores a computer program operable on the processor, and the processor executes the computer program to perform the steps of:
generating a plurality of calling request information, wherein each calling request information corresponds to a plurality of micro services, and sending each calling request information to the corresponding micro service; each piece of calling request information is used for enabling the corresponding micro service to generate a monitoring data identifier corresponding to the calling request information;
acquiring monitoring data identifiers generated by each micro service, and acquiring service logs of each micro service according to each monitoring data identifier;
monitoring the service data of each micro service according to the acquired service log of each micro service;
the monitoring the service data of each micro service according to the acquired service log of each micro service includes:
determining the service success rate of the service data of each micro service according to the acquired service log of each micro service;
monitoring the service success rate of the service data of each micro service according to a preset condition;
the determining the service success rate of the service data of each micro service according to the acquired service log of each micro service includes:
collecting the returned service log, and not processing the service log;
and sending the service log to a service party for configuration, and determining the service success rate of the service log according to the key in the return code configured by the service party and the value indicating successful configuration.
6. The server according to claim 5, wherein the call request information includes a micro-service identification corresponding to each of the micro-services; the sending each piece of the calling request information to the corresponding micro-service comprises:
and sending each piece of calling request information to a corresponding micro service according to each micro service identifier in each piece of calling request information.
7. The server according to claim 5, wherein each service log of the micro-service corresponds to a log identifier, and the log identifier corresponds to a monitoring data identifier of the micro-service; the obtaining the service log of each microservice according to each monitoring data identifier includes:
and acquiring the service logs of the micro-services corresponding to the monitoring data identifications according to the log identifications corresponding to the monitoring data identifications.
8. The server according to any one of claims 5 to 7, wherein the monitoring the service data of each microservice according to the obtained service log of each microservice includes:
determining the average consumed time of the service data of each micro service according to the acquired service log of each micro service;
and monitoring the average consumed time of the service data of each micro service according to preset conditions.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711348482.XA CN108512689B (en) | 2017-12-15 | 2017-12-15 | Micro-service monitoring method and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711348482.XA CN108512689B (en) | 2017-12-15 | 2017-12-15 | Micro-service monitoring method and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108512689A CN108512689A (en) | 2018-09-07 |
| CN108512689B true CN108512689B (en) | 2021-08-27 |
Family
ID=63374776
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711348482.XA Active CN108512689B (en) | 2017-12-15 | 2017-12-15 | Micro-service monitoring method and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108512689B (en) |
Families Citing this family (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109213616A (en) * | 2018-09-25 | 2019-01-15 | 江苏润和软件股份有限公司 | A kind of micro services software systems method for detecting abnormality based on calling map analysis |
| CN109144487B (en) * | 2018-09-26 | 2024-02-13 | 河南智锐科技有限公司 | Method, device, computer equipment and storage medium for developing business of parts |
| CN109522115A (en) * | 2018-10-11 | 2019-03-26 | 平安科技（深圳）有限公司 | Resource allocation method, electronic equipment and storage medium |
| CN109542718B (en) * | 2018-10-22 | 2023-02-07 | 中国平安人寿保险股份有限公司 | Service call monitoring method and device, storage medium and server |
| CN111143154A (en) * | 2018-11-06 | 2020-05-12 | 招商局国际信息技术有限公司 | Wharf operating system operation monitoring method and device, server and storage medium |
| CN109672741B (en) * | 2018-12-25 | 2020-01-14 | 南方电网数字电网研究院有限公司 | Micro-service monitoring method and device, computer equipment and storage medium |
| CN109873736A (en) * | 2019-01-18 | 2019-06-11 | 苏宁易购集团股份有限公司 | A kind of micro services monitoring method and system |
| CN112910684B (en) * | 2019-04-03 | 2022-07-26 | 福建天泉教育科技有限公司 | Method and terminal for monitoring key data through real-time streaming platform |
| CN110297738A (en) * | 2019-05-21 | 2019-10-01 | 深圳壹账通智能科技有限公司 | Monitoring method, device, equipment and the storage medium of system service |
| CN110535902A (en) * | 2019-07-16 | 2019-12-03 | 平安普惠企业管理有限公司 | The processing method and electronic device of monitoring intelligent are realized based on micro services |
| CN110427299B (en) * | 2019-07-19 | 2022-02-11 | 腾讯科技（深圳）有限公司 | Log processing method, related device and system for micro-service system application |
| CN110324209B (en) * | 2019-08-02 | 2020-10-09 | 泰康保险集团股份有限公司 | Micro-service system monitoring method and device, electronic equipment and computer readable medium |
| CN110532148B (en) * | 2019-08-12 | 2022-12-23 | 北京金堤科技有限公司 | Monitoring method and device of micro-service system |
| CN110765089A (en) * | 2019-10-25 | 2020-02-07 | 北京浪潮数据技术有限公司 | Distributed equipment and log recording method, device and storage medium thereof |
| CN110943858B (en) * | 2019-11-21 | 2022-07-12 | 中国联合网络通信集团有限公司 | Fault positioning method and device |
| CN110888783B (en) * | 2019-11-21 | 2023-07-07 | 望海康信(北京)科技股份公司 | Method and device for monitoring micro-service system and electronic equipment |
| CN111078447B (en) * | 2019-11-24 | 2023-09-19 | 杭州安恒信息技术股份有限公司 | Abnormality positioning method, device, equipment and medium in micro-service architecture |
| CN111125728A (en) * | 2019-12-04 | 2020-05-08 | 深圳昂楷科技有限公司 | Method and device for treating database security problems and treatment equipment |
| CN111176955A (en) * | 2020-01-07 | 2020-05-19 | 深圳壹账通智能科技有限公司 | Monitoring method, device and equipment of microservice and computer readable storage medium |
| CN111488289B (en) * | 2020-04-26 | 2024-01-23 | 支付宝实验室(新加坡)有限公司 | Fault positioning method, device and equipment |
| CN111786813B (en) * | 2020-06-05 | 2022-08-05 | 北京思特奇信息技术股份有限公司 | Service problem processing method based on log |
| CN112035317B (en) * | 2020-08-28 | 2022-06-17 | 北京浪潮数据技术有限公司 | Micro-service link monitoring method, device, equipment and medium |
| CN112685252A (en) * | 2020-12-25 | 2021-04-20 | 深圳前海微众银行股份有限公司 | Micro-service monitoring method, device, equipment and storage medium |
| CN112685261B (en) * | 2021-01-05 | 2022-10-04 | 武汉长江通信智联技术有限公司 | Micro-service operation state monitoring method based on observer mode |
| CN113190373B (en) * | 2021-05-31 | 2022-04-05 | 中国人民解放军国防科技大学 | Micro-service system fault root cause positioning method based on fault feature comparison |
| CN113824590B (en) * | 2021-09-18 | 2024-04-26 | 武汉联影医疗科技有限公司 | Method for predicting problem in micro service network, computer device, and storage medium |
| CN113938374B (en) * | 2021-12-20 | 2022-06-03 | 飞狐信息技术（天津）有限公司 | Processing method and device for monitoring instrument panel |
| CN116302862B (en) * | 2023-05-18 | 2023-08-11 | 浙江华东工程数字技术有限公司 | Monitoring alarm method and system under micro-service architecture |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105740376A (en) * | 2016-01-27 | 2016-07-06 | 北京铭万智达科技有限公司 | API (Application Program Interface) calling statistics and monitoring method in micro-service |
| CN106326017A (en) * | 2016-08-17 | 2017-01-11 | 广东亿迅科技有限公司 | Realization system for call chain based on Annotation application |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN106790718A (en) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | Service call link analysis method and system |
| CN106850782A (en) * | 2017-01-17 | 2017-06-13 | 泰康保险集团股份有限公司 | For the method and system of log processing |
| CN107135276A (en) * | 2017-06-28 | 2017-09-05 | 北京中电普华信息技术有限公司 | A kind of full link monitoring methods, devices and systems under micro services framework |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100031316A1 (en) * | 2008-07-30 | 2010-02-04 | International Business Machines Corporation | System access log monitoring and reporting system |
| CN105978728B (en) * | 2016-06-20 | 2019-09-03 | 深圳前海微众银行股份有限公司 | The monitoring method of intelligent monitor system and operational indicator |
| CN106126672A (en) * | 2016-06-27 | 2016-11-16 | 安徽科成信息科技有限公司 | A kind of update method of Linking All Classes network monitoring daily record |
-
2017
- 2017-12-15 CN CN201711348482.XA patent/CN108512689B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105740376A (en) * | 2016-01-27 | 2016-07-06 | 北京铭万智达科技有限公司 | API (Application Program Interface) calling statistics and monitoring method in micro-service |
| CN106326017A (en) * | 2016-08-17 | 2017-01-11 | 广东亿迅科技有限公司 | Realization system for call chain based on Annotation application |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN106850782A (en) * | 2017-01-17 | 2017-06-13 | 泰康保险集团股份有限公司 | For the method and system of log processing |
| CN106790718A (en) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | Service call link analysis method and system |
| CN107135276A (en) * | 2017-06-28 | 2017-09-05 | 北京中电普华信息技术有限公司 | A kind of full link monitoring methods, devices and systems under micro services framework |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108512689A (en) | 2018-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108512689B (en) | Micro-service monitoring method and server | |
| CN110908883B (en) | User portrait data monitoring method, system, equipment and storage medium | |
| CN108038130B (en) | Automatic false user cleaning method, device, equipment and storage medium | |
| CN110362455B (en) | Data processing method and data processing device | |
| WO2019076001A1 (en) | Information updating method and device | |
| CN104426947A (en) | Terminal intelligent updating method and system, terminal and data updating server | |
| CN113760677A (en) | Abnormal link analysis method, device, equipment and storage medium | |
| CN112087320A (en) | Abnormity positioning method and device, electronic equipment and readable storage medium | |
| CN116737765A (en) | Service alarm information processing method and device, electronic equipment and storage medium | |
| CN111062503B (en) | Power grid monitoring alarm processing method, system, terminal and storage medium | |
| CN107885634B (en) | Method and device for processing abnormal information in monitoring | |
| CN105100216A (en) | Multi-service monitoring method and device | |
| CN118014558A (en) | Fault processing method and device, nonvolatile storage medium and electronic equipment | |
| CN110011845B (en) | Log collection method and system | |
| CN117271177A (en) | Root cause positioning method and device based on link data, electronic equipment and storage medium | |
| CN112965793B (en) | Identification analysis data-oriented data warehouse task scheduling method and system | |
| CN113297261A (en) | Early warning method and device for data processing, server and storage medium | |
| EA201800181A1 (en) | POS TERMINAL NETWORK MANAGEMENT SYSTEM | |
| CN112035315A (en) | Webpage data monitoring method and device, computer equipment and storage medium | |
| CN118331823B (en) | Method and system for managing and monitoring alarm of space engineering business operation log | |
| CN111130919B (en) | Interface monitoring method, device and system and storage medium | |
| CN117057527B (en) | Intelligent operation and maintenance method and system for industrial Internet of things of automobile manufacturing equipment | |
| CN118093707B (en) | Multi-mode data acquisition method, system, terminal and storage medium | |
| CN110601875B (en) | Information output method, information output apparatus, management device, and computer-readable storage medium | |
| CN117955822A (en) | Log monitoring method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |