WO2020228289A1 - 日志获取方法、装置、终端及存储介质 - Google Patents

日志获取方法、装置、终端及存储介质 Download PDF

Info

Publication number
WO2020228289A1
WO2020228289A1 PCT/CN2019/118603 CN2019118603W WO2020228289A1 WO 2020228289 A1 WO2020228289 A1 WO 2020228289A1 CN 2019118603 W CN2019118603 W CN 2019118603W WO 2020228289 A1 WO2020228289 A1 WO 2020228289A1
Authority
WO
WIPO (PCT)
Prior art keywords
log
log information
terminal
upload
target
Prior art date
Application number
PCT/CN2019/118603
Other languages
English (en)
French (fr)
Inventor
邹昆伦
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020228289A1 publication Critical patent/WO2020228289A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements

Definitions

  • This application relates to the field of computer technology, and in particular to a log acquisition method, device, terminal and storage medium.
  • the server side usually obtains all logs of the application regularly. If the frequency of obtaining logs is high, it will consume too much network resources and may not necessarily obtain useful information; If the frequency of obtaining logs is low, the time required to obtain each time is too long. The information obtained requires a lot of data processing, and it takes a long time to obtain meaningful information. This makes it difficult to obtain logs in the prior art. Low efficiency.
  • This application provides a log acquisition method, the method includes:
  • the log information with the number of occurrences greater than or equal to the first preset number of the plurality of log information is log information with the first upload priority, and it is determined that the number of occurrences in the plurality of log information is less than the first preset number and
  • the log information greater than or equal to the second preset number of times is the log information of the second upload priority, wherein the first upload priority is higher than the second upload priority;
  • the terminal If the terminal is in the preset operating state, upload the log information of the second upload priority to the server of the target application; if the terminal is not in the preset operating state, upload the log information of the second upload priority
  • the log information is stored in the terminal.
  • the method further includes:
  • a message for adjusting the transmission frequency of the instruction to obtain the log is sent.
  • the sending a message for adjusting the sending frequency of the instruction to obtain the log according to the first quantity and/or the second quantity includes:
  • a first message is sent, where the first message is used to increase the sending frequency of the log acquisition instruction;
  • a second message is sent, where the second message is used to reduce the frequency of sending the log acquisition instruction.
  • the obtaining the target log of the target application includes:
  • the obtaining the target log of the target application includes:
  • the target application is an application with an operating frequency greater than a preset operating frequency and/or an operating time greater than a preset operating time.
  • the low power consumption operating state includes a charging standby state
  • the high-rate transmission state is a WIFI connection state
  • This application also provides a log acquisition device, which includes:
  • the obtaining module is configured to obtain the target log of the target application from the terminal according to the log obtaining instruction when receiving the log obtaining instruction;
  • a statistics module configured to count the number of occurrences of each log information among the multiple log information contained in the target log
  • the determining module is configured to determine that the log information with the number of occurrences greater than or equal to the first preset number among the plurality of log information is log information with the first upload priority, and determine that the number of occurrences in the plurality of log information is less than the first upload priority.
  • a log information of a preset number of times and greater than or equal to a second preset number of times is log information of a second upload priority, wherein the first upload priority is higher than the second upload priority;
  • the first upload module is configured to upload the log information of the first upload priority to the server of the target application, and delete the log information of the terminal that is the same as the log information of the first upload priority;
  • a judging module configured to judge whether the terminal is in a preset operating state, and the preset operating state is a low-power operating state or a high-rate transmission state;
  • the second upload module is configured to upload the log information of the second upload priority to the server of the target application if the terminal is in the preset operating state, and if the terminal is not in the preset operating state, upload all The log information of the second upload priority is stored in the terminal.
  • the device further includes a sending module, and the sending module is configured to:
  • a message for adjusting the transmission frequency of the instruction to obtain the log is sent.
  • the sending by the sending module, according to the first quantity and/or the second quantity, sending a message for adjusting the sending frequency of the instruction to obtain the log includes:
  • a first message is sent, where the first message is used to increase the sending frequency of the log acquisition instruction;
  • a second message is sent, where the second message is used to reduce the frequency of sending the log acquisition instruction.
  • the obtaining module obtaining the target log of the target application includes:
  • the obtaining module obtaining the target log of the target application includes:
  • the target application is an application with an operating frequency greater than a preset operating frequency and/or an operating time greater than a preset operating time.
  • the low power consumption operating state includes a charging standby state
  • the high-rate transmission state is a WIFI connection state
  • the present application also provides a terminal, the terminal includes a memory and a processor, the memory is configured to store at least one instruction, and the processor is configured to execute the at least one instruction to implement the log acquisition method described in any embodiment .
  • the present application also provides a non-volatile readable storage medium, wherein the non-volatile readable storage medium stores at least one instruction, and when the at least one instruction is executed by a processor, the The described log acquisition method.
  • this application provides a log acquisition method, device, terminal, and storage medium.
  • the target log of the target application is acquired from the terminal according to the instruction to acquire the log;
  • this application obtains the target log of the target application after receiving the instruction, and selectively uploads multiple log information contained in the target log according to different priorities, the log information with high priority can be transmitted to the target application in time.
  • Server so that the server of the target application can obtain important information in time, and save the log information with low priority locally when the terminal is not in the preset running state, so as to avoid uploading too much irrelevant information, and avoiding too much information to be transmitted at the same time.
  • System resources affect system operation, so that the application server can obtain valuable log information more efficiently, save terminal resources, and upload priority log information to the target application server in time when the terminal is in the preset running state. Make the server save complete log information when the terminal is running.
  • FIG. 1 is a flowchart of a log acquisition method provided by an embodiment of the present application
  • Fig. 2 is a functional module diagram of a log obtaining device provided by an embodiment of the present application
  • Fig. 3 is a schematic structural diagram of a terminal implementing a preferred embodiment of the log acquisition method according to the present application.
  • FIG. 1 is a flowchart of a log acquisition method provided by an embodiment of the application. According to different needs, the order of the steps in the flowchart can be changed, and some steps can be omitted.
  • the method described in this application is applied to a terminal, and the terminal may be an electronic device such as a mobile phone or a tablet computer.
  • the instructions for obtaining logs in this embodiment are used to obtain logs generated during application running.
  • the target application is the application indicated by the instruction. For example, if the server of the first application sends an instruction to obtain the log to the client of the first application, the target log of the first application is obtained from the terminal.
  • the target application is an application with an operating frequency greater than a preset operating frequency and/or an operating time greater than a preset operating time.
  • the specific values of the preset operating frequency and the preset operating time can be preset according to needs.
  • the running frequency of the first application is greater than the preset running frequency and/or the running time of the first application is greater than the preset running time, then the The target log of the first application.
  • the acquired target log of the target application may be a log whose error reporting type is a preset type, for example, the error reporting type is a type related to the code of the application.
  • the acquired target log may also be a log containing preset keywords.
  • acquiring the target log of the target application includes: acquiring the log generated by the operation of the application after the last time the instruction to acquire the log is received as the target log.
  • the last time the log acquisition instruction is received may be after the target log acquisition last time. After each log acquisition instruction is received, the log newly generated by the target application is acquired, and the acquired log is not acquired, reducing Redundancy of information obtained.
  • the obtaining the target log of the target application includes:
  • the version information of the target application is acquired, and it can be determined whether the target application is updated according to the version information of the target application. Specifically, it can be judged whether the version information of the target application is consistent with the previously obtained version information; or it can be judged whether the target application has a version update mark, and if there is a version update mark, it can be determined that the target application has an update.
  • the updated code module of the target application is obtained.
  • the updated code module of the target application may include a newly added code module after the target application is updated, or a code module repaired after the application target is updated (that is, there is a modified code module).
  • the log related to the updated code module of the application can be obtained, so as to know whether the application has malfunctions or other information after the update. After the application is updated, it is beneficial to Fix the problem in time to improve the problem of running after the application is released.
  • S12 Count the number of occurrences of each log information among the multiple pieces of log information included in the target log.
  • the acquired target log may include multiple pieces of log information.
  • the upload priority can be used to identify the upload sequence of each log information among the multiple log information. For example, when the upload priority is high, upload first, and when the upload priority is low, upload at other designated times.
  • the cumulative number of occurrences of each log information in the preset statistical time (such as 2 hours, or 6 hours, or one week, or one month) in the multiple log information is counted to obtain the appearance of each log information frequency.
  • the specific values of the first preset number of times and the second preset number of times can be preset as needed, and the value of the first preset number of times is greater than the value of the second preset number of times.
  • the upload priority of each log information contained in the target log can also be determined by the following method:
  • the target log Determine whether there is a log containing the first keyword in the target log, and if there is a log containing the first keyword, determine that the log containing the first keyword is a log of the first upload priority, and is not the first upload priority
  • the other logs are the logs of the second upload priority. Wherein, the upload priority identified by the first upload priority is higher than the second upload priority.
  • the upload priority of these log information is the first upload priority, which is higher than the second upload priority. Uploading of log information is helpful to quickly solve recurring problems, or to obtain user deterministic operating habits in time.
  • the log information with the first priority uploading priority is uploaded to the application server first, so that application developers can obtain application-related problems in time and solve them in time, saving storage space on the terminal. , Deleting the same log information in the terminal as the log information of the first upload priority can also further release the occupied storage space on the terminal.
  • S15 Determine whether the terminal is in a preset operating state, and the preset operating state is a low-power operating state or a high-rate transmission state.
  • Determining whether the terminal is in the preset running state may include determining whether the number of applications launched when the terminal is running is lower than the preset number of running applications, whether the hardware resources consumed by the terminal are less than 30% of the hardware resources that the terminal can support, etc. .
  • judging whether the terminal is in a preset operating state is used to determine whether the terminal is in a state that can continuously upload log information, or judging the operating state of the terminal is used to determine whether the terminal currently has more schedulable resources. For example, it is determined whether the number of applications launched when the terminal is running is less than three.
  • the terminal When the terminal is in a low-power operation state, the terminal does not occupy excessive system resources. When the terminal is in a high-rate transmission state, the terminal can support continuous and fast upload, saving time for uploading logs and increasing sales of uploaded logs.
  • the log with the upload priority of the second upload priority is saved, and useful log information can be saved, so that it can be uploaded when needed.
  • uploading the log information with the upload priority of the second upload priority to the application server can enable the developer to obtain the log information in time, and upload the log information The process does not affect the use of other applications, and avoids causing the terminal to freeze when running.
  • the low power consumption operating state includes a charging standby state
  • the high-rate transmission state is a WIFI connection state
  • the terminal when the terminal is in the WIFI connection state, the network status of the terminal is relatively stable, and the cost of network transmission is saved; when the terminal is in the charging standby state, the terminal will not have low battery or no power to continue transmission. The situation, that is, in this state, the terminal can support stable data transmission.
  • the log information of the second upload priority is uploaded to the server of the application, which is conducive to the fast and stable transmission of data in the log transmission process .
  • the method further includes:
  • a message for adjusting the transmission frequency of the instruction to obtain the log is sent.
  • the sending, according to the first number and/or the second number, the message for adjusting the sending frequency of the instruction to obtain the log includes:
  • a first message is sent, where the first message is used to increase the sending frequency of the log acquisition instruction;
  • a second message is sent, where the second message is used to reduce the frequency of sending the log acquisition instruction.
  • the upper limit of the preset number of logs and the lower limit of the preset number of logs may be determined according to the type of application.
  • a message for adjusting the sending frequency of the instruction may be sent to the server of the application, so that the server sends an instruction for obtaining logs to the client according to the adjusted frequency.
  • the target log of the target application is acquired from the terminal according to the instruction to acquire the log; each log of the multiple log information contained in the target log is counted The number of occurrences of information; determining that the number of occurrences of the plurality of log information is greater than or equal to the first preset number of log information as the log information of the first upload priority, and determining that the number of occurrences of the plurality of log information is less than the first
  • the log information of a preset number of times and greater than or equal to the second preset number of times is log information of the second upload priority, wherein the first upload priority is higher than the second upload priority; the first upload The priority log information is uploaded to the server of the target application, and the log information in the terminal that is the same as the log information of the first upload priority is deleted; it is determined whether the terminal is in a preset operating state, and the preview Suppose the operating state is a low-power operating state or a high-rate transmission state
  • this application obtains the target log of the target application after receiving the instruction, and selectively uploads multiple log information contained in the target log according to different priorities, the log information with high priority can be transmitted to the target application in time.
  • Server so that the server of the target application can obtain important information in time, and save the log information with low priority locally when the terminal is not in the preset running state, so as to avoid uploading too much irrelevant information, and avoiding too much information to be transmitted at the same time.
  • System resources affect system operation, so that the application server can obtain valuable log information more efficiently, save terminal resources, and upload priority log information to the target application server in time when the terminal is in the preset running state. Make the server save complete log information when the terminal is running.
  • FIG. 2 is a functional module diagram of a log acquisition device provided in an embodiment of this application.
  • the log acquisition device 20 includes an acquisition module 210, a statistics module 220, a determination module 230, a first upload module 240, a judgment module 250, and a second upload module 260.
  • the module referred to in this application refers to a series of computer-readable instruction segments that can be executed by the processor of the terminal and can complete fixed functions, which are stored in the memory of the terminal.
  • the terminal may be a mobile phone, a tablet computer, etc. Electronic equipment. In this embodiment, the function of each module will be described in detail in subsequent embodiments.
  • the obtaining module 210 is configured to obtain the target log of the target application from the terminal according to the log obtaining instruction when receiving the log obtaining instruction.
  • the instructions for obtaining logs in this embodiment are used to obtain logs generated during application running.
  • the application is the application indicated by the instruction.
  • the target application is the application indicated by the instruction. For example, if the server of the first application sends an instruction to obtain the log to the client of the first application, the target log of the first application is obtained from the terminal.
  • the target application is an application with an operating frequency greater than a preset operating frequency and/or an operating time greater than a preset operating time.
  • the specific values of the preset operating frequency and the preset operating time can be preset according to needs.
  • the running frequency of the first application is greater than the preset running frequency and/or the running time of the first application is greater than the preset running time, then the The target log of the first application.
  • the acquired target log of the target application may be a log whose error reporting type is a preset type, for example, the error reporting type is a type related to the code of the application.
  • the acquired target log may also be a log containing preset keywords.
  • the obtaining module obtaining the target log of the target application includes: obtaining the log generated by the operation of the application after the last time the instruction to obtain the log is received is the target log .
  • the last time the log acquisition instruction is received may be after the target log acquisition last time. After each log acquisition instruction is received, the log newly generated by the target application is acquired, and the acquired log is not acquired, reducing Redundancy of information obtained.
  • the obtaining module obtaining the target log of the target application includes:
  • the version information of the target application is acquired, and it can be determined whether the target application is updated according to the version information of the target application. Specifically, it can be judged whether the version information of the target application is consistent with the previously obtained version information; or it can be judged whether the target application has a version update mark, and if there is a version update mark, it can be determined that the target application has an update.
  • the updated code module of the target application is obtained.
  • the updated code module of the target application may include a newly added code module after the target application is updated, or a code module repaired after the application target is updated (that is, there is a modified code module).
  • the log related to the updated code module of the application can be obtained, so as to know whether the application has malfunctions or other information after the update. After the application is updated, it is beneficial to Fix the problem in time to improve the problem of running after the application is released.
  • the statistics module 220 is configured to count the number of occurrences of each log information among the multiple log information included in the target log.
  • the acquired target log may include multiple pieces of log information.
  • the determining module 230 is configured to determine that the log information with the number of occurrences greater than or equal to the first preset number of the multiple pieces of log information is the log information of the first upload priority, and determine that the number of occurrences in the multiple pieces of log information is less than the number of occurrences.
  • the log information of the first preset number of times and greater than or equal to the second preset number of times is the log information of the second upload priority, wherein the first upload priority is higher than the second upload priority.
  • the upload priority can be used to identify the upload sequence of each log information among the multiple log information. For example, when the upload priority is high, upload first, and when the upload priority is low, upload at other designated times.
  • the cumulative number of occurrences of each log information in the preset statistical time (such as 2 hours, or 6 hours, or one week, or one month) in the multiple log information is counted to obtain the appearance of each log information frequency.
  • the specific values of the first preset number of times and the second preset number of times can be preset as needed, and the value of the first preset number of times is greater than the value of the second preset number of times.
  • the upload priority of these log information is the first upload priority, which is higher than the second upload priority. Uploading of log information is helpful to quickly solve recurring problems, or to obtain user deterministic operating habits in time.
  • the first upload module 240 is configured to upload the log information of the first upload priority to the server of the target application, and delete the log information of the terminal that is the same as the log information of the first upload priority.
  • the log information with the upload priority of the first upload priority is first uploaded to the server of the target application, so that application developers can obtain application-related problems in a timely manner and solve them in a timely manner, thereby saving time on the terminal.
  • Storage space, deleting the same log information in the terminal as the log information of the first upload priority can also further release the occupied storage space on the terminal.
  • the judging module 250 is configured to judge whether the terminal is in a preset operating state, and the preset operating state is a low-power operating state or a high-rate transmission state.
  • Determining whether the terminal is in the preset running state may include determining whether the number of applications launched when the terminal is running is lower than the preset number of running applications, whether the hardware resources consumed by the terminal are less than 30% of the hardware resources that the terminal can support, etc. .
  • judging whether the terminal is in a preset operating state is used to determine whether the terminal is in a state that can continuously upload log information, or judging the operating state of the terminal is used to determine whether the terminal currently has more schedulable resources. For example, it is determined whether the number of applications launched when the terminal is running is less than three.
  • the terminal When the terminal is in a low-power operation state, the terminal does not occupy excessive system resources. When the terminal is in a high-rate transmission state, the terminal can support continuous and fast upload, saving the time of uploading logs and increasing the sales volume of uploaded logs.
  • the second upload module 260 is configured to upload the log information of the second upload priority to the server of the target application if the terminal is in the preset operating state, and if the terminal is not in the preset operating state, The log information of the second upload priority is stored in the terminal.
  • the log with the upload priority of the second upload priority is saved, and useful log information can be saved, so that it can be uploaded when needed.
  • uploading the log information with the upload priority of the second upload priority to the server of the target application can enable the developer to obtain the log information in time and upload the log The process does not affect the use of other applications, and avoids causing the terminal to freeze when running.
  • the low power consumption operating state includes a charging standby state
  • the high-rate transmission state is a WIFI connection state
  • the terminal when the terminal is in the WIFI connection state, the network status of the terminal is relatively stable, and the cost of network transmission is saved; when the terminal is in the charging standby state, the terminal will not have low battery or no power to continue transmission. The situation, that is, in this state, the terminal can support stable data transmission.
  • the log information of the second upload priority is uploaded to the server of the application, which is conducive to the fast and stable transmission of data in the log transmission process .
  • the device further includes a sending module, and the sending module is configured to:
  • a message for adjusting the transmission frequency of the instruction to obtain the log is sent.
  • the sending, according to the first number and/or the second number, the message for adjusting the sending frequency of the instruction to obtain the log includes:
  • a first message is sent, where the first message is used to increase the sending frequency of the log acquisition instruction;
  • a second message is sent, where the second message is used to reduce the frequency of sending the log acquisition instruction.
  • the upper limit of the preset number of logs and the lower limit of the preset number of logs may be determined according to the type of application.
  • a message for adjusting the transmission frequency of the instruction to obtain the log is sent.
  • the sending, according to the first number and/or the second number, the message for adjusting the sending frequency of the instruction to obtain the log includes:
  • a first message is sent, where the first message is used to increase the sending frequency of the log acquisition instruction;
  • a second message is sent, where the second message is used to reduce the frequency of sending the log acquisition instruction.
  • the upper limit of the preset number of logs and the lower limit of the preset number of logs may be determined according to the type of application.
  • a message for adjusting the sending frequency of the instruction may be sent to the server of the application, so that the server sends an instruction for obtaining logs to the client according to the adjusted frequency.
  • the log acquisition device obtaineds the target log of the target application from the terminal by the acquisition module when receiving the instruction to acquire the log; the statistics module counts multiple pieces of log information contained in the target log The number of occurrences of each log information in the log information; the determining module determines that the log information with the number of occurrences greater than or equal to the first preset number of the plurality of log information is the log information of the first upload priority, and determines that among the plurality of log information The log information whose number of occurrences is less than the first preset number of times and greater than or equal to the second preset number of times is log information of the second upload priority, wherein the first upload priority is higher than the second upload priority; The first upload module uploads the log information of the first upload priority to the server of the target application, and deletes the same log information in the terminal as the log information of the first upload priority; the judgment module determines Whether the terminal is in a preset operating state, and the preset operating state is a low-power operating state or a high-rate transmission
  • this application obtains the target log of the target application after receiving the instruction, and selectively uploads multiple log information contained in the target log according to different priorities, the log information with high priority can be transmitted to the target application in time.
  • Server so that the server of the target application can obtain important information in time, and save the log information with low priority locally when the terminal is not in the preset running state, so as to avoid uploading too much irrelevant information, and avoiding too much information to be transmitted at the same time.
  • System resources affect the operation of the system, so that the application server can obtain valuable log information more efficiently, save terminal resources, and upload low-priority log information to the target application server in time when the terminal is in the preset running state. Make the server save complete log information when the terminal is running.
  • the aforementioned integrated unit implemented in the form of a software function module may be stored in a non-volatile readable storage medium.
  • the above-mentioned software function module is stored in a non-volatile readable storage medium, and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) execute each of this application All or part of the steps of the method described in the embodiment.
  • the terminal 3 includes at least one sending device 31, at least one memory 32, at least one processor 33, at least one receiving device 34, and at least one communication bus.
  • the communication bus is used to realize the connection and communication between these components.
  • the terminal 3 is a device that can automatically perform numerical calculation and/or information processing in accordance with pre-set or stored instructions. Its hardware includes, but is not limited to, a microprocessor and an application specific integrated circuit (ASIC) , Field-Programmable Gate Array (FPGA), Digital Processor (Digital Signal Processor, DSP), embedded equipment, etc.
  • the terminal 3 may also include network equipment and/or user equipment.
  • the network device includes, but is not limited to, a single network server, a server group composed of multiple network servers, or a cloud composed of a large number of hosts or network servers based on Cloud Computing, where cloud computing is distributed computing One type, a super virtual computer composed of a group of loosely coupled computer sets.
  • the terminal 3 can be, but is not limited to, any electronic product that can interact with a user through a keyboard, a touch panel, or a voice control device, for example, a tablet computer, a smart phone, a monitoring device, and other terminals.
  • the network where the terminal 3 is located includes, but is not limited to, the Internet, a wide area network, a metropolitan area network, a local area network, a virtual private network (Virtual Private Network, VPN), etc.
  • the receiving device 34 and the sending device 31 may be wired sending ports or wireless devices, for example, including an antenna device, which is used for data communication with other devices.
  • the memory 32 is used to store program codes.
  • the memory 32 may be a circuit with a storage function without a physical form in an integrated circuit.
  • the memory 32 may also be a memory in physical form, such as a memory stick, a TF card (Trans-flash Card), a smart media card (smart media card), a secure digital card (secure digital card), and a flash memory card. (flash card) and other storage devices.
  • the processor 33 may include one or more microprocessors and digital processors.
  • the processor 33 can call the program code stored in the memory 32 to perform related functions.
  • the various modules described in FIG. 2 are program codes stored in the memory 32 and executed by the processor 33 to implement a log acquisition method.
  • the processor 33 is also called a central processing unit (CPU, Central Processing Unit), which is a very large-scale integrated circuit, which is a computing core (Core) and a control core (Control Unit).
  • CPU Central Processing Unit
  • Core computing core
  • Control Unit Control Unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)
  • Telephone Function (AREA)

Abstract

本申请提供一种日志获取方法，包括：当接收到获取日志的指令时，从终端获取目标应用的目标日志；统计目标日志包含的多条日志信息中每条日志信息的出现次数；确定出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，确定出现次数小于第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息；将第一上传优先级的日志信息上传，删除终端中与第一上传优先级的日志信息相同的日志信息；判断终端是否为预设运行状态；若是，将第二上传优先级的日志信息上传，若否，将第二上传优先级的日志信息保存在终端。本申请还公开了一种日志获取装置、终端和非易失性可读存储介质。本申请能够提高日志获取的效率。

Description

日志获取方法、装置、终端及存储介质
本申请要求于2019年05月15日提交中国专利局，申请号为201910403713.5，发明名称为“日志获取方法、装置、终端及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种日志获取方法、装置、终端及存储介质。
背景技术
随着技术的发展，各种类型的应用软件越来越多，当应用软件在运行时都会输出日志，通过日志可以获取应用软件运行的各种状况，有利于对应用进行优化。然而，在现有技术中进行日志采集时，通常是由服务器端定时获取应用的所有日志，若获取日志的频率较高，会消耗过多的网络资源，且不一定能得到有用的信息；若获取日志的频率较低，则每次获取的时间过长，得到的信息多却需要经过大量的数据处理，花费较长时间才获取到有意义的信息，这都使得现有技术中获取日志的效率较低。
发明内容
鉴于以上内容，有必要提供一种日志获取方法、装置、终端及存储介质，可提高日志获取的效率。
本申请提供一种日志获取方法，所述方法包括：
当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；
统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；
确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；
将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与 所述第一上传优先级的日志信息相同的日志信息；
判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；
若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
在本申请可选实施例中，所述方法还包括：
获取所述第一上传优先级的日志信息的第一数量和/或所述第二上传优先级的日志信息的第二数量；
根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
在本申请可选实施例中，所述根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息包括：
若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
在本申请可选实施例中，所述获取目标应用的目标日志包括：
获取所述目标应用的版本信息；
根据所述目标应用的版本信息判断所述目标应用是否存在更新；
若所述目标应用存在更新，获取所述目标应用更新后的代码模块；
获取与所述目标应用更新后的代码模块相关的日志为所述目标日志。
在本申请可选实施例中，所述获取目标应用的目标日志包括：
获取最近一次接收到所述获取日志的指令之后所述应用运行所产生的日志为所述目标日志。
在本申请可选实施例中，所述目标应用为运行频率大于预设运行频率和/或运行时间大于预设运行时间的应用。
在本申请可选实施例中，所述低功耗运行状态包括充电待机状态，所述高速率传输状态为WIFI连接状态。
本申请还提供一种日志获取装置，所述装置包括：
获取模块，用于当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；
统计模块，用于统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；
确定模块，用于确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；
第一上传模块，用于将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；
判断模块，用于判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；
第二上传模块，用于若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
在本申请可选实施例中，所述装置还包括发送模块，所述发送模块用于：
获取所述第一上传优先级的日志信息的第一数量和/或所述第二上传优先级的日志信息的第二数量；
根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
在本申请可选实施例中，所述发送模块根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息包括：
若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
在本申请可选实施例中，所述获取模块获取目标应用的目标日志包括：
获取所述目标应用的版本信息；
根据所述目标应用的版本信息判断所述目标应用是否存在更新；
若所述目标应用存在更新，获取所述目标应用更新后的代码模块；
获取与所述目标应用更新后的代码模块相关的日志为所述目标日志。
在本申请可选实施例中，所述获取模块获取目标应用的目标日志包括：
获取最近一次接收到所述获取日志的指令之后所述应用运行所产生的日志为所述目标日志。
在本申请可选实施例中，所述目标应用为运行频率大于预设运行频率和/或运行时间大于预设运行时间的应用。
在本申请可选实施例中，所述低功耗运行状态包括充电待机状态，所述高速率传输状态为WIFI连接状态。
本申请还提供一种终端，所述终端包括存储器及处理器，所述存储器用于存储至少一个指令，所述处理器用于执行所述至少一个指令以实现任意实施例中所述的日志获取方法。
本申请还提供一种非易失性可读存储介质，其特征在于，所述非易失性可读存储介质存储有至少一个指令，所述至少一个指令被处理器执行时实现任意实施例中所述的日志获取方法。
由以上技术方案看出，本申请提供一种日志获取方法、装置、终端及存储介质，当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。由于本申请在接收指令之后，获取目标应用的目标日志，并对目标日志包含的多条日志信息根据不同的优先级选择性的上传，使得优先级高的日志信息能够及时地传到目标应用的服务器，从而目标应用的服务器能够及时地获取到重要信息，将优先级低的日志信息在终端不为预设运行状态时保存在本地，避免上传过多无关信息，也避免同时传输过多信息占用系统资源影响系统运行，使应用的服务器更高效的获取有价值的日志信息，节省终端资源，将优先级地的日志信息在终端为预设运行状态时及时上传至目标应用的服务器可以在不影响终端运行的情况下使服务器保存完整的日志信息。
附图说明
图1是本申请实施例提供的日志获取方法的流程图；
图2是本申请实施例提供的日志获取装置的功能模块图；
图3是本申请实现日志获取方法的较佳实施例的终端的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
为使本申请的上述目的、特征和优点能够更加明显易懂，下面结合附图和具体实施方式对本申请作进一步详细的说明。
如图1所示，图1为本申请实施例提供的一种日志获取方法的流程图。根据不同的需求，该流程图中步骤的顺序可以改变，某些步骤可以省略。
S11，当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志。
本申请所述的方法应用于终端，所述终端可以是手机、平板电脑等电子设备。
本实施例中所述获取日志的指令用于获取应用运行过程中产生的日志。
所述目标应用为所述指令指示的应用。例如，第一应用的服务器向第一应用的客户端发送获取日志的指令，则从终端获取第一应用的目标日志。
一种可能的实施例中，所述目标应用为运行频率大于预设运行频率和/或运行时间大于预设运行时间的应用。
其中，预设运行频率和预设运行时间的具体值可以根据需要预先设定。
例如，当获取到接收到获取第一应用的服务器发送的日志的指令时，若第一应用的运行频率大于预设运行频率和/或第一应用的运行时间大于预设运行时间时，才获取第一应用的目标日志。
一种可能的实施例中，所获取的目标应用的目标日志可以是报错类型为预设类型的日志，例如，报错类型为与应用的代码相关的类型。或者，所获取的目标日志也可以是包含预设关键字的日志。
可选的，在本申请另一实施例中，获取目标应用的目标日志包括：获取最近一次接收到所述获取日志的指令之后所述应用运行所产生的日志为所述目标日志。
最近一次接收到所述获取日志的指令之后可以是上一次获取目标日志之后，则在每次 接收到获取日志的指令之后，获取目标应用新产生的日志，不对已获取过的日志进行获取，减少获取到的信息的冗余。
可选的，在本申请另一实施例中，所述获取目标应用的目标日志包括：
获取所述目标应用的版本信息；
根据所述目标应用的版本信息判断所述目标应用是否存在更新；
若所述目标应用存在更新，获取所述目标应用更新后的代码模块；
获取与所述目标应用更新后的代码模块相关的日志为所述目标日志。
通常，每个应用在编码发布之后，都会存在一个版本与其对应。在本实施例中，获取目标应用的版本信息，可以根据目标应用的版本信息判断该目标应用是否存在更新。具体的，可以判断目标应用的版本信息是否与前一次获取到的版本信息一致；或者可以判断目标应用是否存在版本更新标记，若存在版本更新标记，则可以确定该目标应用存在更新。
在本实施例中，若该目标应用存在更新，获取目标应用更新后的代码模块。其中，目标应用更新后的代码模块可以包括目标应用更新之后新增的代码模块，或者是应目标用更新之后修复的代码模块(即存在修改的代码模块)。
在本实施例中，在接收到获取日志指令之后，获取与应用更新后的代码模块相关的日志，可以及时地了解应用在更新之后是否存在故障问题等信息，在应用更新之后，有利于对出现的问题及时修复，进而提高应用发布之后运行的问题。
S12，统计所述目标日志包含的多条日志信息中每条日志信息的出现次数。
在本实施例中，获取到的目标日志可以包括多条日志信息。
S13，确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级。
其中，上传优先级可以用于标识多条日志信息中各条日志信息上传的先后。例如，上传优先级为高时，优先上传，上传优先级为低时，在其他指定时间上传。
在本实施例中，统计多条日志信息中每条日志信息在预设的统计时间(如2小时，或者6小时，或者一周，或者一个月)内的累计出现次数得到每条日志信息的出现次数。
其中，第一预设次数和第二预设次数的具体值可以根据需要预先设定，并且，所述第一预设次数的值大于第二预设次数的值。
在本申请其他实施例中，还可以通过以下方法判断目标日志中包含的各条日志信息的上传优先级：
判断所述目标日志中是否存在包含第一关键字的日志，若存在包含第一关键字的日志，确定包含第一关键字的日志为第一上传优先级的日志，以及第一上传优先级以外的其他日志为第二上传优先级的日志。其中，第一上传优先级标识的上传优先级高于第二上传优先级。
由于出现次数较多的日志信息表示应用运行过程中重复出现相同的问题，因此，在本实施例中，可以确定这些日志信息的上传优先级为第一上传优先级，优先于第二上传优先级的日志信息上传，有利于快速解决重复出现的问题，或者及时获取用户确定性的操作习惯。
S14，将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息。
在本申请实施例中，将上传优先级为第一优先级的日志信息优先上传至应用的服务器，可以使应用的开发人员及时获取到应用的相关问题并及时地解决，节省终端上的存储空间，删除终端中与第一上传优先级的日志信息相同的日志信息，也可以进一步释放终端上被占用的存储空间。
S15，判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态。
判断终端是否为预设运行状态可以包括判断终端运行时所启动应用的数量是否低于预设应用运行数量，终端所消耗的硬件资源是否低于终端可支持的硬件资源的百分之三十等。
在本实施例中，判断终端是否为预设运行状态用于确定终端是否为可以连续上传日志信息的状态，或者，判断终端的运行状态用于确定终端当前的可调度资源是否较多。例如，判断终端运行时所启动应用的数量是否小于3个。
当终端处于低功耗运行状态，终端未被占用过多的系统资源。当终端处于高速率传输状态时，终端可以支持连续快速的上传，节省上传日志的时间以及提高上传日志的销量。
S16，若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
在本实施例中，将上传优先级为第二上传优先级的日志保存，可以将有用的日志信息进行保存，便于在需要获取时再上传。
在本申请实施例中，当终端为预设运行状态时，将上传优先级为第二上传优先级的日志信息上传至应用的服务器，可以使开发人员及时地获取到日志信息，并且上传日志的过程中不影响其他应用的使用，避免引起终端运行时的卡顿。
进一步的，在本申请另一实施例中，所述低功耗运行状态包括充电待机状态，所述高速率传输状态为WIFI连接状态。
在本实施例中，当终端为WIFI连接状态时，终端的网络状态较稳定，且节省网络传输的费用；当终端为充电待机状态时，终端不会出现电量过低或者没电无法续传的情况，即在此状态下，终端可以支持稳定的数据传输。
因此，在本实施例中，当终端为WIFI连接状态以及充电待机状态时，将第二上传优先级的日志信息上传至所述应用的服务器，有利于日志传输过程中的数据能够快速稳定的传输。
可选的，在本申请另一实施例中，所述方法还包括：
获取所述第一上传优先级的日志信息的第一数量和/或所述第二上传优先级的日志信息的第二数量；
根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
所述根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息包括：
若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
具体的，所述预设日志数量上限值以及预设日志数量下限值可以根据应用的类型来确定。
在本实施例中，可以向应用的服务器发送调整所述指令的发送频率的消息，使得服务器根据调整后的频率向客户端发送获取日志的指令。
在本实施例中，通过对第一上传优先级的日志信息以及第二上传优先级的日志信息的数量获取，进而发送调整指令的发送频率的消息，能够避免频繁获取日志却获取不到的情况，也避免了由于日志获取频率过低，获取间隔时间过长导致的不能及时上传重要日志的问题。
本实施例所提供的日志获取方法，当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且 大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。由于本申请在接收指令之后，获取目标应用的目标日志，并对目标日志包含的多条日志信息根据不同的优先级选择性的上传，使得优先级高的日志信息能够及时地传到目标应用的服务器，从而目标应用的服务器能够及时地获取到重要信息，将优先级低的日志信息在终端不为预设运行状态时保存在本地，避免上传过多无关信息，也避免同时传输过多信息占用系统资源影响系统运行，使应用的服务器更高效的获取有价值的日志信息，节省终端资源，将优先级地的日志信息在终端为预设运行状态时及时上传至目标应用的服务器可以在不影响终端运行的情况下使服务器保存完整的日志信息。
如图2所示，图2为本申请实施例提供一种日志获取装置的功能模块图。日志获取装置20包括获取模块210、统计模块220、确定模块230、第一上传模块240、判断模块250和第二上传模块260。本申请所称的模块是指一种能够被终端的处理器所执行并且能够完成固定功能的一系列计算机可读指令段，其存储在终端的存储器中，所述终端可以是手机、平板电脑等电子设备。在本实施例中，关于各模块的功能将在后续的实施例中详述。
获取模块210，用于当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志。
本实施例中所述获取日志的指令用于获取应用运行过程中产生的日志。
所述应用为所述指令指示的应用。
所述目标应用为所述指令指示的应用。例如，第一应用的服务器向第一应用的客户端发送获取日志的指令，则从终端获取第一应用的目标日志。
一种可能的实施例中，所述目标应用为运行频率大于预设运行频率和/或运行时间大于预设运行时间的应用。
其中，预设运行频率和预设运行时间的具体值可以根据需要预先设定。
例如，当获取到接收到获取第一应用的服务器发送的日志的指令时，若第一应用的 运行频率大于预设运行频率和/或第一应用的运行时间大于预设运行时间时，才获取第一应用的目标日志。
一种可能的实施例中，所获取的目标应用的目标日志可以是报错类型为预设类型的日志，例如，报错类型为与应用的代码相关的类型。或者，所获取的目标日志也可以是包含预设关键字的日志。
可选的，在本申请另一实施例中，所述获取模块获取目标应用的目标日志包括：获取最近一次接收到所述获取日志的指令之后所述应用运行所产生的日志为所述目标日志。
最近一次接收到所述获取日志的指令之后可以是上一次获取目标日志之后，则在每次接收到获取日志的指令之后，获取目标应用新产生的日志，不对已获取过的日志进行获取，减少获取到的信息的冗余。
可选的，在本申请另一实施例中，所述获取模块获取目标应用的目标日志包括：
获取所述目标应用的版本信息；
根据所述目标应用的版本信息判断所述目标应用是否存在更新；
若所述目标应用存在更新，获取所述目标应用更新后的代码模块；
获取与所述目标应用更新后的代码模块相关的日志为所述目标日志。
通常，每个应用在编码发布之后，都会存在一个版本与其对应。在本实施例中，获取目标应用的版本信息，可以根据目标应用的版本信息判断该目标应用是否存在更新。具体的，可以判断目标应用的版本信息是否与前一次获取到的版本信息一致；或者可以判断目标应用是否存在版本更新标记，若存在版本更新标记，则可以确定该目标应用存在更新。
在本实施例中，若该目标应用存在更新，获取目标应用更新后的代码模块。其中，目标应用更新后的代码模块可以包括目标应用更新之后新增的代码模块，或者是应目标用更新之后修复的代码模块(即存在修改的代码模块)。
在本实施例中，在接收到获取日志指令之后，获取与应用更新后的代码模块相关的日志，可以及时地了解应用在更新之后是否存在故障问题等信息，在应用更新之后，有利于对出现的问题及时修复，进而提高应用发布之后运行的问题。
统计模块220，用于统计所述目标日志包含的多条日志信息中每条日志信息的出现次数。
在本实施例中，获取到的目标日志可以包括多条日志信息。
确定模块230，用于确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设 次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级。
其中，上传优先级可以用于标识多条日志信息中各条日志信息上传的先后。例如，上传优先级为高时，优先上传，上传优先级为低时，在其他指定时间上传。
在本实施例中，统计多条日志信息中每条日志信息在预设的统计时间(如2小时，或者6小时，或者一周，或者一个月)内的累计出现次数得到每条日志信息的出现次数。
其中，第一预设次数和第二预设次数的具体值可以根据需要预先设定，并且，所述第一预设次数的值大于第二预设次数的值。
在本申请其他本实施例中，还可以判断所述目标日志中是否存在包含第一关键字的日志，若存在包含第一关键字的日志，确定包含第一关键字的日志为第一上传优先级的日志，以及第一上传优先级以外的其他日志为第二上传优先级的日志。其中，第一上传优先级标识的上传优先级高于第二上传优先级。
由于出现次数较多的日志信息表示应用运行过程中重复出现相同的问题，因此，在本实施例中，可以确定这些日志信息的上传优先级为第一上传优先级，优先于第二上传优先级的日志信息上传，有利于快速解决重复出现的问题，或者及时获取用户确定性的操作习惯。
第一上传模块240，用于将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息。
在本申请实施例中，将上传优先级为第一上传优先级的日志信息优先上传至目标应用的服务器，可以使应用的开发人员及时获取到应用的相关问题并及时地解决，节省终端上的存储空间，删除终端中与第一上传优先级的日志信息相同的日志信息，也可以进一步释放终端上被占用的存储空间。
判断模块250，用于判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态。
判断终端是否为预设运行状态可以包括判断终端运行时所启动应用的数量是否低于预设应用运行数量，终端所消耗的硬件资源是否低于终端可支持的硬件资源的百分之三十等。
在本实施例中，判断终端是否为预设运行状态用于确定终端是否为可以连续上传日志信息的状态，或者，判断终端的运行状态用于确定终端当前的可调度资源是否较多。例如，判断终端运行时所启动应用的数量是否小于3个。
当终端处于低功耗运行状态，终端未被占用过多的系统资源。当终端处于高速率传输状 态时，终端可以支持连续快速的上传，节省上传日志的时间以及提高上传日志的销量。
第二上传模块260，用于若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
在本实施例中，将上传优先级为第二上传优先级的日志保存，可以将有用的日志信息进行保存，便于在需要获取时再上传。
在本申请实施例中，当终端为预设运行状态时，将上传优先级为第二上传优先级的日志信息上传至目标应用的服务器，可以使开发人员及时地获取到日志信息，并且上传日志的过程中不影响其他应用的使用，避免引起终端运行时的卡顿。
进一步的，在本申请另一实施例中，所述低功耗运行状态包括充电待机状态，所述高速率传输状态为WIFI连接状态。
在本实施例中，当终端为WIFI连接状态时，终端的网络状态较稳定，且节省网络传输的费用；当终端为充电待机状态时，终端不会出现电量过低或者没电无法续传的情况，即在此状态下，终端可以支持稳定的数据传输。
因此，在本实施例中，当终端为WIFI连接状态以及充电待机状态时，将第二上传优先级的日志信息上传至所述应用的服务器，有利于日志传输过程中的数据能够快速稳定的传输。
可选的，在本申请另一实施例中，所述装置还包括发送模块，所述发送模块用于：
获取所述第一上传优先级的日志信息的第一数量和/或所述第二上传优先级的日志信息的第二数量；
根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
所述根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息包括：
若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
具体的，所述预设日志数量上限值以及预设日志数量下限值可以根据应用的类型来确定。
根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
所述根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息包括：
若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
具体的，所述预设日志数量上限值以及预设日志数量下限值可以根据应用的类型来确定。
在本实施例中，可以向应用的服务器发送调整所述指令的发送频率的消息，使得服务器根据调整后的频率向客户端发送获取日志的指令。
在本实施例中，通过对第一上传优先级的日志信息以及第二上传优先级的日志信息的数量获取，进而发送调整指令的发送频率的消息，能够避免频繁获取日志却获取不到的情况，也避免了由于日志获取频率过低，获取间隔时间过长导致的不能及时上传重要日志的问题。
本申请提供的所述日志获取装置通过当接收到获取日志的指令时，获取模块依据所述获取日志的指令从终端获取目标应用的目标日志；统计模块统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；确定模块确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；第一上传模块将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；判断模块判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；若所述终端为预设运行状态，第二上传模块将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，第二上传模块将所述第二上传优先级的日志信息保存在所述终端。由于本申请在接收指令之后，获取目标应用的目标日志，并对目标日志包含的多条日志信息根据不同的优先级选择性的上传，使得优先级高的日志信息能够及时地传到目标应用的服务器，从而目标应用的服务器能够及时地获取到重要信息，将优先级低的日志信息在终端不为预设运行状态时保存在本地，避免上传过多无关信息，也避免同时传输过多信息占用系统资源影响系统运行，使应用的服务器更高效的获取有价值的日志信息，节省终端资源，将优先级低的日志信息在终端为预设运行状态时及时上传至目标应用的服务器可以在不影响终端运行的情况下使服务器保存完整的日志信息。
上述以软件功能模块的形式实现的集成的单元，可以存储在一个非易失性可读存储介质中。上述软件功能模块存储在一个非易失性可读存储介质中，包括若干指令用以使 得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。
如图3所示，是本申请实现日志获取方法的较佳实施例的终端3的结构示意图。在本实施例中，终端3包括至少一个发送装置31、至少一个存储器32、至少一个处理器33、至少一个接收装置34以及至少一个通信总线。其中，所述通信总线用于实现这些组件之间的连接通信。
所述终端3是一种能够按照事先设定或存储的指令，自动进行数值计算和/或信息处理的设备，其硬件包括但不限于微处理器、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程门阵列(Field－Programmable Gate Array，FPGA)、数字处理器(Digital Signal Processor，DSP)、嵌入式设备等。所述终端3还可包括网络设备和/或用户设备。其中，所述网络设备包括但不限于单个网络服务器、多个网络服务器组成的服务器组或基于云计算(Cloud Computing)的由大量主机或网络服务器构成的云，其中，云计算是分布式计算的一种，由一群松散耦合的计算机集组成的一个超级虚拟计算机。
所述终端3可以是，但不限于任何一种可与用户通过键盘、触摸板或声控设备等方式进行人机交互的电子产品，例如，平板电脑、智能手机、监控设备等终端。
所述终端3所处的网络包括，但不限于互联网、广域网、城域网、局域网、虚拟专用网络(Virtual Private Network，VPN)等。
其中，所述接收装置34和所述发送装置31可以是有线发送端口，也可以为无线设备，例如包括天线装置，用于与其他设备进行数据通信。
所述存储器32用于存储程序代码。所述存储器32可以是集成电路中没有实物形式的具有存储功能的电路。或者，所述存储器32也可以是具有实物形式的存储器，如内存条、TF卡(Trans-flash Card)、智能媒体卡(smart media card)、安全数字卡(secure digital card)、快闪存储器卡(flash card)等储存设备等等。
所述处理器33可以包括一个或者多个微处理器、数字处理器。所述处理器33可调用存储器32中存储的程序代码以执行相关的功能。例如，图2中所述的各个模块是存储在所述存储器32中的程序代码，并由所述处理器33所执行，以实现一种日志获取方法。所述处理器33又称中央处理器(CPU，Central Processing Unit)，是一块超大规模的集成电路，是运算核心(Core)和控制核心(Control Unit)。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的 划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
最后应说明的是，以上实施例仅用以说明本申请的技术方案而非限制，尽管参照较佳实施例对本申请进行了详细说明，本领域的普通技术人员应当理解，可以对本申请的技术方案进行修改或等同替换，而不脱离本申请技术方案的精神和范围。

Claims (20)

  1. 一种日志获取方法，其特征在于，所述方法包括：
    当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；
    统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；
    确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；
    将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；
    判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；
    若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    获取所述第一上传优先级的日志信息的第一数量和/或所述第二上传优先级的日志信息的第二数量；
    根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
  3. 如权利要求2所述的方法，其特征在于，所述根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息包括：
    若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
    若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述获取目标应用的目标日志包括：
    获取所述目标应用的版本信息；
    根据所述目标应用的版本信息判断所述目标应用是否存在更新；
    若所述目标应用存在更新，获取所述目标应用更新后的代码模块；
    获取与所述目标应用更新后的代码模块相关的日志为所述目标日志。
  5. 如权利要求1至3中任一项所述的方法，其特征在于，所述获取目标应用的目标日志包括：
    获取最近一次接收到所述获取日志的指令之后所述应用运行所产生的日志为所述目标日志。
  6. 如权利要求1至3中任一项所述的方法，其特征在于，所述目标应用为运行频率大于预设运行频率和/或运行时间大于预设运行时间的应用。
  7. 如权利要求1至3中任一项所述的方法，其特征在于，所述低功耗运行状态包括充电待机状态，所述高速率传输状态为WIFI连接状态。
  8. 一种日志获取装置，其特征在于，所述装置包括：
    获取模块，用于当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；
    统计模块，用于统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；
    确定模块，用于确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；
    第一上传模块，用于将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；
    判断模块，用于判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；
    第二上传模块，用于若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
  9. 一种终端，其特征在于，所述终端包括存储器及处理器，所述存储器用于存储至少一个计算机可读指令，所述处理器用于执行所述至少一个计算机可读指令以实现以下步骤：
    当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；
    统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；
    确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；
    将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；
    判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；
    若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
  10. 如权利要求9所述的终端，其特征在于，所述处理器执行所述至少一个计算机可读指令还用以实现以下步骤：
    获取所述第一上传优先级的日志信息的第一数量和/或所述第二上传优先级的日志信息的第二数量；
    根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
  11. 如权利要求10所述的终端，其特征在于，所述处理器执行所述至少一个计算机可读指令以实现所述根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息时，具体包括：
    若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
    若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
  12. 如权利要求9至11中任一项所述的终端，其特征在于，所述处理器执行所述至少一个计算机可读指令以实现所述获取目标应用的目标日志时，具体包括：
    获取所述目标应用的版本信息；
    根据所述目标应用的版本信息判断所述目标应用是否存在更新；
    若所述目标应用存在更新，获取所述目标应用更新后的代码模块；
    获取与所述目标应用更新后的代码模块相关的日志为所述目标日志。
  13. 如权利要求9至11中任一项所述的终端，其特征在于，所述处理器执行所述至少一个计算机可读指令以实现所述获取目标应用的目标日志时，具体包括：
    获取最近一次接收到所述获取日志的指令之后所述应用运行所产生的日志为所述目标日志。
  14. 如权利要求9至11中任一项所述的终端，其特征在于，所述目标应用为运行频率大于预设运行频率和/或运行时间大于预设运行时间的应用。
  15. 一种非易失性可读存储介质，其上存储有计算机指令，其特征在于：所述非易失性可读存储介质存储有至少一个计算机可读指令，所述至少一个计算机可读指令被处理器执行时实现以下步骤：
    当接收到获取日志的指令时，依据所述获取日志的指令从终端获取目标应用的目标日志；
    统计所述目标日志包含的多条日志信息中每条日志信息的出现次数；
    确定所述多条日志信息中出现次数大于等于第一预设次数的日志信息为第一上传优先级的日志信息，以及确定所述多条日志信息中出现次数小于所述第一预设次数且大于等于第二预设次数的日志信息为第二上传优先级的日志信息，其中，所述第一上传优先级高于所述第二上传优先级；
    将所述第一上传优先级的日志信息上传至所述目标应用的服务器，且删除所述终端中与所述第一上传优先级的日志信息相同的日志信息；
    判断所述终端是否为预设运行状态，所述预设运行状态为低功耗运行状态或高速率传输状态；
    若所述终端为预设运行状态，将所述第二上传优先级的日志信息上传至所述目标应用的服务器，若所述终端不为预设运行状态，将所述第二上传优先级的日志信息保存在所述终端。
  16. 如权利要求15所述的非易失性可读存储介质，其特征在于，所述至少一个计算机可读指令被所述处理器执行还用以实现以下步骤：
    获取所述第一上传优先级的日志信息的第一数量和/或所述第二上传优先级的日志信息的第二数量；
    根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息。
  17. 如权利要求16所述的非易失性可读存储介质，其特征在于，所述至少一个计算机可读指令被所述处理器执行以实现所述根据所述第一数量和/或所述第二数量，发送调整所述获取日志的指令的发送频率的消息时，具体包括：
    若所述第一数量或所述第二数量大于预设日志数量上限值，发送第一消息，所述第一消息用于增加所述获取日志的指令的发送频率；
    若所述第一数量和所述第二数量小于预设日志数量下限值，发送第二消息，所述第二消息用于降低所述获取日志的指令的发送频率。
  18. 如权利要求15至17中任一项所述的非易失性可读存储介质，其特征在于，所述至少一个计算机可读指令被所述处理器执行以实现所述获取目标应用的目标日志时，具体包括：
    获取所述目标应用的版本信息；
    根据所述目标应用的版本信息判断所述目标应用是否存在更新；
    若所述目标应用存在更新，获取所述目标应用更新后的代码模块；
    获取与所述目标应用更新后的代码模块相关的日志为所述目标日志。
  19. 如权利要求15至17中任一项所述的非易失性可读存储介质，其特征在于，所述至少一个计算机可读指令被所述处理器执行以实现所述获取目标应用的目标日志时，具体包括：
    获取最近一次接收到所述获取日志的指令之后所述应用运行所产生的日志为所述目标日志。
  20. 如权利要求15至17中任一项所述的非易失性可读存储介质，其特征在于，所述目标应用为运行频率大于预设运行频率和/或运行时间大于预设运行时间的应用。
