CN110377444B - Fault alarm method, device, electronic equipment and computer readable storage medium - Google Patents
Fault alarm method, device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN110377444B CN110377444B CN201910562452.1A CN201910562452A CN110377444B CN 110377444 B CN110377444 B CN 110377444B CN 201910562452 A CN201910562452 A CN 201910562452A CN 110377444 B CN110377444 B CN 110377444B
- Authority
- CN
- China
- Prior art keywords
- fault alarm
- fault
- screenshot
- received
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a fault alarm method, a device, an electronic device and a computer readable storage medium, wherein the method comprises the following steps: detecting whether a fault alarm operation is received; if a fault alarm operation is received, acquiring a screenshot corresponding to the fault alarm operation, and acquiring historical operation information of an application program before the screenshot is displayed; and reporting the screenshot and the historical operation information as fault record information. When a fault alarm exists, the technical scheme provided by the invention not only uploads the interface screenshot, but also uploads the historical operation information of the user together, so that the operation of the user in the fault reporting process is reduced, and a service provider can conveniently and accurately find the fault and solve the problem.
Description
Technical Field
The embodiment of the invention relates to the technical field of fault alarm, in particular to a fault alarm method, a device, electronic equipment and a computer readable storage medium.
Background
Many clients have a fault alarm function at present. And the user reports the faults found in the using process to the service provider through a fault alarm function, so that the service provider can find and solve the faults in time.
However, the existing fault alarm function is complicated in use, requires a series of operations of a user, and is poor in user experience. And after the user reports the fault, the service provider cannot find the position of the problem in time due to limited information quantity reported, so that the difficulty of fault solution is increased.
The above description of the process of finding a problem is merely for aiding in understanding the technical solution of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
To solve the above technical problems or at least partially solve the above technical problems, embodiments of the present invention provide a fault alarm method, a fault alarm device, an electronic device, and a computer readable storage medium.
According to a first aspect of an embodiment of the present disclosure, there is provided a fault alerting method, including:
detecting whether a fault alarm operation is received;
if a fault alarm operation is received, acquiring a screenshot corresponding to the fault alarm operation, and acquiring historical operation information of an application program before the screenshot is displayed;
and reporting the screenshot and the historical operation information as fault record information.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the detecting whether a fault alarm operation is received includes:
detecting whether a screenshot is saved;
if the screenshot is detected to be saved, generating a fault alarm button in the current application program interface;
detecting whether a triggering operation of the fault alarm button is received or not;
and if the triggering operation is received, judging that the fault alarm operation is received.
With reference to the first aspect, in a second possible implementation manner of the first aspect, the detecting whether a fault alarm operation is received further includes:
detecting whether a triggering operation of a quick fault alarm button is received or not; the quick fault alarm button is generated on any interface of the application program;
and if the triggering operation is received, judging that the fault alarm operation is received.
With reference to the first aspect, in a third possible implementation manner of the first aspect, the historical operation information includes: operation path information and request response information.
According to a second aspect of embodiments of the present disclosure, there is provided a fault alerting device, comprising:
the detection module is used for detecting whether a fault alarm operation is received or not;
the acquisition module is used for acquiring a screenshot corresponding to the fault alarm operation when the fault alarm operation is received and acquiring historical operation information of an application program before the screenshot is displayed;
and the fault alarm module is used for reporting the screenshot and the historical operation information as fault record information.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the detection module includes:
the first detection submodule is used for detecting whether a screenshot is stored or not;
the second detection sub-module is used for generating a fault alarm button in the current application program interface if the screenshot is detected to be saved;
the third detection sub-module is used for detecting whether the triggering operation of the fault alarm button is received or not;
and the first judging submodule is used for judging that the fault alarm operation is received if the trigger operation is received.
With reference to the second aspect, in a second possible implementation manner of the second aspect, the detection module further includes:
the fourth detection sub-module is used for detecting whether triggering operation of the quick fault alarm button is received or not; the quick fault alarm button is generated on any interface of the application program;
and the second judging sub-module is used for judging that the fault alarm operation is received if the trigger operation is received.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
and a processor for implementing any of the above-described method steps when executing a program stored on the memory.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a malfunction alerting method program that when executed by a processor implements the steps of any of the malfunction alerting methods described above.
Compared with the closest prior art, the embodiment of the invention firstly detects whether the fault alarm operation is received, if the fault alarm operation is received, the screenshot corresponding to the fault alarm operation is obtained, the historical operation information of the application program before the screenshot is displayed is obtained, and finally the screenshot and the historical operation information are reported as fault record information. When a fault alarm exists, the scheme not only uploads the interface screenshot, but also uploads the historical operation information of the user together, so that the operation of the user in the fault reporting process is reduced, and a service provider can find the fault more accurately and solve the problem conveniently.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart illustrating a fault alerting method according to an exemplary embodiment;
FIG. 2 is a schematic diagram of a scenario illustrated according to an example embodiment;
FIG. 3 is a flowchart illustrating a method of detecting whether a fault alert operation is received in an interface of an application, according to an exemplary embodiment;
FIG. 4 is a flowchart illustrating another method of detecting whether a fault alert operation is received in an interface of an application, according to an exemplary embodiment;
FIG. 5 is a schematic diagram of a fault alerting device shown in accordance with an exemplary embodiment;
fig. 6 is a schematic diagram of an electronic device according to an exemplary embodiment.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
A mobile client implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present invention, and are not of specific significance per se. Thus, "module" and "component" may be used in combination.
The main body of execution of each step of the present disclosure is a client, which may be a client on a terminal device. The terminal device may be a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palm top computer, a PAD (Personal Digital Assistant ), a PMP (Portable Media Player, portable multimedia player), a navigation apparatus, etc., a stationary terminal such as a digital TV, a desktop computer, etc.
When a user operates or browses an application program or a web page to find a fault, reporting the fault by using an existing fault alarm method is complicated, and because the reported information amount is limited, a service provider cannot find a problem in time, aiming at the problem, an exemplary embodiment of the present disclosure shows a fault alarm method to implement fast reporting of the fault, and facilitate the service provider to find the fault and solve the problem more accurately, as shown in fig. 1, the fault alarm method may include the following steps:
in step S101, it is detected whether a failure alarm operation is received.
Taking a certain application program on a mobile phone as an example, fig. 2 is a schematic view of a scenario shown in an exemplary embodiment of the present disclosure, where the scenario includes: a fault alarm button 1 and an application interface 2.
When a user opens a certain application program, a screenshot is carried out in an application program interface 2 of the application program in a certain screenshot mode, after the screenshot is completed, the screenshot is stored, when the client detects that the screenshot is stored, a fault alarm button 1 is generated on the current application program interface 2, and the user can carry out fault alarm operation by clicking the button.
The screenshot can be performed by pressing a volume key and a power key simultaneously, can be performed by sliding a screen by multiple fingers, and can be performed by other screenshot modes.
The storage path of the screenshot can be a storage path fixed by the application program or a storage path selected by the user. While the save path may be read by the client.
In addition, fig. 2 is only a schematic diagram of the present disclosure, and the position of the fault alarm button 1 in the drawing may be changed according to actual situations, and is not limited specifically. The malfunction alerting button 1 may be a hover button, the position of which may be changed manually.
In the embodiment of the present disclosure, when the fail-alarm button 1 is triggered, a fail-alarm operation is generated. Therefore, in this step, the client detects whether a malfunction alerting operation is received by listening to the system event.
In one possible embodiment of the disclosure, as shown in fig. 3, the detecting whether a fault alarm operation is received specifically includes:
s111, detecting whether a screenshot is saved.
In the embodiment of the disclosure, the client detects the saved path information of the screenshot in real time, and the path may be a saved path inherent to the application program or other saved paths authorized by the application program. When a new screenshot is detected in the path, the operation of step S112 is performed.
And S112, if the screenshot is detected to be saved, generating a fault alarm button in the current application program interface.
In the embodiment of the disclosure, when the client detects that a new screenshot is saved in the saving path, a fault alarm button 1 is generated in the application program interface where the current system stays.
S113, detecting whether a triggering operation of the fault alarm button is received.
In the embodiment of the disclosure, when the client detects that a new screenshot is saved, a fault alarm button 1 is generated in an application program interface where the system stays, and the client further detects whether a trigger operation of the fault alarm button 1 exists. The triggering operation may be a clicking operation, a double-clicking operation, or other operations that may cause the fault alarm button 1 to perform fault alarm. When the client detects any of the above-described trigger operations of the malfunction alerting button 1, the operation of step S114 is performed.
And S114, if the triggering operation is received, judging that the fault alarm operation is received.
In the embodiment of the present disclosure, when the client detects the trigger operation of the fault alarm button 1 by the user, it is determined that the fault alarm operation is received.
That is, the user performs screenshot after finding a fault, then saves the picture, and when the client detects that the screenshot is saved, generates a fault alarm button in the application program interface where the current system stays. When the user clicks the fault alarm button, the user is prompted to confirm whether the picture to be uploaded is the screenshot picture. If the user confirms that the screenshot is the screenshot picture, the client side uploads the screenshot and operation path information related to the screenshot to the server.
The location of the picture save may be a default save path or any save path selected by the user, but the save paths are all readable by the client.
In another possible embodiment of the present disclosure, as shown in fig. 4, the detecting whether a fault alarm operation is received specifically includes:
s121, detecting whether triggering operation of a quick fault alarm button is received or not; the shortcut fault alarm button is generated at any interface of the application program.
Before detecting whether the triggering operation of the quick fault alarm button is received, the method can further comprise: and detecting whether the application program interface comprises a shortcut fault alarm button.
In the embodiment of the disclosure, the client detects whether a shortcut fault alarm button related to fault alarm exists in a current interface of an application program, and the current page can be directly subjected to screenshot through the shortcut fault alarm button and then fault alarm is carried out. That is, the interface where the fault is found is subjected to screenshot before the fault is reported, that is, the fault is determined to be reported first, and then the screenshot operation is performed.
The shortcut fault alarm button is generated by an application program, and is dynamically generated on an interface browsed by a user when the user browses the interface. That is, the quick fault alarm button is arranged on each interface, and when the user finds that the currently browsed interface is wrong, the user can directly click the quick fault alarm button to report the fault, so that the user can report the fault conveniently.
The shortcut malfunction button may be a hover button whose position may be changed manually by a user.
When detecting that the current application interface contains the rapid fault alarm button, the client side can continuously detect whether the triggering operation of the button is performed, wherein the triggering operation can be clicking operation, double clicking operation or other operations capable of enabling the rapid fault alarm button to perform fault alarm. When the client detects any triggering operation of the quick fault alarm button, the operation of step S122 is performed.
S122, if the triggering operation is received, judging that the fault alarm operation is received.
When a fault alarm operation is received, in step 102, a screenshot corresponding to the fault alarm operation is obtained, and historical operation information of an application program before the screenshot is displayed is obtained.
As shown in fig. 2, after the fault alarm button 1 is triggered, the client receives the fault alarm operation, and then obtains a screenshot corresponding to the fault alarm operation, and also obtains historical operation information of all operations of the user on the application program after the application program is opened before the interface is currently displayed.
Wherein the history operation information includes operation path information and request response information.
In one possible implementation manner of the present disclosure, the acquiring the historical operation information of the application program before the screenshot shows specifically includes:
recording the application program and external data call request, response information and operation information for operating an interface of the application program;
request response information corresponding to the data call request and operation path information corresponding to the operation information are obtained.
In another possible embodiment of the present disclosure, acquiring the historical operation information of the application program before the screenshot shows further includes:
storing request response information and/or operation path information in a preset storage space according to time sequence;
detecting whether the residual space of the preset storage space is smaller than a preset value;
and if the residual space of the preset storage space is smaller than a preset value, covering the request response information and/or the operation path information stored in the preset storage space from first to last according to the storage time sequence of the request response information and/or the operation path information.
In the disclosed embodiment, the storage space is not infinite, and has a predetermined value, and when the predetermined value is exceeded, the storage space is covered by the head, that is, if the storage space can store 100 pieces of information, when 101 pieces of information exist, the 101 th piece of information covers the 1 st piece of information, then the 102 th piece of information covers the 2 nd piece of information, and so on.
Specifically, when the user operates the application program, the client records the operation path of the user, and the operation path is sequentially stored in the running memory or other places.
For the record of the operation path, there is a record specification of the relevant operation path, so that the service provider can restore the actual operation path to reproduce the fault according to the operation path information recorded by the client. Different application programs have different operation path specifications, and corresponding operation path specifications are determined according to specific application programs. The present disclosure takes an operation path specification page-card-block-action of an application program as an example, and is specifically described below.
pages are pages that must uniquely identify the current page;
the card is a card, and must be able to uniquely identify the card within the current page;
the block is a block which can uniquely identify the block in the current card;
an action is an action, such as inputting, clicking, sliding, pulling, etc., which must uniquely identify the user's operation.
When clicking a block, the operation path information of the block is recorded.
For example: the vipdome-gueyoulike-block 2-click, where vipdome represents vip pick page, guestroll represents you like card, block2 represents the second block, click represents click, vipdome-gueyoulike-block 2-click represents the second block of you like card clicked on vip pick page.
When the client requests the background interface, the interface and the return value which are called each time are sequentially stored in the running memory.
The user operation path information and the request response information are recorded by a table, each editing a reference number, and then recorded one by one into the table, but the table is not infinitely recorded, but only a predetermined number of pieces of information can be recorded, for example, N pieces of information can be recorded by default, and if N pieces are exceeded, N is set in version by the client from the head. For example, the memory space can store 100 pieces of information, when there is 101 pieces of information, 101 pieces of information will overwrite 1 piece of information, then 102 pieces of information overwrite 2 pieces of information, and so on. In this case, in order to facilitate the service provider to know the order of operations or requests, the recorded operation path information and request response information should be provided with an information sequence number.
The request response information includes request information and response information.
The request information comprises information such as request links, request types, request message heads, request message bodies and the like.
The response information includes information such as a response code, a response message body, and the like.
In step S103, the screenshot and the historical operation information are reported as fault record information.
When the interface screenshot of the application program and the operation information corresponding to the screenshot are acquired, the client side can upload the acquired screenshot and the operation path information and/or the request response information to the server.
In another possible embodiment of the present disclosure, the step specifically includes:
compressing the screenshot and the historical operation information;
and reporting the compressed information as fault record information.
That is, in order to save space, the transmission speed is made faster, and the acquired screenshot and information are compressed first and then transmitted to the server.
Based on the same inventive concept as the above method, in another embodiment of the present disclosure, a fault alarm device is also disclosed, as shown in fig. 5, including: a detection module 101, an acquisition module 102 and a fault alarm module 103.
The detection module 101 is configured to detect whether a failure alarm operation is received;
the acquiring module 102 is configured to acquire a screenshot corresponding to a fault alarm operation when the fault alarm operation is received, and acquire historical operation information of an application program before the screenshot is displayed;
the fault alert module 103 is configured to report the screenshot and the historical operating information as fault log information.
In another embodiment of the present disclosure, the detection module includes: the device comprises a first detection sub-module, a second detection sub-module, a third detection sub-module and a first judgment sub-module.
The first detection module is configured to detect whether a screenshot is saved;
the second detection module is configured to generate a fault alarm button in the current application program interface if the screenshot is detected to be saved;
the third detection module is configured to detect whether a triggering operation of the fault alarm button is received; the quick fault alarm button is generated on any interface of the application program;
the first determination submodule is configured to determine that a fault alarm operation is received if the trigger operation is received.
In another embodiment of the present disclosure, the detection module further comprises: the fourth detection sub-module and the second judgment sub-module.
The fourth detection sub-module is configured to detect whether a triggering operation of the quick fault alarm button is received; the shortcut fault alarm button is generated at any interface of the application program.
The second determination submodule is configured to determine that a fault alarm operation is received if the trigger operation is received.
In another embodiment of the present disclosure, the acquiring module includes: the system comprises a first recording sub-module and a first acquisition sub-module.
The first recording submodule is configured to record the application program and an external data call request;
the first acquisition module is configured to acquire request response information corresponding to the data call request.
In another embodiment of the present disclosure, the acquiring module further includes: the system comprises a second recording sub-module and a second acquisition sub-module.
The second recording sub-module is configured to record operation information for operating the application program;
the second acquisition sub-module is configured to acquire operation path information corresponding to the operation information.
In another embodiment of the present disclosure, the acquiring module further includes: the device comprises a storage sub-module, a fifth detection sub-module and an execution sub-module.
The storage sub-module is configured to store request response information and operation path information in a preset storage space according to time sequence;
the fifth detection submodule is configured to detect whether the residual space of the preset storage space is smaller than a preset value;
the execution sub-module is configured to cover the request response information and/or the operation path information stored in the preset storage space from first to last according to the storage time sequence of the request response information and/or the operation path information if the remaining space of the preset storage space is smaller than a preset value.
In another embodiment of the present disclosure, the fault alert module includes: the compression sub-module and the fault alarm sub-module.
The compression sub-module is configured to compress the screenshot and the historical operating information;
the fault alarm sub-module is configured to report the compressed information as fault record information.
In another embodiment of the present disclosure, there is also provided an electronic device, as shown in fig. 6, including a processor 501, a communication interface 502, a memory 503, and a communication bus 504, where the processor 501, the communication interface 502, and the memory 503 complete communication with each other through the communication bus 504;
a memory 503 for storing a computer program;
the processor 501 is configured to execute the program stored in the memory 503, and implement the following steps:
detecting whether a fault alarm operation is received;
if a fault alarm operation is received, acquiring a screenshot corresponding to the fault alarm operation, and acquiring historical operation information of an application program before the screenshot is displayed;
and reporting the screenshot and the historical operation information as fault record information.
The communication bus 504 mentioned above for the electronic device may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The communication bus 504 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 5, but not only one bus or one type of bus.
The communication interface 502 is used for communication between the electronic device and other devices described above.
The memory 503 may include a random access memory (Random Access Memory, simply referred to as RAM) or may include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor 501 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In another embodiment of the present application, there is further provided a computer readable storage medium, where a fault alert method program is stored on the computer readable storage medium, and when the fault alert method program is executed by a processor, the steps of any one of the above fault alert methods are implemented.
When the embodiment of the invention is specifically implemented, the above embodiments can be referred to, and the invention has corresponding technical effects.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processors (Digital Signal Processing, DSP), digital signal processing devices (DSP devices, DSPD), programmable logic devices (Programmable Logic Device, PLD), field programmable gate arrays (Field-Programmable Gate Array, FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.
For a software implementation, the techniques described herein may be implemented by means of units that perform the functions described herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in essence or a part contributing to the prior art or 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 method described in the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
From the foregoing description of the embodiments, it will be apparent to those skilled in the art that the methods described in the various embodiments of the present invention may be implemented by means of software plus necessary general purpose hardware platforms, or of course by means of hardware, although in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a client device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention or the method according to some parts of the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (4)
1. A fault alerting method, comprising:
detecting whether a fault alarm operation is received;
if a fault alarm operation is received, acquiring a screenshot corresponding to the fault alarm operation, and acquiring historical operation information of an application program before the screenshot is displayed, wherein the historical operation information comprises: operation path information and request response information;
reporting the screenshot and the historical operation information as fault record information;
the detecting whether a fault alarm operation is received includes:
detecting whether a triggering operation of a quick fault alarm button is received or not; the quick fault alarm button is generated on any interface of the application program;
if the triggering operation is received, the current page is subjected to screenshot, then fault alarm is carried out, and at the moment, the fault alarm operation is judged to be received.
2. A fault warning device, comprising:
the detection module is used for detecting whether a fault alarm operation is received or not;
the acquisition module is used for acquiring a screenshot corresponding to the fault alarm operation when the fault alarm operation is received and acquiring historical operation information of an application program before the screenshot is displayed, wherein the historical operation information comprises: operation path information and request response information;
the fault alarm module is used for reporting the screenshot and the historical operation information as fault record information;
the detection module comprises:
the fourth detection sub-module is used for detecting whether triggering operation of the quick fault alarm button is received or not; the quick fault alarm button is generated on any interface of the application program;
and the second judging submodule is used for carrying out screenshot on the current page if the triggering operation is received, then carrying out fault alarm, and judging that the fault alarm operation is received.
3. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
a processor for implementing the steps of the fault alerting method of claim 1 when executing a program stored on a memory.
4. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a malfunction alerting method program, which when executed by a processor, implements the steps of the malfunction alerting method of claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910562452.1A CN110377444B (en) | 2019-06-26 | 2019-06-26 | Fault alarm method, device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910562452.1A CN110377444B (en) | 2019-06-26 | 2019-06-26 | Fault alarm method, device, electronic equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110377444A CN110377444A (en) | 2019-10-25 |
| CN110377444B true CN110377444B (en) | 2023-06-30 |
Family
ID=68249424
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910562452.1A Active CN110377444B (en) | 2019-06-26 | 2019-06-26 | Fault alarm method, device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110377444B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111240878A (en) * | 2020-01-08 | 2020-06-05 | 北京奇艺世纪科技有限公司 | Fault reporting positioning method, electronic equipment and computer readable storage medium |
| CN113127250B (en) * | 2021-04-28 | 2023-09-01 | 北京奇艺世纪科技有限公司 | Fault reporting method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107247637A (en) * | 2017-07-27 | 2017-10-13 | 广州云测信息技术有限公司 | A kind of APP fault determination methods and device |
| WO2018203848A2 (en) * | 2016-12-23 | 2018-11-08 | Turkcell Teknoloji̇ Araştirma Ve Geli̇şti̇rme Anoni̇m Şi̇rketi̇ | A system displaying near real-time quality tendency and generating alarm |
| CN108924029A (en) * | 2018-04-11 | 2018-11-30 | 阿里巴巴集团控股有限公司 | A kind of method and device that customer service data are sent |
| CN109376071A (en) * | 2018-09-03 | 2019-02-22 | 平安普惠企业管理有限公司 | Application software exception feedback method, device, computer equipment and storage medium |
-
2019
- 2019-06-26 CN CN201910562452.1A patent/CN110377444B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018203848A2 (en) * | 2016-12-23 | 2018-11-08 | Turkcell Teknoloji̇ Araştirma Ve Geli̇şti̇rme Anoni̇m Şi̇rketi̇ | A system displaying near real-time quality tendency and generating alarm |
| CN107247637A (en) * | 2017-07-27 | 2017-10-13 | 广州云测信息技术有限公司 | A kind of APP fault determination methods and device |
| CN108924029A (en) * | 2018-04-11 | 2018-11-30 | 阿里巴巴集团控股有限公司 | A kind of method and device that customer service data are sent |
| CN109376071A (en) * | 2018-09-03 | 2019-02-22 | 平安普惠企业管理有限公司 | Application software exception feedback method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110377444A (en) | 2019-10-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11748224B2 (en) | Detection and analysis of energy consumption of software applications | |
| CN107222331B (en) | method and device for monitoring performance of distributed application system, storage medium and equipment | |
| US10521333B2 (en) | Automated system for fixing and debugging software deployed to customers | |
| JP2016535369A (en) | Provision of application programs and user recommendation information | |
| CN109543891B (en) | Method and apparatus for establishing capacity prediction model, and computer-readable storage medium | |
| CN106357480B (en) | Method and device for monitoring network performance of application and mobile terminal | |
| CN110674025A (en) | Interactive behavior monitoring method and device and computer equipment | |
| CN111198797B (en) | Operation monitoring method and device and operation analysis method and device | |
| CN110377444B (en) | Fault alarm method, device, electronic equipment and computer readable storage medium | |
| CN114077525A (en) | Abnormal log processing method and device, terminal equipment, cloud server and system | |
| CN108900514A (en) | Attack tracking of information source tracing method and device based on homogeneous assays | |
| CN107741902B (en) | Program application detection method and program application detection device | |
| CN110489339A (en) | Client's side pressure observes and predicts table generating method, system, medium and electronic equipment | |
| CN111176918A (en) | Server testing method, system, equipment and computer readable storage medium | |
| CN105740122A (en) | Method and system for monitoring mobile phone memory leak | |
| CN111459660A (en) | Dynamic allocation method of cloud host on host, electronic device and storage medium | |
| CN111309743A (en) | Report pushing method and device | |
| CN113259152A (en) | Network diagnosis method, network diagnosis device, electronic equipment and storage medium | |
| CN105323748B (en) | Test error uploading method and device | |
| CN112286761A (en) | Database state detection method and device, electronic equipment and storage medium | |
| US20140067912A1 (en) | System for Remote Server Diagnosis and Recovery | |
| CN115445212A (en) | Game gift bag pushing method and device, computer equipment and storage medium | |
| CN112965711A (en) | Job test method and apparatus, electronic device, and storage medium | |
| CN109976576B (en) | Method and device for preventing mistaken touch of mobile terminal screen | |
| CN106708705B (en) | Terminal background process monitoring method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |