CN115454956A - Log generation method and device, electronic equipment and storage medium - Google Patents
Log generation method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115454956A CN115454956A CN202211114905.2A CN202211114905A CN115454956A CN 115454956 A CN115454956 A CN 115454956A CN 202211114905 A CN202211114905 A CN 202211114905A CN 115454956 A CN115454956 A CN 115454956A
- Authority
- CN
- China
- Prior art keywords
- service
- information
- log
- service state
- target order
- 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
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
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/73—Program documentation
Abstract
The disclosure provides a log generation method and device, an electronic device and a storage medium. One embodiment of the method comprises: acquiring a target order mark; determining service state information according to the target order mark, wherein the service state information comprises a corresponding relation between service state depth information and service state description information; acquiring service content information corresponding to the target order identification; and generating a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information. This embodiment enables a standardized output of the log.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a log generation method and apparatus, an electronic device, and a storage medium.
Background
The log is a data file used for recording business parameters related to the order, and can be used for related personnel to know the business processing condition of the order. In some cases, a standardized format of log output is also required to perform complex log analysis and data statistics.
Disclosure of Invention
The disclosure provides a log generation method and device, an electronic device and a storage medium.
In a first aspect, the present disclosure provides a log generating method, including:
acquiring a target order mark;
determining service state information according to the target order mark, wherein the service state information comprises a corresponding relation between service state depth information and service state description information;
acquiring service content information corresponding to the target order identification;
and generating a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information.
In some optional embodiments, the log splicing rule includes a splicing sequence between service attribute information, where the service attribute information includes a service attribute name and a corresponding service attribute value.
In some optional embodiments, the service content information includes at least one target service attribute name and a corresponding target service attribute value.
In some optional embodiments, the generating a log corresponding to the target order identifier according to a preset log splicing rule, the service content information, and the service state information includes:
and according to the splicing sequence among the service attribute information, splicing the service attribute values corresponding to the service attribute information in the service content information and the service state information to generate a log corresponding to the target order identifier, wherein the log comprises service state description information which is determined according to the corresponding relationship between the service state depth information and the service state description information.
In a second aspect, the present disclosure provides a log generating apparatus, including:
a first acquisition unit configured to acquire a target order identification;
a determining unit configured to determine service state information according to the target order identifier, wherein the service state information includes a correspondence between service state depth information and service state description information;
a second obtaining unit configured to obtain service content information corresponding to the target order identification;
and the generating unit is configured to generate a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information.
In some optional embodiments, the log splicing rule includes a splicing sequence between service attribute information, where the service attribute information includes a service attribute name and a corresponding service attribute value.
In some optional embodiments, the service content information includes at least one target service attribute name and a corresponding target service attribute value.
In some optional embodiments, the generating unit is further configured to:
and according to the splicing sequence among the service attribute information, splicing the service content information and the service attribute values corresponding to the service attribute information in the service state information to generate a log corresponding to the target order identifier, wherein the log comprises the service state description information, and the service state description information is determined according to the corresponding relation between the service state depth information and the service state description information.
In a third aspect, the present disclosure provides an electronic device, comprising: one or more processors; a storage device, on which one or more programs are stored, which, when executed by the one or more processors, cause the one or more processors to implement the method as described in any implementation manner of the first aspect.
In a fourth aspect, the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by one or more processors, implements the method as described in any implementation form of the first aspect.
The disclosure provides a log generation method and device, an electronic device and a storage medium. One embodiment of the method comprises: acquiring a target order mark; determining service state information according to the target order mark, wherein the service state information comprises a corresponding relation between service state depth information and service state description information; acquiring service content information corresponding to the target order mark; and generating a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information. This embodiment enables a standardized output of the log.
Drawings
Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which one embodiment of the present disclosure may be applied;
FIG. 2 is a flow diagram for one embodiment of a log generation method according to the present disclosure;
FIG. 3 is a schematic diagram of a data structure for traffic status information provided in accordance with the present disclosure;
FIG. 4A is a flow diagram for one embodiment of a log generation method according to the present disclosure;
FIG. 4B is a flowchart illustration of one embodiment of a log generation method according to the present disclosure;
FIG. 4C is a schematic comparison of logs provided in accordance with the present disclosure;
FIG. 5 is a schematic block diagram of one embodiment of a log generation apparatus according to the present disclosure;
FIG. 6 is a schematic block diagram of a computer system suitable for use in implementing the electronic device of the present disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the log generation method or log generation apparatus of the present disclosure may be applied.
As shown in fig. 1, system architecture 100 may include terminal device 101, network 102, and server 103. Network 102 is the medium used to provide communication links between terminal devices 101 and server 103. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use terminal device 101 to interact with server 103 over network 102 to receive or send messages and the like. Various communication client applications, such as a log output application, a log processing application, a web browser application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like, may be installed on the terminal device 101.
The terminal apparatus 101 may be hardware or software. When the terminal device 101 is hardware, it may be various electronic devices having a display screen and supporting text input, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like. When the terminal apparatus 101 is software, it can be installed in the electronic apparatuses listed above. It may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.
The server 103 may be a server that provides various services, such as a background server that provides support for log output type applications displayed on the terminal device 101. The background server can analyze and process the received data such as the log output request and the like, and feed back the processing result to the terminal equipment.
In some cases, the log generation method provided by the present disclosure may be performed by both the terminal device 101 and the server 103, for example, the step of "obtaining the target order identification ·" may be performed by the terminal device 101, and the remaining steps may be performed by the server 103. The present disclosure is not limited thereto. Accordingly, the log generation means may be provided in the terminal device 101 and the server 103, respectively.
In some cases, the log generating method provided by the present disclosure may be executed by the server 103, and accordingly, the log generating apparatus may also be disposed in the server 103, and in this case, the system architecture 100 may also not include the terminal device 101.
In some cases, the log generating method provided by the present disclosure may be executed by the terminal device 101, and accordingly, the log generating apparatus may also be disposed in the terminal device 101, and in this case, the system architecture 100 may also not include the server 103.
The server 103 may be hardware or software. When the server 103 is hardware, it may be implemented as a distributed server cluster composed of a plurality of servers, or may be implemented as a single server. When the server 103 is software, it may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a log generation method according to the present disclosure is shown. The log generation method comprises the following steps:
Here, the target order identification may be information for uniquely identifying the target order, and may be, for example, an order number or the like.
In this embodiment, an executive body (e.g., the server 103 shown in fig. 1) of the log generation method may obtain the target order identifier from the order platform.
Here, the service state information may include a correspondence between service state depth information and service state description information.
In this embodiment, the execution main body may determine the service state information corresponding to the target order identifier according to a preset correspondence between the order identifier and the service state information. Here, the correspondence between the order identification and the service status information may be presented in the form of a correspondence table.
Specifically, base table information of workflow storage business states can be added in system configuration, extraction and processing logic of the business state information is compiled, and the business state information is extracted and processed into a specified data structure. For example, as shown in fig. 3, the processed service status information data structure is Map, the first Key (Key) is a unique identifier (destination order identifier) of the service, and the first Value (Value) is the service status information. The service state information is a Map composed of a current node name (service state description information) and a node depth (service state depth information), that is, a second Key (Key) is the service state depth information, and a second Value (Value) is the service state description information. For example, the first Key (Key) is "transID12345". The second Key (Key) in the service state information is in a primary state, and the corresponding second Value (Value) is in a face label. The second Key (Key) in the service status information is "secondary status", and the corresponding second Value (Value) is "signed contract".
Further, the current traffic state information may be loaded into a distributed cache.
Here, the service content information may be a data file of service parameters related to the target order. Optionally, the service content information may include at least one target service attribute name and a corresponding target service attribute value.
In this embodiment, the execution main body may acquire the service content information corresponding to the target order identifier in various manners. For example, the execution main body may determine the service content information corresponding to the target order identifier according to a preset correspondence between the order identifier and the service content information. For another example, the execution subject may obtain the service content information corresponding to the target order identifier according to the annotation added by the user for the target order.
And 204, generating a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information.
Here, the log splicing rule may include a splicing order between the service attribute information. The splicing order may be used to characterize the arrangement order of the service attribute information in the output log. The service attribute information may include a service attribute name and a corresponding service attribute value. The service attribute name may be, for example, a value parameter of the service state information key, a service state information depth, a current method operation name, a parameter of interest for entry, and a parameter of interest for exit.
In this embodiment, the execution subject may generate a log corresponding to the target order identifier according to a preset log splicing rule based on the service state information determined in step 202 and the service content information acquired in step 203.
Step 204 may also be implemented by: and splicing the service attribute values corresponding to the service attribute information in the service content information and the service state information according to the splicing sequence of the service attribute information to generate a log corresponding to the target order mark. The log may include service state description information. The service state description information may be determined according to a correspondence between the service state depth information and the service state description information.
Further, the executing body may also send the target log generated in step 204 to the terminal device, so that the terminal device presents or stores the received target log.
Referring to fig. 4A, fig. 4A is a flowchart of an embodiment of a log generation method according to the present disclosure. Logs were collected and presented by ELK (Elasticsearch, logstack, kibana) as shown in fig. 4A.
Here, elastic search: a distributed search and analysis engine. Are often used as the basic search engine for applications, making them complex search functions.
Logstash: a data collection engine. The data can be dynamically collected, filtered, analyzed, enriched, unified in format and the like, and then stored in a position designated by a user.
Kibana: data analysis and visualization platforms, typically used in conjunction with the Elasticsearch, search, analyze and present data therein in a statistical chart.
Referring to fig. 4B, fig. 4B is a flowchart illustrating a log generating method according to an embodiment of the disclosure. Fig. 4B shows a flowchart of log generation in the case where the traffic state depth in the traffic state information is "2".
Referring to fig. 4C, fig. 4C is a schematic diagram illustrating a log comparison provided according to the present disclosure. Fig. 4C is a schematic diagram illustrating a log comparison between before the log generation method provided by the present disclosure and the output log generated by the log generation method provided by the present disclosure. By adopting the log generation method provided by the disclosure, the standard log with the standard output is not required to be spliced manually, the code is simpler, and the log with the standard format can be output only by adding comments and filling corresponding attributes; the log output code is non-invasive to the service code, the log output format is modified in batch, only the corresponding log output AOP method needs to be adjusted, and the log output point does not need to be modified independently.
The disclosure provides a log generation method and device, an electronic device and a storage medium. One embodiment of the method comprises: acquiring a target order mark; determining service state information according to the target order mark, wherein the service state information comprises a corresponding relation between service state depth information and service state description information; acquiring service content information corresponding to the target order mark; and generating a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information. This embodiment enables a standardized output of the log.
The technical effects that can be achieved include, but are not limited to:
1. the log output standard and the log output format of the service system are unified.
2. By means of configuration and annotation, the writing work of log output codes is simplified, the log output and the code writing of business functions are decoupled, and the invasion of the log output to the business codes is reduced.
3. The log output function is cohesive, and the adjustment of the log output standard and the log output format is more flexible.
With further reference to fig. 5, as an implementation of the method shown in the above-mentioned figures, the present disclosure provides an embodiment of a log generating apparatus, which corresponds to the embodiment of the method shown in fig. 2, and which can be specifically applied to various electronic devices.
As shown in fig. 5, the log generation apparatus 500 of the present embodiment includes: a first acquisition unit 501, a determination unit 502, a second acquisition unit 503, and a generation unit 504. The first obtaining unit 501 is configured to obtain a target order identifier. A determining unit 502 configured to determine service state information according to the target order identifier, wherein the service state information includes a correspondence between service state depth information and service state description information. A second obtaining unit 503, configured to obtain the service content information corresponding to the target order identification. The generating unit 504 is configured to generate a log corresponding to the target order identifier according to a preset log splicing rule, the service content information, and the service status information.
In this embodiment, specific processes of the first obtaining unit 501, the determining unit 502, the second obtaining unit 503, and the generating unit 504 of the log generating apparatus 500 and technical effects brought by the specific processes can refer to related descriptions of step 201, step 202, step 203, and step 204 in the corresponding embodiment of fig. 2, which are not described herein again.
In some optional embodiments, the log splicing rule may include a splicing order between service attribute information, where the service attribute information includes a service attribute name and a corresponding service attribute value.
In some optional embodiments, the service content information may include at least one target service attribute name and a corresponding target service attribute value.
In some optional embodiments, the generating unit 504 may be further configured to splice service attribute values corresponding to each service attribute information in the service content information and the service status information according to a splicing order among the service attribute information, and generate a log corresponding to the target order identifier, where the log includes service status description information, and the service status description information is determined according to a corresponding relationship between the service status depth information and the service status description information.
It should be noted that details of implementation and technical effects of each unit in the log generating device provided by the present disclosure may refer to descriptions of other embodiments in the present disclosure, and are not described herein again.
Referring now to FIG. 6, a block diagram of a computer system 600 suitable for use in implementing the electronic device of the present disclosure is shown. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the present disclosure.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An Input/Output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input section 606 including a touch screen, a tablet, a keyboard, a mouse, or the like; an output section 607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication section 609. The above-described functions defined in the method of the present disclosure are performed when the computer program is executed by a Central Processing Unit (CPU) 601. It should be noted that the computer readable medium in the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, python, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in this disclosure may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a first acquisition unit, a determination unit, a second acquisition unit, and a generation unit. Where the names of these units do not in some cases constitute a limitation on the unit itself, for example, the first acquiring unit may also be described as "acquiring the target order identification unit".
As another aspect, the present disclosure also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: acquiring a target order mark; determining service state information according to the target order identification, wherein the service state information comprises a corresponding relation between service state depth information and service state description information; acquiring service content information corresponding to the target order mark; and generating a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is possible without departing from the inventive concept as defined above. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Claims (10)
1. A method of log generation, comprising:
acquiring a target order mark;
determining service state information according to the target order identification, wherein the service state information comprises a corresponding relation between service state depth information and service state description information;
acquiring service content information corresponding to the target order mark;
and generating a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information.
2. The method of claim 1, wherein the log stitching rule comprises a stitching order between service attribute information, and the service attribute information comprises a service attribute name and a corresponding service attribute value.
3. The method of claim 2, wherein the service content information comprises at least one target service attribute name and a corresponding target service attribute value.
4. The method of claim 3, wherein the generating a log corresponding to the target order identifier according to a preset log splicing rule, the service content information, and the service status information comprises:
and according to the splicing sequence among the service attribute information, splicing the service content information and the service attribute values corresponding to the service attribute information in the service state information to generate a log corresponding to the target order identifier, wherein the log comprises the service state description information, and the service state description information is determined according to the corresponding relation between the service state depth information and the service state description information.
5. A log generation apparatus comprising:
a first obtaining unit configured to obtain a target order identification;
a determining unit configured to determine service state information according to the target order identifier, wherein the service state information includes a correspondence between service state depth information and service state description information;
a second obtaining unit configured to obtain service content information corresponding to the target order identification;
and the generating unit is configured to generate a log corresponding to the target order mark according to a preset log splicing rule, the service content information and the service state information.
6. The apparatus of claim 5, wherein the log stitching rule comprises a stitching order between service attribute information, and the service attribute information comprises a service attribute name and a corresponding service attribute value.
7. The apparatus of claim 6, wherein the service content information comprises at least one target service attribute name and a corresponding target service attribute value.
8. The apparatus of claim 7, wherein the generating unit is further configured to:
and according to the splicing sequence among the service attribute information, splicing the service content information and the service attribute values corresponding to the service attribute information in the service state information to generate a log corresponding to the target order identifier, wherein the log comprises the service state description information, and the service state description information is determined according to the corresponding relation between the service state depth information and the service state description information.
9. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-4.
10. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211114905.2A CN115454956A (en) | 2022-09-14 | 2022-09-14 | Log generation method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211114905.2A CN115454956A (en) | 2022-09-14 | 2022-09-14 | Log generation method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115454956A true CN115454956A (en) | 2022-12-09 |
Family
ID=84302655
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211114905.2A Pending CN115454956A (en) | 2022-09-14 | 2022-09-14 | Log generation method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115454956A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116107524A (en) * | 2023-04-13 | 2023-05-12 | 杭州朗和科技有限公司 | Low-code application log processing method, medium, device and computing equipment |
-
2022
- 2022-09-14 CN CN202211114905.2A patent/CN115454956A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116107524A (en) * | 2023-04-13 | 2023-05-12 | 杭州朗和科技有限公司 | Low-code application log processing method, medium, device and computing equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109062563B (en) | Method and device for generating page | |
| CN113987074A (en) | Distributed service full-link monitoring method and device, electronic equipment and storage medium | |
| CN110543297B (en) | Method and apparatus for generating source code | |
| CN109359194B (en) | Method and apparatus for predicting information categories | |
| CN110780874B (en) | Method and device for generating information | |
| CN109766127B (en) | Method for updating application version information | |
| CN110232091B (en) | Method, system and apparatus for synchronizing data | |
| CN108933695B (en) | Method and apparatus for processing information | |
| CN112948726A (en) | Method, device and system for processing abnormal information | |
| CN113010405A (en) | Application program testing method and device | |
| CN115454956A (en) | Log generation method and device, electronic equipment and storage medium | |
| CN112559024A (en) | Method and device for generating transaction code change list | |
| CN111124541A (en) | Configuration file generation method, device, equipment and medium | |
| CN114840379A (en) | Log generation method, device, server and storage medium | |
| CN110554892A (en) | Information acquisition method and device | |
| CN109889402B (en) | Method and apparatus for generating information | |
| CN112988583A (en) | Method and device for testing syntax compatibility of database | |
| CN113011858A (en) | Audit project configuration and execution method and device | |
| CN112084114A (en) | Method and apparatus for testing an interface | |
| CN113626301A (en) | Method and device for generating test script | |
| CN108628909B (en) | Information pushing method and device | |
| CN112131379A (en) | Method, device, electronic equipment and storage medium for identifying problem category | |
| CN113407229A (en) | Method and device for generating offline script | |
| CN112579428A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN115309612B (en) | Method and device for monitoring data |
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 |