CN115061890A - Troubleshooting method and equipment for software system and storage medium - Google Patents
Troubleshooting method and equipment for software system and storage medium Download PDFInfo
- Publication number
- CN115061890A CN115061890A CN202210734033.3A CN202210734033A CN115061890A CN 115061890 A CN115061890 A CN 115061890A CN 202210734033 A CN202210734033 A CN 202210734033A CN 115061890 A CN115061890 A CN 115061890A
- Authority
- CN
- China
- Prior art keywords
- user
- unique identifier
- log
- session
- interface request
- 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/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
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Computer Hardware Design (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a fault elimination method, equipment and a storage medium of a software system, wherein the method comprises the following steps: responding to screen capturing operation of a user at the front end, and adding a unique identifier for a screen capturing picture; responding to a fault removal request provided by a user based on a screen capture picture, and acquiring a unique identifier from the screen capture picture; and performing obstacle removing processing based on the unique identifier. Through the mode, the efficiency and the accuracy of removing obstacles can be improved.
Description
Technical Field
The present application relates to the field of software system technologies, and in particular, to a method, a device, and a storage medium for troubleshooting a software system.
Background
At present, the troubleshooting process of a software system mainly comprises the following steps: after the client finds the abnormity, manually capturing a screen and retaining the evidence; then, dialing a manual customer service for feedback, providing personal information for the manual customer service, and waiting for the customer service personnel to report to a developer for investigation; then, the developer positions the problem and makes a repair plan and feeds the repair plan back to the customer service staff, and the customer service staff informs the customer and informs the customer of the repair plan secondarily after the repair is formally carried out. Therefore, the time for removing the obstacles is long, the overall working efficiency is difficult to improve, and the customer satisfaction is also influenced.
Disclosure of Invention
The technical problem mainly solved by the application is to provide a fault removing method, equipment and a storage medium of a software system, and the fault removing efficiency and accuracy can be improved.
In order to solve the technical problem, the application adopts a technical scheme that: provided is a troubleshooting method of a software system, including: responding to screen capturing operation of a user at the front end, and adding a unique identifier for a screen capturing picture; responding to a fault removal request provided by a user based on a screen capture picture, and acquiring a unique identifier from the screen capture picture; and performing obstacle removing processing based on the unique identifier.
Responding to the screen capture operation of a user at the front end, and adding a unique identifier for the screen capture picture comprises the following steps: generating a watermark by using the unique identifier; and adding the watermark to a specified area of the screenshot picture.
Wherein, the unique identification comprises the user identification of the user; the step of fault elimination processing based on the unique identification comprises the following steps: and inquiring the log and/or interface request corresponding to the user from the recorded log and/or interface request based on the unique identification.
The recorded log and/or interface request comprises a log and/or interface request recorded by a front end and a log and/or interface request recorded by a back end; the step of performing troubleshooting based on the unique identifier further comprises: and correlating the log and/or the interface request recorded at the front end and the log and/or the interface request recorded at the back end corresponding to the user according to respective timestamps.
Wherein, in response to the screen capture operation of the user at the front end, before adding the unique identifier for the screen capture picture, the method comprises the following steps: generating a unique identifier in response to a session generation operation of a user at a front end; the log and/or interface request generated by the session presence process is associated with a unique identification.
Wherein, the unique identifier further comprises a session identifier for distinguishing different sessions; the step of performing troubleshooting based on the unique identifier further comprises: and inquiring the log and/or the interface request of the target session corresponding to the screenshot picture from the recorded log and/or interface request based on the unique identification.
Wherein the session identifier is a session establishment time.
The method for removing the fault based on the unique identifier comprises the following steps: and inquiring logs and/or interface requests of other sessions meeting preset time requirements with the target session from the recorded logs and/or interface requests based on the session establishment time.
And the other sessions are sessions with the establishment time earlier than the target session and the time interval less than or equal to the preset time threshold.
In order to solve the above technical problem, another technical solution adopted by the present application is: the fault removing device of the software system comprises a storage and a processor, wherein the storage stores program instructions, and the processor is used for executing the program instructions to realize the fault removing method of the software system.
In order to solve the above technical problem, another technical solution adopted by the present application is: there is provided a computer readable storage medium for storing program instructions executable to implement the method of troubleshooting the software system described above.
In the above embodiment, the obstacle elimination processing is performed based on the unique identifier acquired from the screen shot picture. On one hand, the unique identification of the current full-flow log of the user can be locked through the unique identification obtained from the screen capture picture, and the fault elimination query of the full-link log is opened, so that the fault problem is accurately positioned, the possibility of erroneous judgment and misjudgment is avoided, and the fault elimination accuracy is improved; on the other hand, the fault removing process is simple and short in time consumption, namely the fault removing timeliness is higher, and the situations of secondary customer complaints and customer loss of a user are reduced; in addition, only the user needs to provide the screen capture picture when the front end is abnormal and cannot operate normally, and the experience of the user is improved.
Drawings
FIG. 1 is a schematic flow chart diagram illustrating an embodiment of a troubleshooting method for a software system provided herein;
FIG. 2 is a schematic flow chart diagram illustrating one embodiment of associating unique identifiers with a log and/or interface request provided herein;
FIG. 3 is a flowchart illustrating an embodiment of step S11 shown in FIG. 1;
FIG. 4 is a schematic block diagram of an embodiment of a fault clearance device of the software system provided herein;
FIG. 5 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present application.
Detailed Description
The embodiments of the present application will be described in detail below with reference to the drawings.
In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular system structures, interfaces, techniques, etc. in order to provide a thorough understanding of the present application.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship. Further, the term "plurality" herein means two or more than two. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating an embodiment of a troubleshooting method of a software system provided in the present application. It should be noted that the embodiment of the present application is not limited to the flow sequence shown in fig. 1 if substantially the same result is obtained. As shown in fig. 1, the present embodiment includes:
step S11: and responding to the screen capture operation of the user at the front end, and adding a unique identifier for the screen capture picture.
The method is used for carrying out fault removal processing on the software system. Wherein, from the user's perspective, the software system can be regarded as the interface of the user and the computer, make the user use the computer conveniently through the order or menu that the operation software system provides; from the perspective of resource management, the software system is a manager of computer system resources, and has the main functions and purposes of improving the utilization rate of system resources, improving a friendly user interface and creating a good working environment, so that a user can flexibly and conveniently use a computer, and the whole computer system can efficiently run.
When the user finds abnormality at the front end and cannot normally operate, the user is used to manually screen capture and leave a certificate, and then problem feedback is carried out on customer service personnel corresponding to the software system. Therefore, in the embodiment, in response to the screen capturing operation of the user at the front end, the unique identifier is added to the screen capturing picture, so that a developer of a subsequent software system can perform fault removing processing according to the unique identifier added to the screen capturing picture, so as to timely and accurately locate a fault problem, that is, the timeliness and the accuracy of fault removing are improved, and the possibility of misjudgment and misjudgment is reduced. In addition, the user continues to use the mode of the screen capturing feedback problem, and the experience of the user is improved.
In an embodiment, the unique identifier may be generated into a watermark, and then the generated watermark may be added to the screenshot picture to add the unique identifier to the screenshot picture. It is to be understood that in other embodiments, the unique identifier may also be added to the screenshot picture in other ways, which are not limited herein.
In order to facilitate subsequent troubleshooting based on the unique identifier, the log and/or the interface request generated by the user during the session of the front end needs to be marked with the unique identifier. Therefore, in an embodiment, as shown in fig. 2, fig. 2 is a schematic flowchart of an example of associating a unique identifier with a log and/or an interface request provided in the present application, and before adding a unique identifier to a screenshot picture in response to a screenshot operation of a user at a front end, the method specifically includes the following sub-steps:
step S21: the unique identifier is generated in response to a session generation operation by a user at the front end.
In this embodiment, the unique identifier is generated in response to a session generation operation of the user at the front end. Specifically, when a user enters a software system or H5 page, a unique identification is generated in response to the user entering the software system or H5 page.
In an embodiment, the unique identifier may include identification information such as a user identifier of the user (e.g., a client number, a name, an identification number, etc. of the user) or a session identifier that distinguishes different sessions (e.g., a session setup time, etc.). It is to be understood that, in other embodiments, the unique identifier may also include both a user identifier of the user and a session identifier for distinguishing different sessions, or the unique identifier may also include other identification information, which is not specifically limited herein. In a specific embodiment, the user identifier of the user or the session identifier that distinguishes different sessions, and other identification information may be directly used as the unique identifier. In consideration of protection of personal information of a user, in other specific embodiments, an encryption algorithm is used to encrypt identification information such as a user identifier of the user or session identifiers for distinguishing different sessions to generate a unique identifier, so that on one hand, a required unique identifier is generated, and on the other hand, the personal information of the user and the like are protected in an encryption manner, thereby avoiding leakage of the user information. In order to further improve the confidentiality of personal information of a user, in another embodiment, identification information such as a user identifier of the user or session identifiers for distinguishing different sessions and a random number are encrypted by an encryption algorithm to generate a unique identifier. The encryption algorithm is not limited, and can be specifically set according to actual use requirements. For example, a Data Encryption Standard (DES), an RSA Encryption Algorithm, or a Secure Hash Algorithm (SHA) and the like.
In an embodiment, after the unique identifier is generated, the unique identifier may be saved in the user session so that the unique identifier may be directly called for use later, so as to add the unique identifier to the screenshot picture, and the like.
Step S22: the log and/or interface request generated by the session presence process is associated with a unique identification.
In this embodiment, the log and/or the interface request generated by the session existence process are associated with the unique identifier, so as to mark the log and/or the interface request generated by the session existence process with an identification mark, that is, leave a trace of the unique identifier on the log and/or the interface request generated by the session existence process.
In an embodiment, after the unique identifier is generated, the unique identifier is stored in the user session, and in the process of the user session being valid, all log and/or interface requests are marked with the unique identifier, that is, the log and/or interface requests generated in the session existence process are associated with the unique identifier.
Step S12: and responding to a fault elimination request made by a user based on the screen capture picture, and acquiring the unique identifier from the screen capture picture.
In the embodiment, the unique identifier is acquired from the screen capture picture in response to a troubleshooting request provided by the user based on the screen capture picture. That is to say, when the user finds that the front end is abnormal, the abnormality can be fed back through the screen capture picture and a request for troubleshooting can be provided, at the moment, the unique identifier can be obtained from the screen capture picture in response to a troubleshooting request provided by the user based on the screen capture picture, so that a follow-up developer can lock the unique identifier of the current full-flow log of the user according to the unique identifier obtained from the screen capture picture, troubleshoot and inquire of the full-link log are put through, the fault problem can be timely and accurately positioned, and the timeliness and the accuracy of troubleshooting are improved.
Step S13: and performing obstacle removing processing based on the unique identifier.
In the present embodiment, the obstacle elimination processing is performed based on the unique identifier. That is to say, the uniqueness mark that obtains through following the screen capture picture can lock the uniqueness mark of user's full flow log at that time, makes through the troubleshooting inquiry of full link log to accurately and in time fix a position the trouble problem, improved the timeliness and the accuracy of troubleshooting. In the existing troubleshooting process, due to the conditions of low specialty, fuzzy description, privacy protection and the like, user feedback information collected by customer service personnel of a butt joint user often cannot directly hit key points, so that key information is lost, and therefore, developers cannot effectively and timely troubleshoot problems. Therefore, the fault removing processing is carried out based on the unique identification obtained from the screen capture picture, on one hand, the fault removing process is simple and easy, the consumed time is short, namely the timeliness of fault removing is higher, and the situations of secondary customer complaints and customer loss of a user are reduced; on the other hand, the uniqueness identification of the current full-flow log of the user can be locked through the uniqueness identification obtained from the screen capture picture, and fault elimination query of the full-link log is opened, so that the problem of faults is accurately positioned, the possibility of erroneous judgment and misjudgment is avoided, and the fault elimination accuracy is improved; in addition, only the user needs to provide the screen capture picture when the front end is abnormal and cannot operate normally, and the experience of the user is improved.
In one embodiment, the unique identifier includes a user identifier of the user, and the log and/or the interface request corresponding to the user can be queried from the recorded log and/or interface request according to the user identifier of the user. Since the log and/or the interface request generated in the session existence process are associated with the unique identifier, that is, since the log and/or the interface request generated in the session existence process are marked with the unique identifier, when the unique identifier comprises the user identifier of the user, all the log and/or the interface request generated in the session existence process are marked with the user identifier. Therefore, the log and/or the interface request with the user mark can be inquired from the recorded log and/or the interface request according to the user mark of the user, the log and/or the interface request with the user mark can be the log and/or the interface request corresponding to the user, namely the log and/or the interface request corresponding to the user can be inquired from the recorded log and/or the interface request according to the user mark of the user, so that the full-flow log corresponding to the user can be locked, the fault elimination inquiry of the full-link log is opened, the fault problem is accurately and timely positioned, and the timeliness and the accuracy of fault elimination are improved.
In a specific embodiment, the recorded log and/or interface request includes a front-end recorded log and/or interface request and a back-end recorded log and/or interface request, and the front-end recorded log and/or interface request and the back-end recorded log and/or interface request corresponding to the user may be associated according to respective timestamps. That is to say, the log and/or the interface request recorded at the front end corresponding to the user and the log and/or the interface request recorded at the back end of the same timestamp are associated, so that the log and/or the interface request recorded at the front end corresponding to the user and the log and/or the interface request recorded at the back end of the same timestamp can be compared and analyzed, and then the fault problem is determined according to the comparison and analysis result, that is, the fault problem is located. It is to be understood that, in other specific embodiments, the troubleshooting query on the full link log corresponding to the user may also be implemented in other manners, which is not limited herein.
Because the log and/or the interface request corresponding to the user may relate to a plurality of sessions, and the log and/or the interface request related to other sessions are not related to the screen capture picture obtained by the screen capture operation of the user at the front end, directly performing troubleshooting query on the log and/or the interface request corresponding to the user may affect troubleshooting efficiency, and lead to a situation that troubleshooting takes a long time. Therefore, in other embodiments, the unique identifier further includes a session identifier for distinguishing different sessions, that is, in this embodiment, the unique identifier includes a user identifier of the user and a session identifier for distinguishing different sessions, and a log and/or an interface request of a target session corresponding to the screenshot picture can be queried from the recorded log and/or interface request according to the user identifier of the user and the session identifier for distinguishing different sessions. Since the log and/or the interface request generated in the session existence process are associated with the unique identifier, that is, since all log and/or interface requests generated in the session existence process are marked with the unique identifier, when the unique identifier comprises the user identifier and the session identifier of the user, all log and/or interface requests generated in the session existence process are marked with the user identifier and the session identifier. Therefore, the log and/or the interface request with the user identification trace of the user and the session identification trace of the target session can be inquired from the recorded log and/or the interface request according to the user identification and the session identification trace of the user, the log and/or the interface request with the user identification trace and the session identification trace of the target session are the log and/or the interface request corresponding to the screenshot picture, namely the log and/or the interface request corresponding to the screenshot picture can be inquired from the recorded log and/or the interface request according to the user identification of the user, on one hand, the full-flow log of the user in the session process can be locked to get through the troubleshooting inquiry of the full-link log, the fault problem can be accurately and timely positioned, and the timeliness and the accuracy of troubleshooting are improved; on the other hand, the range of the log and/or the interface request of the fault-removing inquiry is narrowed, and the fault-removing efficiency is improved.
In one embodiment, the session to distinguish between different sessions is identified as the session setup time, which may be understood as the current system time when the user entered the software system or H5 page. It is to be understood that, in other specific embodiments, the session identifier for distinguishing between different sessions may also be other types of identification information, and is not limited in particular herein.
In one embodiment, the session identifier for distinguishing different sessions is a session establishment time, and logs and/or interface requests of other sessions meeting a preset time requirement with the target session can be inquired from the recorded logs and/or interface requests based on the session establishment time. That is, the log and/or the interface request of the target session and the log and/or the interface request of other sessions are compared and analyzed, and the fault reason is determined according to the comparison and analysis result, namely the fault problem is positioned.
The preset time requirement is not limited, and the preset time requirement can be specifically set according to actual use requirements. For example, the other sessions meeting the preset time requirement with the target session are sessions with the establishment time earlier than the target session and the time interval less than or equal to the preset time threshold. For example, the user successfully executes the operation a in the previous session, and the operation a cannot be executed due to the misoperation in the target session corresponding to the screenshot picture, so that the fault cause can be determined by comparing the log and/or the interface request of the previous session with the log and/or the interface request of the target session, that is, the precise positioning of the fault problem is realized. It can be understood that, in other specific embodiments, the troubleshooting query of the full link log of the target session corresponding to the screenshot picture may also be implemented in other manners, which is not limited specifically herein.
In the above embodiment, the obstacle elimination processing is performed based on the unique identifier acquired from the screen shot picture. On one hand, the unique identification of the current full-flow log of the user can be locked through the unique identification obtained from the screen capture picture, and the fault elimination query of the full-link log is opened, so that the fault problem is accurately positioned, the possibility of erroneous judgment and misjudgment is avoided, and the fault elimination accuracy is improved; on the other hand, the fault removing process is simple and short in time consumption, namely the fault removing timeliness is higher, and the situations of secondary customer complaints and customer loss of a user are reduced; in addition, only the user needs to provide the screenshot picture when the front end is abnormal and cannot operate normally, and the experience of the user is improved.
Referring to fig. 3, fig. 3 is a flowchart illustrating an embodiment of step S11 shown in fig. 1. It should be noted that the embodiment of the present application is not limited to the flow sequence shown in fig. 3 if substantially the same result is obtained. As shown in fig. 3, the present embodiment includes:
step S111: a watermark is generated using the unique identifier.
In this embodiment, a watermark is generated using a unique identifier. That is to say, when the user finds that the front end is abnormal and cannot normally operate, the user performs the screen capturing operation, and at this time, in response to the screen capturing operation of the user at the front end, the unique identifier is used for generating the watermark, so that the unique identifier watermark is printed on the screen capturing picture and the unique identifier is added to the screen capturing picture.
Step S112: and adding the watermark to a specified area of the screenshot picture.
In the embodiment, the watermark generated by using the unique identifier is added to the designated area of the screenshot picture, so that the unique identifier watermark is automatically printed on the screenshot picture, and the unique identifier is added to the screenshot picture.
The designated area of the screenshot picture is not limited, and the screenshot picture can be specifically set according to actual use requirements. For example, the designated area of the screenshot picture is the lower right corner area of the screenshot picture; for another example, the designated area of the screenshot picture is the upper left corner area of the screenshot picture; for another example, the designated area of the screenshot is the center area of the screenshot.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an embodiment of a troubleshooting apparatus of a software system provided in the present application. The obstacle deflector 40 of the software system includes a memory 41 and a processor 42 coupled to each other, and the processor 42 is configured to execute program instructions stored in the memory 41 to implement the steps of any one of the above-described obstacle deflecting method embodiments of the software system. In one particular implementation scenario, the troubleshooting device 40 of the software system may include, but is not limited to: the microcomputer, the server, and in addition, the troubleshooting device 40 of the software system may further include a mobile device such as a notebook computer, a tablet computer, and the like, which is not limited herein.
In particular, the processor 42 is configured to control itself and the memory 41 to implement the steps of any of the above-described embodiments of the troubleshooting method of the software system. Processor 42 may also be referred to as a CPU (Central Processing Unit). The processor 42 may be an integrated circuit chip having signal processing capabilities. The Processor 42 may also be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. In addition, the processor 42 may be commonly implemented by an integrated circuit chip.
Referring to fig. 5, fig. 5 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present application. The computer readable storage medium 50 of the embodiments of the present application stores program instructions 51, and the program instructions 51, when executed, implement the methods provided by any of the embodiments of the troubleshooting method of the software system of the present application and any non-conflicting combinations. The program instructions 51 may form a program file stored in the computer-readable storage medium 50 in the form of a software product, so as to enable a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods according to the embodiments of the present application. And the aforementioned computer-readable storage medium 50 includes: various media capable of storing program codes, such as a usb disk, a portable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, or terminal devices such as a computer, a server, a mobile phone, and a tablet. If the technical scheme of the application relates to personal information, a product applying the technical scheme of the application clearly informs personal information processing rules before processing the personal information, and obtains personal independent consent.
If the technical scheme of the application relates to sensitive personal information, a product applying the technical scheme of the application obtains individual consent before processing the sensitive personal information, and simultaneously meets the requirement of 'express consent'. For example, at a personal information collection device such as a camera, a clear and significant identifier is set to inform that the personal information collection range is entered, the personal information is collected, and if the person voluntarily enters the collection range, the person is considered as agreeing to collect the personal information; or on the device for processing the personal information, under the condition of informing the personal information processing rule by using obvious identification/information, obtaining personal authorization by modes of popping window information or asking a person to upload personal information of the person by himself, and the like; the personal information processing rule may include information such as a personal information processor, a personal information processing purpose, a processing method, and a type of personal information to be processed.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (11)
1. A method of troubleshooting a software system, the method comprising:
responding to screen capturing operation of a user at the front end, and adding a unique identifier for a screen capturing picture;
acquiring the unique identifier from the screen capture picture in response to a troubleshooting request made by the user based on the screen capture picture;
and carrying out obstacle elimination processing based on the unique identifier.
2. The method according to claim 1, wherein the step of adding a unique identifier to the screenshot picture in response to the screenshot operation of the user at the front end comprises:
generating a watermark by using the unique identifier;
and adding the watermark to a specified area of the screenshot picture.
3. The method of claim 1, wherein the unique identifier comprises a user identifier of the user;
the step of performing obstacle clearance processing based on the unique identifier comprises the following steps:
and inquiring the log and/or interface request corresponding to the user from the recorded log and/or interface request based on the unique identification.
4. The method of claim 3, wherein the logged log and/or interface requests comprise a front-end logged log and/or interface request and a back-end logged log and/or interface request;
the step of performing obstacle clearance processing based on the unique identifier further comprises:
and associating the front-end recorded log and/or interface request corresponding to the user with the back-end recorded log and/or interface request according to respective timestamps.
5. The method according to claim 3, wherein the adding of the unique identifier to the screenshot picture in response to the screenshot operation of the user at the front end comprises:
generating the unique identification in response to a session generation operation of the user at a front end;
and associating the log and/or the interface request generated by the session existence process with the unique identification.
6. The method of claim 5, wherein the unique identifier further comprises a session identifier for distinguishing between different sessions;
the step of performing obstacle clearance processing based on the unique identifier further comprises:
and inquiring the log and/or interface request of the target session corresponding to the screenshot picture from the recorded log and/or interface request based on the unique identification.
7. The method of claim 6, wherein the session identifier is a session setup time.
8. The method of claim 7, wherein the step of troubleshooting based on the unique identifier comprises:
and inquiring logs and/or interface requests of other sessions meeting preset time requirements with the target session from the recorded logs and/or interface requests based on the session establishment time.
9. The method of claim 8, wherein the other sessions are sessions that are established earlier in time than the target session and have a time interval less than or equal to a preset time threshold.
10. A troubleshooting apparatus for a software system characterized in that the troubleshooting apparatus for a software system comprises a memory storing program instructions and a processor for executing the program instructions to implement a troubleshooting method of the software system as recited in any one of claims 1 to 9.
11. A computer-readable storage medium for storing program instructions executable to implement a method of troubleshooting the software system as recited in any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210734033.3A CN115061890A (en) | 2022-06-25 | 2022-06-25 | Troubleshooting method and equipment for software system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210734033.3A CN115061890A (en) | 2022-06-25 | 2022-06-25 | Troubleshooting method and equipment for software system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115061890A true CN115061890A (en) | 2022-09-16 |
Family
ID=83201549
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210734033.3A Pending CN115061890A (en) | 2022-06-25 | 2022-06-25 | Troubleshooting method and equipment for software system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115061890A (en) |
-
2022
- 2022-06-25 CN CN202210734033.3A patent/CN115061890A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110647438B (en) | Event monitoring method and device, computer equipment and storage medium | |
| CN107678869B (en) | Client abnormity positioning method and device, computer equipment and storage medium | |
| KR101883400B1 (en) | detecting methods and systems of security vulnerability using agentless | |
| CN107451040B (en) | Method and device for positioning fault reason and computer readable storage medium | |
| EP3013086A1 (en) | Method, apparatus and electronic device for connection management | |
| CN112631913B (en) | Method, device, equipment and storage medium for monitoring operation faults of application program | |
| CN110164101B (en) | Alarm information processing method and equipment | |
| CN111614696B (en) | Network security emergency response method and system based on knowledge graph | |
| US7647530B2 (en) | Network fault pattern analyzer | |
| CN104937605A (en) | Attack analysis system, coordination device, attack analysis coordination method, and program | |
| CN111930882A (en) | Server abnormity tracing method, system and storage medium | |
| US10341182B2 (en) | Method and system for detecting network upgrades | |
| CN114077525A (en) | Abnormal log processing method and device, terminal equipment, cloud server and system | |
| CN113360475B (en) | Data operation and maintenance method, device and equipment based on intranet terminal and storage medium | |
| CN110442582B (en) | Scene detection method, device, equipment and medium | |
| CN112491883A (en) | Method, device, electronic device and storage medium for detecting web attack | |
| CN114139178A (en) | Data link-based data security monitoring method and device and computer equipment | |
| CN116089205A (en) | Automatic operation and maintenance management method, device, server and storage medium | |
| CN113163012B (en) | Internet of things equipment management method and device based on block chain | |
| TW201931186A (en) | Identity recognition method, apparatus and system | |
| CN115061890A (en) | Troubleshooting method and equipment for software system and storage medium | |
| US9756078B2 (en) | Proactive internet connectivity probe generator | |
| CN115511368A (en) | Method, device, equipment, medium and power grid management platform for generating operation ticket of electric system | |
| CN112291113A (en) | Port bandwidth auditing method and device | |
| CN113296831B (en) | Application identifier extraction method and device, computer equipment and storage medium |
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 |