CN111061696B - Method and device for analyzing transaction message log - Google Patents
Method and device for analyzing transaction message log Download PDFInfo
- Publication number
- CN111061696B CN111061696B CN201911304492.2A CN201911304492A CN111061696B CN 111061696 B CN111061696 B CN 111061696B CN 201911304492 A CN201911304492 A CN 201911304492A CN 111061696 B CN111061696 B CN 111061696B
- Authority
- CN
- China
- Prior art keywords
- transaction
- log
- message
- data
- format
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/26—Visual data mining; Browsing structured data
Abstract
The application provides a method and a device for analyzing a transaction message log, wherein the method comprises the steps of firstly, obtaining the transaction message log; then determining the type of the transaction message log according to the message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to preliminarily analyze the transaction message log to obtain a data message; then, according to the message body characteristics of the data message, determining the format type of the data message, and performing secondary analysis by using an analysis method corresponding to the format type to obtain transaction data; and finally, filling the transaction data into a visual template to obtain a visual transaction message log. Thus, the transaction message log is converted into a data message with a uniform format through preliminary analysis; and transaction data is obtained through secondary analysis and is filled in a visual template, and transaction message logs are displayed by using the unified visual template, so that technicians can conveniently check the transaction data, and the efficiency of troubleshooting and system testing is improved.
Description
Technical Field
The present application relates to the field of software testing, and in particular, to a method and an apparatus for analyzing a transaction message log.
Background
At present, with the increase of banking business and the wide application of computers, a bank background system is more and more huge. Particularly for various banking businesses, a large number of independent peripheral transaction systems are needed to provide services, and the independent peripheral transaction systems need to be associated with a core system, so that the whole banking system is extremely complex and large.
When testing a bank system, a technician needs to check a transaction message log and restore transaction data to determine the system where a problem exists. However, the transaction message log is generated by intersystem communication, and does not conform to the human language specification, so that the reading of technicians is difficult. The existing message visualization technology is not suitable for a complex system formed by combining a plurality of systems, such as a bank. Therefore, a method for processing transaction message logs is needed to uniformly process messages of multiple transaction systems, which is convenient for technicians to check.
Disclosure of Invention
In view of this, the embodiment of the present application provides an analysis method and an analysis device for transaction message logs, which aim to process transaction message logs of different formats, display the transaction message logs in a visual form, and facilitate technical staff to analyze problems.
In order to achieve the purpose, the invention provides the following technical scheme:
a method for analyzing a transaction message log comprises the following steps:
acquiring a transaction message log generated by communication between a front-end system and a transaction system, wherein the transaction system comprises a core transaction system and a plurality of peripheral transaction systems;
determining the type of the transaction message log according to the message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to carry out preliminary analysis on the transaction message log to obtain a data message; the log format source file records a generation rule of a transaction message log;
determining the format type of the data message according to the message body characteristics of the data message, and performing secondary analysis on the data message by using an analysis method corresponding to the format type to obtain transaction data;
and filling the transaction data into a visual template to obtain a visual transaction message log.
Optionally, the transaction message log includes a core transaction log and a plurality of peripheral transaction logs; the log format source file comprises a core log format source file and a plurality of peripheral log format source files;
the core transaction log is generated according to the source file in the core log format when a core transaction system runs;
the multiple peripheral transaction logs are generated according to the corresponding peripheral log format source files when the multiple peripheral transaction systems run.
Optionally, the selecting a log format source file corresponding to the transaction message log to perform preliminary analysis on the transaction message log to obtain a data message includes:
determining a transaction system type corresponding to the transaction message log according to the type of the transaction message log;
selecting a log format source file corresponding to the transaction system type, and sorting out basic information of the transaction message log according to a generation rule recorded in the log format source file;
and filling the basic information into a data message template to obtain the data message.
Optionally, after the basic information of the transaction message log is sorted out according to the generation rule recorded in the log format source file, the method further includes:
comparing whether the basic information is consistent with the basic information required by the generation rule;
and when the basic information is inconsistent with the basic information required by the generation rule, skipping the subsequent steps, directly taking the transaction message log as an error log, and outputting the basic information.
Optionally, the performing, by using an analysis method corresponding to the format type, a secondary analysis on the data packet to obtain transaction data includes:
determining a grammar rule of the data message according to the format type;
transaction attribute data are extracted from the data messages, and the logic relation among the transaction attribute data is determined according to the grammar rule;
and combining the transaction attribute data according to the logic relationship to obtain transaction data.
Optionally, the format types of the transaction message log include a matching type by tag, a matching type by byte, and a special format type; the special format types include an XML format type and a JSON format type.
Optionally, after obtaining the visual transaction message log, the method further includes:
acquiring the position of each transaction data in the visual transaction message log in the transaction message log;
and associating the transaction data with the position of the transaction data in the transaction message log so that a research and development staff can locate the transaction message log through a visual message.
An apparatus for parsing a transaction message log, the apparatus comprising:
the system comprises an acquisition module, a transaction module and a transaction module, wherein the acquisition module is used for acquiring a transaction message log generated by the communication between a front-end system and a transaction system, and the transaction system comprises a core transaction system and a plurality of peripheral transaction systems;
the preliminary analysis module is used for determining the type of the transaction message log according to the message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to carry out preliminary analysis on the transaction message log to obtain a data message; the log format source file records a generation rule of a transaction message log;
the secondary analysis module is used for determining the format type of the data message according to the message body characteristics of the data message and carrying out secondary analysis on the data message by using an analysis method corresponding to the format type to obtain transaction data;
and the visualization module is used for filling the transaction data into a visualization template to obtain a visualization transaction message log.
Optionally, the types of the transaction message logs include a core transaction log and a plurality of peripheral transaction logs; the types of the log format source files comprise a core log format source file and a plurality of peripheral log format source files; the core transaction log is generated according to the source file in the core log format when a core transaction system runs; the multiple peripheral transaction logs are generated according to the corresponding peripheral log format source files when multiple peripheral transaction systems run;
the preliminary analysis module comprises:
the system determining module is used for determining the transaction system type corresponding to the transaction message log according to the type of the transaction message log;
the selection sorting module is used for selecting a log format source file corresponding to the transaction system type and sorting out basic information of the transaction message log according to a generation rule recorded in the log format source file;
and the filling module is used for filling the basic information into a data message template to obtain the data message.
Optionally, the secondary parsing module includes:
the first determining module is used for determining the grammar rule of the data message according to the format type;
the second determining module is used for extracting transaction attribute data from the data message and determining the logic relation between the transaction attribute data according to the grammar rule;
and the combination module is used for combining the transaction attribute data according to the logic relation to obtain transaction data.
The embodiment of the application provides a method and a device for analyzing transaction message logs, and the method comprises the steps of firstly obtaining transaction message logs generated by communication between a front-end system and a transaction system; then determining the type of the transaction message log according to the message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to preliminarily analyze the transaction message log to obtain a data message; then, determining the format type of the data message according to the message body characteristics of the data message, and performing secondary analysis on the data message by using an analysis method corresponding to the format type to obtain transaction data; and finally, filling the transaction data into a visual template to obtain a visual transaction message log. Therefore, transaction message logs of different transaction systems are converted into data messages with a uniform format through preliminary analysis; and transaction data are obtained through secondary analysis and filled in a visual template, visualization of transaction message logs is completed, and finally transaction message logs from different transaction systems and in different formats can be displayed through a unified visual template, so that technicians can read the transaction message logs conveniently, and the efficiency of troubleshooting and system testing is improved.
Drawings
To illustrate the technical solutions in the present embodiment or the prior art more clearly, the drawings needed to be used in the description of the embodiment or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, 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 method for parsing a transaction message log according to an embodiment of the present application.
Fig. 2 is a specific schematic diagram of a transaction message log provided in the embodiment of the present application.
Fig. 3 is a schematic diagram of a visual transaction message log provided in an embodiment of the present application.
Fig. 4 is a schematic diagram of an analysis process of a transaction message log according to an embodiment of the present application.
Fig. 5 is a schematic structural diagram of an analysis device for transaction message logs according to an embodiment of the present application.
Fig. 6 is a schematic structural diagram of an apparatus for parsing a transaction message log according to an embodiment of the present disclosure.
Fig. 7 is a schematic structural diagram of an apparatus for parsing a transaction message log according to an embodiment of the present application.
Detailed Description
At present, with the development of banking business, a computer system supporting banking business services behind the computer system becomes more and more huge. The various services provided by banks have respective function positioning, different technical lines are often involved, and a large number of computer systems are required for ensuring the services. For the service of the transaction type, the bank can be divided into core transaction and peripheral transaction according to the transaction type, wherein the core transaction is the core business of the bank and is processed by a core transaction system; the peripheral transactions include all other services except the core services, and are processed by a plurality of peripheral transaction systems. In addition, the bank system also comprises a front-end system which is used for receiving various information and transmitting the information back to the corresponding core transaction system or the peripheral transaction system. Therefore, the smooth proceeding of banking business is ensured through the mutual cooperation of the plurality of transaction systems and the front-end system.
When debugging or updating the bank system, technicians can analyze transaction message logs generated by communication between each transaction system and the front-end system and find an environment which can be optimized from the transaction message logs. However, the banking system is too complex, the transaction message logs are large in number and do not conform to the human language specification, and therefore the transaction message logs are inconvenient for technicians to read. In addition, because the transaction message logs may come from different transaction systems, the basic formats may have great differences, and the existing message analysis method cannot directly analyze the transaction message logs.
In order to provide a technical scheme capable of performing unified processing and visualization on transaction message logs from different systems, the application provides an analysis method and device for transaction message logs, and a preferred embodiment of the application will be described in the following from the perspective of a service area of a bank system. It should be noted that the present application may be used in a banking system, and may also be used in other transaction systems that are composed of multiple subsystems.
Referring to fig. 1, fig. 1 is a flowchart of an analysis method for a transaction message log according to an embodiment, including:
s101: and acquiring a transaction message log generated by the communication between the front-end system and the transaction system.
In this embodiment, the server may obtain a transaction message log generated by the front-end system and the transaction system in communication. Specifically, when processing some transaction services, the banking system may first acquire the relevant information of the client and the relevant information of the transaction from the front-end system, and send the information to a core transaction system or a peripheral transaction system that processes the transaction services; and after the corresponding transaction system in the background finishes processing, returning a processing result to the front-end system, wherein the transaction message log is generated in the communication process, and the structure of the transaction message log is approximately as shown in fig. 2.
S102: determining the type of the transaction message log according to the message header of the transaction message log, and selecting a log format source file corresponding to the type of the transaction message log; and preliminarily analyzing the transaction message log to obtain a data message.
After the transaction message log is obtained, the server can determine the type of the transaction message log according to the message header of the transaction message log, namely, which transaction belongs to the transaction corresponding to the transaction message log, and then select a log format source file corresponding to the type of the transaction message log to perform preliminary analysis on the transaction message log to obtain a transaction data message.
In some implementations, the transaction message log is generated from a log-format source file during operation of the transaction system, where the log-format source file is equivalent to a generation template of the transaction message log. Specifically, the log format source file comprises a core log format source file and a plurality of peripheral log format source files. When the core transaction system is communicated with the front-end system, a core transaction log can be generated according to the source file in the core log format and by combining some specific related information of the transaction; similarly, when a peripheral transaction system communicates with the front-end system, a peripheral log format source file corresponding to the peripheral transaction system can be used, and a peripheral transaction log can be generated by combining some specific relevant information of the transaction.
Further, when analyzing the transaction message log, the server may determine the transaction system type corresponding to the transaction message log according to the type of the transaction message log; and selecting a log format source file corresponding to the transaction system type, and sorting out basic information of the transaction message log according to a generation rule recorded in the log format source file. Because the transaction message log is generated according to the log format source file, the server can easily select the corresponding log format source file to perform preliminary analysis on the transaction message log after determining the type of the transaction message log, and restore the relevant information of the transaction used when the transaction system generates the transaction message log as the basic information. Therefore, by detecting and preliminarily analyzing the message header of the transaction message log, the transaction message logs from a plurality of systems and with different formats can be arranged into the data message with basically uniform format.
When the bank system processes various transactions, some transaction errors may occur, and at this time, the transaction system may interrupt the transactions and report errors, and an error log is generated according to a method different from a log format source file. Therefore, in some implementation manners, when the server performs preliminary analysis on the transaction message log, it may also be determined whether the transaction corresponding to the current transaction message log is an error transaction according to the log format source file. Specifically, the server may compare whether the basic information is consistent with the basic information required by the generation rule after the basic information of the transaction message log is sorted out according to the generation rule recorded in the log format source file; and when the basic information is inconsistent with the basic information required by the generation rule, skipping the subsequent steps, directly taking the transaction message log as an error log, and outputting the basic information. Therefore, by comparing whether the basic information quantity of the current transaction message log is consistent with the theoretical quantity, the error of the message can be realized, and the error log can be found out.
S103: determining the format type of the data message according to the message body characteristics of the data message; and carrying out secondary analysis on the data message by using a corresponding analysis method to obtain transaction data.
Although the server obtains the data message with a uniform format through preliminary parsing, basic features such as syntax of the data message may still be different because each transaction system may have a completely different architecture, even not written in the same language. Therefore, after the data message is obtained, the server can determine the format type of the data message according to the message body characteristics of the data message, so that an analysis method is selected to carry out secondary analysis on the data message, and uniform transaction data are obtained.
Specifically, the data packet may include format types such as a tag matching type, a byte matching type, and a special format type, where the special format type includes an XML format type, a JSON format type, and the like. When the data message is analyzed for the second time, the server may extract part of the data in the data message, analyze the data, and determine the format type of the data message according to the syntactic characteristics of the data message. Then, determining a grammar rule of the data message according to the format type, extracting transaction attribute data from the data message, and determining a logic relation between the transaction attribute data according to the grammar rule; and finally, combining the transaction attribute data according to the logic relation to obtain transaction data. Therefore, the data message is analyzed for the second time, and the specific situation of the transaction message log corresponding to the transaction is restored, so that subsequent visual processing is facilitated.
S104: and filling the transaction data into a visual template to obtain a visual transaction message log.
After the transaction data is obtained, the server can fill the transaction data into a visual template to obtain a visual transaction message log, so that a technician can conveniently check the transaction data. Specifically, the server may fill the data of the text information type into a table created in advance, and display the data of the number type in a form of a bar graph or a pie graph. As shown in fig. 3, the server may also directly fill all transaction data into a form of the visual template, and display related information such as a transaction message log text and a message log list at other positions of the visual template. After the visualized transaction message log is obtained, the transaction message log is basically analyzed, and the whole process is shown in fig. 4.
The embodiment provides an analysis method of a transaction message log, which comprises the steps of firstly, obtaining the transaction message log generated by the communication between a front-end system and a transaction system; then determining the type of the transaction message log according to the message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to preliminarily analyze the transaction message log to obtain a data message; then, determining the format type of the data message according to the message body characteristics of the data message, and performing secondary analysis on the data message by using an analysis method corresponding to the format type to obtain transaction data; and finally, filling the transaction data into a visual template to obtain a visual transaction message log. Therefore, transaction message logs of different transaction systems are converted into data messages with a uniform format through preliminary analysis; and transaction data are obtained through secondary analysis and filled in a visual template, visualization of transaction message logs is completed, and finally transaction message logs from different transaction systems and in different formats can be displayed through a unified visual template, so that technicians can read the transaction message logs conveniently, and the efficiency of troubleshooting and system testing is improved.
In some other implementations, the server may associate the transaction data with its specific location in the transaction message log in order for the technician to analyze the transaction message log. Specifically, the server may obtain the position of each transaction data in the visual transaction message log in the transaction message log; and correlating the transaction data with the position of the transaction data in the transaction message log so that research and development personnel can locate the transaction message log through the visual message. Therefore, technicians can directly position the corresponding position in the transaction message log by clicking transaction data and the like, and the efficiency of system optimization testing is improved.
The foregoing provides some specific implementation manners of the method for analyzing the transaction message log according to the embodiment of the present application, and based on this, the present application also provides a corresponding apparatus. The above-mentioned device provided by the embodiments of the present application will be described in terms of functional modularity.
Referring to the schematic structural diagram of the service data storage device shown in fig. 5, the device 500 includes:
the obtaining module 510 is configured to obtain a transaction message log generated by communication between the front-end system and the transaction system.
A preliminary analysis module 520, configured to determine the type of the transaction message log according to a message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to preliminarily analyze the transaction message log to obtain a data message; the log format source file records a generation rule of a transaction message log.
The secondary analysis module 530 is configured to determine a format type of the data packet according to the packet body characteristic of the data packet, and perform secondary analysis on the data packet by using an analysis method corresponding to the format type to obtain transaction data.
And the visualization module 540 is configured to fill the transaction data into a visualization template to obtain a visualization transaction message log.
The embodiment provides an analysis device for transaction message logs, which converts the transaction message logs of different transaction systems into data messages with a uniform format through preliminary analysis; and transaction data are obtained through secondary analysis and filled in a visual template, visualization of transaction message logs is completed, and finally transaction message logs from different transaction systems and in different formats can be displayed through a unified visual template, so that technicians can read the transaction message logs conveniently, and the efficiency of troubleshooting and system testing is improved.
Optionally, referring to fig. 6, on the basis of the apparatus shown in fig. 5, the preliminary parsing module 520 includes:
the system determining module 521 is configured to determine, according to the transaction message log, a transaction system type corresponding to the transaction message log.
And the selecting and sorting module 522 is configured to select a log format source file corresponding to the transaction system type, and sort out basic information of the transaction message log according to a generation rule recorded in the log format source file.
A filling module 523, configured to fill the basic information into a data packet template to obtain the data packet.
Therefore, by detecting and preliminarily analyzing the message header of the transaction message log, the transaction message logs from a plurality of systems and with different formats can be arranged into data messages with basically uniform formats.
Optionally, referring to fig. 7, on the basis of the apparatus shown in fig. 5, the secondary parsing module 530 includes:
a first determining module 531, configured to determine a syntax rule of the data packet according to the format type.
A second determining module 532, configured to extract transaction attribute data from the data packet, and determine a logical relationship between the transaction attribute data according to the syntax rule.
The combining module 533 is configured to combine the transaction attribute data according to the logical relationship, so as to obtain transaction data.
Therefore, the data message is analyzed for the second time, and the specific situation of the transaction message log corresponding to the transaction is restored, so that subsequent visual processing is facilitated.
In the embodiments of the present application, the names "first" and "second" in the names "first determination module" and "second determination module" are used merely as name labels, and do not represent the first and second in sequence.
As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by software plus a general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the apparatus embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the description of the method embodiments for relevant points. The above-described apparatus and system embodiments are intended to be illustrative only. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only an exemplary embodiment of the present application, and is not intended to limit the scope of the present application.
Claims (10)
1. A method for analyzing a transaction message log is characterized by comprising the following steps:
acquiring a transaction message log generated by communication between a front-end system and a transaction system, wherein the transaction system comprises a core transaction system and a plurality of peripheral transaction systems;
determining the type of the transaction message log according to the message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to preliminarily analyze the transaction message log to obtain a data message; the log format source file records a generation rule of a transaction message log;
determining the format type of the data message according to the message body characteristics of the data message, and performing secondary analysis on the data message by using an analysis method corresponding to the format type to obtain transaction data;
and filling the transaction data into a visual template to obtain a visual transaction message log.
2. The method of claim 1, wherein the transaction message log comprises a core transaction log and a plurality of peripheral transaction logs; the log format source file comprises a core log format source file and a plurality of peripheral log format source files;
the core transaction log is generated according to the source file in the core log format when a core transaction system runs;
the multiple peripheral transaction logs are generated according to the corresponding peripheral log format source files when multiple peripheral transaction systems run.
3. The method of claim 2, wherein the selecting a log format source file corresponding to the transaction message log to perform a preliminary parsing on the transaction message log to obtain a data message comprises:
determining a transaction system type corresponding to the transaction message log according to the type of the transaction message log;
selecting a log format source file corresponding to the transaction system type, and sorting out basic information of the transaction message log according to a generation rule recorded in the log format source file;
and filling the basic information into a data message template to obtain the data message.
4. The method of claim 3, wherein after sorting out the basic information of the transaction message log according to the generation rule recorded in the log format source file, the method further comprises:
comparing whether the basic information is consistent with the basic information required by the generation rule;
and when the basic information is inconsistent with the basic information required by the generation rule, skipping the subsequent steps, directly taking the transaction message log as an error log, and outputting the basic information.
5. The method according to claim 1, wherein the performing a second parsing on the data packet by using a parsing method corresponding to the format type to obtain transaction data comprises:
determining a grammar rule of the data message according to the format type;
transaction attribute data are extracted from the data messages, and the logic relation among the transaction attribute data is determined according to the grammar rule;
and combining the transaction attribute data according to the logic relationship to obtain transaction data.
6. The method of claim 1, wherein the format types of the transaction message log include a per-tag match type, a per-byte match type, and a special format type; the special format types include an XML format type and a JSON format type.
7. The method of claim 1, wherein after obtaining the visual transaction message log, the method further comprises:
acquiring the position of each transaction data in the visual transaction message log in the transaction message log;
and associating the transaction data with the position of the transaction data in the transaction message log so that a research and development staff can locate the transaction message log through a visual message.
8. An apparatus for parsing a transaction message log, the apparatus comprising:
the system comprises an acquisition module, a transaction module and a processing module, wherein the acquisition module is used for acquiring a transaction message log generated by the communication between a front-end system and a transaction system, and the transaction system comprises a core transaction system and a plurality of peripheral transaction systems;
the preliminary analysis module is used for determining the type of the transaction message log according to the message header of the transaction message log; selecting a log format source file corresponding to the type of the transaction message log to preliminarily analyze the transaction message log to obtain a data message; the log format source file records a generation rule of a transaction message log;
the secondary analysis module is used for determining the format type of the data message according to the message body characteristics of the data message and carrying out secondary analysis on the data message by using an analysis method corresponding to the format type to obtain transaction data;
and the visualization module is used for filling the transaction data into a visualization template to obtain a visualization transaction message log.
9. The apparatus of claim 8, wherein the categories of the transaction message logs include a core transaction log and a plurality of peripheral transaction logs; the types of the log format source files comprise a core log format source file and a plurality of peripheral log format source files; the core transaction log is generated according to the source file in the core log format when a core transaction system runs; the various peripheral transaction logs are generated according to the peripheral log format source files corresponding to the various peripheral transaction systems when the various peripheral transaction systems run;
the preliminary analysis module comprises:
the system determining module is used for determining the transaction system type corresponding to the transaction message log according to the type of the transaction message log;
the selection sorting module is used for selecting a log format source file corresponding to the transaction system type and sorting out basic information of the transaction message log according to a generation rule recorded in the log format source file;
and the filling module is used for filling the basic information into a data message template to obtain the data message.
10. The apparatus of claim 8, wherein the secondary parsing module comprises:
the first determining module is used for determining the grammar rule of the data message according to the format type;
the second determining module is used for extracting transaction attribute data from the data message and determining the logic relation between the transaction attribute data according to the grammar rule;
and the combination module is used for combining the transaction attribute data according to the logic relation to obtain transaction data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911304492.2A CN111061696B (en) | 2019-12-17 | 2019-12-17 | Method and device for analyzing transaction message log |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911304492.2A CN111061696B (en) | 2019-12-17 | 2019-12-17 | Method and device for analyzing transaction message log |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111061696A CN111061696A (en) | 2020-04-24 |
| CN111061696B true CN111061696B (en) | 2023-03-31 |
Family
ID=70302115
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911304492.2A Active CN111061696B (en) | 2019-12-17 | 2019-12-17 | Method and device for analyzing transaction message log |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111061696B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112235262A (en) * | 2020-09-26 | 2021-01-15 | 建信金融科技有限责任公司 | Message analysis method and device, electronic equipment and computer readable storage medium |
| CN112835800A (en) * | 2021-02-05 | 2021-05-25 | 兴业证券股份有限公司 | Log playback method and device |
| CN114928663A (en) * | 2022-06-02 | 2022-08-19 | 蜂助手股份有限公司 | Method and device for recognizing callback message |
| CN116450578B (en) * | 2023-06-15 | 2023-09-15 | 中国航发四川燃气涡轮研究院 | Aircraft engine material data maintenance management method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001250025A (en) * | 1999-12-14 | 2001-09-14 | Citicorp Dev Center Inc | Method and system for managing financial transaction information |
| CN104462460A (en) * | 2014-12-16 | 2015-03-25 | 武汉理工大学 | Method of constructing REST (representational state transfer) styled ontology annotation visualization system |
| CN107273269A (en) * | 2017-06-12 | 2017-10-20 | 北京奇虎科技有限公司 | Daily record analysis method and device |
| CN109324996A (en) * | 2018-10-12 | 2019-02-12 | 平安科技（深圳）有限公司 | Journal file processing method, device, computer equipment and storage medium |
| CN110309113A (en) * | 2018-03-06 | 2019-10-08 | 阿里巴巴集团控股有限公司 | Log analytic method, system and equipment |
| CN110502426A (en) * | 2019-07-08 | 2019-11-26 | 中国工商银行股份有限公司 | The test method and device of distributed data processing system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190108112A1 (en) * | 2017-10-05 | 2019-04-11 | Hcl Technologies Limited | System and method for generating a log analysis report from a set of data sources |
-
2019
- 2019-12-17 CN CN201911304492.2A patent/CN111061696B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001250025A (en) * | 1999-12-14 | 2001-09-14 | Citicorp Dev Center Inc | Method and system for managing financial transaction information |
| CN104462460A (en) * | 2014-12-16 | 2015-03-25 | 武汉理工大学 | Method of constructing REST (representational state transfer) styled ontology annotation visualization system |
| CN107273269A (en) * | 2017-06-12 | 2017-10-20 | 北京奇虎科技有限公司 | Daily record analysis method and device |
| CN110309113A (en) * | 2018-03-06 | 2019-10-08 | 阿里巴巴集团控股有限公司 | Log analytic method, system and equipment |
| CN109324996A (en) * | 2018-10-12 | 2019-02-12 | 平安科技（深圳）有限公司 | Journal file processing method, device, computer equipment and storage medium |
| CN110502426A (en) * | 2019-07-08 | 2019-11-26 | 中国工商银行股份有限公司 | The test method and device of distributed data processing system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111061696A (en) | 2020-04-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111061696B (en) | Method and device for analyzing transaction message log | |
| CN102831052B (en) | Test exemple automation generating apparatus and method | |
| US8473916B2 (en) | Method and system for providing a testing framework | |
| WO2020088326A1 (en) | Interface operation and maintenance method and apparatus | |
| CN103577551A (en) | Method and device for submitting data to database in batch | |
| CN110069413B (en) | Test data communication, test method, device, equipment and storage medium | |
| CN105405221A (en) | Method and device for automated test | |
| CN111782117A (en) | Interface display method and device, storage medium and electronic device | |
| CN116719750B (en) | Software testing method and device, server equipment and storage medium | |
| CN113836014A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN111324480B (en) | Large-scale host transaction fault positioning system and method | |
| CN111506305A (en) | Tool kit generation method and device, computer equipment and readable storage medium | |
| CN114416597A (en) | Test case record generation method and device | |
| CN113238940B (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN114092246A (en) | Problem positioning method and device for financial transaction link | |
| CN114297074A (en) | Method for realizing automatic testing of functions, interfaces and performances based on dynamic configuration | |
| CN113742529A (en) | Multi-table front-end processing method and device | |
| CN111427796A (en) | System testing method and device and electronic equipment | |
| CN113138906A (en) | Call chain data acquisition method, device, equipment and storage medium | |
| CN109062797B (en) | Method and device for generating information | |
| CN113050925B (en) | Block chain intelligent contract repairing method and device | |
| CN111324706B (en) | Labeling method and device and electronic equipment | |
| EP4339786A1 (en) | Method of tracing call relationship and displaying log information accordingly in msa | |
| CN112948266B (en) | Database grammar testing system, method, device, equipment and storage medium | |
| CN109508245A (en) | A kind of method and terminal for realizing anomaly analysis |
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 |