CN111625424A - Positioning method, device, equipment and readable storage medium - Google Patents
Positioning method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN111625424A CN111625424A CN202010469793.7A CN202010469793A CN111625424A CN 111625424 A CN111625424 A CN 111625424A CN 202010469793 A CN202010469793 A CN 202010469793A CN 111625424 A CN111625424 A CN 111625424A
- Authority
- CN
- China
- Prior art keywords
- request
- target
- route
- trend information
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000004044 response Effects 0.000 claims abstract description 78
- 230000002159 abnormal effect Effects 0.000 claims abstract description 55
- 238000012545 processing Methods 0.000 claims abstract description 32
- 238000001514 detection method Methods 0.000 claims abstract description 13
- 238000004590 computer program Methods 0.000 claims description 9
- 230000005856 abnormality Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000012216 screening Methods 0.000 description 4
- 238000004883 computer application Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
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/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Position Fixing By Use Of Radio Waves (AREA)
Abstract
The invention discloses a positioning method, a positioning device, positioning equipment and a readable storage medium, wherein the method comprises the following steps: carrying out anomaly detection on request response of the software system; after the abnormal response is detected, determining a target request to which the abnormal response belongs; acquiring request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and an application identifier for processing a target request is recorded in the request route according to a processing sequence; and determining an application path generating abnormal response by using the application identifier in the request trend information. The method can effectively position the abnormal response under the condition that the Opentracing application and the high-performance storage cluster are not needed to be deployed.
Description
Technical Field
The present invention relates to the field of computer application technologies, and in particular, to a positioning method, apparatus, device, and readable storage medium.
Background
With the continuous development of information-based systems, more and more projects adopt the development mode of micro-services. Under the micro-service mode, the modules are mutually independent, which is beneficial to more deeply and completely realizing the functions of the modules and reducing the coupling among the modules. However, since the modules often need to call each other in the micro service mode, it will bring new challenges to the problem (such as abnormal response) location between the modules, i.e. it is difficult to locate the complete source path of the request response exception, and it is difficult to find the application causing the exception.
In order to more quickly and clearly locate the problem in the complex micro-service invocation, the opentracking specification (open distributed tracking specification) has come up with the advent of various software implementations, such as Zipkin, Pinpoint, skywalk, etc., which are very necessary for large internet applications, but have drawbacks for small and medium-sized software systems: 1. an application of opentracking needs to be deployed separately, and a high-performance storage cluster is needed. This means that a very large hardware cost investment is required. 2. Code intrusiveness, any project needs to be modified to access an Opentracing monitoring system, configuration files or start scripts are modified rarely, and implementation codes of business logic are intruded mostly. This means that a large number of research and development personnel are required to perform access adaptation work during access;
in summary, how to effectively solve the problems of abnormal response positioning and the like in the software system is a technical problem that needs to be solved urgently by those skilled in the art at present.
Disclosure of Invention
The invention aims to provide a positioning method, a positioning device, positioning equipment and a readable storage medium, when an abnormal response problem occurs, an application path for processing a corresponding request is quickly determined based on request routing information, a screening range is narrowed for further finding out an application causing the abnormality, and positioning can be performed without deploying an Opentracking application and a high-performance storage cluster.
In order to solve the technical problems, the invention provides the following technical scheme:
a method of positioning, comprising:
carrying out anomaly detection on request response of the software system;
after detecting an abnormal response, determining a target request to which the abnormal response belongs;
acquiring request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and the request route records an application identifier of the processed target request according to a processing sequence;
and determining an application path generating the abnormal response by using the application identifier in the request trend information.
Preferably, the process of recording the request trend information includes:
after the target request reaches a gateway, acquiring a request ID of the target request;
creating a request route, and adding the application identifier in the request route in the process of processing the target request by each application;
and obtaining the request trend information of the target request by using the request ID and the request route.
Preferably, after obtaining the request trend information of the target request by using the request ID and the request route, the method further includes:
and recording the request trend information in a target log corresponding to the target request.
Preferably, the obtaining the request trend information of the target request by using the request ID of the target request includes:
acquiring the target log from a log system by using the request ID;
and reading the request trend information from the target log.
Preferably, after the target request arrives at the gateway, acquiring the request ID of the target request includes:
judging whether a request head of the target request comprises the request ID;
if not, taking an arrival timestamp or a newly generated UUID as the request ID, and adding the request ID into the request header;
and if so, acquiring the request ID from the request header.
Preferably, adding the application identifier in the request route includes:
and carrying out assignment processing on the request route by utilizing the application identifier.
Preferably, obtaining the request trend information of the target request by using the request ID and the request route includes:
taking the request ID as identification information of the request trend information;
and filling an application path in the request trend information by using the request route.
A positioning device, comprising:
the abnormality detection module is used for carrying out abnormality detection on the request response of the software system;
the target request determining module is used for determining a target request to which an abnormal response belongs after the abnormal response is detected;
the request trend information acquisition module is used for acquiring the request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and the request route records an application identifier of the processed target request according to a processing sequence;
and the application path acquisition module is used for determining the application path generating the abnormal response by using the application identifier in the request trend information.
A positioning apparatus, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the above positioning method when executing the computer program.
A readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned positioning method.
By applying the method provided by the embodiment of the invention, the request response of the software system is subjected to anomaly detection; after the abnormal response is detected, determining a target request to which the abnormal response belongs; acquiring request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and an application identifier for processing a target request is recorded in the request route according to a processing sequence; and determining an application path generating abnormal response by using the application identifier in the request trend information.
In the method, after an abnormal response in the software system is checked, a target request of the abnormal response is determined first. Then, request trend information of the target request is acquired based on the request ID of the target request. The request trend information comprises a request ID and a request route; the request route records the application identification of the processed target request according to the processing sequence. Thus, the application path that generated a response can be determined directly using the request-walk information. That is, it is determined which application processes in turn cause an abnormal response to occur. The screening scope is further narrowed for finding applications that respond to anomalies. That is to say, the method can effectively locate the abnormal response without deploying an opentracking application and without a high-performance storage cluster.
Accordingly, embodiments of the present invention further provide a positioning apparatus, a device and a readable storage medium corresponding to the positioning method, which have the above technical effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart illustrating an implementation of a positioning method according to an embodiment of the present invention;
fig. 2 is a flow chart of request trend information recording according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a positioning apparatus according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a positioning apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a positioning apparatus according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a flowchart illustrating a positioning method according to an embodiment of the present invention, where the method can be applied to a micro service mode software system. The method comprises the following steps:
s101, carrying out abnormity detection on the request response of the software system.
In this embodiment, the request response of the software system can be detected. Specifically, whether an abnormality occurs may be determined by determining whether the response meets an abnormal response condition. For example, whether the size of the data content of the response is larger than a preset threshold value is judged, whether the numerical value of the response exceeds a normal interval is judged, whether the response meets the user authority of the request is judged, and the like.
S102, after the abnormal response is detected, determining a target request to which the abnormal response belongs.
The target request of the abnormal response can be determined by the request information recorded in the response. For example, the target request for the exception response is determined based on the request ID in the response, or initiator + time of initiation.
The target request may be any request received in the software system. In this embodiment, neither the request content of the target request nor the initiator is limited.
S103, acquiring the request trend information of the target request by using the request ID of the target request.
The request routing information includes a request ID and a request route, and the request route records an application identifier for processing a target request according to a processing sequence.
Wherein, the request id (traceid) may be a unique identifier such as a request timestamp, UUID, etc. traceId: for uniquely identifying a complete request, i.e. a request whose traceId is exactly the same, i.e. remains the same, regardless of how many application nodes it passes.
Request trend information for the target request may be determined based on the request ID.
In particular, referring to FIG. 2, the request trend information may be recorded when the target request is processed. The specific recording process comprises the following steps:
s201, after the target request reaches the gateway, obtaining the request ID of the target request.
In order to realize abnormal response positioning, after a target request arrives at a gateway, a request ID (traceId) of the target request is obtained first, so that the target request is uniquely identified based on the request ID.
It should be noted that the gateway may or may not carry the request ID when receiving the target request itself. But for the convenience of positioning, a request ID can be added to a target request which does not carry the request ID at the gateway. That is, the request ID may be obtained in different manners depending on whether the target request carries the request ID. Namely, if the target request carries the request ID, directly acquiring the request ID from the target request; if the target request does not carry the request ID, the request ID can be generated for the target request.
Specifically, the obtaining of the request ID includes:
step one, judging whether a request head of a target request comprises a request ID;
step two, if not, taking the arrival time stamp or the newly generated UUID as a request ID, and adding the request ID into a request header of the target request;
and step three, if so, acquiring the request ID from the request head.
The UUID is a universal Unique Identifier (universal Unique Identifier).
In this embodiment, the request ID may be tagged in the request header of the target request. That is, if the request header of the target request received by the gateway has the request ID, the target request can be normally sent to the corresponding application; if the request header of the target request received by the gateway does not have the request ID, a request ID can be generated for the target request, and the target request is sent to the corresponding application after the request ID is added to the request header.
Preferably, in order to avoid occupying system resources due to recording request routing information, an abnormal response positioning mode and a normal mode can be set. That is, after the target request reaches the gateway, whether the current system is in an abnormal response positioning mode can be judged; if so, the request ID is obtained. If not, the gateway indicates that the positioning is not needed currently, the request trend information of the target request does not need to be recorded, and the gateway can directly process the target request without acquiring the request ID.
S202, creating a request route, and adding an application identifier in the request route in the process of processing a target request by each application.
After the request ID is obtained, a request route may be created, and then an application identifier of the processed target request is added to the request route.
Wherein request routing (raceroute): for marking the trend of a request. For example: and A _ B _ C _ D _ E represents that the request is initiated from the application A, passes through the application B, the application C and the application D in sequence and finally reaches the application E.
Therein, the application identity, i.e. the flag of the application, e.g. "a 01" -represents node 1 of the a application.
In practical applications, when a target request is processed by each application, the target request sequentially passes through each application, so that the task of adding an application identifier for processing the target request to a request route can be executed by each application. Specifically, the application identifier is used for assignment processing of the request route. Preferably, when the request header of the target request received by the gateway does not include the request ID, it is determined whether the current software system is in the abnormal response positioning mode by determining whether the request header includes the request ID. Specifically, if the request header has a request ID, then in the abnormal response positioning mode, a request route may be created in the request header, and then each application processing the target request adds its own application identifier to the request route.
For example, the following steps are carried out: when receiving the target request, each application first checks whether the header of the target request includes the traceId. If the value is included, the positioning configuration is opened (namely the software system is in an abnormal response positioning mode), and the positioning information is recorded, at this time, whether the value of traceRoute exists or not needs to be checked in the header of the request; if not, the application is the first node of the whole target request link, at this time, traceRoute needs to be added to the header (request header) and is assigned as the flag of the application (such as "a 01" -representing node 1 of the a application); if there is a traceRoute already in the header, it indicates that the target request has passed through at least one application node, and at this time, the value of the original traceRoute needs to be added with the flag of the current application. For example, a "B02" (second node of B application) is added after "a 01", i.e., traceRoute ═ a01_ B02, which indicates that the target request is processed by the first node of a application and the second node of B application.
S203, obtaining the request trend information of the target request by using the request ID and the request route.
After the request ID is obtained and the application identifier is added to the request route, the request ID and the request can be used to obtain the request trend information of the target request.
Specifically, each request passes through the gateway and then is processed by the application, so that the request routing information can be the sequence information of the application identifier and the application identifier in the request route, which takes the request ID as the unique identifier. That is, the request routing information of the target request is obtained by using the request ID and the request route, and includes: taking the request ID as identification information of request trend information; and filling an application path in the request trend information by using the request route. The application path filling may specifically fill the application path according to the sequence of the application identifiers in the request route.
And S104, determining an application path generating an abnormal response by using the application identifier in the request trend information.
And for the target request to which the abnormal response belongs, acquiring an application path which processes the target request by using the request trend information. Further, problems can be located based on these application identifications.
Preferably, in order to search the request trend information, the request trend information can be fused in the system log. Specifically, after the request trend information of the target request is obtained, the request trend information may also be recorded in a target log corresponding to the target request. Therefore, when the application identification is obtained by utilizing the request trend information, the target log can be obtained from the log system by utilizing the request ID; request trend information is read from the target log. That is, the request trend information is integrated with the system log information, so that any log in the system log can know which request the log belongs to and what trend information of the request belongs to. According to the request trend information, the initial position of the problem can be directly positioned.
Acquiring a request ID of a target request after the target request reaches a gateway; creating a request route, and adding an application identifier for processing a target request in the request route; obtaining request trend information of a target request by using the request ID and the request route; and if the response of the target request has a problem, acquiring the application identifier by using the request trend information.
By applying the method provided by the embodiment of the invention, the request response of the software system is subjected to anomaly detection; after the abnormal response is detected, determining a target request to which the abnormal response belongs; acquiring request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and an application identifier for processing a target request is recorded in the request route according to a processing sequence; and determining an application path generating abnormal response by using the application identifier in the request trend information.
In the method, after an abnormal response in the software system is checked, a target request of the abnormal response is determined first. Then, request trend information of the target request is acquired based on the request ID of the target request. The request trend information comprises a request ID and a request route; the request route records the application identification of the processed target request according to the processing sequence. Thus, the application path that generated a response can be determined directly using the request-walk information. That is, it is determined which application processes in turn cause an abnormal response to occur. The screening scope is further narrowed for finding applications that respond to anomalies. That is to say, the method can effectively locate the abnormal response without deploying an opentracking application and without a high-performance storage cluster.
Corresponding to the above method embodiments, the embodiments of the present invention further provide a positioning apparatus, and the positioning apparatus described below and the positioning method described above may be referred to correspondingly.
Referring to fig. 3, the apparatus includes the following modules:
an anomaly detection module 101, configured to perform anomaly detection on a request response of a software system;
the target request determining module 102 is configured to determine, after detecting the abnormal response, a target request to which the abnormal response belongs;
a request direction information obtaining module 103, configured to obtain request direction information of the target request by using a request ID of the target request; the request routing information comprises a request ID and a request route, and an application identifier for processing a target request is recorded in the request route according to a processing sequence;
the application path obtaining module 104 is configured to determine, by using the application identifier in the request trend information, an application path that generates an abnormal response.
By applying the device provided by the embodiment of the invention, the request response of the software system is subjected to abnormity detection; after the abnormal response is detected, determining a target request to which the abnormal response belongs; acquiring request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and an application identifier for processing a target request is recorded in the request route according to a processing sequence; and determining an application path generating abnormal response by using the application identifier in the request trend information.
In the device, after an abnormal response in the software system is checked, a target request of the abnormal response is determined firstly. Then, request trend information of the target request is acquired based on the request ID of the target request. The request trend information comprises a request ID and a request route; the request route records the application identification of the processed target request according to the processing sequence. Thus, the application path that generated a response can be determined directly using the request-walk information. That is, it is determined which application processes in turn cause an abnormal response to occur. The screening scope is further narrowed for finding applications that respond to anomalies. That is to say, the device can effectively locate the abnormal response without deploying an opentracking application or a high-performance storage cluster.
In a specific embodiment of the present invention, the request trend information recording module includes:
a request ID obtaining unit, configured to obtain a request ID of a target request after the target request reaches a gateway;
a request route obtaining unit, configured to create a request route, and add an application identifier to the request route in a process of processing a target request by each application;
and the request routing information determining unit is used for obtaining the request routing information of the target request by using the request ID and the request route.
In one embodiment of the present invention, the method further comprises:
and the storage unit is used for recording the request trend information in a target log corresponding to the target request after the request trend information of the target request is obtained by using the request ID and the request route.
In a specific embodiment of the present invention, the request trend information obtaining module 103 is specifically configured to obtain a target log from a log system by using a request ID; request trend information is read from the target log.
In an embodiment of the present invention, the request ID obtaining unit is specifically configured to determine whether a request header of the target request includes a request ID; if not, taking the arrival timestamp or the newly generated UUID as a request ID, and adding the request ID into a request header; if so, the request ID is obtained from the request header.
In a specific embodiment of the present invention, the request route obtaining unit is specifically configured to perform assignment processing for the request route by using the application identifier.
In a specific embodiment of the present invention, the request-oriented information determining unit is configured to use a request ID as identification information of the request-oriented information; and filling an application path in the request trend information by using the request route.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a positioning apparatus, and a positioning apparatus described below and a positioning method described above may be referred to correspondingly.
Referring to fig. 4, the positioning apparatus includes:
a memory 332 for storing a computer program;
a processor 322 for implementing the steps of the positioning method of the above-described method embodiments when executing the computer program.
Specifically, referring to fig. 5, a specific structural diagram of a positioning apparatus provided in this embodiment is shown, where the positioning apparatus may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, where the memory 332 stores one or more computer applications 342 or data 344. Memory 332 may be, among other things, transient or persistent storage. The program stored in memory 332 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the pointing device 301.
The positioning apparatus 301 may also include one or more power sources 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341.
The steps in the positioning method described above may be implemented by the structure of the positioning apparatus.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a readable storage medium, and a readable storage medium described below and a positioning method described above may be referred to in correspondence with each other.
A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the positioning method of the above-mentioned method embodiment.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. 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.
Claims (10)
1. A method of positioning, comprising:
carrying out anomaly detection on request response of the software system;
after detecting an abnormal response, determining a target request to which the abnormal response belongs;
acquiring request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and the request route records an application identifier of the processed target request according to a processing sequence;
and determining an application path generating the abnormal response by using the application identifier in the request trend information.
2. The positioning method according to claim 1, wherein the process of recording the request trend information comprises:
after the target request reaches a gateway, acquiring a request ID of the target request;
creating a request route, and adding the application identifier in the request route in the process of processing the target request by each application;
and obtaining the request trend information of the target request by using the request ID and the request route.
3. The method according to claim 2, wherein after obtaining the request routing information of the target request by using the request ID and the request route, the method further comprises:
and recording the request trend information in a target log corresponding to the target request.
4. The method according to claim 3, wherein obtaining the request trend information of the target request by using the request ID of the target request comprises:
acquiring the target log from a log system by using the request ID;
and reading the request trend information from the target log.
5. The method of claim 2, wherein obtaining the request ID of the target request after the target request arrives at the gateway comprises:
judging whether a request head of the target request comprises the request ID;
if not, taking an arrival timestamp or a newly generated UUID as the request ID, and adding the request ID into the request header;
and if so, acquiring the request ID from the request header.
6. The positioning method according to claim 2, wherein adding the application identifier to the request route comprises:
and carrying out assignment processing on the request route by utilizing the application identifier.
7. The method according to claim 2, wherein obtaining the request routing information of the target request by using the request ID and the request route comprises:
taking the request ID as identification information of the request trend information;
and filling an application path in the request trend information by using the request route.
8. A positioning device, comprising:
the abnormality detection module is used for carrying out abnormality detection on the request response of the software system;
the target request determining module is used for determining a target request to which an abnormal response belongs after the abnormal response is detected;
the request trend information acquisition module is used for acquiring the request trend information of the target request by using the request ID of the target request; the request routing information comprises a request ID and a request route, and the request route records an application identifier of the processed target request according to a processing sequence;
and the application path acquisition module is used for determining the application path generating the abnormal response by using the application identifier in the request trend information.
9. A positioning apparatus, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the positioning method according to any one of claims 1 to 7 when executing the computer program.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the positioning method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010469793.7A CN111625424A (en) | 2020-05-28 | 2020-05-28 | Positioning method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010469793.7A CN111625424A (en) | 2020-05-28 | 2020-05-28 | Positioning method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111625424A true CN111625424A (en) | 2020-09-04 |
Family
ID=72259539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010469793.7A Pending CN111625424A (en) | 2020-05-28 | 2020-05-28 | Positioning method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111625424A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2171818A1 (en) * | 1995-03-31 | 1996-10-01 | Ron Kleinman | Method and apparatus for interpreting exceptions in a distributed object system |
| CN108459939A (en) * | 2018-01-08 | 2018-08-28 | 平安科技（深圳）有限公司 | A kind of log collecting method, device, terminal device and storage medium |
| CN109600375A (en) * | 2018-12-13 | 2019-04-09 | 锐捷网络股份有限公司 | Message tracing method, device, electronic equipment and storage medium |
| CN109802854A (en) * | 2018-12-14 | 2019-05-24 | 平安普惠企业管理有限公司 | Method, apparatus, computer equipment and the storage medium of tracking network request |
| CN110069354A (en) * | 2019-04-15 | 2019-07-30 | 必成汇(成都)科技有限公司 | The full link trace method of micro services and micro services framework |
| CN110134538A (en) * | 2019-05-10 | 2019-08-16 | 重庆天蓬网络有限公司 | Method, apparatus, medium and the electronic equipment of quick positioning question log |
| CN110737592A (en) * | 2019-09-16 | 2020-01-31 | 平安科技（深圳）有限公司 | link abnormity identification method, server and computer readable storage medium |
| CN110765089A (en) * | 2019-10-25 | 2020-02-07 | 北京浪潮数据技术有限公司 | Distributed equipment and log recording method, device and storage medium thereof |
-
2020
- 2020-05-28 CN CN202010469793.7A patent/CN111625424A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2171818A1 (en) * | 1995-03-31 | 1996-10-01 | Ron Kleinman | Method and apparatus for interpreting exceptions in a distributed object system |
| CN108459939A (en) * | 2018-01-08 | 2018-08-28 | 平安科技（深圳）有限公司 | A kind of log collecting method, device, terminal device and storage medium |
| CN109600375A (en) * | 2018-12-13 | 2019-04-09 | 锐捷网络股份有限公司 | Message tracing method, device, electronic equipment and storage medium |
| CN109802854A (en) * | 2018-12-14 | 2019-05-24 | 平安普惠企业管理有限公司 | Method, apparatus, computer equipment and the storage medium of tracking network request |
| CN110069354A (en) * | 2019-04-15 | 2019-07-30 | 必成汇(成都)科技有限公司 | The full link trace method of micro services and micro services framework |
| CN110134538A (en) * | 2019-05-10 | 2019-08-16 | 重庆天蓬网络有限公司 | Method, apparatus, medium and the electronic equipment of quick positioning question log |
| CN110737592A (en) * | 2019-09-16 | 2020-01-31 | 平安科技（深圳）有限公司 | link abnormity identification method, server and computer readable storage medium |
| CN110765089A (en) * | 2019-10-25 | 2020-02-07 | 北京浪潮数据技术有限公司 | Distributed equipment and log recording method, device and storage medium thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6651183B1 (en) | Technique for referencing failure information representative of multiple related failures in a distributed computing environment | |
| US10623235B2 (en) | Correlating computing network events | |
| CN107241229B (en) | Service monitoring method and device based on interface testing tool | |
| CN112486629B (en) | Micro-service state detection method, micro-service state detection device, electronic equipment and storage medium | |
| CN110287696B (en) | Detection method, device and equipment for rebound shell process | |
| CN109491889B (en) | Method and device for automatic test in NFV | |
| CN113438292A (en) | Agent deployment method and device based on automatic operation and maintenance tool | |
| CN109522181A (en) | A kind of performance test methods of distributed memory system, device and equipment | |
| CN110134538B (en) | Method, device, medium and electronic equipment for quickly positioning problem log | |
| CN114356521A (en) | Task scheduling method and device, electronic equipment and storage medium | |
| CN114691445A (en) | Cluster fault processing method and device, electronic equipment and readable storage medium | |
| CN111625424A (en) | Positioning method, device, equipment and readable storage medium | |
| CN114500249B (en) | Root cause positioning method and device | |
| CN111200654A (en) | Client request error processing method and device | |
| CN112866979B (en) | User information association method, device, equipment and medium based on 5G service interface | |
| CN116302989A (en) | Pressure testing method and system, storage medium and computer equipment | |
| CN115987821A (en) | Gateway routing test method and device | |
| CN110825542A (en) | Method, device and system for detecting fault disk in distributed system | |
| CN114064510A (en) | Function testing method and device, electronic equipment and storage medium | |
| CN113656003A (en) | Software package management method and related equipment | |
| CN113467941A (en) | Method and device for sharing information | |
| CN113157528A (en) | Operation change monitoring method and device based on big data service cloud | |
| CN113032263A (en) | Case test processing method and device, server and readable storage medium | |
| CN110647473A (en) | Anti-interference method and device for automatic regression test, computer equipment and storage medium | |
| CN117439871B (en) | Meter reading fault positioning method and device, storage medium and electronic equipment |
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 |