PCT/CN2019/118603 2019-05-15 2019-11-14 日志获取方法、装置、终端及存储介质 WO2020228289A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910403713.5 2019-05-15
CN201910403713.5A CN110266514A (zh) 2019-05-15 2019-05-15 日志获取方法、装置、终端及存储介质

Publications (1)

Publication Number Publication Date
WO2020228289A1 true WO2020228289A1 (zh) 2020-11-19

Family

ID=67913163

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/118603 WO2020228289A1 (zh) 2019-05-15 2019-11-14 日志获取方法、装置、终端及存储介质

Country Status (2)

Country Link
CN (1) CN110266514A (zh)
WO (1) WO2020228289A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115391161A (zh) * 2022-10-28 2022-11-25 荣耀终端有限公司 日志传输方法、设备、系统及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110266514A (zh) * 2019-05-15 2019-09-20 平安科技（深圳）有限公司 日志获取方法、装置、终端及存储介质
CN112712610B (zh) * 2020-12-30 2024-02-27 深圳市元征科技股份有限公司 车辆诊断日志处理方法、装置、终端设备及可读存储介质
CN113055459B (zh) * 2021-03-09 2022-11-01 北京奇艺世纪科技有限公司 日志投递方法和装置、电子设备及存储介质
CN113572818A (zh) * 2021-06-29 2021-10-29 青岛海尔科技有限公司 日志文件的上传方法和装置、存储介质及电子装置
CN116346729B (zh) * 2023-02-24 2024-02-09 安芯网盾(北京)科技有限公司 一种数据日志上报的限流方法及系统
CN116449961B (zh) * 2023-06-14 2023-10-10 蔚来汽车科技(安徽)有限公司 输入事件控制方法、系统、电子设备、存储介质及车辆

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468222A (zh) * 2014-12-15 2015-03-25 北京奇虎科技有限公司 上报日志信息的方法、装置及系统
CN104618474A (zh) * 2015-01-27 2015-05-13 杭州华三通信技术有限公司 设备信息保存方法以及装置
CN106293541A (zh) * 2016-08-19 2017-01-04 浪潮(北京)电子信息产业有限公司 一种存储系统的日志管理方法和系统
US20170150214A1 (en) * 2015-11-25 2017-05-25 Le Holdings (Beijing) Co., Ltd. Method and apparatus for data processing
CN110266514A (zh) * 2019-05-15 2019-09-20 平安科技（深圳）有限公司 日志获取方法、装置、终端及存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104753985B (zh) * 2013-12-30 2018-12-28 腾讯科技（深圳）有限公司 会话列表显示方法和装置
CN108400888B (zh) * 2018-01-29 2021-07-23 深圳壹账通智能科技有限公司 一种日志处理方法、存储介质及终端设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468222A (zh) * 2014-12-15 2015-03-25 北京奇虎科技有限公司 上报日志信息的方法、装置及系统
CN104618474A (zh) * 2015-01-27 2015-05-13 杭州华三通信技术有限公司 设备信息保存方法以及装置
US20170150214A1 (en) * 2015-11-25 2017-05-25 Le Holdings (Beijing) Co., Ltd. Method and apparatus for data processing
CN106293541A (zh) * 2016-08-19 2017-01-04 浪潮(北京)电子信息产业有限公司 一种存储系统的日志管理方法和系统
CN110266514A (zh) * 2019-05-15 2019-09-20 平安科技（深圳）有限公司 日志获取方法、装置、终端及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115391161A (zh) * 2022-10-28 2022-11-25 荣耀终端有限公司 日志传输方法、设备、系统及存储介质
CN115391161B (zh) * 2022-10-28 2023-04-07 荣耀终端有限公司 日志传输方法、设备、系统及存储介质

