CN109582655B - Method and device for positioning system log and computer readable storage medium - Google Patents
Method and device for positioning system log and computer readable storage medium Download PDFInfo
- Publication number
- CN109582655B CN109582655B CN201811326212.3A CN201811326212A CN109582655B CN 109582655 B CN109582655 B CN 109582655B CN 201811326212 A CN201811326212 A CN 201811326212A CN 109582655 B CN109582655 B CN 109582655B
- Authority
- CN
- China
- Prior art keywords
- session identifier
- request
- log
- application
- api
- 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/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Abstract
The invention is suitable for the technical field of operation and maintenance, and provides a system log positioning method and device and a computer readable storage medium, wherein the positioning method comprises the following steps: receiving a first Application Programming Interface (API) calling request from a first application, wherein the API calling request is used for triggering one-time data calling in a response process of a service request; extracting a session identifier from the first API call request, wherein the session identifier is used for uniquely identifying the service request, is generated by an initiator of the service request and is written into the first API call request by the first application; and when the log related to the data call is output, the session identifier is output together, and the session identifier is used for searching the log generated in the response process of the service request. The invention greatly shortens the time for developing, testing and positioning problems and improves the operation and maintenance efficiency of the system.
Description
Technical Field
The invention belongs to the technical field of operation and maintenance, and particularly relates to a system log positioning method and device and a computer readable storage medium.
Background
Due to the increasing traffic in the service system, a series of distributed frameworks are introduced into the service system in order to improve the system throughput. After the distributed framework is introduced, when a service request is initiated through an Application Programming Interface (API), the generated system logs can be dispersedly stored in different system sub-modules or different servers, and for each service request, the system background may call N system sub-modules or servers to perform service response correspondingly at the same time, which brings great difficulty to the positioning of the system logs and reduces the efficiency of system operation and maintenance.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for positioning a system log, and a computer-readable storage medium, so as to solve the problem that it is difficult to position the system log in a distributed framework.
A first aspect of an embodiment of the present invention provides a method for positioning a system log, including:
receiving a first Application Programming Interface (API) calling request from a first application, wherein the API calling request is used for triggering one-time data calling in a response process of a service request;
extracting a session identifier from the first API call request, wherein the session identifier is used for uniquely identifying the service request, is generated by an initiator of the service request and is written into the first API call request by the first application;
and when the log related to the data call is output, the session identifier is output together, and the session identifier is used for searching the log generated in the response process of the service request.
A second aspect of an embodiment of the present invention provides a device for locating a system log, including:
the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a first Application Programming Interface (API) calling request from a first application, and the API calling request is used for triggering one-time data calling in a response process of a service request;
an extracting unit, configured to extract a session identifier from the first API call request, where the session identifier is used to uniquely identify the service request, is generated by an initiator of the service request, and is written into the first API call request by the first application;
and the log output unit is used for outputting the session identifier when the log related to the data call is output, wherein the session identifier is used for searching the log generated in the response process of the service request.
A third aspect of the embodiments of the present invention provides a device for locating a system log, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method for locating a system log as described above when executing the computer program.
A fourth aspect of the embodiments of the present invention provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the method for locating a system log as described above.
Compared with the prior art, the embodiment of the invention has the following beneficial effects: in the embodiment of the invention, once a service request is initiated and a session identifier is generated, the session identifier is extracted by a corresponding application in each data calling process of realizing the service request, and the session identifier is output when a log related to data calling is output, which is equivalent to that all logs related to the service request carry the session identifier. Therefore, no matter how many sub-modules or servers in the distributed framework are called in the service request process, log positioning can be carried out through the session identification, the time for developing, testing and positioning problems is greatly shortened, and the operation and maintenance efficiency of the system is improved.
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 flow chart of an implementation of a positioning method for providing a system log according to an embodiment of the present invention;
FIG. 2 is a flow chart of an implementation of a positioning method for providing a system log according to another embodiment of the present invention;
FIG. 3 is a schematic diagram of an implementation of a method for locating a system log according to an embodiment of the present invention;
fig. 4 is an exemplary diagram of an implementation scenario of a method for locating a system log according to an embodiment of the present invention;
FIG. 5 is a block diagram of a location device for system logs provided by an embodiment of the present invention;
fig. 6 is a schematic diagram of a device for locating a system log according to 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.
Fig. 1 shows an implementation flow of the positioning method for providing the system log according to the embodiment of the present invention, which is detailed as follows:
s101: receiving a first Application Programming Interface (API) call request from a first application, wherein the API call request is used for triggering one data call in the response process of the service request.
When a service request is initiated in the service system, a data call is made through one or more APIs to complete a response to the service request, i.e., one or more data call procedures complete the service request procedure. Data calls are usually made between two applications in a service system, and application a triggers a data call in the process of implementing a service request by initiating an API call request to application B. Herein, the manner of the API call includes but is not limited to: HTTP call, message queue call, and Dubbo call.
S102: and extracting a session identifier from the first API call request, wherein the session identifier is used for uniquely identifying the service request, is generated by an initiator of the service request and is written into the first API call request by the first application.
Each time a service request is initiated, an initial initiator of the service request generates a session identifier, the session identifier is used for uniquely identifying the service request, and the session identifier appears in the whole process of the service request and is written into the API call request initiated by the data caller corresponding to each data call process. In the embodiment of the invention, the application extracts the session identifier from the API call request after receiving the API call request.
Further, the session identifier is written into header information of the API call request by the data caller before the API call request is initiated, and the application receiving the API call request can obtain the session identifier from the header information of the API call request.
S103: and when the log related to the data call is output, the session identifier is output together, and the session identifier is used for searching the log generated in the response process of the service request.
After receiving the API call request, the application, on one hand, performs data call based on the API call request and returns corresponding data to the data caller, and on the other hand, during the whole data call process, the application performs log output, and during the log output, the application outputs the session identifier together.
As an embodiment of the present invention, a configuration file of a log component (e.g., an open source log component logback) may be modified, and preset logic is added to the configuration file of the log component, for example, an expression "% X { session identifier }", where the session identifier is used as a variable value, so that the session identifier may be output while each line of the log is output.
In this way, in fact, once a service request is initiated and a session identifier is generated, the session identifier is extracted by the corresponding application in each data call process for implementing the service request, and the session identifier is output together when a log related to the data call is output, which is equivalent to that all logs related to the service request carry the session identifier. Therefore, no matter how many sub-modules or servers in the distributed framework are called in the service request process, log positioning can be carried out through the session identification, the time for developing, testing and positioning problems is greatly shortened, and the operation and maintenance efficiency of the system is improved. Generally, tests show that, for 2 applications deployed on 2 servers respectively, and the concurrency is over 1000, according to the conventional technology, all logs corresponding to one service request are searched, which takes at least 20 minutes on average and is easy to find errors, and by the scheme provided by the embodiment of the present invention, the whole log locating process can be shortened to 1 to 2 minutes.
Further, as an embodiment of the present invention, as shown in fig. 2, on the basis of the embodiment of the present invention corresponding to fig. 1, the method further includes:
s104: and if a second API call request needs to be initiated to a second application in the data call process, writing the session identifier into the second API call request.
In the process of responding to the first application, if another data calling process is nested and a second API calling request needs to be initiated to the second application through the second API, then the session identifier is written into the second API calling request, so that the second application can repeat the same processing process as S101 to S103 after receiving the second API calling request, and finally output the related logs carrying the same session identifier, that is, the purpose that all logs related to the service request process carry the same session identifier is achieved.
For convenience of understanding, the following further describes the embodiments of the present invention through practical application scenarios:
for a service request initiated in a service system, in order to complete a response to the service request, an application a needs to call an application B, the application B calls an application C, … …, in the whole calling process, the application a transmits a session identifier to the application B, and the application B outputs the session identifier to a log at the same time when outputting the log. Similarly, when the application B calls the application C, the application B transmits the session identifier to the application C, when the application C outputs the log, the session identifier is output to the log together, and so on, and the session identifier can run through the life cycle of the whole service request no matter how many applications need to be called in the response process of the service request. When a problem occurs in the response of a service request, all relevant log information is required to be queried to locate which code block the problem occurs in. When a plurality of users use the service system in the same time period, each user behavior outputs log information, and it is difficult to distinguish which logs are generated by which service requests (because there is only one log file in the service system in the same time period, the log file may contain log information corresponding to different service requests). If the technical scheme provided by the embodiment of the invention is adopted, the corresponding session identification is output together when each row of logs are output, and each row of logs can see which service request is generated correspondingly.
Fig. 3 shows an implementation schematic diagram of the embodiment of the present invention, and as can be seen from fig. 3, when data is called between applications, a caller application writes a session identifier into header information and transmits the session identifier to a callee application, and the callee acquires the session identifier from the header information. And the logback is used as a log component adopted by the service system, and each application can output the corresponding session identifier together when generating the system log by modifying the configuration file.
Next, based on the above-described embodiments, how to perform the transmission of the session identifier and the output of the log are respectively described for different API call modes:
HTTP calling mode
The HTTP interface is called:
firstly, adding a filter in WEB application, acquiring a session identifier in HTTP request header information in the filter, putting the session identifier into a logback current thread context through MDC.put (), then modifying a logback configuration file, adding an expression, and outputting a session identifier variable value, such as: % X { session identification }, so that the session identification is output at each row of log output.
The HTTP interface caller:
get () to get the conversation label in the logback context, when sending HTTP request, put the conversation label into the request header information and transmit to the next HTTP interface called party.
Message Queue (MQ) calling mode
And (4) MQ receiver:
firstly, acquiring MessageProperties from a Message received by an MQ queue Message, then acquiring header information from the MessageProperties to acquire a session identifier, similarly putting the session identifier into a current thread context of a logback through MDC.put (), then modifying a configuration file of the logback, adding an expression, and outputting a variable value of the session identifier.
And (3) MQ sender:
get () to get the session ID in the logback context, when sending the Message, put the session ID into the Message header information and transmit to the next receiver.
Dubbo calling mode
Dubbo interface provider:
the session identifier in the request context is obtained through an Rpcontext.getContext (). getAttachments (). get ("session identifier") method, then the session identifier is put into the logback current thread context through MDC.put (), then the logback configuration file is modified, the expression is added, and the value of the session identifier variable is output.
Dubbo interface consumer:
get the session id in the logback through mdc.get (), then put the session id into the implicit parameter set through rpccontext.getcontext ().setattachment ("session id", "value"), and transmit to the next receiver.
Fig. 4 shows a specific application scenario, in which, for the same service request, the a application calls the B application by means of HTTP call, the B application calls the C application by means of Dubbo call, and the C application calls the D application by means of MQ call, and during the above-mentioned whole response process to the service request, the generated system logs are all marked with the same session identifier to indicate the system logs generated during the response process to the service request, so as to facilitate log locating during the operation and maintenance process.
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.
Corresponding to the above-described embodiments of the method for locating a system log, fig. 5 shows a block diagram of modules of a locating device for a system log provided by an embodiment of the present invention, where the device may be a software module of a single application running in a business system. For convenience of explanation, only portions related to the embodiments of the present invention are shown.
Referring to fig. 5, the apparatus includes:
a receiving unit 51, configured to receive a first application programming interface API call request from a first application, where the API call request is used to trigger a data call in a response process of a service request;
an extracting unit 52, configured to extract a session identifier from the first API call request, where the session identifier is used to uniquely identify the service request, and is generated by an initiator of the service request and written into the first API call request by the first application;
and a log output unit 53, configured to output the session identifier when outputting the log related to the data call, where the session identifier is used to search the log generated in the response process of the service request.
Optionally, the device for locating the system log further includes:
and the writing unit is used for writing the session identifier into the second API call request if the second API call request needs to be initiated to the second application in the data call process.
Optionally, the log output unit 53 is specifically configured to:
and adding preset logic in a configuration file of the log component, wherein the preset logic is used for outputting the session identifier while outputting each row of logs.
Optionally, the extracting unit 52 is specifically configured to:
and acquiring the session identifier from the header information of the first API call request, wherein the session identifier is written into the header information of the first API call request by the first application before the first API call request is initiated.
Optionally, the API call mode includes any one of:
HTTP call, message queue call, and Dubbo call.
Fig. 6 is a schematic diagram of a system log locating device provided in an embodiment of the present invention, which may be disposed in a server of a service system. As shown in fig. 6, the location device 6 of the system log of this embodiment includes: a processor 60, a memory 61 and a computer program 62, such as a location program for a system log, stored in said memory 61 and executable on said processor 60. The processor 60, when executing the computer program 62, implements the steps in the above-described embodiments of the method for locating a system log, such as the steps 101 to 103 shown in fig. 1. Alternatively, the processor 60, when executing the computer program 62, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the modules 51 to 53 shown in fig. 5.
Illustratively, the computer program 62 may be partitioned into one or more modules/units that are stored in the memory 61 and executed by the processor 60 to implement the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 62 in the location means 6 of the system log. For example, the computer program 62 may be divided into a receiving unit, an extracting unit and a log outputting unit, and the specific functions of the respective modules are as follows:
the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a first Application Programming Interface (API) calling request from a first application, and the API calling request is used for triggering one-time data calling in a response process of a service request;
an extracting unit, configured to extract a session identifier from the first API call request, where the session identifier is used to uniquely identify the service request, is generated by an initiator of the service request, and is written into the first API call request by the first application;
and the log output unit is used for outputting the session identifier when the log related to the data call is output, wherein the session identifier is used for searching the log generated in the response process of the service request.
Optionally, the method further comprises:
and the writing unit is used for writing the session identifier into the second API call request if the second API call request needs to be initiated to the second application in the data call process.
Optionally, the log output unit is specifically configured to:
and adding preset logic in a configuration file of the log component, wherein the preset logic is used for outputting the session identifier while outputting each row of logs.
Optionally, the extracting unit is specifically configured to:
and acquiring the session identifier from the header information of the first API call request, wherein the session identifier is written into the header information of the first API call request by the first application before the first API call request is initiated.
Optionally, the API call mode includes any one of:
HTTP call, message queue call, and Dubbo call.
It will be understood by those skilled in the art that fig. 6 is only an example of the location means 6 of the system log, and does not constitute a limitation to the location means 6 of the system log, and may comprise more or less components than those shown, or some components in combination, or different components, for example, the location means 6 of the system log may further comprise an input-output device, a network access device, a bus, etc.
The Processor 60 may be a Central Processing Unit (CPU), or may be other general purpose Processor, a Digital Signal Processor (DSP), a microprocessor, or any conventional Processor.
The memory 61 may be an internal storage unit of the location means 6 of the system log, such as a hard disk or a memory of the location means 6 of the system log. The memory 61 may also be an external storage device of the positioning apparatus 6 of the system log, 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 equipped on the positioning apparatus 6 of the system log. Further, the memory 61 may also comprise both an internal storage unit of the positioning means 6 of the system log and an external storage device. The memory 61 is used for storing the computer programs and other programs and data required by the positioning means 6 of the system log. The memory 61 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
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 (8)
1. A method for locating a system log, comprising:
receiving a first Application Programming Interface (API) calling request from a first application, wherein the API calling request is used for triggering one-time data calling in a response process of a service request; the data call is made between two applications in a business system;
extracting a session identifier from the first API call request, wherein the session identifier is used for uniquely identifying the service request, is generated by an initiator of the service request and is written into the first API call request by the first application;
outputting the session identifier together with the log associated with the data call when outputting the log, including: and adding preset logic in a configuration file of the log component, wherein the preset logic is used for outputting the session identifier while outputting each row of logs, and the session identifier is used for searching logs generated in the response process of the service request.
2. The method for locating a system log of claim 1, further comprising:
and if a second API call request needs to be initiated to a second application in the data call process, writing the session identifier into the second API call request.
3. The method for locating a system log according to claim 1, wherein the extracting a session identifier from the first API call request comprises:
and acquiring the session identifier from the header information of the first API call request, wherein the session identifier is written into the header information of the first API call request by the first application before the first API call request is initiated.
4. The method for locating the system log according to claim 1, wherein the mode of the API call comprises any one of the following:
HTTP call, message queue call, and Dubbo call.
5. An apparatus for locating a system log, comprising:
the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a first Application Programming Interface (API) calling request from a first application, and the API calling request is used for triggering one-time data calling in a response process of a service request; the data call is made between two applications in a business system;
an extracting unit, configured to extract a session identifier from the first API call request, where the session identifier is used to uniquely identify the service request, is generated by an initiator of the service request, and is written into the first API call request by the first application;
a log output unit, configured to output the session identifier when outputting a log related to the data call, where the session identifier is used to search a log generated in a response process of the service request; the log output unit is specifically configured to: and adding preset logic in a configuration file of the log component, wherein the preset logic is used for outputting the session identifier while outputting each row of logs.
6. The system log locating apparatus of claim 5, further comprising:
and the writing unit is used for writing the session identifier into the second API call request if the second API call request needs to be initiated to the second application in the data call process.
7. An apparatus for locating a system log, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to any one of claims 1 to 4 when executing the computer program.
8. 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 |
|---|---|---|---|
| CN201811326212.3A CN109582655B (en) | 2018-11-08 | 2018-11-08 | Method and device for positioning system log and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811326212.3A CN109582655B (en) | 2018-11-08 | 2018-11-08 | Method and device for positioning system log and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109582655A CN109582655A (en) | 2019-04-05 |
| CN109582655B true CN109582655B (en) | 2021-01-08 |
Family
ID=65921919
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811326212.3A Active CN109582655B (en) | 2018-11-08 | 2018-11-08 | Method and device for positioning system log and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109582655B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112579552A (en) * | 2019-09-30 | 2021-03-30 | 杭州海康威视数字技术股份有限公司 | Log storage and calling method, device and system |
| CN111143311B (en) * | 2019-12-13 | 2023-10-13 | 东软集团股份有限公司 | Inter-application association determination and log association search methods, devices, media and equipment |
| CN112118286B (en) * | 2020-08-04 | 2021-08-17 | 紫光云(南京)数字技术有限公司 | Multi-thread link tracking method and device based on MDC and computer readable storage medium |
| CN112882919A (en) * | 2021-03-29 | 2021-06-01 | 浪潮云信息技术股份公司 | Log link tracking method and system of micro-service architecture based on log4j |
| CN114090112B (en) * | 2021-10-27 | 2023-06-16 | 青岛海尔科技有限公司 | Method and device for loading configuration file, storage medium and electronic device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103731427B (en) * | 2013-12-31 | 2017-04-12 | 华为技术有限公司 | Conversation processing method, device and system |
| CN104077179B (en) * | 2014-06-16 | 2017-06-06 | 武汉理工大学 | A kind of local API Calls method of web oriented browser |
| CN104317626B (en) * | 2014-11-13 | 2017-08-11 | 北京奇虎科技有限公司 | The methods, devices and systems of application software control of authority in terminal device |
| CN107707368A (en) * | 2017-09-12 | 2018-02-16 | 厦门集微科技有限公司 | The fee deduction treatment method and server of a kind of API service |
-
2018
- 2018-11-08 CN CN201811326212.3A patent/CN109582655B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109582655A (en) | 2019-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109582655B (en) | Method and device for positioning system log and computer readable storage medium | |
| CN109558748B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN107436844B (en) | Method and device for generating interface use case aggregate | |
| CN110445860B (en) | Message sending method, device, terminal equipment and storage medium | |
| CN110048879B (en) | Microservice registration method, microservice registration device, electronic equipment and computer-readable storage medium | |
| US10021634B2 (en) | Method and device for switching SIM cards of communication terminal and computer storage medium | |
| CN108664521B (en) | Method and device for providing serial number, electronic equipment and readable storage medium | |
| CN110602056A (en) | Service parameter transmission method and device | |
| CN105515887A (en) | Application test method, server and system | |
| CN109587351B (en) | Call testing method, device, equipment and storage medium | |
| CN113852639B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN108833500B (en) | Service calling method, service providing method, data transmission method and server | |
| CN111008130B (en) | Intelligent question-answering system testing method and device | |
| CN117194245A (en) | Automatic test method, device, equipment and storage medium | |
| CN104320766A (en) | Spam short message identification method, device and equipment | |
| CN110852744A (en) | Method, device, terminal equipment and medium for switching transaction channels | |
| CN109299948A (en) | A kind of red packet sending method, device, wearable device and storage medium | |
| CN109348053B (en) | Telephone number mark processing method, server, terminal device and computer readable storage medium | |
| CN112788078B (en) | Data transmission method, receiving device, sending device and computer equipment | |
| US9374474B1 (en) | System, method, and computer program for detecting duplicated telecommunications events in a consumer telecommunications network | |
| CN111988473B (en) | Voice communication call control method and device based on intelligent contract | |
| CN115913912A (en) | Message interception and service link diagram generation method and device | |
| CN112818336A (en) | Data access method, data access device and computer readable storage medium | |
| CN116455917B (en) | Data synchronization method and device, electronic equipment and computer readable storage medium | |
| CN110708208B (en) | Monitoring data acquisition method and device, storage medium and terminal |
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 |