CN108520063B - Event log processing method and device and terminal equipment - Google Patents
Event log processing method and device and terminal equipment Download PDFInfo
- Publication number
- CN108520063B CN108520063B CN201810319344.7A CN201810319344A CN108520063B CN 108520063 B CN108520063 B CN 108520063B CN 201810319344 A CN201810319344 A CN 201810319344A CN 108520063 B CN108520063 B CN 108520063B
- Authority
- CN
- China
- Prior art keywords
- identifier
- time
- acquiring
- interface
- event log
- 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.)
- Expired - Fee Related
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
Abstract
The application is applicable to the field of communication, and provides a method and a device for processing an event log and a terminal device, wherein the method comprises the following steps: acquiring corresponding event log information according to a preset event identifier, wherein the event log information comprises time information and an interface identifier; acquiring an image corresponding to the interface identifier; and correspondingly displaying the time information and the image on a time axis. By the method, the efficiency and the accuracy of event log analysis can be improved.
Description
Technical Field
The present application belongs to the field of communications, and in particular, to a method and an apparatus for processing an event log, and a terminal device.
Background
In the development of the Android system, developers generally need to analyze event logs (event logs) in large quantities to analyze system defects (bugs). The Event log is one of log systems in an Android system, the log mainly records the invocation of the life cycle of Activity in the system, the creation and destruction of application processes and the like, and because the Event log is recorded according to a specific format, only developers familiar with the Service (AMS) of a management interface can accurately recover the behavior of the system at the time from the Event log, but developers unfamiliar with the AMS cannot accurately recover the system behavior corresponding to the time with problems from the Event log, so that the working efficiency is reduced, and even the analysis result is inaccurate.
Disclosure of Invention
In view of this, embodiments of the present application provide an event log processing method and apparatus, and a terminal device, so as to solve the problem that a developer unfamiliar with AMS has low work efficiency when analyzing an event log.
A first aspect of an embodiment of the present application provides a method for processing an event log, including:
acquiring corresponding event log information according to a preset event identifier, wherein the event log information comprises time information and an interface identifier;
acquiring an image corresponding to the interface identifier;
and correspondingly displaying the time information and the image on a time axis.
A second aspect of the embodiments of the present application provides an event log processing apparatus, including:
the event log information acquisition unit is used for acquiring corresponding event log information according to a preset event identifier, wherein the event log information comprises time information and an interface identifier;
the image acquisition unit is used for acquiring an image corresponding to the interface identifier;
and the time axis display unit is used for correspondingly displaying the time information and the image on a time axis.
A third aspect of the embodiments of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the processing method of the event log when executing the computer program.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, which stores a computer program, which, when executed by a processor, implements the steps of the method for processing event logs as described.
Compared with the prior art, the embodiment of the application has the advantages that:
because the time information and the image corresponding to the interface identifier are correspondingly displayed on the time axis, even if a developer is unfamiliar with AMS, the developer can analyze which time information the system has bug from the visual information displayed on the time axis, and therefore the analysis efficiency and accuracy are improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flowchart of a method for processing an event log according to an embodiment of the present application;
FIG. 2 is a schematic diagram of displaying an image and time information on a time axis according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an event log processing apparatus according to an embodiment of the present application;
fig. 4 is a schematic diagram of a terminal device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In particular implementations, the mobile terminals described in embodiments of the present application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers having touch sensitive surfaces (e.g., touch screen displays and/or touch pads). It should also be understood that in some embodiments, the devices described above are not portable communication devices, but rather are desktop computers having touch-sensitive surfaces (e.g., touch screen displays and/or touch pads).
In the discussion that follows, a mobile terminal that includes a display and a touch-sensitive surface is described. However, it should be understood that the mobile terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.
The mobile terminal supports various applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disc burning application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, an exercise support application, a photo management application, a digital camera application, a web browsing application, a digital music player application, and/or a digital video player application.
Various applications that may be executed on the mobile terminal may use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal can be adjusted and/or changed between applications and/or within respective applications. In this way, a common physical architecture (e.g., touch-sensitive surface) of the terminal can support various applications with user interfaces that are intuitive and transparent to the user.
In addition, in the description of the present application, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
The first embodiment is as follows:
fig. 1 shows a flowchart of a method for processing an event log according to an embodiment of the present application, which is detailed as follows:
step S101, acquiring corresponding event log information according to a preset event identifier, wherein the event log information comprises time information and an interface identifier;
in this step, the preset event identifier may be a sentence or phrase corresponding to the event in the event log. For example, assuming that the preset event identifier includes am _ set _ reset _ activity, the event log information corresponding to the am _ set _ reset _ activity is acquired. The interface identifier is mainly a name of an interface (activity).
In this step, corresponding event log information may be filtered out according to a preset event identification in the generated event log (event log). And sending a command corresponding to the preset event identifier to the activity, and then acquiring corresponding event log information.
Step S102, acquiring an image corresponding to the interface identifier;
in this step, the acquired image includes at least one of: an interface screenshot, a preset all black image, a symbolic marker (e.g., an exclamation point "!"), and the like.
Optionally, before step S102, to quickly acquire an image corresponding to the interface identifier, the method includes:
and pre-storing an image corresponding to the interface identifier.
For example, the interface identifier is stored in advance in correspondence with the interface screenshot and a preset all-black image, so that a corresponding image can be acquired subsequently as required.
Correspondingly, the step S102 specifically includes:
and acquiring an image corresponding to the interface identifier from a pre-stored image.
And step S103, correspondingly displaying the time information and the image on a time axis.
In this step, when it is determined that a certain activity operates at a certain time information, an image corresponding to the activity is displayed on the time information of the time axis. Specifically, assuming that 4 pieces of time information and 4 images corresponding thereto are acquired, the 4 pieces of time information are: 10:01, 10:02, 10:04 and 10:07 are ordered in sequence, and corresponding images are displayed under corresponding time information, as shown in fig. 2. In the time axis of fig. 2, the image corresponding to the 10:01 point is the application interface 1, and the image displayed by the user through the time axis (the image corresponding to the application interface 1) can quickly determine that the application corresponding to the application interface 1 is in the running state at the 10:01 point.
In the embodiment of the application, corresponding event log information is obtained according to a preset event identifier, the event log information comprises time information and an interface identifier, an image corresponding to the interface identifier is obtained, and the time information and the image are correspondingly displayed on a time axis. Because the time information and the image corresponding to the interface identifier are correspondingly displayed on the time axis, even if a developer is unfamiliar with AMS, the developer can analyze which time information the system has bug from the visual information displayed on the time axis, and therefore the analysis efficiency and accuracy are improved.
Optionally, because the time axis can display limited information, the preset event identifier may be several events that the user pays more attention to, or the terminal device counts the first several events that the bug occurs most in the preset time period, and then takes the identifiers of the several events as the preset event identifier. In this embodiment of the present application, it is assumed that the preset event identifier includes an application recovery instruction issuing identifier (am _ set _ recovered _ activity) and an application recovery instruction responding identifier (am _ on _ recovery _ captured), at this time, the step S101 includes:
a1, recording the issuing time of the application recovery instruction and the interface identifier carried by the application recovery instruction issuing identifier according to the application recovery instruction issuing identifier;
and A2, acquiring the response time of the application corresponding to the interface identification responding to the application recovery instruction.
Specifically, the AMS issues a resume instruction (am _ set _ resumed _ activity) to resume the application, or, when am _ set _ resumed _ activity is read from the event log, records an interface identifier (activity name) and an issue time of the resume instruction, and then reads an am _ on _ resume _ captured event to obtain a response time of the application executing onResume.
Correspondingly, the step S102 specifically includes:
if the difference between the response time and the sending time is smaller than a preset time threshold, acquiring an interface screenshot corresponding to the interface identifier, wherein the response time is used as time information of a time axis, if the difference between the response time and the sending time is larger than or equal to the preset time threshold, acquiring a full black image corresponding to the interface identifier, and determining the time information of the time axis according to the sending time and the preset time threshold.
The preset duration threshold may be set according to a tolerance duration of a system of the terminal device itself, for example, in an android system, the preset duration threshold may be set to 5 seconds, and of course, may also be set to other thresholds, which is not limited herein.
Determining time information of a time axis according to the sending time and the preset time threshold specifically comprises: and taking the sum of the sending time and a preset time threshold value as the time information of the time shaft.
In the above steps, if the difference between the response time and the sending time is greater than or equal to the preset time threshold, it is indicated that the activity corresponding to the interface identifier has a bug, and at this time, a completely black image is obtained, so that a developer can visually analyze that the corresponding time information has the bug according to the completely black image displayed by the time axis.
Optionally, since the all-black image does not include the interface identifier, in order to facilitate a developer to more clearly analyze a specific interface where the bug appears, the step S103 specifically includes: and correspondingly displaying the time information and the all-black image and the interface identifier on a time axis respectively. For example, an interface logo is also displayed on the time information of the time axis.
Optionally, because the all-black image does not include an interface identifier, in order to facilitate a developer to more clearly analyze a specific interface where a bug appears, if a difference between the response time and the emission time is greater than or equal to a preset time threshold, the all-black image corresponding to the interface identifier is acquired, time information of the all-black image on a time axis is determined according to the emission time and the preset time threshold, an interface screenshot corresponding to the interface identifier is acquired, and the time information of the interface screenshot on the time axis is determined according to the response time.
Optionally, before the step a2, the method includes:
judging whether the application corresponding to the interface identifier responds to the application recovery instruction or not, so as to determine time information of a time axis according to the sending time of the application recovery instruction and a preset time threshold when the application recovery instruction is not responded, and correspondingly, the acquiring the image corresponding to the interface identifier specifically comprises: and acquiring a full black image corresponding to the interface identifier.
Determining time information of a time axis according to the sending time of the application recovery instruction and a preset time threshold specifically comprises: and taking the sum of the sending time and a preset time threshold value as the time information of the time shaft.
Of course, if it is determined that the application corresponding to the interface identifier responds to the application recovery command, step a2 is executed.
Optionally, the preset event identifier includes a screen identifier (screen _ signed), in this case, the step S101 includes:
and acquiring a value corresponding to the screen identifier and an interface identifier according to the screen identifier, and recording the time for acquiring the value corresponding to the screen identifier. Since the screen has only 2 states, which are on screen or off screen, respectively, the corresponding values of the screen identifier may be set to 0 and 1, for example, "0" is used to indicate that the current screen is in the off screen state, and "1" is used to indicate that the current screen is in the on screen state. In this step, the recorded time for acquiring the value corresponding to the screen identifier will be time information on the time axis.
Correspondingly, the step S102 specifically includes:
judging whether the screen is in a black screen state according to the value corresponding to the screen identifier, and if so, acquiring a full black image corresponding to the interface identifier; and if the screen is in a bright screen state, acquiring an image of the locked screen corresponding to the interface identifier.
Optionally, since the screen is in a black screen state and the application corresponding to the interface identifier does not respond to the application recovery instruction, both of the two cases are to acquire the full black image, so as to facilitate a developer to quickly distinguish which case the bug causes on the time axis, when the screen is in the black screen state, the full black image corresponding to the interface identifier and the interface identifier are acquired, and correspondingly, the step S103 specifically includes: and correspondingly displaying the time information, the total black and the interface identification on a time axis respectively. For example, an interface logo is also displayed on the time information of the time axis.
Optionally, the preset event identifier includes process crash identifiers (such as am _ crash and am _ proc _ ded), and since such identifiers are not accurate enough if represented by a mere interface screenshot or a completely black image, when the preset event identifier includes a process crash identifier (such as am _ crash and am _ proc _ ded), the image obtained in step S102 is a symbolic marker (such as an exclamation mark "|") corresponding to the interface identifier, so that the symbolic marker (such as an exclamation mark "|") and time information will be displayed on the time axis. Of course, in order to make the display result more intuitive, the interface identifier may also be displayed on the time axis.
Example two:
corresponding to the method for processing an event log provided in the first embodiment, the first embodiment of the present application provides a schematic structural diagram of an event log processing apparatus, and specifically, as shown in fig. 3, for convenience of description, only departments related to the first embodiment of the present application are shown.
The event log processing device comprises: an event log information acquisition unit 31, an image acquisition unit 32, and a time axis display unit 33. Wherein:
an event log information obtaining unit 31, configured to obtain corresponding event log information according to a preset event identifier, where the event log information includes time information and an interface identifier;
the preset event identifier may be a sentence or a phrase corresponding to an event in the event log.
The interface identifier is mainly a name of an interface (activity).
The event log information obtaining unit 31 may filter out corresponding event log information according to a preset event identifier in the generated event log (event log). And sending a command corresponding to the preset event identifier to the activity, and then acquiring corresponding event log information.
An image obtaining unit 32, configured to obtain an image corresponding to the interface identifier;
wherein the acquired image comprises at least one of: an interface screenshot, a preset all black image, a symbolic marker (e.g., an exclamation point "!"), and the like.
Optionally, in order to be able to quickly acquire an image corresponding to the interface identifier, the processing device of the event log includes:
the image pre-storage unit is used for pre-storing the image corresponding to the interface identifier;
correspondingly, the image obtaining unit 32 is specifically configured to obtain an image corresponding to the interface identifier from a pre-stored image.
And a time axis display unit 33, configured to display the time information and the image in a time axis.
In the embodiment of the application, the time information and the image corresponding to the interface identifier are correspondingly displayed on the time axis, so that even though a developer is unfamiliar with AMS, the developer can analyze which time information of the system has bug from the visual information displayed on the time axis, and the analysis efficiency and accuracy are improved.
Optionally, because the time axis can display limited information, the preset event identifier may be several events that the user pays more attention to, or the terminal device counts the first several events that the bug occurs most in the preset time period, and then takes the identifiers of the several events as the preset event identifier. Assuming that the preset event identifier includes an application recovery instruction issue identifier (am _ set _ recovered _ activity) and a response application recovery instruction identifier (am _ on _ recovery _ cause), at this time, the event log information obtaining unit 31 includes:
the sending time recording module is used for sending an identification according to the application recovery instruction to record the sending time of the application recovery instruction and the interface identification carried by the application recovery instruction sending identification;
the response time acquisition module is used for acquiring the response time of the application corresponding to the interface identifier responding to the application recovery instruction;
correspondingly, the image obtaining unit 32 is specifically configured to, if the difference between the response time and the sending time is smaller than a preset time threshold, obtain an interface screenshot corresponding to the interface identifier, where the response time is used as time information of a time axis, and if the difference between the response time and the sending time is greater than or equal to the preset time threshold, obtain a blackout image corresponding to the interface identifier, and determine the time information of the time axis according to the sending time and the preset time threshold.
The preset duration threshold may be set according to a tolerance duration of a system of the terminal device itself, for example, in an android system, the preset duration threshold may be set to 5 seconds, and of course, may also be set to other thresholds, which is not limited herein.
Determining time information of a time axis according to the sending time and the preset time threshold specifically comprises: and taking the sum of the sending time and a preset time threshold value as the time information of the time shaft.
Optionally, since the all-black image does not include an interface identifier, in order to facilitate a developer to more clearly analyze a specific interface where a bug appears, the time axis display unit 33 is specifically configured to: and correspondingly displaying the time information and the all-black image and the interface identifier on a time axis respectively. For example, an interface logo is also displayed on the time information of the time axis.
Optionally, since the all-black image does not include the interface identifier, in order to facilitate a developer to more clearly analyze a specific interface where a bug appears, the image obtaining unit 32 is specifically configured to obtain an interface screenshot corresponding to the interface identifier if a difference between the response time and the issue time is smaller than a preset duration threshold, where the response time is used as time information of a time axis; if the difference between the response time and the sending time is greater than or equal to a preset time threshold, acquiring a full black image corresponding to the interface identifier, determining the time information of the full black image on a time axis according to the sending time and the preset time threshold, acquiring an interface screenshot corresponding to the interface identifier, and determining the time information of the interface screenshot on the time axis according to the response time.
Optionally, the event log processing apparatus includes:
a response-to-no judgment unit, configured to judge whether an application corresponding to the interface identifier responds to the application recovery instruction, so that when the application recovery instruction is not responded, time information of a time axis is determined according to the sending time of the application recovery instruction and a preset time threshold, and correspondingly, the image acquisition unit 32 is specifically configured to: and acquiring a full black image corresponding to the interface identifier.
Determining time information of a time axis according to the sending time of the application recovery instruction and a preset time threshold specifically comprises: and taking the sum of the sending time and a preset time threshold value as the time information of the time shaft.
Optionally, the preset event identifier includes a screen identifier, and at this time, the event log information obtaining unit 31 includes:
acquiring a value corresponding to the screen identifier and an interface identifier according to the screen identifier, and recording the time for acquiring the value corresponding to the screen identifier;
correspondingly, the image acquiring unit 32 is specifically configured to:
judging whether the screen is in a black screen state according to the value corresponding to the screen identifier, and if so, acquiring a full black image corresponding to the interface identifier; and if the screen is in a bright screen state, acquiring an image of the locked screen corresponding to the interface identifier.
Optionally, since the screen is in a black screen state and the application corresponding to the interface identifier does not respond to the application recovery instruction, both of the two cases are to acquire a full black image, so as to facilitate a developer to quickly distinguish which kind of bug is caused on the time axis, when the screen is in the black screen state, the image acquiring unit 32 is specifically configured to acquire the full black image corresponding to the interface identifier and the interface identifier, and correspondingly, the time axis displaying unit 33 is specifically configured to: and correspondingly displaying the time information, the total black and the interface identification on a time axis respectively. For example, an interface logo is also displayed on the time information of the time axis.
Optionally, the preset event identifier includes process crash identifiers (such as am _ crash and am _ proc _ ded), and since such identifiers are not accurate enough if represented by a mere interface screenshot or a completely black image, when the preset event identifier includes a process crash identifier (such as am _ crash and am _ proc _ ded), the image acquired by the image acquiring unit 32 is a symbolic mark (such as an exclamation mark "|") corresponding to the interface identifier, so that the symbolic mark (such as an exclamation mark "|") and time information will be displayed on the time axis. Of course, in order to make the display result more intuitive, the interface identifier may also be displayed on the time axis.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Example three:
fig. 4 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in fig. 4, the terminal device 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42 stored in said memory 41 and executable on said processor 40. The processor 40, when executing the computer program 42, implements the steps in the various image processing method embodiments described above, such as the steps S101 to S103 shown in fig. 1. Alternatively, the processor 40, when executing the computer program 42, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the units 31 to 33 shown in fig. 3.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 42 in the terminal device 4. For example, the computer program 42 may be divided into an event log information acquisition unit 31, an image acquisition unit 32, and a time axis display unit 33, and the specific functions of each unit are as follows:
an event log information obtaining unit 31, configured to obtain corresponding event log information according to a preset event identifier, where the event log information includes time information and an interface identifier;
an image obtaining unit 32, configured to obtain an image corresponding to the interface identifier;
and a time axis display unit 33, configured to display the time information and the image in a time axis.
The terminal device 4 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 40, a memory 41. Those skilled in the art will appreciate that fig. 4 is merely an example of a terminal device 4 and does not constitute a limitation of terminal device 4 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the terminal device may also include input-output devices, network access devices, buses, etc.
The Processor 40 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 41 may be an internal storage unit of the terminal device 4, such as a hard disk or a memory of the terminal device 4. The memory 41 may also be an external storage device of the terminal device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the terminal device 4. The memory 41 is used for storing the computer program and other programs and data required by the terminal device. The memory 41 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
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 implementation. 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 application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (9)
1. A method for processing an event log, comprising:
acquiring corresponding event log information according to a preset event identifier, wherein the event log information comprises time information and an interface identifier;
acquiring an image corresponding to the interface identifier;
correspondingly displaying the time information and the image on a time axis;
the preset event identifier includes a screen identifier, and the acquiring of the corresponding event log information according to the preset event identifier includes:
acquiring a value corresponding to the screen identifier and an interface identifier according to the screen identifier, and recording the time for acquiring the value corresponding to the screen identifier;
correspondingly, the acquiring the image corresponding to the interface identifier specifically includes:
judging whether the screen is in a black screen state according to the value corresponding to the screen identifier, and if so, acquiring a full black image corresponding to the interface identifier; and if the screen is in a bright screen state, acquiring an image of the locked screen corresponding to the interface identifier.
2. The method of processing an event log according to claim 1, wherein prior to said obtaining an image corresponding to said interface identification, comprising:
pre-storing an image corresponding to the interface identifier;
correspondingly, the acquiring of the image corresponding to the interface identifier specifically includes:
and acquiring an image corresponding to the interface identifier from a pre-stored image.
3. The method for processing the event log according to claim 1 or 2, wherein the preset event identifier includes an application recovery instruction issuing identifier and a response application recovery instruction identifier, and at this time, the acquiring the corresponding event log information according to the preset event identifier includes:
recording the sending time of the application recovery instruction and an interface identifier carried by the sending identifier of the application recovery instruction according to the sending identifier of the application recovery instruction;
acquiring response time of the application corresponding to the interface identification responding to the application recovery instruction;
correspondingly, the acquiring the image corresponding to the interface identifier specifically includes:
if the difference between the response time and the sending time is smaller than a preset time threshold, acquiring an interface screenshot corresponding to the interface identifier, wherein the response time is used as time information of a time axis, if the difference between the response time and the sending time is larger than or equal to the preset time threshold, acquiring a full black image corresponding to the interface identifier, and determining the time information of the time axis according to the sending time and the preset time threshold.
4. The method for processing the event log according to claim 3, wherein before the obtaining of the response time of the application corresponding to the interface identifier in response to the application recovery instruction, the method comprises:
judging whether the application corresponding to the interface identifier responds to the application recovery instruction or not, so as to determine time information of a time axis according to the sending time of the application recovery instruction and a preset time threshold when the application recovery instruction is not responded, and correspondingly, the acquiring the image corresponding to the interface identifier specifically comprises: and acquiring a full black image corresponding to the interface identifier.
5. An apparatus for processing an event log, comprising:
the event log information acquisition unit is used for acquiring corresponding event log information according to a preset event identifier, wherein the event log information comprises time information and an interface identifier;
the image acquisition unit is used for acquiring an image corresponding to the interface identifier;
a time axis display unit, which is used for correspondingly displaying the time information and the image on a time axis;
the preset event identifier includes a screen identifier, and at this time, the event log information acquiring unit includes:
acquiring a value corresponding to the screen identifier and an interface identifier according to the screen identifier, and recording the time for acquiring the value corresponding to the screen identifier;
correspondingly, the image acquisition unit is used for:
judging whether the screen is in a black screen state according to the value corresponding to the screen identifier, and if so, acquiring a full black image corresponding to the interface identifier; and if the screen is in a bright screen state, acquiring an image of the locked screen corresponding to the interface identifier.
6. The apparatus for processing the event log according to claim 5, wherein the apparatus for processing the event log comprises:
the image pre-storage unit is used for pre-storing the image corresponding to the interface identifier;
correspondingly, the image acquiring unit is specifically configured to acquire an image corresponding to the interface identifier from a pre-stored image.
7. The apparatus for processing event log according to claim 5 or 6, wherein the preset event identifier comprises an application recovery instruction issuing identifier and a response application recovery instruction identifier, and at this time, the event log information obtaining unit comprises:
the sending time recording module is used for sending an identification according to the application recovery instruction to record the sending time of the application recovery instruction and the interface identification carried by the application recovery instruction sending identification;
the response time acquisition module is used for acquiring the response time of the application corresponding to the interface identifier responding to the application recovery instruction;
correspondingly, the image obtaining unit is specifically configured to obtain an interface screenshot corresponding to the interface identifier if a difference between the response time and the sending time is smaller than a preset time threshold, where the response time is used as time information of a time axis, obtain a completely black image corresponding to the interface identifier if the difference between the response time and the sending time is greater than or equal to the preset time threshold, and determine the time information of the time axis according to the sending time and the preset time threshold.
8. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 4 when executing the computer program.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810319344.7A CN108520063B (en) | 2018-04-11 | 2018-04-11 | Event log processing method and device and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810319344.7A CN108520063B (en) | 2018-04-11 | 2018-04-11 | Event log processing method and device and terminal equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108520063A CN108520063A (en) | 2018-09-11 |
| CN108520063B true CN108520063B (en) | 2020-12-25 |
Family
ID=63432012
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810319344.7A Expired - Fee Related CN108520063B (en) | 2018-04-11 | 2018-04-11 | Event log processing method and device and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108520063B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109858548B (en) * | 2019-01-29 | 2023-04-18 | Oppo广东移动通信有限公司 | Method and device for judging abnormal power consumption, storage medium and communication terminal |
| CN109999495B (en) * | 2019-03-28 | 2023-02-28 | 网易（杭州）网络有限公司 | Method and system for processing artificial intelligence AI unit state information |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7188220B2 (en) * | 2003-03-24 | 2007-03-06 | American Megatrends, Inc. | Method and system for managing the contents of an event log stored within a computer |
| JP5751496B2 (en) * | 2012-12-27 | 2015-07-22 | 横河電機株式会社 | Event analysis apparatus and computer program |
| CN105260082B (en) * | 2015-10-16 | 2018-12-07 | 华为技术有限公司 | A kind of test data methods of exhibiting and exploitation terminal |
| CN105740144B (en) * | 2016-01-27 | 2018-11-23 | 浪潮(北京)电子信息产业有限公司 | A kind of automated testing method and system of Android mobile terminal |
| CN105824958B (en) * | 2016-03-31 | 2019-06-18 | 广州华多网络科技有限公司 | A kind of methods, devices and systems of inquiry log |
| CN105912731A (en) * | 2016-05-30 | 2016-08-31 | 北京网智天元科技股份有限公司 | Information showing method and device based on time axis |
| CN107102795A (en) * | 2017-05-31 | 2017-08-29 | 努比亚技术有限公司 | A kind of log recording method, mobile terminal and computer-readable recording medium |
-
2018
- 2018-04-11 CN CN201810319344.7A patent/CN108520063B/en not_active Expired - Fee Related
Non-Patent Citations (1)
| Title |
|---|
| 面向在线交易日志的用户购买行为可视化分析;贾若雨等;《软件学报》;20170930;第28卷(第9期);2450-2467 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108520063A (en) | 2018-09-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109215037B (en) | Target image segmentation method and device and terminal equipment | |
| CN109376645B (en) | Face image data optimization method and device and terminal equipment | |
| CN111338901A (en) | Redis monitoring method, Redis monitoring device and terminal | |
| CN109359582B (en) | Information searching method, information searching device and mobile terminal | |
| CN108520063B (en) | Event log processing method and device and terminal equipment | |
| CN114996103A (en) | Page abnormity detection method and device, electronic equipment and storage medium | |
| CN112671609A (en) | Asset census and safety detection method and device and terminal equipment | |
| CN106484779B (en) | File operation method and device | |
| CN109358927B (en) | Application program display method and device and terminal equipment | |
| CN110765085A (en) | Log information writing method, system, storage medium and mobile terminal | |
| CN107679222B (en) | Picture processing method, mobile terminal and computer readable storage medium | |
| CN108845924B (en) | Control response area display control method, electronic device, and storage medium | |
| US9069951B2 (en) | Inferring security decisions from trusted users | |
| CN112817831A (en) | Application performance monitoring method, device, computer system and readable storage medium | |
| CN109444905B (en) | Dynamic object detection method and device based on laser and terminal equipment | |
| CN107862010B (en) | Method and device for acquiring information of application system of Internet of things and mobile terminal | |
| CN108536512B (en) | Interface switching method and device and terminal equipment | |
| CN112912855A (en) | Starting-up detection method, starting-up detection device and mobile terminal | |
| CN108509111B (en) | Application notification method and device and terminal equipment | |
| CN109241787B (en) | Call detection method and device for image input device and computer readable storage medium | |
| CN112763251A (en) | Mobile robot testing method and device | |
| CN110837433A (en) | Performance optimization method and device and electronic equipment | |
| CN110874723A (en) | Electronic red packet detection method, electronic red packet detection device and mobile terminal | |
| CN110875875B (en) | Electronic red packet message detection method and device and terminal equipment | |
| CN110008706B (en) | Host security state management method and device and terminal equipment |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20201225 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |