CN112433991A - Problem positioning method and device - Google Patents
Problem positioning method and device Download PDFInfo
- Publication number
- CN112433991A CN112433991A CN202011310644.2A CN202011310644A CN112433991A CN 112433991 A CN112433991 A CN 112433991A CN 202011310644 A CN202011310644 A CN 202011310644A CN 112433991 A CN112433991 A CN 112433991A
- Authority
- CN
- China
- Prior art keywords
- log
- information
- target
- log information
- call chain
- 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 37
- 238000012216 screening Methods 0.000 claims description 14
- 238000012163 sequencing technique Methods 0.000 claims description 3
- 238000001914 filtration Methods 0.000 claims description 2
- 230000004807 localization Effects 0.000 claims 4
- 238000005516 engineering process Methods 0.000 abstract description 4
- 238000012544 monitoring process Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 210000002303 tibia Anatomy 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0281—Customer communication at a business location, e.g. providing product or service information, consulting
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Entrepreneurship & Innovation (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Game Theory and Decision Science (AREA)
- Library & Information Science (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a problem positioning method and a device, wherein the method comprises the following steps: acquiring system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises a service identifier and call detail information; associating system log information and call chain log information of each service based on the service identifier; receiving a query request of a user, wherein the query request at least comprises a target service identifier; target system log information and target call chain log information are obtained through inquiry based on the target service identification so as to obtain target log detail information and target call detail information; generating problem detail information based on the target log detail information and the target calling detail information; the logs of all the systems are connected in series by using a call chain technology, manual guessing is not needed to judge which systems the inquired service belongs to and then check the inquired service one by one, the error details of all the related systems can be quickly found, and the inquired problem can be quickly and accurately positioned.
Description
Technical Field
The invention relates to the technical field of computer information processing, in particular to a problem positioning method and device.
Background
In the e-commerce industry, when a customer service meets a feedback problem, the problem reason can be firstly inquired through some internal systems, when the problem reason cannot be inquired by the internal systems, the problem reason can be fed back to a service or a development co-worker, the service or the development co-worker generally locates the problem by checking a log after receiving the customer service feedback, and then the located problem details are fed back to the customer service.
When a service or development is carried out and logs are checked simultaneously, it is necessary to manually judge which systems the problem service relates to, and then inquire the log positioning problem of the related system to obtain the problem reason, but one service link may span multiple systems, so that the problem positioning becomes very difficult, the system log information of the multiple systems is inquired one by one, the positioning difficulty is high, the positioning time is long, the labor cost is high, and great challenges are provided for the recovery of the clock level, the service continuity and the user experience.
Therefore, a fast and accurate problem positioning method is very important.
Disclosure of Invention
The invention aims to: a problem location method and apparatus are provided.
The technical scheme of the invention is as follows: in a first aspect, a problem location method is provided, the method comprising:
acquiring system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises a service identifier and call detail information;
associating system log information and call chain log information of each service based on the service identifier;
receiving a query request of a user, wherein the query request at least comprises a target service identifier;
target system log information and target calling chain log information are obtained through inquiry based on the target service identification so as to obtain target log detail information and target calling detail information;
and generating question detail information based on the target log detail information and the target calling detail information.
In some preferred embodiments, after the obtaining the system log information and the call chain log information, the method further includes:
screening the system log information and the call chain log information to obtain error log information;
the querying and acquiring target system log information and target call chain log information based on the target service identifier specifically includes:
and searching the error log information based on the target service identifier to obtain target system log information and target call chain log information.
In some preferred embodiments, after the filtering the system log information and the call chain log information to obtain the error log information, the method further comprises:
storing the error log information.
In some preferred embodiments, the obtaining the system log information and the call chain log information specifically includes:
receiving a system log and a buried point log generated when a buried point which is configured in a service system in advance runs in the service system;
generating the call chain log based on the buried point log;
and analyzing the system log and the call chain log to obtain the system log information and the call chain log information.
In some preferred embodiments, the buried point log comprises at least: TraceId, error code and call detail information;
the generating the call chain log based on the buried point log specifically includes:
screening out the buried point logs with the same TraceId;
and summarizing the buried point logs with the same traceId to generate the call chain log.
In some preferred embodiments, at least the traceId, SpanId and parentsspanid fields are included in the buried point log to record link and node information.
In some preferred embodiments, the target log detail information includes at least error code, elapsed time and traffic field information;
the generating of the question detail information based on the target log detail information and the target invocation detail information specifically includes:
sequencing all errors in the target log detail information according to a preset rule;
generating problem detail information based on the target calling detail information and the sequenced target log detail information; the problem detail information comprises wrong service field information and related calling information of a preset serial number in the target log detail.
In some preferred embodiments, the receiving the system log and receiving the embedded point log generated by the embedded point configured in the business system in advance when the business system runs specifically include:
receiving a system log and a buried point log which is generated when a buried point which is configured in a business system in advance is operated in the business system based on a flash component;
and analyzing the system log and the call chain log based on the flash component to obtain the system log information and the call chain log information.
In a second aspect, there is provided an issue locating apparatus, the apparatus comprising:
the acquisition module is used for acquiring system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises a service identifier and call detail information;
the correlation module is used for correlating the system log information and the call chain log information of each service based on the service identification;
a receiving module, configured to receive a query request of a user, where the query request at least includes a target service identifier;
the query module is used for querying and acquiring target system log information and target call chain log information based on the target service identifier so as to acquire target log detail information and target call detail information;
and the generating module is used for generating the problem detail information based on the target log detail information and the target calling detail information.
In some preferred embodiments, the obtaining module includes:
the receiving unit is used for receiving the system log and receiving a buried point log generated by buried points which are configured in the service system in advance when the service system runs; the buried point log at least comprises: TraceId, error code and call detail information;
the screening unit is used for screening the embedded point logs with the same traceId;
the summarizing unit is used for summarizing the buried point logs with the same traceId to generate the call chain log information;
and the analysis unit is used for analyzing the system log and the call chain log to obtain the system log information and the call chain log information.
Compared with the prior art, the invention has the advantages that: a problem location method is provided, comprising: acquiring system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises a service identifier and call detail information; associating system log information and call chain log information of each service based on the service identifier; receiving a query request of a user, wherein the query request at least comprises a target service identifier; target system log information and target call chain log information are obtained through inquiry based on the target service identification so as to obtain target log detail information and target call detail information; generating problem detail information based on the target log detail information and the target calling detail information;
the logs of all the systems are connected in series by using a call chain technology, so that when problem location is carried out, system log information of error service can be accurately found to check error details, the call relation of the error service on all the systems on the same link can be displayed, the system which the queried service belongs to does not need to be guessed and judged manually and then checked one by one, the error details of all the related systems can be quickly found, and the queried problem can be quickly and accurately located.
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 description of the embodiments will be briefly introduced 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 creative efforts.
Fig. 1 is a flowchart of a problem locating method provided in embodiment 1;
FIG. 2 is a flowchart of an issue locating apparatus provided in embodiment 2;
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. 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.
In order to solve the problem situation that when a problem is fed back currently, the system log information of a plurality of systems on a service link needs to be checked one by one to locate the problem and obtain the problem details, the problem locating method provided by the embodiment provides a problem locating method, and a call chain technology is adopted to quickly and accurately locate the system related to the problem and obtain the problem detail information.
The method and apparatus for analyzing and processing the cost will be further described with reference to the following embodiments.
Example 1: the present embodiment provides a problem location method, as shown in fig. 1, the method includes:
and S1, acquiring system log information and call chain log information. The system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises service identification and call detail information.
In the distributed service architecture, a service request is processed by different service nodes, a result is returned to a user after the processing is finished, and a byte code is inserted into a buried point of each service node to record each node of each request tibia, so that a complete call chain is formed. More specifically, the nodes involved in the service are predetermined according to the existing service types, so that a predetermined buried point configuration is carried out and stored in a configuration database. The buried point configuration includes at least a buried point that tracks specified fields of a specified class.
Preferably, a muga call chain is adopted for distributed tracking based on byte codes and logs, a customized Agent is run at a server, a globally unique traceId is generated for each request, logs collected by different applications can be strung together to form a call chain through the traceId, and finally a call track of the service is drawn.
Specifically, the step includes the following substeps:
s11, receiving system logs and receiving embedded point logs generated when embedded points configured in the business system in advance run.
Preferably, the system log is received based on the flash component, and the embedded point log generated when the embedded point configured in the business system in advance is operated in the business system is received.
The buried point log at least comprises: traceId, error code and call detail information. Each error corresponds to an error code, so that the errors can be identified conveniently. In addition, at least the traceId, SpanId and parentsspanid fields are included in the buried point log to record link and node information.
The receiving sequence of the system log information and the buried point log is not limited in this embodiment.
The specific acquisition means for the buried point log may be any implemented Trace tool set, such as a Trace annotation, a Trace API, and the like, which is not limited in this embodiment.
And S12, generating a call chain log based on the buried point log. Specifically, the method comprises the following steps:
and S121, screening the embedded point logs with the same traceId.
And S122, summarizing the buried point logs with the same traceId to generate a call chain log.
And generating a globally unique traceId in each request, and stringing logs collected by different applications together to form a call chain through the traceId so as to draw a call track of the service finally.
Preferably, the generated call chain log may be summarized according to a preset dimension of an association identifier associated with the service log, for example, if the call chain log is associated with the service log through the service identifier, the call chain log is summarized according to the dimension of the service identifier, which is convenient for searching and positioning the call chain log according to the service identifier subsequently.
And S13, analyzing the system log and the call chain log to obtain system log information and call chain log information.
Specifically, the system log includes a traffic log and a monitoring log for each system on the traffic link.
In this embodiment, the analysis modes of the service log, the monitoring log and the call chain log of the system in the method are not specifically limited, such as json, regular expression, array subscript, and the like, and the specified prefix of the specified file may also be configured. After configuration is completed, the configuration data is cached in Redis and is periodically acquired by the streaming message processing component.
The system log information at least comprises service identification and log detail information, and the call chain log information at least comprises the service identification and the call detail information.
Preferably, the system log and the call chain log are analyzed based on a flash component to obtain the system log information and the call chain log information, the received logs are analyzed, and the analyzed service fields and the log original text are stored in an ElasticSearch and used for inquiring a system to perform problem positioning and log display.
As a preference, the method further comprises the following steps:
s14, screening the system log information and calling the chain log information to obtain error log information.
Specifically, each problem service in the monitoring log of the system contains an error code, and a normal service has no error code, and error-containing monitoring log information in monitoring log information is screened out according to error code verification. And extracting traceId from the error-containing monitoring log information, throwing the traceId to the service log information and calling chain log information to carry out traceId verification, thereby screening error-containing service log information containing the traceId in the service log information of the system and error-containing calling chain log containing the traceId in the calling chain log information. The error log information comprises error-containing monitoring log information, error-containing service log information and error-containing call chain log information.
And S15, storing the error log information. When the error log needs to be inquired subsequently, the stored error log information is searched, and the searching efficiency is improved.
And S2, associating the system log information and the call chain log information of each service based on the service identification.
Each service executed in the system has a unique service identifier, and the service identifier can be an order number or a special field such as a subscriber number which can distinguish each service from other services.
And associating the system log information of each service with the call chain log information based on the service identifier, so that the call chain log information can be conveniently positioned from the system log information.
S3, receiving a query request of a user, wherein the query request at least comprises a target service identification.
The system log information and the call chain log information both have service identification, and the system log information and the call chain log information related to the service can be positioned according to the service identification.
S4, obtaining target system log information and target call chain log information based on the target service identification inquiry so as to obtain target log detail information and target call detail information.
The target log detail information at least comprises error codes, consumed duration and service field information, so that after the target log detail information of the service is inquired according to the service identification, the error details of the problem can be acquired in detail and accurately, and developers can conveniently and directly locate the failure reason.
And S5, generating question detail information based on the target log detail information and the target call detail information.
The method specifically comprises the following substeps:
and S51, sorting all errors in the target log detail information according to a preset rule.
The reason for the failure of one service may be one, and it is also possible that two or more than two reasons are used, and therefore, the error included in the target log detail information corresponding to the service may be one, or may be two or more than two reasons. And sequencing all errors in the target log detail information according to a preset rule is favorable for solving major errors when two or more errors exist in the target log detail information corresponding to the target service. Illustratively, the consumed duration can reflect the difficulty of errors to a certain extent, and the sequence of the consumed duration from long to short is selected as a preset rule, and the errors are sequenced according to the length of the consumed duration.
And S52, generating question detail information based on the target calling detail information and the sorted target log detail information.
The problem detail information comprises wrong service field information and related calling information of a preset serial number in the target log detail.
Illustratively, the preset rule is to sort according to the elapsed time length, the preset sequence numbers include 1, 2, 3, 4 and 5, and the problem detail information includes the sequence numbers of 1, 2, 3, 4 and 5 in the sorted target log details, and the target invocation information corresponding to the sequence numbers of 1, 2, 3, 4 and 5 in the target log detail information.
As a more preferable implementation, after the problem detail information is obtained, the root cause log identification of the service system is combined, the reason that the order failed is finally output, and simultaneously, the logs of all systems through which the order passes are output, and the logs are displayed according to the sequence of the call chain, and the logs containing the error information are displayed in a bold manner.
The problem positioning method provided by the embodiment comprises the following steps: acquiring system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises a service identifier and call detail information; associating system log information and call chain log information of each service based on the service identifier; receiving a query request of a user, wherein the query request at least comprises a target service identifier; target system log information and target call chain log information are obtained through inquiry based on the target service identification so as to obtain target log detail information and target call detail information; generating problem detail information based on the target log detail information and the target calling detail information; the logs of all the systems are connected in series by using a call chain technology, so that when problem location is carried out, system log information of error service can be accurately found to check error details, the call relation of the error service on all the systems on the same link can be displayed, the system which the queried service belongs to does not need to be guessed and judged manually and then checked one by one, the error details of all the related systems can be quickly found, and the queried problem can be quickly and accurately located.
Furthermore, 3 fields (traceId/spanId/parentsspanid) of the call chain can be configured to output corresponding call chain information, and the call chain information is non-invasive to the service code of the system.
Example 2: this embodiment provides a problem locating device, the device includes:
an obtaining module 21, configured to obtain system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises service identification and call detail information.
And the associating module 22 is configured to associate the system log information and the call chain log information of each service based on the service identifier.
The receiving module 23 is configured to receive an inquiry request of a user, where the inquiry request at least includes a target service identifier.
And the query module 24 is configured to query and acquire target system log information and target call chain log information based on the target service identifier to acquire target log detail information and target call detail information.
And a generating module 25, configured to generate the problem detail information based on the target log detail information and the target invocation detail information.
Specifically, the obtaining module includes:
a receiving unit 211, configured to receive a system log and a buried point log generated when a buried point configured in a service system in advance runs in the service system; the buried point log at least comprises: TraceId, error code and call detail information.
And a screening unit 212 for screening the embedded point logs with the same TraceId.
And a summarizing unit 213, configured to summarize the traceId-identical buried point logs to generate the call chain log information.
An analyzing unit 214, configured to analyze the system log and the call chain log to obtain the system log information and the call chain log information.
Preferably, the screening module 26 is configured to screen the system log information and the call chain log information to obtain the error log information. The generating module 25 is further configured to search the error log information based on the target service identifier to obtain target system log information and target call chain log information.
And a storage module 27 for storing the error log information.
As a preference, the generating module 25 includes:
the sorting unit 251 is used for sorting all errors in the target log detail information according to a preset rule;
a generating unit 252, configured to generate question detail information based on the target invocation detail information and the sorted target log detail information; the problem detail information comprises wrong service field information and related calling information of a preset serial number in the target log detail.
It should be noted that: in the problem location device provided in the foregoing embodiment, when a problem location processing service is performed, only the division of the functional modules is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, a problem location device provided in this embodiment and an embodiment of a problem location method provided in embodiment 1 belong to the same concept, that is, the device is based on this method, and the specific implementation process thereof is described in detail in the method embodiment and is not described herein again.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
It should be understood that the above-mentioned embodiments are only illustrative of the technical concepts and features of the present invention, and are intended to enable those skilled in the art to understand the contents of the present invention and implement the present invention, and not to limit the scope of the present invention. All modifications made according to the spirit of the main technical scheme of the invention are covered in the protection scope of the invention.
Claims (10)
1. A problem location method, comprising:
acquiring system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises a service identifier and call detail information;
associating system log information and call chain log information of each service based on the service identifier;
receiving a query request of a user, wherein the query request at least comprises a target service identifier;
target system log information and target calling chain log information are obtained through inquiry based on the target service identification so as to obtain target log detail information and target calling detail information;
and generating question detail information based on the target log detail information and the target calling detail information.
2. The problem location method according to claim 1, wherein after said obtaining system log information and call chain log information, said method further comprises:
screening the system log information and the call chain log information to obtain error log information;
the querying and acquiring target system log information and target call chain log information based on the target service identifier specifically includes:
and searching the error log information based on the target service identifier to obtain target system log information and target call chain log information.
3. A problem localization method according to claim 2,
after the filtering the system log information and the call chain log information to obtain error log information, the method further includes:
storing the error log information.
4. The problem location method according to claim 1, wherein the obtaining of the system log information and the call chain log information specifically includes:
receiving a system log and a buried point log generated when a buried point which is configured in a service system in advance runs in the service system;
generating the call chain log based on the buried point log;
and analyzing the system log and the call chain log to obtain the system log information and the call chain log information.
5. The problem location method of claim 4, wherein the buried point log comprises at least: TraceId, error code and call detail information;
the generating the call chain log based on the buried point log specifically includes:
screening out the buried point logs with the same TraceId;
and summarizing the buried point logs with the same traceId to generate the call chain log.
6. A problem localization method according to claim 5,
at least the traceId, SpanId and parentsspanid fields are included in the buried point log to record link and node information.
7. A problem localization method according to claim 6,
the target log detail information at least comprises error codes, consumed duration and service field information;
the generating of the question detail information based on the target log detail information and the target invocation detail information specifically includes:
sequencing all errors in the target log detail information according to a preset rule;
generating problem detail information based on the target calling detail information and the sequenced target log detail information; the problem detail information comprises wrong service field information and related calling information of a preset serial number in the target log detail.
8. The problem location method according to claim 4, wherein the receiving the system log and the receiving the embedded point log generated by embedded points pre-configured in the business system when the business system runs specifically include:
receiving a system log and a buried point log which is generated when a buried point which is configured in a business system in advance is operated in the business system based on a flash component;
and analyzing the system log and the call chain log based on the flash component to obtain the system log information and the call chain log information.
9. An issue localization apparatus, comprising:
the acquisition module is used for acquiring system log information and call chain log information; the system log information at least comprises a service identifier and log detail information; the call chain log information at least comprises a service identifier and call detail information;
the correlation module is used for correlating the system log information and the call chain log information of each service based on the service identification;
a receiving module, configured to receive a query request of a user, where the query request at least includes a target service identifier;
the query module is used for querying and acquiring target system log information and target call chain log information based on the target service identifier so as to acquire target log detail information and target call detail information;
and the generating module is used for generating the problem detail information based on the target log detail information and the target calling detail information.
10. The problem location device of claim 9, wherein said acquisition module comprises:
the receiving unit is used for receiving the system log and receiving a buried point log generated by buried points which are configured in the service system in advance when the service system runs; the buried point log at least comprises: TraceId, error code and call detail information;
the screening unit is used for screening the embedded point logs with the same traceId;
the summarizing unit is used for summarizing the buried point logs with the same traceId to generate the call chain log information;
and the analysis unit is used for analyzing the system log and the call chain log to obtain the system log information and the call chain log information.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011310644.2A CN112433991A (en) | 2020-11-20 | 2020-11-20 | Problem positioning method and device |
| CA3139971A CA3139971A1 (en) | 2020-11-20 | 2021-11-22 | Problem positioning method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011310644.2A CN112433991A (en) | 2020-11-20 | 2020-11-20 | Problem positioning method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112433991A true CN112433991A (en) | 2021-03-02 |
Family
ID=74693202
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011310644.2A Pending CN112433991A (en) | 2020-11-20 | 2020-11-20 | Problem positioning method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112433991A (en) |
| CA (1) | CA3139971A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112965852A (en) * | 2021-03-30 | 2021-06-15 | 中信银行股份有限公司 | Error positioning method and device based on log analysis |
| CN113220522A (en) * | 2021-04-09 | 2021-08-06 | 北京房江湖科技有限公司 | Automatic positioning method and device for service abnormity |
| CN115904872A (en) * | 2022-12-01 | 2023-04-04 | 深圳市雁联计算系统有限公司 | Transaction link monitoring method, system and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114880407B (en) * | 2022-05-30 | 2024-06-21 | 上海九方云智能科技有限公司 | User intelligent identification method and system based on strong and weak relation network |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109669842A (en) * | 2018-12-27 | 2019-04-23 | 中国移动通信集团江苏有限公司 | Log call method, device, equipment and computer storage medium |
| CN111522922A (en) * | 2020-03-26 | 2020-08-11 | 浙江口碑网络技术有限公司 | Log information query method and device, storage medium and computer equipment |
-
2020
- 2020-11-20 CN CN202011310644.2A patent/CN112433991A/en active Pending
-
2021
- 2021-11-22 CA CA3139971A patent/CA3139971A1/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109669842A (en) * | 2018-12-27 | 2019-04-23 | 中国移动通信集团江苏有限公司 | Log call method, device, equipment and computer storage medium |
| CN111522922A (en) * | 2020-03-26 | 2020-08-11 | 浙江口碑网络技术有限公司 | Log information query method and device, storage medium and computer equipment |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112965852A (en) * | 2021-03-30 | 2021-06-15 | 中信银行股份有限公司 | Error positioning method and device based on log analysis |
| CN113220522A (en) * | 2021-04-09 | 2021-08-06 | 北京房江湖科技有限公司 | Automatic positioning method and device for service abnormity |
| CN115904872A (en) * | 2022-12-01 | 2023-04-04 | 深圳市雁联计算系统有限公司 | Transaction link monitoring method, system and storage medium |
| CN115904872B (en) * | 2022-12-01 | 2024-03-12 | 深圳市雁联计算系统有限公司 | Transaction link monitoring method, system and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CA3139971A1 (en) | 2022-05-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112433991A (en) | Problem positioning method and device | |
| CN107908541B (en) | Interface testing method and device, computer equipment and storage medium | |
| CN109359094B (en) | Distributed system log full-link tracking method and device | |
| CN107301197B (en) | Service data tracking processing system and method | |
| CN112506807B (en) | Automatic test system for interface serving multiple systems | |
| CN110807085B (en) | Fault information query method and device, storage medium and electronic device | |
| CN107977473B (en) | Logback-based distributed system log retrieval method and system | |
| CN105389352A (en) | Log processing method and apparatus | |
| CN112488769B (en) | Advertisement putting test method, device, equipment and storage medium | |
| CN107168845B (en) | Fault positioning method and device | |
| US20220156247A1 (en) | Event records in a log file | |
| CN111563041A (en) | Test case on-demand accurate execution method | |
| CN110083581B (en) | Log tracing method and device, storage medium and computer equipment | |
| CN112307374A (en) | Jumping method, device and equipment based on backlog and storage medium | |
| CN102207956A (en) | Database management method, database management system and program thereof | |
| CN112711496A (en) | Log information full link tracking method and device, computer equipment and storage medium | |
| CN107347016B (en) | Signaling flow model identification method and abnormal signaling flow identification method | |
| CN110888985A (en) | Alarm information processing method and device, electronic equipment and storage medium | |
| CN114817968A (en) | Method, device and equipment for tracing path of featureless data and storage medium | |
| US10241957B2 (en) | Workload patterns for realistic load recreation in performance testing | |
| CN109144801A (en) | It is a kind of to be directed to the test method of MOC card, device and equipment in server | |
| CN115061908A (en) | Method and device for positioning defect code, storage medium and computer equipment | |
| CN115022213B (en) | Method for identifying request abnormality and storage medium | |
| CN113128848A (en) | Data quality monitoring method for full-service index, electronic equipment and storage medium | |
| CN106777010B (en) | Log providing method and device and log obtaining method, device and 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210302 |