Also Published As

Publication number Publication date
CN110266514A (zh) 2019-09-20

Similar Documents

Publication Publication Date Title
WO2020228289A1 (zh) 日志获取方法、装置、终端及存储介质
US10650026B2 (en) Automatic mode switching in a synchronous replication environment
US10713079B2 (en) System and method for managing telemetry data and agents in a telemetry system
US20160048682A1 (en) Method and Apparatus for Clearing Malicious Power-Consuming Application, and User Terminal
US10025686B2 (en) Generating and communicating platform event digests from a processor of a system
CN107239339B (zh) 系统性能优化参数确定方法、系统性能优化方法及装置
US20140215236A1 (en) Power-efficient inter processor communication scheduling
US10455509B2 (en) Energy efficient data handling for mobile devices
CN106921506B (zh) 移动设备的数据采集上报方法和系统
US20120297216A1 (en) Dynamically selecting active polling or timed waits
TWI621013B (zh) 監控服務設備之系統
CN108628890A (zh) 一种数据导出方法及系统
CN113760982A (zh) 一种数据处理方法和装置
US10235062B1 (en) Selection of computer resources to perform file operations in a power-efficient manner
US10554510B2 (en) Enabling additional metrics in a monitoring system to diagnose problems
Ravindra et al. Latency aware elastic switching-based stream processing over compressed data streams
US11243603B2 (en) Power management of an event-based processing system
KR101890046B1 (ko) 전력 소비 감소를 위한 동시적 네트워크 애플리케이션 스케줄링
CN114661563B (zh) 基于流处理框架的数据处理方法以及系统
US20220334906A1 (en) Multimodal user experience degradation detection
WO2012102727A1 (en) Distributing information
EP3396553A1 (en) Method and device for processing data after restart of node
CN111090627B (zh) 基于池化的日志存储方法、装置、计算机设备及存储介质
US20230132786A1 (en) Artificial intelligence based power consumption optimization
CN112099857B (zh) 电子设备的休眠唤醒方法及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19928476

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19928476

Country of ref document: EP

Kind code of ref document: A1