CN116107781A - Log tracking method, device, electronic equipment and computer program product - Google Patents
Log tracking method, device, electronic equipment and computer program product Download PDFInfo
- Publication number
- CN116107781A CN116107781A CN202111322389.8A CN202111322389A CN116107781A CN 116107781 A CN116107781 A CN 116107781A CN 202111322389 A CN202111322389 A CN 202111322389A CN 116107781 A CN116107781 A CN 116107781A
- Authority
- CN
- China
- Prior art keywords
- tracking
- service request
- log
- executing
- identifier
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application provides a log tracking method, a log tracking device, electronic equipment and a computer program product, and relates to the technical field of data processing. The log tracking method comprises the following steps: generating a tracking identifier for the service request; carrying the tracking identifier to execute the service request; and obtaining a log generated in the process of executing the service request according to the tracking identification. According to the log tracking method provided by the embodiment of the application, the tracking mark is generated for the service request before the service request is executed, then the service request is executed with the tracking mark when the service request is executed, when the log is required to be tracked, all logs generated in the process of executing the service request can be obtained according to the tracking mark, so that all logs of the same service request in the executed process can be efficiently obtained, the subsequent identification and analysis of the logs are facilitated, the position of a fault of a system or a software program can be accurately obtained, and the subsequent quick repair of the system or the software program is facilitated.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a log tracking method, apparatus, electronic device, and computer program product.
Background
Network equipment, systems, service programs and the like can generate an event record called log during operation; each row of logs in the event record records the description of related operations such as date, time, user and action, and when network equipment, a system or a service program fails, the reason of the failure can be queried through tracking the logs.
At present, mobile BOSS systems are widely applied along with the expansion of service ranges and the increasing of service volumes, mobile terminals APP (software programs) are continuously expanded in government and enterprise system capacity sharing centers (including a nginx host, an application host and a WAS host), so that network complexity is further improved, a program for executing service requests is also more and more complex, a plurality of service centers are possibly involved in calling, logs generated in the process of executing the service requests are remained in each service center, and all logs for executing the same service request cannot be efficiently identified by a traditional method for searching the logs through user numbers, login numbers or service order numbers, so that the logs cannot be quickly extracted, identified and analyzed, and the fault positioning efficiency is low.
Disclosure of Invention
The embodiment of the application provides a log tracking method, a log tracking device, electronic equipment and a computer program product, which are used for solving the technical problems that the traditional method for searching logs through user numbers, login work numbers or service order numbers cannot efficiently identify all logs for executing the same service request, so that the logs cannot be quickly extracted, identified and analyzed, and the fault positioning efficiency is low.
In a first aspect, an embodiment of the present application provides a log tracking method, including the following steps:
generating a tracking identifier for the service request;
carrying the tracking identifier to execute the service request;
and obtaining a log generated in the process of executing the service request according to the tracking identification.
In one embodiment, the executing the service request with the tracking identifier includes:
thread variables are respectively set for executing a plurality of services related to the service request;
and when the service request is executed, the tracking identification is transmitted among a plurality of services according to the execution sequence, and the tracking identification and the thread variable of each service are associated.
In one embodiment, the obtaining, according to the tracking identifier, a log generated in the process of executing the service request includes:
according to the tracking identification and thread variables of a plurality of services, logs generated by executing each service in the process of executing the service request are respectively obtained;
and combining logs generated by executing a plurality of services to obtain the tracking log of the service request.
In one embodiment, the number of services includes any one of:
portal access services and order processing services.
In one embodiment, the generating the tracking identifier for the service request specifically includes:
a unique tracking identifier is generated for the service request.
In one embodiment, the generating the tracking identifier for the service request specifically includes:
and generating the tracking identification for the service request through a single page.
In one embodiment, the log tracking method further comprises the steps of:
and authenticating the tracking identifier.
In a second aspect, an embodiment of the present application provides a log tracking device, including:
the tracking identification generation module is used for: generating a tracking identifier for the service request;
a service request execution module, configured to: carrying the tracking identifier to execute the service request;
the log tracking module is used for: and obtaining a log generated in the process of executing the service request according to the tracking identification.
In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory storing a computer program, where the processor implements the steps of the log tracking method according to the first aspect when executing the program.
In a fourth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements the steps of the log tracking method of the first aspect.
According to the log tracking method, the device, the electronic equipment and the computer program product, the tracking identification is generated for the service request before the service request is executed, then the service request is executed with the tracking identification when the service request is executed, and when the log is required to be tracked, all logs generated in the process of executing the service request can be obtained according to the tracking identification. By the log tracking method, the device, the electronic equipment and the computer program product, all logs of the same service request in the executed process can be efficiently obtained, subsequent identification and analysis of the logs are facilitated, the fault position of the system or the software program is accurately obtained, and subsequent quick repair is facilitated.
Drawings
For a clearer description of the present application or of the prior art, the drawings that are used in the description of the embodiments or of the prior art will be briefly described, it being apparent that the drawings in the description below are some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a log tracking method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a log tracking device according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
Fig. 1 is a flow chart of a log tracking method according to an embodiment of the present application.
Referring to fig. 1, a log tracking method provided in an embodiment of the present application may include:
s110, generating a tracking identifier for the service request;
s120, carrying the tracking identifier to execute the service request;
s130, obtaining a log generated in the process of executing the service request according to the tracking identification.
It should be noted that, an execution body of the log tracking method provided in the embodiment of the present application may be a network side device, for example, a device for processing a service request, etc.
Before the network side device performs S110, the network side device performs S100:
obtain the service request and generate Token for the service request.
The service request can be sent by a user at a client or by a system developer in a system, and the network side equipment can acquire the service request and generate Token for the service request.
Note that Token means a Token (temporary) in computer authentication and a Token means a flag in lexical analysis. The Token actually says a more popular point can call a secret number, and before business asking is executed, the secret number is checked, and different secret numbers are authorized to be operated differently.
In step S110, the network side device generates a tracking identifier for the service request.
The network-side device may generate the trace identifier by UUID (Universally Unique Identifier, universally unique identification code).
Specifically, for example, the network side device may generate a TraceID (full chain tracking) identifier for the service request. The TraceID (full chain tracking) identification may indicate the context ID of a call from which the chain of footprints for executing the service request may be learned.
In step S120, the network side device carries the tracking identifier to execute the service request.
The network side equipment carries the tracking identifier to execute the service request, namely the tracking identifier traverses the whole process of executing the service request, and all logs of the whole process of executing the service request can be obtained according to the tracking identifier, so that omission is avoided.
In step S130, the network side device obtains a log generated during the execution of the service request according to the tracking identifier.
The footprint of the tracking mark is the total path for executing the service request, and all logs of the whole process for executing the service request can be obtained according to the tracking mark, so that a user or a system developer can obtain a fine analysis result according to all logs generated by executing the same service request.
According to the log tracking method, the tracking identification is generated for the service request before the service request is executed, then the service request is executed with the tracking identification when the service request is executed, and when the log is required to be tracked, all logs generated in the process of executing the service request can be obtained according to the tracking identification. By the log tracking method provided by the embodiment of the application, all logs of the same service request in the executed process can be efficiently acquired, the subsequent identification and analysis of the logs are facilitated, the refined analysis result of the system or the software program can be accurately obtained, particularly when faults occur, the fault positions can be effectively positioned through the logs, and the subsequent quick repair is facilitated.
In one embodiment, the executing the service request with the tracking identifier includes:
thread variables are respectively set for executing a plurality of services related to the service request;
and when the service request is executed, the tracking identification is transmitted among a plurality of services according to the execution sequence, and the tracking identification and the thread variable of each service are associated.
The network side equipment sets thread variables for a plurality of services related to executing the service request respectively, then when executing the service request, the tracking identification is transferred among the plurality of services according to the execution sequence, and the tracking identification and the thread variables of the services are associated (namely, the tracking identification is stored in the thread variables of the services).
When the tracking identifier is transferred between services, the tracking identifier (for example, traceID identifier) can be added to the protocol header for the caller, and the tracking identifier can be uniformly intercepted by a pre-interceptor or a filter for the callee. When the tracking identifier reaches a certain service, the tracking identifier is also transmitted inside the service, and for the transmission of the tracking identifier inside the service, the network side equipment can transmit the tracking identifier through a thread variable associated with the tracking identifier.
It should be noted that the thread variable may be a local thread variable (TreadLocal). Treadlocal is a class of storage within a thread that stores data within a given thread, after which only the given thread can obtain the stored data, and provides thread local variables that differ from their normal counterparts in that each thread accessing a variable (via its get or set method) has its own local variable that is independent of the initialized copy of the variable.
TreadLocal may be set by Eruda (mobile debug).
The complete path of a certain service request can be traced and executed according to the tracing identification by combining the tracing identification (traceID identification) and the thread variable (Treadlocal), so that fault location and service logic combing are facilitated.
In one embodiment, the obtaining, according to the tracking identifier, a log generated in the process of executing the service request includes:
according to the tracking identification and thread variables of a plurality of services, logs generated by executing each service in the process of executing the service request are respectively obtained;
and combining logs generated by executing a plurality of services to obtain the tracking log of the service request.
When a program for executing the service request is related to calling a plurality of service centers, logs generated in the process of executing the service request are printed in a plurality of devices, the logs generated by executing each service in the process of executing the service request are obtained through tracking identification and thread variable, and then the logs generated by executing a plurality of services are combined, so that the tracking logs generated in the whole process of executing the service request can be quickly obtained at one time, the logs can be quickly and accurately analyzed and abnormal capture by a user or a system developer, and convenient, effective and accurate information is provided for back-end monitoring and fault positioning processing.
In one embodiment, the number of services includes any one of:
portal access services and order processing services.
Portal access service is portal service, and order processing service is Orderser.
When the portal service (portal service) outputs the log, the thread variable (TreadLocal) of the portal service is printed to each row of the log, so that the log output by the portal service can carry the tracking identifier (for example, traceID 1) associated with the thread variable of the portal service. When the same business request is executed and other services, such as an order processing service (Orderser), need to be continuously invoked, the portal access service transmits a tracking identification (TraceID 1) to the order processing service, the tracking identification is associated with a thread variable of the order processing service, and when the order processing service outputs a log, the thread variable of the order processing service is printed on each row of the log, and likewise, the log output by the order processing service can be enabled to carry the tracking identification (TraceID 1) associated with the thread variable of the order processing service.
However, when the service request is executed, the tracking identifier of the other service request is different from the tracking identifier of the executed service request, for example, traceID2, and not TraceID1.
Therefore, by combining the trace identifier (TraceID identifier) and the thread variable (TreadLocal), a complete path for executing a certain service request can be traced according to the trace identifier.
In one embodiment, the generating the tracking identifier for the service request specifically includes:
a unique tracking identifier is generated for the service request.
For example, the trace identifier may be generated by a UUID (Universally Unique Identifier, a universally unique identification code) to avoid the presence of duplicate trace identifiers, which may confuse the resulting log of traces.
In one embodiment, the generating the tracking identifier for the service request specifically includes:
and generating the tracking identification for the service request through a single page.
For example, tracking identifications may be generated for service requests via H5 pages.
The H5 page is a single page and has the self-adaptive capability of a mobile terminal, namely the H5 page is simply adapted according to different terminal screen sizes so as to achieve the best display effect of different screens; and the H5 page supports multimedia functions such as playback of background music or video; the H5 page also has a preloading function, namely the loading of the page is completed before the user clicks, so that the reading fluency is ensured, and a special effect of rolling detection is used, namely a large number of characters or pictures can be automatically loaded while the page is slid, so that a dynamic aesthetic feeling is caused; the H5 page also supports slide page turning, with each page content being individually paged.
The H5 page can be used for quickly, efficiently and humanizedly generating the tracking identification for the service request.
In one embodiment, the log tracking method further comprises the steps of:
and authenticating the tracking identifier.
In particular, reverse authentication may be achieved by storing the tracking identity in a thread variable. When the authentication is passed, the Token, the tracking identifier (traceID) and the like are added to the portal access service (PortalService), and the tracking identifier (traceID) and the thread variable of the portal access service are associated (namely, the tracking identifier is stored in the thread variable of the portal access service).
The log tracking method provided by the embodiment of the application supports the unique tracking identification of the service request generated by the APP calling H5 page; the log tracking of the service requests called each other among the services can be realized; high-efficiency low-consumption log tracking can be realized through Eruda, treadLocal thread variables; and all logs generated by executing the same service request can be rapidly extracted, identified and analyzed through flexible thread coding configuration, so that the fault positioning efficiency and accuracy are greatly improved.
According to the log tracking method provided by the embodiment of the application, the debugging window is effectively used, convenience is provided for development, test and debugging of the follow-up APP new requirements, development efficiency is improved, and development life cycle is greatly shortened; the method is applicable to any mobile terminal equipment without depending on other equipment, and can solve the compatibility problem of various mobile terminals; the plug-in can be compiled and customized, and a foundation is laid for the functions of follow-up APP performance resource monitoring, browser characteristic detection, geographic position, gravity sensing and the like.
The following describes the log tracking device provided in the embodiments of the present application, and the log tracking device described below and the log tracking method described above may be referred to correspondingly.
Fig. 2 is a schematic structural diagram of a log tracking device according to an embodiment of the present application.
Referring to fig. 2, a log tracking device provided in an embodiment of the present application may include:
the tracking identifier generating module 210 is configured to: generating a tracking identifier for the service request;
a service request execution module 220, configured to: carrying the tracking identifier to execute the service request;
a log tracking module 230 for: and obtaining a log generated in the process of executing the service request according to the tracking identification.
In one embodiment, the service request execution module 220 includes:
a thread variable setting sub-module for: thread variables are respectively set for executing a plurality of services related to the service request;
the tracking identifier transfer and association sub-module is used for: and when the service request is executed, the tracking identification is transmitted among a plurality of services according to the execution sequence, and the tracking identification and the thread variable of each service are associated.
In one embodiment, the log tracking module 230 includes:
the service log obtaining sub-module is used for: according to the tracking identification and thread variables of a plurality of services, logs generated by executing each service in the process of executing the service request are respectively obtained;
the tracking log obtaining sub-module is used for: and combining logs generated by executing a plurality of services to obtain the tracking log of the service request.
In one embodiment, the number of services includes any one of:
portal access services and order processing services.
In one embodiment, the tracking identifier generating module 210 is specifically configured to:
a unique tracking identifier is generated for the service request.
In one embodiment, the tracking identifier generating module 210 is specifically configured to:
and generating the tracking identification for the service request through a single page.
In one embodiment, the log tracking device further comprises:
the tracking identification authentication module is used for: and authenticating the tracking identifier.
Fig. 3 illustrates a physical schematic diagram of an electronic device, as shown in fig. 3, where the electronic device may include: processor 810, communication portal (Communication Interface) 820, memory 830, and communication bus 840, wherein processor 810, communication portal 820, memory 830 accomplish communication with each other through communication bus 840. The processor 810 may call a computer program in the memory 830 to perform the steps of the log tracking method, including, for example:
generating a tracking identifier for the service request;
carrying the tracking identifier to execute the service request;
and obtaining a log generated in the process of executing the service request according to the tracking identification.
Further, the logic instructions in the memory 830 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In another aspect, embodiments of the present application further provide a computer program product, where the computer program product includes a computer program, where the computer program may be stored on a non-transitory computer readable storage medium, where the computer program when executed by a processor is capable of executing the steps of the log tracking method provided in the foregoing embodiments, for example, including:
generating a tracking identifier for the service request;
carrying the tracking identifier to execute the service request;
and obtaining a log generated in the process of executing the service request according to the tracking identification.
In another aspect, embodiments of the present application further provide a processor-readable storage medium storing a computer program for causing a processor to perform the steps of the method provided in the above embodiments, for example, including:
generating a tracking identifier for the service request;
carrying the tracking identifier to execute the service request;
and obtaining a log generated in the process of executing the service request according to the tracking identification.
The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), and the like.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.
Claims (10)
1. A log tracking method, comprising the steps of:
generating a tracking identifier for the service request;
carrying the tracking identifier to execute the service request;
and obtaining a log generated in the process of executing the service request according to the tracking identification.
2. The method of claim 1, wherein the executing the service request with the tracking identifier comprises:
thread variables are respectively set for executing a plurality of services related to the service request;
and when the service request is executed, the tracking identification is transmitted among a plurality of services according to the execution sequence, and the tracking identification and the thread variable of each service are associated.
3. The method according to claim 2, wherein the obtaining, according to the tracking identifier, a log generated during the execution of the service request includes:
according to the tracking identification and thread variables of a plurality of services, logs generated by executing each service in the process of executing the service request are respectively obtained;
and combining logs generated by executing a plurality of services to obtain the tracking log of the service request.
4. The log tracking method of claim 2, wherein the number of services comprises any one of:
portal access services and order processing services.
5. The method for tracking logs according to any one of claims 1 to 4, wherein the generating a tracking identifier for the service request is specifically:
a unique tracking identifier is generated for the service request.
6. The method for tracking logs according to any one of claims 1 to 4, wherein the generating a tracking identifier for the service request is specifically:
and generating the tracking identification for the service request through a single page.
7. The log tracking method as defined in any one of claims 1-4, further comprising the step of:
and authenticating the tracking identifier.
8. A log tracking device, comprising:
the tracking identification generation module is used for: generating a tracking identifier for the service request;
a service request execution module, configured to: carrying the tracking identifier to execute the service request;
the log tracking module is used for: and obtaining a log generated in the process of executing the service request according to the tracking identification.
9. An electronic device comprising a processor and a memory storing a computer program, characterized in that the processor implements the steps of the log tracking method of any of claims 1 to 7 when executing the computer program.
10. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the log tracking method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111322389.8A CN116107781A (en) | 2021-11-09 | 2021-11-09 | Log tracking method, device, electronic equipment and computer program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111322389.8A CN116107781A (en) | 2021-11-09 | 2021-11-09 | Log tracking method, device, electronic equipment and computer program product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116107781A true CN116107781A (en) | 2023-05-12 |
Family
ID=86266047
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111322389.8A Pending CN116107781A (en) | 2021-11-09 | 2021-11-09 | Log tracking method, device, electronic equipment and computer program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116107781A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116881040A (en) * | 2023-09-08 | 2023-10-13 | 杭州小电科技股份有限公司 | Service operation processing method and device, electronic device and storage medium |
-
2021
- 2021-11-09 CN CN202111322389.8A patent/CN116107781A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116881040A (en) * | 2023-09-08 | 2023-10-13 | 杭州小电科技股份有限公司 | Service operation processing method and device, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108628743B (en) | Application program testing method, device, equipment and storage medium | |
| CN113840012B (en) | Block chain-based screen recording evidence obtaining method and system and electronic equipment | |
| CN108427613B (en) | Abnormal interface positioning method and device, computer equipment and storage medium | |
| CN109033772B (en) | Verification information input method and device | |
| CN108984389B (en) | Application program testing method and terminal equipment | |
| WO2015131804A1 (en) | Call stack relationship acquiring method and apparatus | |
| CN109308263B (en) | Applet testing method, device and equipment | |
| CN109299015B (en) | Software testing method, device and system | |
| US20170005858A1 (en) | Log processing method and client | |
| CN105487966A (en) | Program testing method, device and system | |
| CN109683997B (en) | Method for accessing application program interface through sandbox, sandbox and sandbox equipment | |
| CN107239403A (en) | A kind of positioning problems method and apparatus | |
| CN116107781A (en) | Log tracking method, device, electronic equipment and computer program product | |
| US9501390B1 (en) | Enhancing automated mobile application testing | |
| CN102750493B (en) | Access right control method, Apparatus and system | |
| CN112115060A (en) | Audio test method and system based on terminal | |
| CN111753270A (en) | Application program login verification method, device, equipment and storage medium | |
| CN111324539A (en) | Account switching test method and system | |
| CN115276844B (en) | Communication module testing method and device, storage medium and electronic equipment | |
| CN113535578B (en) | CTS test method, CTS test device and CTS test equipment | |
| CN115016995A (en) | Interface testing method, computer device and computer storage medium | |
| CN111736893B (en) | Software package version verification method and related device | |
| CN113535580A (en) | CTS (clear to send) testing method, device and testing equipment | |
| CN114513329A (en) | Industrial Internet information security assessment method and device | |
| CN105988917B (en) | Abnormal information acquisition method and device |
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 |