CN114531340B - Log acquisition method and device, electronic equipment, chip and storage medium - Google Patents

Log acquisition method and device, electronic equipment, chip and storage medium Download PDF

Info

Publication number
CN114531340B
CN114531340B CN202210147478.1A CN202210147478A CN114531340B CN 114531340 B CN114531340 B CN 114531340B CN 202210147478 A CN202210147478 A CN 202210147478A CN 114531340 B CN114531340 B CN 114531340B
Authority
CN
China
Prior art keywords
log
type
target
abnormal
network
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
Application number
CN202210147478.1A
Other languages
Chinese (zh)
Other versions
CN114531340A (en
Inventor
候祥
王建
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202210147478.1A priority Critical patent/CN114531340B/en
Publication of CN114531340A publication Critical patent/CN114531340A/en
Application granted granted Critical
Publication of CN114531340B publication Critical patent/CN114531340B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/069Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/22Matching criteria, e.g. proximity measures
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/24Classification techniques
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The application is suitable for the technical field of Internet, and provides a log acquisition method, a log acquisition device, electronic equipment, a chip and a storage medium. The log acquisition method comprises the following steps: acquiring a problem type of an abnormal problem of a Wi-Fi network, determining a target log type based on the problem type of the abnormal problem, wherein the target log type is a log type matched with the problem type of the abnormal problem; and acquiring a target log from a log generated when the abnormal problem occurs in the Wi-Fi network based on the problem type of the abnormal problem and the target log type, wherein the target log refers to a log matched with the problem type of the abnormal problem and the target log type. The method and the system can acquire the log related to the abnormal problem of the Wi-Fi network.

Description

Log acquisition method and device, electronic equipment, chip and storage medium
Technical Field
The application belongs to the technical field of internet, and particularly relates to a log acquisition method, a log acquisition device, electronic equipment, a chip and a storage medium.
Background
In recent years, with the high-speed development of the mobile internet, demands of people on networks are gradually increased, and electronic equipment can be networked by adopting a Wi-Fi network, so that functions of internet of everything, intelligent management and the like are realized. When the electronic equipment is networked by adopting a Wi-Fi network, abnormal problems such as abnormal connection, abnormal surfing, abnormal direct connection and the like can occur.
Disclosure of Invention
The embodiment of the application provides a log acquisition method, a device, electronic equipment, a chip and a storage medium, which are used for acquiring logs related to abnormal problems of a Wi-Fi network.
In a first aspect, an embodiment of the present application provides a log obtaining method, including:
acquiring a problem type of an abnormal problem of the Wi-Fi network;
determining a target log type based on the problem type of the abnormal problem, wherein the target log type is a log type matched with the problem type of the abnormal problem;
and acquiring a target log from a log generated when the abnormal problem occurs in the Wi-Fi network based on the problem type of the abnormal problem and the target log type, wherein the target log refers to a log matched with the problem type of the abnormal problem and the target log type.
According to the embodiment of the application, by acquiring the problem type of the abnormal problem of the Wi-Fi network, the log type (namely, the target log type) matched with the problem type of the abnormal problem of the Wi-Fi network can be determined based on the problem type of the abnormal problem of the Wi-Fi network, and the log (namely, the target log) matched with the problem type of the abnormal problem and the target log type can be acquired more accurately from the log generated when the abnormal problem occurs in the Wi-Fi network based on the problem type of the abnormal problem and the target log type, wherein the acquired target log is the log related to the abnormal problem of the Wi-Fi network.
In a second aspect, an embodiment of the present application provides a log obtaining apparatus, including:
the type acquisition module is used for acquiring the problem type of the abnormal problem of the Wi-Fi network;
the type determining module is used for determining a target log type based on the problem type of the abnormal problem, wherein the target log type is a log type matched with the problem type of the abnormal problem;
the target acquisition module is used for acquiring a target log from a log generated when the abnormal problem occurs in the Wi-Fi network based on the problem type of the abnormal problem and the target log type, wherein the target log refers to a log matched with the problem type of the abnormal problem and the target log type.
In a third aspect, an embodiment of the present application provides an electronic 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 log obtaining method according to the first aspect described above when the processor executes the computer program.
In a fourth aspect, an embodiment of the present application provides a chip, including a processor, where the processor is configured to read and execute a computer program stored in a memory, to perform the steps of the log obtaining method according to the first aspect.
Optionally, the memory is connected to the processor through a circuit or a wire.
In a fifth aspect, an embodiment of the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the log obtaining method according to the first aspect described above.
In a sixth aspect, embodiments of the present application provide a computer program product which, when run on an electronic device, causes the electronic device to perform the steps of the log obtaining method as described in the first aspect above.
It will be appreciated that the second, third, fourth, fifth and sixth aspects provided above are all used to perform the corresponding methods provided above, and therefore the advantages achieved by the above are referred to as advantages in the corresponding methods provided above, and are not described here again.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed 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 application, 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 schematic diagram of an implementation flow of a log obtaining method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an implementation flow of a log obtaining method according to another embodiment of the present application;
FIG. 3 is a schematic flow chart of an implementation of a log obtaining method according to another embodiment of the present application;
FIG. 4-1 is an exemplary diagram of a desktop of an electronic device;
FIG. 4-2 is an exemplary diagram of a crawl log page;
4-3 are another exemplary diagrams of a crawl log page;
FIGS. 4-4 are exemplary diagrams of selecting a question type page;
FIGS. 4-5 are exemplary diagrams of question type pages;
FIGS. 4-6 are further exemplary diagrams of question type pages;
FIGS. 4-7 are exemplary diagrams of problem detailed description pages;
FIGS. 4-8 are example diagrams of log commit complete pages;
FIGS. 4-9 are example diagrams of a lack of key log pages;
FIGS. 4-10 are further exemplary diagrams of crawling log pages;
FIG. 5 is a schematic diagram of a log obtaining device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to 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 the particular system architecture, 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.
It should 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 should also be understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in the present description and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
Furthermore, the terms "first," "second," "third," and the like in the description of the present specification and in the appended claims, are used for distinguishing between descriptions and not necessarily for indicating or implying a relative importance.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
For ease of understanding, the application is described by way of example with respect to the Android system, but this does not constitute a limitation on the type of operating system of the electronic device.
Before describing the present application, for the convenience of the reader, the terms involved in the present application will be explained.
Wi-Fi is also called "Mobile hotspot", which is a brand authentication of a product by a trademark of Wi-Fi alliance manufacturer, and is a wireless local area network technology created in the IEEE 802.11 standard.
The Android system log (Android log) is used for recording event information of the Android system operation.
The network layer protocol packet log (tcpdump log) is used to record event information of the network layer protocol packet operation.
The Wi-Fi Driver log (Wi-Fi Driver log) is used for recording event information of the Driver layer operation of the Wi-Fi chip. Wi-Fi driven layer logs may also be referred to as Wi-Fi driven logs.
Wi-Fi Firmware layer logs (Wi-Fi Firmware logs) are used to record event information of software system operation of Wi-Fi chips. Wi-Fi firmware layer logs may also be referred to as Wi-Fi firmware logs.
When networking is performed by adopting a Wi-Fi network, the Wi-Fi network can have abnormal problems such as abnormal connection, abnormal surfing, abnormal direct connection and the like. When the electronic equipment generates the abnormal problems, the events related to the abnormal problems can be recorded in a log form, so that the abnormal problems can be solved based on the analyzed reasons by acquiring the logs generated by the electronic equipment when the Wi-Fi network generates the abnormal problems, screening the logs related to the abnormal problems from the logs and analyzing the reasons of the abnormal problems of the Wi-Fi network based on the screened logs.
The related scheme is to obtain a fixed type log by default when a user feeds back an abnormal problem to the Wi-Fi network, but different types of logs may be required for analyzing different abnormal problems, so that the scheme may cause a shortage of a key type log when the logs related to the abnormal problem are obtained, and thus the logs related to the abnormal problem cannot be accurately obtained, and further causes that the cause of the abnormal problem of the Wi-Fi network cannot be accurately analyzed. Where a log associated with an abnormal problem is used to analyze the abnormal problem, the key type may refer to a type of log required to analyze the abnormal problem.
In order to accurately acquire the log related to the abnormal problem, the method and the system can determine the target log type based on the problem type of the abnormal problem of the Wi-Fi network by acquiring the problem type of the abnormal problem of the Wi-Fi network, and can accurately acquire the target log from the log generated when the abnormal problem occurs in the Wi-Fi network based on the target log type, wherein the acquired target log is the log related to the abnormal problem of the Wi-Fi network.
The log obtaining method provided by the embodiment of the application can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (augmented reality, AR)/Virtual Reality (VR) devices, notebook computers, ultra-mobile personal computer (UMPC), netbooks, personal digital assistants (personal digital assistant, PDA) and the like, and the embodiment of the application does not limit the specific types of the electronic devices.
It should be understood that, the sequence number of each step in this embodiment does not mean the execution sequence, and the execution sequence of each process should be determined by its function and internal logic, and should not limit the implementation process of the embodiment of the present application in any way.
In order to illustrate the technical scheme of the application, the following description is made by specific examples.
Referring to fig. 1, a schematic flow chart of an implementation of a log obtaining method according to an embodiment of the present application is provided, where the log obtaining method is applied to an electronic device. As shown in fig. 1, the log obtaining method may include the steps of:
step 101, obtaining the problem type of the abnormal problem of the Wi-Fi network.
The abnormal problem may be any abnormal problem of the Wi-Fi network. For example, wi-Fi networks have the problems of no connection, no internet surfing, automatic disconnection of direct-connection projection screens, automatic closing of personal hot spots in the use process, no connection of personal hot spots, and the like. It should be noted that the present application does not limit the problem of abnormality of Wi-Fi network.
The abnormal problems of the Wi-Fi network can be classified according to a preset classification algorithm, so that the problem types of the abnormal problems of the Wi-Fi network are obtained. The preset classification algorithm may be any classification algorithm that is preset and that can make the types of logs (i.e., log types) required for the abnormal questions belonging to the same question type the same.
For example, the abnormal problems with the same type of the required logs can be classified into the same problem type according to whether the types of the required logs are the same when the abnormal problems of the Wi-Fi network are analyzed. The types of the logs required for analyzing the reason that the Wi-Fi network is not connected are android system logs, wi-Fi drive layer logs and Wi-Fi firmware layer logs; the types of the logs required for analyzing the reason that the Wi-Fi network cannot surf the Internet are android system logs, network layer protocol packet logs, wi-Fi drive layer logs and Wi-Fi firmware layer logs; the types of logs required for analyzing the reason of automatic disconnection of the direct-connected screen are android system logs, network layer protocol packet logs and Wi-Fi drive layer logs; the types of logs required for analyzing the reasons that the personal hot spot is automatically closed or the personal hot spot is not connected in the using process are android system logs and Wi-Fi drive layer logs. When the abnormality problem of the Wi-Fi network is that the Wi-Fi network is not connected, determining that the problem type to which the Wi-Fi network belongs is abnormal connection of the Wi-Fi network; when the abnormality problem of the Wi-Fi network is that the Wi-Fi network cannot surf the Internet, the problem type of the Wi-Fi network can be determined to be the Internet surfing abnormality of the Wi-Fi network; when the abnormal problem of the Wi-Fi network is that the direct-connected screen is automatically disconnected, the problem type of the Wi-Fi network can be determined to be the direct-connected abnormality of the Wi-Fi network; when the abnormality problem of the Wi-Fi network is that the personal hot spot is automatically closed or the personal hot spot is not connected in the using process, the problem type of the Wi-Fi network can be determined to be personal hot spot abnormality.
In an alternative embodiment, obtaining a problem type to which an abnormal problem of the Wi-Fi network belongs includes:
displaying at least one question type;
responsive to a selection operation of the displayed at least one question type, a question type to which the abnormal question of the Wi-Fi network belongs is determined.
When the user finds that the Wi-Fi network has abnormal problems, the user can trigger to display at least one problem type, and select the problem type of the abnormal problem of the Wi-Fi network from the displayed problem types through a selection operation. The selection operation may be any operation capable of selecting a question type, such as a click operation, a slide operation, or the like on a display position of the question type.
In order to facilitate a user to more accurately select a question type, at least one question case may be set for each question type. After displaying at least one question type, in response to an opening operation on the displayed at least one question type, displaying a question case of a question type corresponding to the opening operation, wherein the user can judge whether an abnormal question appearing on the Wi-Fi network belongs to one of the displayed question cases, and if so, the user can select the question type to which the question case belongs. The opening operation may be any operation capable of triggering the question case of displaying the question type, for example, a long-press operation on the display position of the question type, or a virtual button is set at the display position of the question type, and the opening operation may be a click operation on the virtual button.
Of course, while displaying at least one question type, the question cases of each question type may be displayed, and the user may determine the question type to which the abnormal question of the Wi-Fi network belongs based on all the question cases of all the displayed question types.
In another alternative embodiment, when the user finds that an abnormal problem occurs in the Wi-Fi network, the user may also input the abnormal problem into the electronic device, and when the electronic device receives the abnormal problem input by the user, the electronic device obtains a problem type to which the abnormal problem of the Wi-Fi network belongs by performing artificial intelligence (Artificial Intelligence, AI) text parsing on the abnormal problem of the Wi-Fi network, specifically:
encoding the characters in the abnormal problem to obtain vector representation of the characters in the abnormal problem;
according to the arrangement sequence of the characters in the abnormal problems, vector representations of the characters in the abnormal problems are spliced to obtain a feature map corresponding to the abnormal problems;
inputting the feature map corresponding to the abnormal problem into a problem type identification network to obtain the problem type of the abnormal problem.
The problem type recognition network is used for recognizing the problem type of the abnormal problem. The application does not limit the structure of the problem type recognition network.
Step 102, determining a target log type based on the problem type to which the abnormal problem belongs.
The target log type is a log type matching a problem type to which an abnormal problem belongs, and is a type to which a log required for analyzing the abnormal problem belonging to the problem type belongs. For example, if the abnormal problem is that the Wi-Fi network connection is not on, and the problem type of the abnormal problem is that the Wi-Fi network connection is abnormal, the target log type may be determined to be an android system log, a Wi-Fi driving layer log and a Wi-Fi firmware layer log based on the Wi-Fi network connection abnormality, and the reason why the Wi-Fi network connection is not on may be analyzed based on the three types of logs.
Step 103, acquiring a target log from a log generated when the abnormal problem occurs in the Wi-Fi network based on the problem type and the target log type to which the abnormal problem belongs.
The target log refers to a log matched with the type of the problem to which the abnormal problem belongs and the type of the target log.
When the user finds that the Wi-Fi network has an abnormal problem, the user can trigger the electronic equipment to grab the log so as to acquire the log generated when the Wi-Fi network has the abnormal problem.
Optionally, the electronic device may avoid performing step 101, step 102, step 103, etc. simultaneously in the process of capturing the log, so as to reduce capturing of the invalid log. The invalid log may be a log that is not used when analyzing an abnormal problem. For example, if step 101 is performed during the process of the electronic device capturing the log, the electronic device will capture the log generated by performing step 101, which is an invalid log when the abnormal problem is analyzed.
In an alternative embodiment, the closer to the point in time when the user finds that the Wi-Fi network has an abnormal problem, the greater the likelihood that the log captured by the electronic device is related to the abnormal problem, so when the user finds that the Wi-Fi network has an abnormal problem, the user may trigger the electronic device to capture the log first, and after the log capture is finished, trigger the electronic device to execute steps 101 to 103 and the like.
In an alternative embodiment, a log generated when an abnormal problem occurs in the Wi-Fi network is acquired in response to a log grabbing start operation and a log grabbing end operation.
The log grabbing start operation is used for triggering the electronic equipment to start grabbing logs; the log grabbing end operation is used for triggering the electronic equipment to end grabbing logs. The obtained log generated when the Wi-Fi network has an abnormal problem is a log obtained by the electronic equipment in a time period from starting grabbing to ending grabbing.
If the target log is obtained through step 103, the time point of the target log can be marked, the target log is submitted to the server, after the server receives the target log, a researcher can quickly position the target log based on the time point of the target log, and the abnormal problem is solved based on the analysis of the target log; if the target log is not obtained in step 103, the user may be prompted to not obtain the target log, and the user may re-obtain the problem type of the abnormal problem of the Wi-Fi network by triggering the electronic device, or re-grab the log. Wherein the time point of the target log is the time point of the event occurrence recorded by the target log
In an alternative embodiment, if the target log is not obtained, the step of obtaining the problem type of the abnormal problem of the Wi-Fi network and the subsequent steps are performed in a returning manner until the target log is obtained or the number of times of performing in a returning manner reaches the first preset number of times. The number of return executions refers to the number of return executions of the step of acquiring the problem type to which the abnormal problem of the Wi-Fi network belongs and the subsequent steps.
The first preset times are preset times thresholds, and are used for judging whether to return to execute the step and the subsequent steps of acquiring the problem type of the abnormal problem of the Wi-Fi network. For example, when the number of times of returning to execute the step of acquiring the problem type to which the abnormal problem of the Wi-Fi network belongs and the subsequent step reaches the first preset number of times, stopping executing the step of acquiring the problem type to which the abnormal problem of the Wi-Fi network belongs and the subsequent step (i.e., stopping acquiring the target log); and returning to the step and the subsequent step of acquiring the problem type of the abnormal problem of the Wi-Fi network when the times of executing the step and the subsequent step of acquiring the problem type of the abnormal problem of the Wi-Fi network do not reach the first preset times and the target log is not acquired. The number of times of executing the step of acquiring the question type and the subsequent step to which the abnormality of the Wi-Fi network belongs is increased by 1.
In another alternative embodiment, if the target log is not obtained, the step of obtaining the log generated when the Wi-Fi network has an abnormal problem and the subsequent steps in response to the log grabbing start operation and the log grabbing end operation are performed in a return manner until the target log is obtained or the number of times of return execution reaches a second preset number of times. The number of return executions refers to the number of return executions of the step of acquiring a log generated when an abnormality occurs in the Wi-Fi network and the subsequent step in response to the log grabbing start operation and the log grabbing end operation.
The second preset times are preset times thresholds, and are used for judging whether to return to execute the steps of responding to the log grabbing start operation and the log grabbing end operation and acquiring the log generated when the Wi-Fi network has an abnormal problem and the subsequent steps. For example, when the number of steps of acquiring the log generated when the Wi-Fi network has an abnormal problem and the subsequent steps reaches the second preset number, returning to the step of acquiring the log generated when the Wi-Fi network has an abnormal problem and the subsequent steps in response to the log-grabbing start operation and the log-grabbing end operation are stopped; and when the times of acquiring the log generated when the Wi-Fi network has abnormal problems and the subsequent steps do not reach the second preset times and the target log is not acquired, returning to execute the steps of acquiring the log generated when the Wi-Fi network has abnormal problems and the subsequent steps in response to the log grabbing start operation and the log grabbing end operation. It should be noted that, each time the log capturing start operation and the log capturing end operation are executed in response to the return, the step of acquiring the log generated when the Wi-Fi network has an abnormal problem and the subsequent step are executed in response to the log capturing start operation and the log capturing end operation, and the number of times the step of acquiring the log generated when the Wi-Fi network has an abnormal problem and the subsequent step is increased by 1.
Alternatively, the first preset number of times and the second preset number of times may be the same or different, which is not limited herein. For example, the first preset number of times and the second preset number of times are both 5 times, or the first preset number of times is 4 times, and the second preset number of times is 5 times.
According to the embodiment of the application, by acquiring the problem type of the abnormal problem of the Wi-Fi network, the log type (namely the target log type) matched with the problem type of the abnormal problem of the Wi-Fi network can be determined based on the problem type of the abnormal problem of the Wi-Fi network, and the target log can be acquired more accurately from the log generated when the abnormal problem occurs in the Wi-Fi network based on the problem type of the abnormal problem and the target log type.
Referring to fig. 2, a flowchart of an implementation of a log obtaining method according to another embodiment of the present application is shown, where the log obtaining method is applied to an electronic device. As shown in fig. 2, the log obtaining method may include the steps of:
step 201, obtaining a problem type of an abnormal problem of the Wi-Fi network.
The step is the same as step 101, and specific reference may be made to the description related to step 101, which is not repeated here.
Step 202, determining a target log type based on the problem type to which the abnormal problem belongs.
The step is the same as step 102, and the detailed description of step 102 is omitted here.
And 203, searching a log containing the target keywords from the log generated when the Wi-Fi network has an abnormal problem.
The target keyword refers to a keyword matched with the problem type and the target log type of the abnormal problem, namely the target keyword is determined by the problem type and the target log type of the abnormal problem together.
Characters in the abnormal problems can be scanned by adopting a text scanning technology, and whether a log containing the target keywords exists in a log generated when the Wi-Fi network has the abnormal problems or not is searched based on the scanned characters.
The target log types in the application can be at least one, and each target log type corresponds to a target keyword so as to screen out the logs matched with the problem type and the target log type of the abnormal problem from the logs generated when the abnormal problem occurs in the Wi-Fi network through the target keywords. For example, the problem type of the abnormal problem is Wi-Fi network connection abnormality, and then the log type matched with the problem type comprises three types of android system logs, wi-Fi drive layer logs and Wi-Fi firmware layer logs; taking android system logs in the three types as an example, the target keyword matched with the Wi-Fi network connection abnormality and the android system logs is Wi-Fi connected failed, and the logs matched with the Wi-Fi network connection abnormality and the android system logs can be screened from the logs generated when the Wi-Fi network abnormality occurs through the target keyword Wi-Fi connected failed.
In an alternative embodiment, a first correspondence may be stored in the electronic device, where the first correspondence includes at least a mapping relationship between a problem type, a target log type, and a target keyword, where the problem type and the target log type of the abnormal problem belong, and a keyword that matches the problem type and the target log type of the abnormal problem may be obtained based on the first correspondence. Specifically, after obtaining the problem type and the target log type to which the abnormal problem belongs, the electronic device may determine the target keyword from the first correspondence relationship based on the problem type and the target log type to which the abnormal problem belongs.
In another alternative implementation, the first correspondence may be stored in other devices, the electronic device sends a keyword obtaining instruction to the other devices, where the keyword obtaining instruction carries a problem type and a target log type to which the abnormal problem belongs, and after receiving the keyword obtaining instruction from the electronic device, the other devices determine a target keyword from the first correspondence and send the target keyword to the electronic device. Wherein other devices may refer to devices other than electronic devices.
It should be noted that, for the same target log type matched with different problem types, the corresponding target keywords are different, and the logs related to the abnormal problems of different problem types matched with the same target log type can be screened from the grabbed logs by the different target keywords corresponding to the same target log type.
In order to more intuitively represent the first correspondence, taking Wi-Fi network connection abnormality and Wi-Fi network surfing abnormality in the problem type as examples, the first correspondence is represented as shown in table 1.
The 'Wi-Fi connected failed' in the table 1 is a target keyword matched with Wi-Fi network connection abnormality and android system logs, and a log screened from the grabbed logs based on the target keyword can be used for analyzing and solving the problem that Wi-Fi network connection is not available; the Wi-Fi accessed failed is a target keyword matched with the Wi-Fi network Internet surfing abnormality and the android system log, and the log screened from the grabbed log based on the target keyword can be used for analyzing and solving the problem that the Wi-Fi network cannot surf the Internet. The key log model in table 1 includes the target log types and the target keywords matched with the target log types, so that the user can more intuitively see the target keywords matched with different target log types.
In step 204, if the log containing the target keyword is found, the log containing the target keyword is determined to be the target log.
If the log containing the target keywords is found from the log generated when the Wi-Fi network has an abnormal problem, determining the log containing the target keywords as a target log; if the log containing the target keyword is not found in the log generated when the Wi-Fi network has an abnormal problem, determining that the target log is not found (i.e. the target log is not obtained), and performing step 201 and subsequent steps by re-obtaining the log generated when the Wi-Fi network has an abnormal problem and/or returning to search the target log again, thereby increasing the probability of finding the target log through multiple searches.
According to the embodiment of the application, the target keyword can be used for accurately acquiring the target log from the log generated when the Wi-Fi network has the abnormal problem, and the abnormal problem of the Wi-Fi network can be accurately analyzed and solved based on the target log.
Referring to fig. 3, a flowchart of an implementation of a log obtaining method according to another embodiment of the present application is shown, where the log obtaining method is applied to an electronic device. As shown in fig. 3, the log obtaining method may include the steps of:
step 301, obtaining a problem type of the abnormal problem of the Wi-Fi network.
The step is the same as step 101, and specific reference may be made to the description related to step 101, which is not repeated here.
Step 302, determining a target log type based on the problem type to which the abnormal problem belongs.
The step is the same as step 102, and the detailed description of step 102 is omitted here.
In an alternative embodiment, a log type (i.e., a target log type) that matches the problem type to which the abnormal problem belongs may be determined based on the first correspondence in the previous embodiment. Specifically, after the problem type of the abnormal problem is obtained, a log type having a mapping relation with the problem type of the abnormal problem is searched from the first corresponding relation, and the log type is the target log type.
Step 303, searching a target log file from log files in which a log generated when an abnormal problem occurs in the Wi-Fi network is located.
The target log file refers to a target log file with file attribute information matched with the target log type, and the file attribute information comprises a file name and a file suffix name, specifically the file name of the log file and the file suffix name of the log file. For example, taking a log file as an android. Txt as an example, the file name of the log file is android, and the file suffix of the log file is txt.
In an alternative embodiment, a second correspondence may be stored in the electronic device, where the second correspondence includes at least a mapping relationship between the target log type and the matched file attribute information, and file attribute information matched with the target log type may be obtained based on the second correspondence. Specifically, after obtaining the target log type, the electronic device may determine file attribute information that matches the target log type from the second correspondence based on the target log type.
In another optional embodiment, the second correspondence may be stored in another device, and the electronic device sends an attribute information obtaining instruction to the other device, where the attribute information obtaining instruction carries a target log type, and after the other device receives the attribute information obtaining instruction from the electronic device, the other device determines file attribute information matching the target log type from the second correspondence.
Step 304, if the target log file is found and the size of the target log file exceeds the preset threshold, searching the log containing the target keyword from the target log file.
The preset threshold may be a preset threshold of a file size, which is used to determine whether a log is stored in the target log file. For example, the preset threshold may be zero, if the size of the target log file is greater than zero, it may be determined that the log is stored in the target log file, and whether the target log is stored in the target log file may be detected by the target keyword; if the size of the target log file is less than or equal to zero, it may be determined that the target log file is empty, the log is not stored, and it may be determined that the target log is not found.
The file attribute information and the preset threshold value can be called as a log searching condition of the target log file, and the target log file can be searched from the log file where the log generated when the Wi-Fi network has an abnormal problem based on the log searching condition. In order to more intuitively represent the log search condition, various problem types such as Wi-Fi network connection abnormality, wi-Fi network surfing abnormality, wi-Fi network direct abnormality, and personal hot spot abnormality are taken as examples, and the log search condition is represented as shown in table 2.
Android. Txt in table 2 is file attribute information matching with the android system log, driver. Txt is file attribute information matching with the Wi-Fi driver layer log, fw. Txt is file attribute information matching with the Wi-Fi firmware layer log, tcpdump. Pcap is file attribute information matching with the network layer protocol packet log.
In step 305, if the log containing the target keyword is found, the log containing the target keyword is determined to be the target log.
The step is the same as step 204, and the detailed description of step 204 is omitted here.
According to the embodiment of the application, before the logs are screened based on the target keywords, whether the target log files exist in the log files in which the logs generated when the Wi-Fi network has abnormal problems or not is judged, and under the condition that the target log files exist, the logs are screened based on the target keywords, so that the logs can be primarily screened based on file attribute information, the number of the logs screened based on the target keywords is reduced, and the log screening efficiency is improved.
In an actual application scenario, a logging tool may be installed on an electronic device, where the logging tool may be an application program implementing the solution of the present application. 4-1 are exemplary diagrams of a desktop of an electronic device, on which icons, names, etc. of a plurality of applications such as a logging tool, a photographing application, a shopping application, etc. are displayed; if the clicking operation on the icon 2 is received, the method can jump to a grabbing log page shown in fig. 4-2, and prompt characters such as a grabbing log and a plurality of options such as a start option and an end option can be displayed in the grabbing log page; if a click operation of an 'end' option in the capture log page shown in fig. 4-2 is received, the log capture is ended, and the desktop of the electronic device shown in fig. 4-1 is returned; if a clicking operation of a 'start' option in the capture log page shown in fig. 4-2 is received, the method can jump to the capture log page shown in fig. 4-3, and prompt characters such as 'capture log' and a plurality of options such as 'cancel', 'end' can be displayed in the capture log page; if a clicking operation of a cancel option in the log grabbing page shown in fig. 4-3 is received, log grabbing is ended, and a desktop of the electronic device shown in fig. 4-1 is returned; if a click operation of the "end" option in the capture log page shown in fig. 4-3 is received, the method can jump to a selection question type page shown in fig. 4-4, and multiple options such as "selection question type", "return" and the like can be displayed in the selection question type page; if a click operation of selecting a return option in the question type page shown in fig. 4-4 is received, returning to the crawling log page shown in fig. 4-3 or the desktop of the electronic device shown in fig. 4-1; if a click operation of the "select question type" option in the select question type page shown in fig. 4-4 is received, the method can jump to the question type page shown in fig. 4-5, in which the "Wi-Fi network" option is displayed; if a clicking operation on the Wi-Fi network option is received, the method can jump to a problem type page shown in fig. 4-6, and a plurality of problem types such as Wi-Fi network connection abnormality, wi-Fi network surfing abnormality, wi-Fi network direct connection abnormality, personal hot spot abnormality and the like and a return option are displayed on the problem type page shown in fig. 4-6; if a click operation of a 'return' option in the question type page shown in fig. 4-6 is received, returning to the question type page shown in fig. 4-5 or the desktop of the electronic device shown in fig. 4-1; if a clicking operation of any problem type in the problem type pages shown in fig. 4-6 is received, acquiring a target log through the scheme of the application, if the target log is acquired, jumping to the problem detailed description page shown in fig. 4-7, and inputting a problem detailed description and a contact way in the problem detailed description page by a user so as to facilitate the research and development personnel of a log tool to know the detailed situation; if a click operation of a 'return' option in the question detailed description page shown in fig. 4-7 is received, returning to the question type page shown in fig. 4-6 or the desktop of the electronic device shown in fig. 4-1; if a clicking operation of a submit option in the question detailed description page is received, the method can jump to a log submit completion page shown in fig. 4-8, and prompt characters such as submit completion and options such as exit are displayed on the log submit completion page; if a click operation is received on the "exit" option in the log submission completion page, the log tool may be closed. If the target log is not obtained, the method can jump to a page lacking the key log as shown in fig. 4-9, and the page lacking the key log is displayed with prompt files such as 'lacking the key log currently, asking for the reproduction of the problem' and options such as 'cancel', 'start'; if a clicking operation of a cancel option in the page lacking the key log is received, closing the log tool; if a clicking operation of a ' start ' option in the page lacking the key log is received, re-grabbing the log based on the previously selected problem type, and jumping to a grabbing log page shown in fig. 4-10, wherein the grabbing log page displays a ' grabbing log of the XXX type, please reproduce the problem as soon as possible, and if you reproduce the problem, please click prompt characters such as ' complete ', etc. and options such as ' cancel ', ' complete ', etc.; if a click operation of a cancel option in the grabbing log page shown in fig. 4-10 is received, closing the log tool; if a click operation of the "done" option in the crawl log page shown in fig. 4-10 is received, the target log is obtained again based on the scheme of the present application. According to the application, the user can be reminded to grasp more accurate target logs through the pages such as the pages shown in figures 4-1, 4-2, … … and 4-10, the effectiveness of the target logs is guaranteed, and the efficiency of analyzing and solving the abnormal problems is improved.
Referring to fig. 5, a schematic diagram of a log obtaining apparatus according to an embodiment of the present application is shown, for convenience of explanation, only a portion related to the embodiment of the present application is shown.
The log obtaining device includes:
a type obtaining module 51, configured to obtain a problem type to which an abnormal problem of the Wi-Fi network belongs;
a type determining module 52, configured to determine a target log type based on a problem type to which the abnormal problem belongs, where the target log type is a log type that matches the problem type to which the abnormal problem belongs;
the target obtaining module 53 is configured to obtain, based on a problem type to which the abnormal problem belongs and the target log type, a target log from a log generated when the abnormal problem occurs in the Wi-Fi network, where the target log is a log that matches the problem type to which the abnormal problem belongs and the target log type.
Optionally, the target obtaining module 53 includes:
the log searching unit is used for searching a log containing a target keyword from a log generated when the abnormal problem occurs in the Wi-Fi network, wherein the target keyword is a keyword matched with the problem type of the abnormal problem and the target log type;
And the target determining unit is used for determining the log containing the target keyword as the target log if the log containing the target keyword is found.
Optionally, the log searching unit is specifically configured to:
searching a target log file from log files in which a log generated when the abnormal problem occurs in the Wi-Fi network is located, wherein the target log file refers to a log file with file attribute information matched with the target log type, and the file attribute information comprises a file name and a file suffix name;
if the target log file is found and the size of the target log file is larger than a preset threshold, searching a log containing the target keyword from the target log file.
Optionally, the log obtaining device further includes:
and the first execution module is configured to, if the target log is not obtained, return to execute the type obtaining module 51 and the subsequent modules until the target log is obtained or the number of times of return execution reaches a first preset number of times.
Optionally, the log obtaining device further includes:
a question display module for displaying at least one question type;
The above-described type acquisition module 51 is specifically configured to:
and responding to the selection operation of the displayed at least one question type, and determining the question type to which the abnormal question of the Wi-Fi network belongs.
Optionally, the above-mentioned type acquisition module 51 is specifically configured to:
encoding the characters in the abnormal problems to obtain vector representations of the characters in the abnormal problems;
according to the arrangement sequence of the characters in the abnormal problems, vector representations of the characters in the abnormal problems are spliced to obtain a feature map corresponding to the abnormal problems;
and inputting the feature map corresponding to the abnormal problem into a problem type identification network to obtain the problem type of the abnormal problem.
Optionally, the log obtaining device further includes:
the log obtaining module is used for responding to the log grabbing start operation and the log grabbing end operation to obtain the log generated when the Wi-Fi network has the abnormal problem.
Optionally, the log obtaining device further includes:
and the second execution module is used for returning to the execution log acquisition module and the subsequent module if the target log is not acquired until the target log is acquired or the number of times of returning to execution reaches a second preset number of times.
The log obtaining device provided in the embodiment of the present application may be applied to the foregoing method embodiment, and details refer to descriptions of the foregoing method embodiment, which are not repeated herein.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 6, the electronic device 6 of this embodiment includes: one or more processors 60 (only one shown), a memory 61, and a computer program 62 stored in the memory 61 and executable on the at least one processor 60. The processor 60, when executing the computer program 62, implements the steps of the various log acquisition method embodiments described above.
The electronic device may include, but is not limited to, a processor 60, a memory 61. It will be appreciated by those skilled in the art that fig. 6 is merely an example of the electronic device 6 and is not meant to be limiting as the electronic device 6 may include more or fewer components than shown, or may combine certain components, or different components, e.g., the electronic device may further include an input-output device, a network access device, a bus, etc.
The processor 60 may be a central processing unit (Central Processing Unit, CPU), which may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 61 may be an internal storage unit of the electronic device 6, such as a hard disk or a memory of the electronic device 6. The memory 61 may be an external storage device of the electronic device 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the electronic device 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the electronic device 6. The memory 61 is used for storing the computer program and other programs and data required by the electronic device. The memory 61 may also be used for temporarily storing 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-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment 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, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above device may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
The embodiments of the present application also provide a computer readable storage medium storing a computer program, which when executed by a processor implements steps of the above-described respective method embodiments.
Embodiments of the present application also provide a computer program product which, when run on an electronic device, causes the electronic device to perform steps that may be performed in the various method embodiments described above.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
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 application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/electronic device and method may be implemented in other manners. For example, the apparatus/electronic device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, 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 may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
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.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (12)

1. A log obtaining method, comprising:
acquiring a problem type of an abnormal problem of the Wi-Fi network;
determining a target log type based on the problem type of the abnormal problem, wherein the target log type is a log type matched with the problem type of the abnormal problem;
based on the problem type of the abnormal problem and the target log type, acquiring a target log from a log generated when the abnormal problem occurs in the Wi-Fi network, wherein the target log refers to a log matched with the problem type of the abnormal problem and the target log type;
The obtaining, based on the problem type to which the abnormal problem belongs and the target log type, a target log from a log generated when the abnormal problem occurs in the Wi-Fi network includes:
searching a log containing a target keyword from a log generated when the abnormal problem occurs in the Wi-Fi network;
if the log containing the target keyword is found, determining the log containing the target keyword as the target log;
the searching the log containing the target keyword from the log generated when the abnormal problem occurs in the Wi-Fi network comprises the following steps:
searching a target log file from log files in which a log generated when the abnormal problem occurs in the Wi-Fi network is located, wherein the target log file refers to a log file with file attribute information matched with the target log type;
if the target log file is found and the size of the target log file is larger than a preset threshold, searching a log containing the target keyword from the target log file.
2. The log obtaining method according to claim 1, wherein the target keyword refers to a keyword that matches a question type to which the abnormal question belongs and the target log type.
3. The log obtaining method according to claim 2, wherein the file attribute information includes a file name and a file suffix name.
4. A log obtaining method according to any one of claims 1 to 3, further comprising:
and if the target log is not acquired, returning to execute the step and the subsequent steps of acquiring the problem type of the abnormal problem of the Wi-Fi network until the target log is acquired or the number of times of returning execution reaches a first preset number of times.
5. A log obtaining method according to any one of claims 1 to 3, characterized by, before obtaining the problem type to which the abnormal problem of the Wi-Fi network belongs, further comprising:
displaying at least one question type;
the obtaining the problem type of the abnormal problem of the Wi-Fi network comprises the following steps:
and responding to the selection operation of the displayed at least one question type, and determining the question type to which the abnormal question of the Wi-Fi network belongs.
6. A log obtaining method according to any one of claims 1 to 3, wherein the obtaining a problem type to which an abnormal problem of a Wi-Fi network belongs includes:
encoding the characters in the abnormal problems to obtain vector representations of the characters in the abnormal problems;
According to the arrangement sequence of the characters in the abnormal problems, vector representations of the characters in the abnormal problems are spliced to obtain a feature map corresponding to the abnormal problems;
and inputting the feature map corresponding to the abnormal problem into a problem type identification network to obtain the problem type of the abnormal problem.
7. A log obtaining method according to any one of claims 1 to 3, further comprising:
and responding to a log grabbing start operation and a log grabbing end operation, and acquiring a log generated when the Wi-Fi network has the abnormal problem.
8. The log obtaining method according to claim 7, characterized by further comprising:
and if the target log is not obtained, returning to execute the step and the subsequent steps of responding to the log grabbing start operation and the log grabbing end operation and obtaining the log generated when the abnormal problem occurs in the Wi-Fi network until the target log is obtained or the times of returning to execute reach a second preset times.
9. A log obtaining apparatus, characterized by comprising:
the type acquisition module is used for acquiring the problem type of the abnormal problem of the Wi-Fi network;
The type determining module is used for determining a target log type based on the problem type of the abnormal problem, wherein the target log type is a log type matched with the problem type of the abnormal problem;
the target acquisition module is used for acquiring a target log from a log generated when the abnormal problem occurs in the Wi-Fi network based on the problem type of the abnormal problem and the target log type, wherein the target log refers to a log matched with the problem type of the abnormal problem and the target log type;
the target acquisition module includes:
the log searching unit is used for searching a log containing a target keyword from a log generated when the abnormal problem occurs in the Wi-Fi network;
the target determining unit is used for determining the log containing the target keyword as the target log if the log containing the target keyword is found;
the log searching unit is specifically configured to:
searching a target log file from log files in which a log generated when the abnormal problem occurs in the Wi-Fi network is located, wherein the target log file refers to a log file with file attribute information matched with the target log type;
If the target log file is found and the size of the target log file is larger than a preset threshold, searching a log containing the target keyword from the target log file.
10. An electronic 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 log obtaining method according to any of claims 1 to 8 when the computer program is executed.
11. A chip comprising a processor for reading and executing a computer program stored in a memory to perform the steps of the log obtaining method according to any of claims 1 to 8.
12. A computer-readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the log obtaining method according to any one of claims 1 to 8.
CN202210147478.1A 2022-02-17 2022-02-17 Log acquisition method and device, electronic equipment, chip and storage medium Active CN114531340B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210147478.1A CN114531340B (en) 2022-02-17 2022-02-17 Log acquisition method and device, electronic equipment, chip and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210147478.1A CN114531340B (en) 2022-02-17 2022-02-17 Log acquisition method and device, electronic equipment, chip and storage medium

Publications (2)

Publication Number Publication Date
CN114531340A CN114531340A (en) 2022-05-24
CN114531340B true CN114531340B (en) 2023-10-13

Family

ID=81623227

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210147478.1A Active CN114531340B (en) 2022-02-17 2022-02-17 Log acquisition method and device, electronic equipment, chip and storage medium

Country Status (1)

Country Link
CN (1) CN114531340B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022139805A (en) * 2021-03-12 2022-09-26 株式会社島津製作所 Analysis system and presentation method of inspection result by the same, and program

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111475324A (en) * 2020-04-03 2020-07-31 西安广和通无线软件有限公司 Log information analysis method and device, computer equipment and storage medium
CN112306799A (en) * 2020-10-23 2021-02-02 上海传英信息技术有限公司 Abnormal information acquisition method, terminal device and readable storage medium
CN113626227A (en) * 2020-05-06 2021-11-09 深圳Tcl新技术有限公司 Abnormal log information reporting method, intelligent terminal and storage medium
CN113849474A (en) * 2021-09-18 2021-12-28 杭州逗酷软件科技有限公司 Data processing method and device, electronic equipment and readable storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11367009B2 (en) * 2019-07-22 2022-06-21 Chronicle Llc Parsing unlabeled computer security data logs

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111475324A (en) * 2020-04-03 2020-07-31 西安广和通无线软件有限公司 Log information analysis method and device, computer equipment and storage medium
CN113626227A (en) * 2020-05-06 2021-11-09 深圳Tcl新技术有限公司 Abnormal log information reporting method, intelligent terminal and storage medium
CN112306799A (en) * 2020-10-23 2021-02-02 上海传英信息技术有限公司 Abnormal information acquisition method, terminal device and readable storage medium
CN113849474A (en) * 2021-09-18 2021-12-28 杭州逗酷软件科技有限公司 Data processing method and device, electronic equipment and readable storage medium

Also Published As

Publication number Publication date
CN114531340A (en) 2022-05-24

Similar Documents

Publication Publication Date Title
CN111552633A (en) Interface abnormal call testing method and device, computer equipment and storage medium
CN109194689B (en) Abnormal behavior recognition method, device, server and storage medium
CN106569860A (en) Application management method and terminal
CN114154995B (en) Abnormal payment data analysis method and system applied to big data wind control
CN112948224B (en) Data processing method, device, terminal and storage medium
CN111198797A (en) Operation monitoring method and device and operation analysis method and device
CN114531340B (en) Log acquisition method and device, electronic equipment, chip and storage medium
CN111355628A (en) Model training method, business recognition device and electronic device
CN112671878B (en) Block chain information subscription method, device, server and storage medium
CN111314326B (en) Method, device, equipment and medium for confirming HTTP vulnerability scanning host
CN111046393B (en) Vulnerability information uploading method and device, terminal equipment and storage medium
CN110019813A (en) Life insurance case retrieving method, retrieval device, server and readable storage medium storing program for executing
CN112507087A (en) Terminal equipment identification method, equipment, storage medium and device
CN111242256B (en) Information verification method, device and terminal
CN115643044A (en) Data processing method, device, server and storage medium
CN115544558A (en) Sensitive information detection method and device, computer equipment and storage medium
CN111045983B (en) Nuclear power station electronic file management method, device, terminal equipment and medium
CN111222739B (en) Nuclear power station task allocation method and nuclear power station task allocation system
CN113360414A (en) Software testing method, device, readable storage medium and computer program product
CN114398128A (en) Information display method and device
CN113342684A (en) Webpage testing method, device and equipment
WO2020164283A1 (en) Test equipment sharing method and device, storage medium and computer equipment
CN111767544A (en) Multi-frequency replay attack vulnerability determination method, device, equipment and readable storage medium
CN112580038A (en) Anti-virus data processing method, device and equipment
CN114818645B (en) Automatic report generation method, device, equipment and medium based on data body

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