CN109542718B - Service call monitoring method and device, storage medium and server - Google Patents
Service call monitoring method and device, storage medium and server Download PDFInfo
- Publication number
- CN109542718B CN109542718B CN201811232409.0A CN201811232409A CN109542718B CN 109542718 B CN109542718 B CN 109542718B CN 201811232409 A CN201811232409 A CN 201811232409A CN 109542718 B CN109542718 B CN 109542718B
- Authority
- CN
- China
- Prior art keywords
- service
- server
- calling
- call
- identifier
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
- G06F11/3082—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting the data filtering being achieved by aggregating or compressing the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/875—Monitoring of systems including the internet
Abstract
The invention relates to the field of data monitoring, in particular to a monitoring method, a monitoring device, a storage medium and a server for service invocation, wherein the method comprises the following steps: a first service end receives a service calling request, and generates a service calling identifier and a calling data log containing the service calling identifier; transmitting the service calling identifier to a second server according to the service calling request; the second server generates a calling data log containing the service calling identifier according to the service calling request and the service calling identifier, and transmits the service calling identifier to a third server according to the service calling request; the first service end, the second service end and the third service end are connected with a data aggregation center, and the calling data logs are sent to the data aggregation center; and the data aggregation center generates a service calling link from the calling data log with the same service calling identifier according to the service calling identifier. The invention can effectively monitor the service calling.
Description
Technical Field
The invention relates to the field of data monitoring, in particular to a monitoring method and device for service invocation, a storage medium and a server.
Background
With the development of internet technology, the number of users of a client is increasing, the functions of the client are also increasing, multiple services are needed to participate together behind each simple function, for example, the client requests one piece of data at the front end, multiple services need to be started to respond to the request after the request is sent to a background server, target data needed by the client is obtained, then the target data is returned to the client, the phenomenon that some functions cannot normally operate occurs during a certain period of time in the operation process of the client, normal operation of the functions is then restored, and some clients cannot normally respond within a period of time, so how to quickly find out a specific problem is a problem that needs to be solved in the industry at present.
Disclosure of Invention
In order to overcome the technical problems, in particular to the problem that the prior art cannot effectively monitor the relationship among a plurality of services, the following technical scheme is provided:
in a first aspect, the present invention provides a method for monitoring service invocation, including:
a first service end receives a service calling request, and generates a service calling identifier and a calling data log containing the service calling identifier; transmitting the service calling identifier to a second server according to the service calling request;
the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request, so that the third server generates the call data log containing the service call identifier according to the service call request and the service call identifier;
the first service end, the second service end and the third service end are connected with a data aggregation center, and the call data logs are sent to the data aggregation center;
and the data aggregation center generates the call data logs with the same service call identifier into a service call link according to the service call identifier.
Further, after the data aggregation center generates the service invocation link from the invocation data log having the same service invocation identifier according to the service invocation identifier, the method further includes:
monitoring the integrity of the service invocation link;
if the integrity of the service calling link does not meet the preset condition, determining that the service calling link has interruption, acquiring an abnormal service end corresponding to the interruption, and sending alarm information to the abnormal service end.
Further, after the data aggregation center generates the service invocation link from the invocation data log with the same service invocation identifier according to the service invocation identifier, the method further includes:
and counting the calling frequency of each service terminal in the service calling link, and configuring a preset standby service terminal as the service terminal when the calling frequency of a certain service terminal is greater than a preset frequency.
Further, the first server, the second server, and the third server are connected to a data aggregation center, and send the call data log to the data aggregation center, including:
and the first service end, the second service end and the third service end are connected with a data aggregation center, and asynchronously send the call data log to the data aggregation center.
Further, the transmitting the service invocation identifier to a second server according to the service invocation request includes:
the first server determines a second server according to the service calling request and generates a new service calling request;
and transmitting the new service calling request and the service calling identifier to a second server.
Further, the data aggregation center generates the call data log with the same service call identifier into a service call link according to the service call identifier, including:
the data aggregation center acquires call data logs with the same service call identifier; acquiring a time value of the call data log; and generating a service calling link from the calling data log according to the time value sequence.
In a second aspect, the present invention provides a monitoring apparatus for service invocation, including a service module and a data aggregation center module, where the service module includes a first service end, a second service end, and a third service end; wherein the content of the first and second substances,
the first server is used for receiving a service calling request and generating a service calling identifier and a calling data log containing the service calling identifier; transmitting the service calling identifier to a second server according to the service calling request;
the second server is used for generating a calling data log containing the service calling identifier according to the service calling request and the service calling identifier, and transmitting the service calling identifier to a third server according to the service calling request, so that the third server generates the calling data log containing the service calling identifier according to the service calling request and the service calling identifier;
a data aggregation center module: the system comprises a first server, a second server and a third server, wherein the first server, the second server and the third server are used for being connected with the first server, the second server and the third server and receiving the call data logs sent by the first server, the second server and the third server; and generating a service calling link from the calling data log with the same service calling identifier according to the service calling identifier.
Further, the data aggregation center module further performs:
and counting the calling frequency of each service end in the service calling chain circuit, and configuring a preset standby service end as the service end when the calling frequency of a certain service end is greater than the preset frequency.
In a third aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the service call monitoring method described above.
In a fourth aspect, the present invention also provides a server, which includes one or more processors, a memory, and one or more computer programs, wherein the one or more computer programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to perform the service call monitoring method described above.
Compared with the prior art, the invention has the following beneficial effects:
the invention provides a method for monitoring the calling relationship and calling information among a plurality of services for completing a data request, wherein a first service end generates a service calling identifier and a calling data log containing the service calling identifier after receiving a service calling request; then transmitting the service calling identifier to a second server; similarly, the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request; and after generating a call data log, each server sends the call data log to the data aggregation center, the data aggregation center generates a service call link from the call data log with the same service call identifier according to the service call identifier, so that the call relation among services can be known definitely, the services required by each service can be positioned quickly, the problems in the service call process can be counted and found through the service call link subsequently, the problems in each server are checked according to the service call link, the normal operation of each server is ensured, and the normal response of a data request is ensured.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The foregoing and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a flow chart illustrating a monitoring method for service invocation according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating a monitoring method for service invocation according to another embodiment of the present invention;
FIG. 3 is a schematic diagram of a monitoring device for service invocation according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative only and should not be construed as limiting the invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, or operations, but do not preclude the presence or addition of one or more other features, integers, steps, operations, or groups thereof.
It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
It will be appreciated by those skilled in the art that the terms "application," "computer program" and similar terms used herein refer to the same concepts known to those skilled in the art that refer to computer software electronically-adapted to be organized into a series of computer instructions and associated data sources. Unless otherwise specified, such nomenclature is not itself limited by the programming language class, level, or operating system or platform upon which it depends. Of course, such concepts are not limited to any type of terminal.
An embodiment of the present invention provides a monitoring method for service invocation, as shown in fig. 1, the method includes the following steps:
s10: a first service end receives a service calling request, and generates a service calling identifier and a calling data log containing the service calling identifier; and transmitting the service calling identifier to a second server according to the service calling request.
In an item or a client, when a client initiates a request, the request needs to be used for some services, the request of the client is transmitted to a first service end at this time, the first service end is used for processing an initial client request, the first service end generates a service invocation identifier and an invocation data log at the first service end after receiving the service invocation request, then processes the service invocation request according to a service logic of the first service end, and determines a service end which is needed to be used by a subsequent service according to the service invocation request. For example, a client initiates a request, the request first reaches a first server S1, the first server S1 generates a service invocation identifier, and generates an invocation data log after processing the request, and at the same time, determines a subsequent intermediate server to be invoked, in this embodiment, defines the intermediate server invoked by the first server S1 as a second server S2, and then transmits the service invocation identifier to the second server.
S20: and the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request, so that the third server generates the call data log containing the service call identifier according to the service call request and the service call identifier.
After receiving the service calling request and the service calling identifier sent by the first server, the second server processes the service calling request according to the service logic of the second server, generates a calling data log containing the service calling identifier, and determines a server to be used by a successor according to the service calling request, in this embodiment, the server used by the successor of the second server is defined as a third server, and then the service calling identifier is transmitted to the third server; similarly, the third server receives the service call request and the service call identifier sent by the second server, processes the service call request according to the service logic of the third server, and generates a call data log containing the service call identifier.
S30: and the first service end, the second service end and the third service end are connected with a data aggregation center, and the call data log is sent to the data aggregation center.
In this embodiment, the first service end, the second service end and the third service end are connected to the data aggregation center, and it can be known that the first service end, the second service end and the third service end are not three designated service ends, but represent service ends required to be used in a service calling process, the service ends have a front-back calling relationship, the first service end directly calls the second service end, the second service end directly calls the third service end, a calling data log of the service end is generated after the first service end, the second service end and the third service end process a service calling request each time, and then the calling data log is sent to the data aggregation center.
S40: and the data aggregation center generates the call data logs with the same service call identifier into a service call link according to the service call identifier.
And after receiving the call data logs generated by each service end processing the service call request each time, the data aggregation center generates a service call link from the call data logs with the same service call identifier according to the service call identifier contained in each call data log, so as to generate a whole link for service call, and then the data aggregation center can count and find the problems occurring in the service call process through the service call link, and then the problems occurring in each service end are checked according to the service call link.
The embodiment provides a method for monitoring the call relation and call information among a plurality of services completing a data request, wherein a first service end generates a service call identifier and a call data log containing the service call identifier after receiving a service call request; then transmitting the service calling identifier to a second server; similarly, the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request; and after generating a call data log, each server sends the call data log to the data aggregation center, the data aggregation center generates a service call link from the call data log with the same service call identifier according to the service call identifier, so that the call relation among services can be known definitely, the services required by each service can be positioned quickly, the problems in the service call process can be counted and found through the service call link subsequently, the problems in each server are checked according to the service call link, the normal operation of each server is ensured, and the normal response of a data request is ensured.
In an embodiment of the present invention, after the data aggregation center generates the call data log with the same service call identifier into a service call link according to the service call identifier, the method further includes:
monitoring the integrity of the service call link;
if the integrity of the service calling link does not meet the preset condition, determining that the service calling link has interruption, acquiring an abnormal service end corresponding to the interruption, and sending alarm information to the abnormal service end.
In the embodiment, whether the request is normally processed is determined and judged by monitoring the integrity of a service call link, if the integrity of the service call link does not meet a preset condition, the service call link is determined to have interruption, namely, the required service in one call request cannot be correctly and timely fed back, at the moment, an abnormal service end corresponding to the interruption can be obtained from a call data log of the last service end of the service call link, and then alarm information is sent to the abnormal service end, for example, the alarm information is sent to an operator or a maintenance worker of the service end, so that problems occurring in the service ends are quickly and efficiently checked out, the normal operation of each service end is ensured, and the data request of the client can be normally responded.
In an embodiment of the present invention, as shown in fig. 2, after the data aggregation center generates the call data log with the same service call identifier into a service call link according to the service call identifier, the method further includes:
s50: and counting the calling frequency of each service end in the service calling chain circuit, and configuring a preset standby service end as the service end when the calling frequency of a certain service end is greater than the preset frequency.
In this embodiment, after a service call link is generated by the data aggregation center, the call frequency of each service end in the service call link line may be further counted, specifically, the call frequency of each service end in the service call link within a preset time period may be counted, when the call frequency of a certain service end within a period of time is greater than the preset frequency, the service performance of the service end within the period of time thereafter needs to be improved, and a problem that the processing capability of the service end cannot meet a service requirement at the moment, so that the client cannot obtain a normal response occurs is avoided.
In an embodiment of the present invention, the connecting the first server, the second server, and the third server with the data aggregation center, and sending the call data log to the data aggregation center includes:
and the first service end, the second service end and the third service end are connected with a data aggregation center, and asynchronously send the call data log to the data aggregation center.
In order to ensure that each service end can respond to the service request in time during the service processing peak period, in this embodiment, the first service end, the second service end, and the third service end are connected to the data aggregation center, and asynchronously send the call data log to the data aggregation center, and the call data log is sent to the data aggregation center without generating the call data log each time. Preferably, the request quantity of historical different time periods is acquired, the time period that the request quantity is smaller than the preset data quantity is determined, and the generated call data logs which are not sent are sent to the data aggregation center in the time periods. For example, in the acquired historical daily request quantity, the request quantity in the time periods of 0-5 and 12-14.
In an embodiment of the present invention, the transmitting the service invocation identifier to the second server according to the service invocation request includes:
the first server side determines a second server side according to the service calling request and generates a new service calling request;
and transmitting the new service calling request and the service calling identifier to a second server.
In this embodiment, because the processing logic of different service ends is different, the received service invocation request is also applied differently, when the first service end receives the service invocation request, for example, the first service end receives the service invocation request directly sent by the client, then the first service end processes the received service invocation request, and determines that the second service end needs to be invoked according to the processing logic, at this time, the service invocation request is generated into a new service invocation request, and the new service invocation request can be quickly identified and processed by the second service end without being analyzed again, and then the new service invocation request and the service invocation identifier are transmitted to the second service end. Similarly, if the second server determines that the third server needs to be called, the received service calling request is generated into a new service calling request and then is sent to the third server, and the third server can directly identify the service calling request and then process the service calling request, so that the service logic operation of the third server is completed quickly.
Furthermore, because different servers are configured with different resources, and different servers have different computing capabilities and different processing capabilities, in this embodiment, a server with a stronger computing capability may also be obtained, so that the servers can analyze the service request by themselves, and a server with a stronger computing capability only processes the service logic of the server, and then directly forwards the service request to the next server, and the next server with a stronger computing capability analyzes the service request and then performs service processing.
In an embodiment of the present invention, the generating, by the data aggregation center, the service invocation link from the invocation data log having the same service invocation identifier according to the service invocation identifier includes:
the data aggregation center obtains call data logs with the same service call identifier; acquiring a time value of the call data log; and generating a service calling link from the calling data log according to the time value sequence.
In the embodiment, in order to accurately determine the service calling sequence during each service calling, after receiving the calling data logs, the data aggregation center acquires calling data logs with the same service calling identifier, then acquires the time value of each calling data log, generates service calling links by the calling data logs according to the time value sequence, and generates the service calling links according to the calling sequence of the actual service to each service, so that the calling sequence of each service in each service calling link is accurately determined, and a data basis is provided for the problem troubleshooting of the subsequent service.
As shown in fig. 3, in another embodiment, the present invention provides a monitoring apparatus for service invocation, which includes a service module 10 and a data aggregation center module 20: the service module 10 includes a first service end 101, a second service end 102 and a third service end 103; wherein the content of the first and second substances,
the first service terminal 101 is configured to receive a service invocation request, and generate a service invocation identifier and an invocation data log including the service invocation identifier; transmitting the service calling identifier to the second server 102 according to the service calling request;
the second server 102 is configured to generate a call data log including the service call identifier according to the service call request and the service call identifier, and transmit the service call identifier to the third server 103 according to the service call request, so that the third server 103 generates the call data log including the service call identifier according to the service call request and the service call identifier;
the data aggregation center module 20: the system comprises a first server 101, a second server 102 and a third server 103, and is used for connecting with the first server 101, the second server 102 and the third server 103, and receiving the call data logs sent by the first server 101, the second server 102 and the third server 103; and generating a service calling link from the calling data log with the same service calling identifier according to the service calling identifier.
In an embodiment of the present invention, the data aggregation center module 20 further performs:
monitoring the integrity of the service invocation link;
if the integrity of the service calling link does not meet the preset condition, determining that the service calling link has interruption, acquiring an abnormal service end corresponding to the interruption, and sending alarm information to the abnormal service end.
In an embodiment of the present invention, the data aggregation center module 20 further performs:
and counting the calling frequency of each service end in the service calling chain circuit, and configuring a preset standby service end as the service end when the calling frequency of a certain service end is greater than the preset frequency.
In an embodiment of the present invention, when the first server 101, the second server 102, and the third server 103 execute sending the call data log to the data aggregation center module 20, the method includes:
the first server 101, the second server 102 and the third server 103 asynchronously send the call data log to the data aggregation center module 20.
In an embodiment of the present invention, the transmitting, by the first server 101, the service invocation identifier to the second server according to the service invocation request includes:
the first service terminal 101 determines the second service terminal 102 according to the service calling request and generates a new service calling request;
and transmitting the new service calling request and the service calling identifier to the second server 102.
In an embodiment of the present invention, the data aggregation center module 20 executes to generate the service invocation link from the invocation data log having the same service invocation identifier according to the service invocation identifier, including:
the data aggregation center module 20 obtains call data logs with the same service call identifier; acquiring a time value of the call data log; and generating a service calling link from the calling data log according to the time value sequence.
In another embodiment, the present invention provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the service call monitoring method described in the above embodiment. The computer-readable storage medium includes, but is not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks, ROMs (Read-Only memories), RAMs (Random AcceSS memories), EPROMs (EraSable Programmable Read-Only memories), EEPROMs (Electrically EraSable Programmable Read-Only memories), flash memories, magnetic cards, or optical cards. That is, a storage device includes any medium that stores or transmits information in a form readable by a device (e.g., a computer, a cellular phone), and may be a read-only memory, a magnetic or optical disk, or the like.
The computer-readable storage medium provided by the embodiment of the invention can realize that a first service end receives a service calling request and generates a service calling identifier and a calling data log containing the service calling identifier; transmitting the service calling identifier to a second server according to the service calling request; the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request, so that the third server generates the call data log containing the service call identifier according to the service call request and the service call identifier; the first service end, the second service end and the third service end are connected with a data aggregation center, and the calling data logs are sent to the data aggregation center; and the data aggregation center generates a service calling link from the calling data log with the same service calling identifier according to the service calling identifier. By providing a method for monitoring the call relation and call information among a plurality of services completing a data request, a first service end generates a service call identifier and a call data log containing the service call identifier after receiving a service call request; then transmitting the service calling identifier to a second server; similarly, the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request; and after generating a call data log, each server sends the call data log to the data aggregation center, the data aggregation center generates a service call link from the call data log with the same service call identifier according to the service call identifier, so that the call relation among services can be known definitely, the services required by each service can be positioned quickly, the problems in the service call process can be counted and found through the service call link subsequently, the problems in each server are checked according to the service call link, the normal operation of each server is ensured, and the normal response of a data request is ensured.
The computer-readable storage medium provided in the embodiment of the present invention may implement the embodiment of the monitoring method for service invocation, and for specific function implementation, reference is made to the description in the embodiment of the method, which is not described herein again.
In addition, in another embodiment, the present invention further provides a server, as shown in fig. 4, the server includes a processor 403, a memory 405, an input unit 407, a display unit 409, and the like. Those skilled in the art will appreciate that the structural elements shown in fig. 4 do not constitute a limitation to all servers, and may include more or fewer components than those shown, or some of the components may be combined. The memory 405 may be used to store the computer program 401 and the functional modules, and the processor 403 executes the computer program 401 stored in the memory 405, thereby executing various functional applications of the device and data processing. The memory 405 may be an internal memory or an external memory, or include both internal and external memories. The internal memory may include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), flash memory, or random access memory. The external memory may include a hard disk, a floppy disk, a ZIP disk, a usb-disk, a magnetic tape, etc. The disclosed memory includes, but is not limited to, these types of memory. The memory 405 disclosed herein is provided by way of example only and not by way of limitation.
The input unit 407 is configured to receive signal input and user input, and the input unit 407 may include a touch panel and other input devices, where the touch panel may collect touch operations of a user on or near the touch panel (for example, operations of a user on or near the touch panel using any suitable object or accessory such as a finger, a stylus pen, etc.) and drive a corresponding connection device according to a preset program; other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., play control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like. The display unit 409 may be used to display information input by a user or information provided to a user and various menus of the computer device. The display unit 409 may take the form of a liquid crystal display, an organic light emitting diode, or the like. The processor 403 is a control center of the computer device, connects various parts of the entire computer using various interfaces and lines, and performs various functions and processes data by operating or executing software programs and/or modules stored in the memory 403 and calling data stored in the memory.
In one embodiment, the server includes one or more processors 403, and one or more memories 405, one or more computer programs 401, wherein the one or more computer programs 401 are stored in the memory 405 and configured to be executed by the one or more processors 403, and the one or more computer programs 401 are configured to perform the service call monitoring method described in the above embodiment. The one or more processors 403 shown in fig. 4 can execute and implement the functions of the service module 10 shown in fig. 3 and the first service end 101, the second service end 102 and the third service end 103 thereof, and the data aggregation center module 20.
According to the server provided by the embodiment of the invention, the first service end can receive the service calling request, and generate the service calling identifier and the calling data log containing the service calling identifier; transmitting the service calling identifier to a second server according to the service calling request; the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request, so that the third server generates the call data log containing the service call identifier according to the service call request and the service call identifier; the first service end, the second service end and the third service end are connected with a data aggregation center, and the call data logs are sent to the data aggregation center; and the data aggregation center generates a service calling link from the calling data log with the same service calling identifier according to the service calling identifier. By providing a method for monitoring the call relation and call information among a plurality of services completing a data request, a first service end generates a service call identifier and a call data log containing the service call identifier after receiving a service call request; then transmitting the service calling identifier to a second server; similarly, the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request; and after generating a call data log, each server sends the call data log to the data aggregation center, the data aggregation center generates a service call link from the call data log with the same service call identifier according to the service call identifier, so that the call relation among services can be known definitely, the services required by each service can be positioned quickly, the problems in the service call process can be counted and found through the service call link subsequently, the problems in each server are checked according to the service call link, the normal operation of each server is ensured, and the normal response of a data request is ensured.
The server provided in the embodiment of the present invention may implement the embodiment of the monitoring method for service invocation provided above, and for specific function implementation, reference is made to the description in the method embodiment, which is not described herein again.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A method for monitoring service calls, comprising:
a first service end receives a service calling request, and generates a service calling identifier and a calling data log containing the service calling identifier; transmitting the service calling identifier to a second server according to the service calling request;
the second server generates a call data log containing the service call identifier according to the service call request and the service call identifier, and transmits the service call identifier to a third server according to the service call request, so that the third server generates the call data log containing the service call identifier according to the service call request and the service call identifier;
the first service end, the second service end and the third service end are connected with a data aggregation center, and the calling data logs are sent to the data aggregation center;
the data aggregation center generates a service calling link for calling the data log with the same service calling identifier according to the service calling identifier;
for any one of the first server and the second server, if the computing capability of the server does not meet the preset requirement, sending a service call request received by the server to the next server; and if the computing capability of the server meets the preset requirement, generating a new service calling request from the server request received by the server, and directly sending the new service calling request to the next server, wherein the new service calling request is an analyzed service calling request.
2. The method of claim 1, wherein after the data aggregation center generates a service call link from the call data log having the same service call identifier according to the service call identifier, the method further comprises:
monitoring the integrity of the service invocation link;
if the integrity of the service calling link does not meet the preset condition, determining that the service calling link has interruption, acquiring an abnormal service end corresponding to the interruption, and sending alarm information to the abnormal service end.
3. The method of claim 1, wherein after the data aggregation center generates a service call link from the call data log having the same service call identifier according to the service call identifier, the method further comprises:
and counting the calling frequency of each service end in the service calling chain circuit, and configuring a preset standby service end as the service end when the calling frequency of a certain service end is greater than the preset frequency.
4. The method of claim 1, wherein the first server, the second server, and the third server are connected to a data aggregation center, and send the call data log to the data aggregation center, and the method comprises:
and the first service end, the second service end and the third service end are connected with a data aggregation center, and asynchronously send the call data log to the data aggregation center.
5. The method of claim 1, wherein the transmitting the service invocation identifier to a second server according to the service invocation request comprises:
the first server side determines a second server side according to the service calling request and generates a new service calling request;
and transmitting the new service calling request and the service calling identifier to a second server.
6. The method according to claim 1, wherein the data aggregation center generates a service call link from the call data log having the same service call identifier according to the service call identifier, and the method comprises:
the data aggregation center obtains call data logs with the same service call identifier; acquiring a time value of the call data log; and generating a service calling link from the calling data log according to the time value sequence.
7. A device for monitoring service invocation, comprising: the system comprises a service module and a data aggregation center module, wherein the service module comprises a first service end, a second service end and a third service end; wherein the content of the first and second substances,
the first server is used for receiving a service calling request and generating a service calling identifier and a calling data log containing the service calling identifier; transmitting the service calling identifier to a second server according to the service calling request;
the second server is used for generating a calling data log containing the service calling identifier according to the service calling request and the service calling identifier, and transmitting the service calling identifier to a third server according to the service calling request, so that the third server generates the calling data log containing the service calling identifier according to the service calling request and the service calling identifier;
for any one of the first server and the second server, if the computing capability of the server does not meet the preset requirement, sending a service call request received by the server to the next server; if the computing capability of the server side meets the preset requirement, generating a new service calling request from a server request received by the server side, and directly sending the new service calling request to the next server side, wherein the new service calling request is an analyzed service calling request;
a data aggregation center module: the system comprises a first server, a second server and a third server, wherein the first server, the second server and the third server are used for being connected with the first server, the second server and the third server and receiving the call data logs sent by the first server, the second server and the third server; and generating a service calling link from the calling data log with the same service calling identifier according to the service calling identifier.
8. The apparatus of claim 7, wherein the data aggregation center module further performs:
and counting the calling frequency of each service end in the service calling chain circuit, and configuring a preset standby service end as the service end when the calling frequency of a certain service end is greater than the preset frequency.
9. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method for monitoring service calls of any one of claims 1 to 6.
10. A server, comprising:
one or more processors;
a memory;
one or more computer programs, wherein the one or more computer programs are stored in the memory and configured to be executed by the one or more processors, the one or more computer programs configured to perform the service call monitoring method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811232409.0A CN109542718B (en) | 2018-10-22 | 2018-10-22 | Service call monitoring method and device, storage medium and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811232409.0A CN109542718B (en) | 2018-10-22 | 2018-10-22 | Service call monitoring method and device, storage medium and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109542718A CN109542718A (en) | 2019-03-29 |
| CN109542718B true CN109542718B (en) | 2023-02-07 |
Family
ID=65844628
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811232409.0A Active CN109542718B (en) | 2018-10-22 | 2018-10-22 | Service call monitoring method and device, storage medium and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109542718B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110445636B (en) * | 2019-07-03 | 2022-03-18 | 平安科技（深圳）有限公司 | Management platform-based micro-service early warning method and device and computer equipment |
| CN110865927B (en) * | 2019-11-20 | 2021-08-31 | 腾讯科技（深圳）有限公司 | Block chain call link abnormity detection method and device and computer equipment |
| CN112437155B (en) * | 2020-11-20 | 2024-02-20 | 北京水滴科技集团有限公司 | Service data processing method and device and server device |
| CN114697395A (en) * | 2020-12-11 | 2022-07-01 | 北京神州泰岳软件股份有限公司 | Service resource calling execution method, device, service gateway and readable storage medium |
| CN114884807A (en) * | 2022-05-20 | 2022-08-09 | 远景智能国际私人投资有限公司 | Link log generation method and device, Internet of things platform and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004287855A (en) * | 2003-03-20 | 2004-10-14 | Ricoh Co Ltd | Monitoring method, monitoring system and program |
| CN106445784A (en) * | 2016-09-27 | 2017-02-22 | 北京搜狐新动力信息技术有限公司 | Information monitoring method and information monitoring device |
| CN106790718A (en) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | Service call link analysis method and system |
| CN107483221A (en) * | 2016-06-08 | 2017-12-15 | 阿里巴巴集团控股有限公司 | A kind of across application problem investigation method, apparatus and system |
| CN107645562A (en) * | 2017-10-12 | 2018-01-30 | 广州爱九游信息技术有限公司 | Data transmission processing method, device, equipment and system |
| CN107729210A (en) * | 2017-09-29 | 2018-02-23 | 百度在线网络技术（北京）有限公司 | The abnormality diagnostic method and device of Distributed Services cluster |
| CN108038145A (en) * | 2017-11-23 | 2018-05-15 | 携程旅游网络技术（上海）有限公司 | Distributed Services tracking, system, storage medium and electronic equipment |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
| CN108512689A (en) * | 2017-12-15 | 2018-09-07 | 中国平安财产保险股份有限公司 | Micro services business monitoring method and server |
-
2018
- 2018-10-22 CN CN201811232409.0A patent/CN109542718B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004287855A (en) * | 2003-03-20 | 2004-10-14 | Ricoh Co Ltd | Monitoring method, monitoring system and program |
| CN107483221A (en) * | 2016-06-08 | 2017-12-15 | 阿里巴巴集团控股有限公司 | A kind of across application problem investigation method, apparatus and system |
| CN106445784A (en) * | 2016-09-27 | 2017-02-22 | 北京搜狐新动力信息技术有限公司 | Information monitoring method and information monitoring device |
| CN106790718A (en) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | Service call link analysis method and system |
| CN107729210A (en) * | 2017-09-29 | 2018-02-23 | 百度在线网络技术（北京）有限公司 | The abnormality diagnostic method and device of Distributed Services cluster |
| CN107645562A (en) * | 2017-10-12 | 2018-01-30 | 广州爱九游信息技术有限公司 | Data transmission processing method, device, equipment and system |
| CN108038145A (en) * | 2017-11-23 | 2018-05-15 | 携程旅游网络技术（上海）有限公司 | Distributed Services tracking, system, storage medium and electronic equipment |
| CN108512689A (en) * | 2017-12-15 | 2018-09-07 | 中国平安财产保险股份有限公司 | Micro services business monitoring method and server |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109542718A (en) | 2019-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109542718B (en) | Service call monitoring method and device, storage medium and server | |
| US10158541B2 (en) | Group server performance correction via actions to server subset | |
| CN100440157C (en) | Detecting correctable errors and logging information relating to their location in memory | |
| US8812911B2 (en) | Distributed testing of a software platform | |
| US11544137B2 (en) | Data processing platform monitoring | |
| US20210216303A1 (en) | Deployment routing of clients by analytics | |
| US10452469B2 (en) | Server performance correction using remote server actions | |
| CN108600034B (en) | Service pressure management method, device, equipment, system and storage medium | |
| US10382298B2 (en) | Automatic web page load detection | |
| EP3692443B1 (en) | Application regression detection in computing systems | |
| US20160036665A1 (en) | Data verification based upgrades in time series system | |
| US9015731B2 (en) | Event handling system and method | |
| CN114357495B (en) | Prediction machine under-chain aggregation method, device, equipment and medium based on block chain | |
| CN112527600A (en) | Monitoring log processing method, device, equipment and storage medium | |
| CN114090268B (en) | Container management method and container management system | |
| EP3832985B1 (en) | Method and apparatus for processing local hot spot, electronic device and storage medium | |
| CN112698980A (en) | Exception handling method, electronic device, and storage medium | |
| US11966323B2 (en) | Troubleshooting software services based on system calls | |
| CN113377616B (en) | Interface monitoring method, device and computer readable medium | |
| US20220214961A1 (en) | Troubleshooting software services based on system calls | |
| US11599387B2 (en) | Re-initiation of microservices utilizing context information provided via service calls | |
| US20170123818A1 (en) | Dynamic Configuration of Native Functions to Intercept | |
| US20160323397A1 (en) | Aysnchronous Custom Exit Points | |
| CN117097791A (en) | Information processing method, node, system, electronic device and storage medium | |
| CN115981936A (en) | Debugging method, internet of things equipment, debugging server and debugging system |
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 |