CN115357497A - Service fault analysis method, device, medium and computer equipment - Google Patents

Service fault analysis method, device, medium and computer equipment Download PDF

Info

Publication number
CN115357497A
CN115357497A CN202211007400.6A CN202211007400A CN115357497A CN 115357497 A CN115357497 A CN 115357497A CN 202211007400 A CN202211007400 A CN 202211007400A CN 115357497 A CN115357497 A CN 115357497A
Authority
CN
China
Prior art keywords
service
fault
log
information
service fault
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211007400.6A
Other languages
Chinese (zh)
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.)
Guangzhou Cubesili Information Technology Co Ltd
Original Assignee
Guangzhou Cubesili Information Technology Co 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 Guangzhou Cubesili Information Technology Co Ltd filed Critical Guangzhou Cubesili Information Technology Co Ltd
Priority to CN202211007400.6A priority Critical patent/CN115357497A/en
Publication of CN115357497A publication Critical patent/CN115357497A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/362Software debugging
    • G06F11/366Software debugging using diagnostics
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21Server components or server architectures
    • H04N21/218Source of audio or video content, e.g. local disk arrays
    • H04N21/2187Live feed

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the application relates to the field of network live broadcast, and provides a service fault analysis method, a device, a medium and computer equipment, wherein the method comprises the following steps: receiving service fault information of an application program; the service fault information comprises service log information of an application program, fault time point information and a service fault model identifier; acquiring a corresponding service fault log when a fault occurs according to the service log information and the fault time point information; and inputting the service fault log into a service fault model corresponding to the service fault model identification to obtain a service fault analysis result. According to the method and the device, the business fault information of the application program input by the user is received, so that the business fault is automatically analyzed, and a business fault analysis result is obtained, so that non-research and development personnel can quickly obtain the business fault analysis result, the business fault analysis feedback efficiency is improved, the frequency of using the live application program by the user is improved, and the audience retention rate is improved.

Description

Service fault analysis method, device, medium and computer equipment
Technical Field
The embodiment of the application relates to the field of fault analysis, in particular to a method, a device, a medium and computer equipment for service fault analysis.
Background
The webcast refers to a technology that a webcast shares a webcast audio and video stream to audiences on the network through a webcast platform. By means of an open and shared network live broadcast platform, people can more conveniently show talent talents of themselves, in the talent show process, audiences can express love to the anchor through participating in live broadcast interaction, the anchor enjoyed by the audiences can obtain the division of the network live broadcast platform, and certain benefits are obtained; because the live broadcast work is not influenced by the main broadcast academic calendar and the live broadcast field, ordinary people can realize employment in a live broadcast mode, and social employment can be effectively driven.
In the network live broadcast, an anchor user can access a live broadcast application program installed on an anchor client, and the anchor client is triggered to load a live broadcast application program interface for the anchor client, so that the anchor user enters a live broadcast room for live broadcast. The audience user can access the live broadcast application program installed on the audience client side, the audience client side is triggered to load a live broadcast application program interface for the audience client side, a live broadcast room list can be displayed in the live broadcast application program interface, the audience user can click any live broadcast room cover in the live broadcast room list, and the audience user can enter a corresponding anchor live broadcast room to watch live broadcast.
However, there may be more or less some traffic failures for client-installed live applications. In the related art, the processing method for the service failure is as follows: the user submits the service fault problem description to the customer service of the live broadcast application program, then the customer service sends the fault problem description to the research and development end, the research and development end manually analyzes and provides the reason causing the service fault problem and the scheme for solving the service fault problem, and finally, the reason causing the service fault problem and the scheme for solving the service fault problem are fed back to the user. The analysis feedback circulation time of the whole service fault is often as long as several hours, so that the service fault cannot be timely and effectively fed back and solved, the frequency of using a live application program by a user is reduced, and the retention rate of audiences is reduced.
Disclosure of Invention
In order to overcome the problems in the related art, the application provides a service fault analysis method, a device, a medium and a computer device, which can improve the feedback efficiency of service fault analysis, improve the frequency of using live broadcast application programs by users and improve the retention rate of audiences.
According to a first aspect of the embodiments of the present application, a method for analyzing a service fault is provided, which includes the following steps:
receiving service fault information of an application program; the service fault information comprises service log information of an application program, fault time point information and a service fault model identifier;
acquiring a corresponding service fault log when a fault occurs according to the service log information and the fault time point information;
and inputting the service fault log into a service fault model corresponding to the service fault model identification to obtain a service fault analysis result.
According to a second aspect of embodiments of the present application, there is provided a service failure analysis apparatus, including:
the service fault information receiving module is used for receiving service fault information of the application program; the service fault information comprises service log information of an application program, fault time point information and a service fault model identifier;
the service fault log obtaining module is used for obtaining a corresponding service fault log when a fault occurs according to the service log information and the fault time point information;
and the service fault analysis result acquisition module is used for inputting the service fault log into a service fault model corresponding to the service fault model identifier to acquire a service fault analysis result.
According to a third aspect of embodiments herein, there is provided a computer device comprising a processor and a memory; the memory stores a computer program adapted to be loaded by the processor and to perform the service failure analysis method as described above.
According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the service failure analysis method as described above.
The method comprises the steps of receiving service fault information of an application program; the service fault information comprises service log information of an application program, fault time point information and a service fault model identifier; acquiring a corresponding service fault log when a fault occurs according to the service log information and the fault time point information; and inputting the service fault log into a service fault model corresponding to the service fault model identification to obtain a service fault analysis result. According to the method and the device, the business fault information of the application program input by the user is received, so that the business fault is automatically analyzed, and a business fault analysis result is obtained, so that non-research and development personnel can quickly obtain the business fault analysis result, the business fault analysis feedback efficiency is improved, the frequency of using the live application program by the user is improved, and the audience retention rate is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
For a better understanding and practice, the invention is described in detail below with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic block diagram of an application environment of a service fault analysis method provided in an embodiment of the present application;
fig. 2 is a flowchart of a service failure analysis method according to a first embodiment of the present application;
fig. 3 is a flowchart of a method for acquiring service fault model data according to an embodiment of the present application;
fig. 4 is a flowchart of a method for acquiring service fault information according to an embodiment of the present application;
fig. 5 is a flowchart of a method for obtaining a service fault log according to an embodiment of the present application;
fig. 6 is a flowchart of a method for determining a service fault log according to an embodiment of the present application;
fig. 7 is a flowchart of a method for obtaining a service fault analysis result according to an embodiment of the present application;
fig. 8 is a timing flowchart of a service fault analysis method according to an embodiment of the present application;
fig. 9 is a schematic block diagram of a service failure analysis apparatus according to a second embodiment of the present application;
fig. 10 is a block diagram schematically illustrating a structure of a computer device according to a third embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
It should be understood that the embodiments described are only some embodiments of the present application, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without any creative effort belong to the protection scope of the embodiments in the present application.
When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. In the description of the present application, it is to be understood that the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not necessarily used to describe a particular order or sequence, nor are they to be construed as indicating or implying relative importance. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as the case may be. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The word "if"/"if" as used herein may be interpreted as "at \8230; \8230when" or "when 8230; \8230when" or "in response to a determination".
Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
As will be appreciated by those skilled in the art, the terms "client," "terminal device," and "terminal device" as used herein include both wireless signal transmitter devices, which include only wireless signal transmitter devices capable of transmitting, and wireless signal receiver devices, which include only wireless signal receiver devices capable of receiving, and also include receiving and transmitting hardware devices having receiving and transmitting hardware capable of two-way communication over a two-way communication link. Such a device may include: cellular or other communication devices such as personal computers, tablets, etc. having a single line display or a multi-line display or cellular or other communication devices without a multi-line display; PCS (personal communications Service), which may combine voice, data processing, facsimile and/or data communications capabilities; a PDA (Personal Digital Assistant) which may include a radio frequency receiver, a pager, internet/intranet access, web browser, notepad, calendar and/or GPS (Global positioning system) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "client," "terminal device" can be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. The "client", "terminal Device" used herein may also be a communication terminal, a Internet access terminal, and a music/video playing terminal, and may be, for example, a PDA, an MID (Mobile Internet Device), and/or a Mobile phone with music/video playing function, and may also be a smart television, a set-top box, and other devices.
The hardware referred to by the names "server", "client", "service node", etc. is essentially a computer device with the performance of a personal computer, and is a hardware device having necessary components disclosed by the von neumann principle, such as a central processing unit (including an arithmetic unit and a controller), a memory, an input device, an output device, etc., wherein a computer program is stored in the memory, and the central processing unit loads a program stored in an external memory into the internal memory to run, executes instructions in the program, and interacts with the input and output devices, thereby accomplishing specific functions.
It should be noted that the concept of "server" as referred to in this application can be extended to the case of a server cluster. According to the network deployment principle understood by those skilled in the art, each server should be logically divided, and in physical space, the servers can be independent from each other but can be called through an interface, or can be integrated into one physical computer or a set of computer clusters. Those skilled in the art will appreciate this variation and should not be so limited as to restrict the implementation of the network deployment of the present application.
The service fault analysis method provided by the embodiment of the application can be applied to fault analysis of various application programs, and in the embodiment of the application, the scheme of the application is described by taking the application program as a live application program as an example.
Specifically, referring to fig. 1, fig. 1 is a schematic view of an application scenario of the service fault analysis method provided in the embodiment of the present application, where the application scenario of the service fault analysis method provided in the embodiment of the present application includes an anchor client 110, a viewer client 120, and a server 130.
Anchor client 110 interacts with viewer client 120 through server 130. Specifically, both the anchor client 110 and the viewer client 120 may access the internet via a network access to establish a data communication link with the server 130. The network may be any type of communication medium capable of implementing communication between the anchor client 110 and the server 130 and between the viewer client 120 and the server 130, such as a wired communication link, a wireless communication link, or a fiber optic cable, and the like, and the present application is not limited thereto.
It should be noted that the clients proposed in the embodiment of the present application include the anchor client 110 and the viewer client 120.
It is noted that there are many understandings of the concept of "client" in the prior art, for example: it may be understood as an application program installed in a computer device, or may be understood as a hardware device corresponding to a server.
In the embodiments of the present application, the term "client" refers to a hardware device corresponding to a server, and more specifically, refers to a computer device, such as: smart phones, smart interactive tablets, personal computers, and the like.
When the client is a mobile device such as a smart phone and an intelligent interactive tablet, a user can install a matched mobile application program on the client and can also access a Web application program on the client.
When the client is a non-mobile device such as a Personal Computer (PC), the user can install a matching PC application on the client, and similarly can access a Web application on the client.
The mobile terminal application refers to an application program that can be installed in the mobile device, the PC terminal application refers to an application program that can be installed in the non-mobile device, and the Web terminal application refers to an application program that needs to be accessed through a browser.
Specifically, the Web application program may be divided into a mobile version and a PC version according to the difference of the client types, and the page layout modes and the available server support of the two versions may be different.
In the embodiment of the application, the types of live application programs provided to the user are divided into a mobile end live application program, a PC end live application program and a Web end live application program. The user can autonomously select the mode of participating in the live webcast according to different types of the client adopted by the user.
The present application divides clients into an anchor client 110 and a viewer client 130 depending on the identity of the user entering the client in the live room. It should be noted that in practical applications, the functions of viewer client 120 and anchor client 110 may be performed by the same client at different times, respectively. Thus, the same client may act as the viewer client 120 when viewing the live network and as the anchor client 110 when publishing the live video.
The anchor client 110 is a terminal that sends a webcast video, and is generally a client used by an anchor user in webcast. The hardware at which the anchor client 110 is directed essentially refers to a computer device, and in particular, as shown in fig. 1, may be a type of computer device such as a smartphone, smart interactive tablet, and personal computer.
The viewer client 120 refers to an end that receives and views live webcast video, and is typically a client used by a viewer user viewing video in live webcast. The hardware at which the viewer client 120 is pointed is essentially a computer device, and in particular, as shown in fig. 1, may be a type of computer device such as a smart phone, smart interactive tablet, and personal computer.
Server 130 may act as a business server and may be responsible for further connecting related audio data servers, video streaming servers, and other servers providing related support, etc. to form a logically associated server cluster for serving related end devices, such as anchor client 110 and viewer client 120 shown in fig. 1.
In the embodiment of the present application, the anchor client 110 and the viewer client 120 may join the same live broadcast room (i.e., a live broadcast channel), where the live broadcast room is a chat room implemented by means of internet technology and the server 130, and generally has an audio/video broadcast control function. The anchor user is live in the live room through anchor client 110, and the viewer user at viewer client 120 can log into server 130 to watch the live.
In the live broadcast room, interaction between the anchor user and audience users can be realized through known online interaction modes such as voice, video, text and the like, generally, the anchor user performs programs for the audience users in the form of audio and video streams, meanwhile, the audience users can interact with the anchor user in the form of text or virtual gifts, economic transaction behaviors can also be generated in the interaction process, and the application form of the live broadcast room is not limited to online entertainment and can also be popularized to other related scenes.
Specifically, the viewer-user watching the live broadcast process is as follows: a viewer user may click to access a live application installed on the viewer client 120 and choose to enter any one of the live rooms, triggering the viewer client 120 to load a live room interface for the viewer user, including several interactive components within the live room interface, such as: the video component, the virtual gift bar component, the public screen component and the like can enable audience users to watch live broadcast in a live broadcast room by loading the interactive components, and perform various online interactions, wherein the online interaction modes comprise but are not limited to presenting virtual gifts, participating in live broadcast activities, talking on public screen speech and the like.
However, there are more or less some traffic failures for client-installed live applications. In the related art, the service failure processing method is as follows: the user submits the service fault problem description to the customer service of the live broadcast application program, then the customer service sends the fault problem description to the research and development end, the research and development end manually analyzes and provides the reason causing the service fault problem and the scheme for solving the service fault problem, and finally, the reason causing the service fault problem and the scheme for solving the service fault problem are fed back to the user. The analysis feedback circulation time of the whole service fault is often as long as several hours, so that the service fault cannot be timely and effectively fed back and solved, the frequency of using a live application program by a user is reduced, and the retention rate of audiences is reduced.
Based on the above problems, the embodiments of the present application provide a service fault analysis method. Referring to fig. 2, fig. 2 is a schematic flow chart illustrating a service fault analysis method according to a first embodiment of the present application. The service fault analysis method of the embodiment of the application comprises the following steps:
step S101: receiving service fault information of an application program; the service fault information comprises service log information, fault time point information and service fault model identification of the application program.
In the embodiment of the application, an application log automatic analysis system is designed for the service fault analysis method, and after a user inputs service fault information of an application program in the application log automatic analysis system, the application log automatic analysis system analyzes the service fault information and feeds back a corresponding service fault analysis result. The user can be a research and development personnel of the application program or a customer service team personnel, and optionally, the user can even be a consumption user, so that each user can obtain a service fault analysis result in time.
Specifically, the application log automated analysis system may be in the form of a website or an application, etc. When the application log automatic analysis system may be a website, it may be specifically an internal website system deployed in a company to which the application belongs, and a user may log in the website through a browser for use. The hardware equipment where the application program log automatic analysis system is located can be mobile equipment such as a smart phone or an intelligent interactive tablet and can also be non-mobile equipment such as a Personal Computer (PC).
The service log information is used to indicate what happens to the application at various times.
In an alternative embodiment, the service log information may be a compressed packet link of the service log of the application program obtained from a feedback system of the application program, and the service log of the application program may be obtained by decompressing the compressed packet link of the service log, so as to obtain each data table or log file of the application program stored and recorded in time sequence, and further learn what happens to the application program at each time.
In another alternative embodiment, the service log information may also be a service log file obtained from the feedback system of the application, through which the occurrence of the application at various times can be directly learned.
In yet another alternative embodiment, the service log information may also be the user identification of the application program, and according to the user identification of the application program, the corresponding service log file may be obtained from the feedback system of the application program, so as to learn what happens to the application program at various times.
The feedback system of the application program is oriented to the mobile terminal, the log information indicated by the feedback system is the log of a single application program corresponding to a single user, the log information is non-discrete, and the log time is linear and continuous.
The failure time point information is used to indicate the time at which the failure occurred.
The service fault model identification is used for indicating the service fault problem description and the corresponding service fault problem model.
In an optional embodiment, the application log automation analysis system presets a plurality of service fault problem descriptions and corresponding service fault problem models, and a user can select a service fault problem description that meets a current fault from the plurality of service fault problem descriptions, and then determine the corresponding service fault problem model, that is, the service fault model is identified as a text language describing the fault problem, and the text language is bound with the corresponding service fault problem model. Certainly, in specific implementation, the service fault model identifier may also be a specific character identifier such as A1, A2, A3, and the like, where the character identifier corresponds to a text language describing a fault problem and binds a corresponding service fault problem model.
In another optional embodiment, the application log automated analysis system may also receive a description of a fault problem input by a user, and then perform matching according to the description of the fault problem and preset problem description data of a plurality of service fault problem models, so as to determine a corresponding service fault problem model. It will be appreciated that at this point, the business fault model identification may be considered a description of the fault problem entered by the user.
Step S102: and acquiring a corresponding service fault log when a fault occurs according to the service log information and the fault time point information.
As can be seen from the foregoing description, since the service log information is used to indicate what happens to the application program at each time, the service fault log corresponding to the fault occurrence time can be further intercepted from the service log according to the fault time point information.
The failure time point information may be a specific certain time point or a certain time interval.
Step S103: and inputting the service fault log into a service fault model corresponding to the service fault model identification to obtain a service fault analysis result.
The service fault problem model is used for indicating a model for analyzing the service fault, and specifically, the model may be a model obtained by training a neural network, or may be a troubleshooting algorithm generated according to a troubleshooting step of the service fault problem.
It can be understood that the service fault model can be pre-loaded in the application program log automatic analysis system, and the service fault analysis result can be obtained by inputting the service fault log into the corresponding service fault model.
The application program log automatic analysis system can also not load the service fault model, after the service fault log is obtained, the corresponding service fault model is loaded according to the service fault model identification, so that the service fault log is analyzed according to the service fault model, and a service fault analysis result is obtained.
The service failure analysis result may include one or more of the following: the method comprises the following steps of generating reasons of service faults, processing the service faults and processing the contact person modes of the service faults.
The method comprises the steps of receiving service fault information of an application program; the service fault information comprises service log information, fault time point information and a service fault model identifier of the application program; according to the service log information and the fault time point information, obtaining a corresponding service fault log when a fault occurs; and inputting the service fault log into a service fault model corresponding to the service fault model identification to obtain a service fault analysis result. According to the method and the device, the business fault information of the application program input by the user is received, so that the business fault is automatically analyzed, and a business fault analysis result is obtained, so that non-research and development personnel can quickly obtain the business fault analysis result, the business fault analysis feedback efficiency is improved, the frequency of using the live application program by the user is improved, and the audience retention rate is improved.
Referring to fig. 3, in an alternative embodiment, before the step of receiving the service failure information of the application program in step S101, the method includes:
step S110: and sending a request for downloading or updating each service fault model data to the server.
The method comprises the steps that a request for downloading or updating each service fault model data can be automatically sent to a server periodically according to a preset time interval; the method can also receive the operation of downloading or updating each service fault model data triggered by the user in the application program log automatic analysis system, and further send a request for downloading or updating each service fault model data to the server; and when the user accesses the application program log automatic analysis system, automatically triggering to send a request for downloading or updating each service fault model data to the server.
The service fault model data is data required for generating a service fault model, and may include a service troubleshooting step algorithm, neural network model data, and the like.
It will be appreciated that during application use, new business failure problems may occur, requiring new business failure model data to be downloaded from the service area. Similarly, in the process of analyzing the service fault, the service fault model may also be updated to improve the accuracy of the service fault analysis, and further, updated service fault model data needs to be acquired from the server.
Step S120: and storing the data of each service fault model fed back by the server to the local.
It is to be understood that saving to local refers to saving to an application log automated analysis system.
According to the application program log automatic analysis system, the request for downloading or updating each service fault model data is sent to the server, each service fault model data fed back by the server is stored to the local, and then the corresponding service fault data does not need to be obtained from the server, the updated service fault model data can be directly obtained from the local, so that service fault analysis is carried out, and the efficiency and the accuracy of the service fault analysis are improved.
Referring to fig. 4, in an alternative embodiment, the step of receiving the service failure information of the application program in step S101 includes:
step S1011: and responding to the operation that the user accesses the business fault analysis system, and displaying a business fault information input box of the application program.
It is understood that the service failure information input box may include a service log information input box, a failure time point information input box, and a service failure model identification input box. Optionally, the service failure information input box may further include an operation application selection box of the mobile terminal where the application is located, and the operation application may include an android or an IOS, that is, according to different operation applications, corresponding service failure models are different, and corresponding service failure methods are also different. Specifically, according to the operation application program, a service fault model corresponding to the operation application program is obtained, and the service log is analyzed through the service fault model to obtain a corresponding service fault analysis result.
Step S1012: and acquiring the service fault information input by the user in the service fault information input box.
According to the embodiment of the application, the service fault information can be conveniently input by a user through the display of the service fault information input box, and then the corresponding service fault information can be quickly obtained.
Referring to fig. 5, in an alternative embodiment, the service log information includes service log compressed packet links; in step S102, the step of obtaining the service fault log corresponding to the fault according to the service log information and the fault time point information includes:
step S1021: and obtaining a service log compression packet according to the service log compression packet link.
Step S1022: and unpacking the service log compressed packet to obtain service log information.
Step S1023: and acquiring a corresponding service fault log when a fault occurs according to the service log information and the fault time point information.
According to the embodiment of the application, the service log compression packet is obtained through the link of the service log compression packet, and then the service log compression packet is unpacked to obtain the service log information, so that the corresponding service fault log when a fault occurs is obtained, and the service fault log can be quickly obtained.
Referring to fig. 6, in an alternative embodiment, the step of obtaining the service fault log corresponding to the fault occurrence according to the service log information and the fault time point information in step S1023 includes:
step S10231: and dividing the service log information into a plurality of log slice files according to the life cycle of the application program.
Step S10232: and according to the fault time point information, taking the optimal log slice as a service fault log.
The lifecycle is a time period from the time when the application program process is created to be closed, specifically, when the application program is cold-started, for example, when the user slides the application program to close and then opens the application program again, the application program will print an identification log of the cold-start; in the technical scheme, when the application log file is divided into a plurality of log slice files, the log file is traversed row by row, each row of logs between one cold-start identification log (such as A) and the other cold-start identification log (such as B) are collected into the content of one log slice, and the content of the log slice at the moment: a is included, but B is not included.
According to the fault time point information, the optimal log slice is used as the service fault log, the log slice at the fault time point is used as the service fault log according to the fault time point information, and the log slice at the fault time point and the log slices with the preset number before and after the fault time point are used as the service fault log according to the fault time point information; the service fault log selection method can also be used for selecting the service fault log by adopting different optimal log slice selection strategies according to different service fault models.
Compared with a log automatic analysis system facing a server, the log acquired by the system needs to be acquired from different service backgrounds, log information is discrete, and log time is distributed and disordered; the mobile-end-oriented log automatic analysis system is used for collecting logs from logs of a single application program of a single user, log information is non-discrete, and log time is linear and continuous.
Therefore, in the aspect of log file processing, compared with a log automatic analysis system facing a server, the embodiment of the application can screen an optimal log slice file according to the fault occurrence time by cutting the service log information and the large log file into the log slice files according to the life cycle of an application program, so that the data range of the log information when the system analyzes the fault can be reduced from the large log file to a smaller log slice file, the efficiency and the accuracy of obtaining the service fault log are further improved, and the accuracy of service fault analysis is further improved.
Referring to fig. 7, in an alternative embodiment, the step of inputting the service fault log into the service fault model corresponding to the service fault model identifier in step S103 to obtain the service fault analysis result includes:
step S1031: acquiring corresponding service fault model data from local according to the service fault model identification, and loading a corresponding service fault model according to the service fault model data;
step S1032: and inputting the service fault log into a service fault model to obtain a service fault analysis result.
According to the embodiment of the application, when the service fault analysis is required, the corresponding service fault model is loaded according to the service fault model identification, and then the service fault log is input into the service fault model to obtain the service fault analysis result, so that the storage space of the application program log automatic analysis system can be reduced.
It can be understood that the application program log automatic analysis system can be divided into a plurality of modules according to functions so as to implement the above methods, and optionally, the application program log automatic analysis system can include a UI interaction module, a service problem model management module, a log downloading module, a log cutting module, and a service problem model interpreter module. It should be understood that the above module division and fig. 8 are only schematic descriptions, and do not limit the specific modules and the specific operation flow thereof.
The service failure analysis method of the present application is described in detail below with reference to fig. 8 as follows:
when a user accesses the automatic analysis system of the application program log, the UI interaction module requests the service problem model management module to download or update service fault model data; and the service problem model management module downloads or updates service fault model data from the server, stores the service fault model data to the local, and feeds the service fault model data back to the UI interaction module for display.
And the UI interaction module receives a service log compression packet link, fault time point information and a selected service fault model identifier input by a user.
The UI interaction module sends the service log compression packet link to the log downloading module; and the log downloading module downloads the service log file compression package, unpacks the service log file compression package, acquires service log information, stores the service log information to the local, and feeds the service log information back to the UI interaction module for display.
The UI interaction module sends the service log information and the fault time point information to the log cutting module; and the log cutting module divides the service log information into a plurality of log slice files according to the life cycle of the application program, takes the log slice of the fault time point as a service fault log according to the fault time point information, and feeds the service fault log back to the UI interaction module for display.
The UI interaction module sends the service fault log and the service fault model identification to a service problem model interpreter module to request for analyzing and answering the service fault problem; and the business problem model interpreter module loads a corresponding business fault model according to the business fault model identification, interprets and executes the business fault model, analyzes the business fault log according to the logic corresponding to the model to obtain a business fault analysis result, and feeds the business fault analysis result back to the UI interaction module for display.
Please refer to fig. 9, which is a schematic structural diagram of a service fault analysis apparatus according to a second embodiment of the present application. The apparatus 200 comprises:
a service failure information receiving module 201, configured to receive service failure information of an application; the service fault information comprises service log information, fault time point information and a service fault model identifier of the application program;
a service fault log obtaining module 202, configured to obtain a corresponding service fault log when a fault occurs according to the service log information and fault time point information;
the service fault analysis result obtaining module 203 is configured to input the service fault log to the service fault model corresponding to the service fault model identifier, and obtain a service fault analysis result.
It should be noted that, when the service failure analysis apparatus provided in the second embodiment of the present application executes a service failure analysis method in live broadcast, the division of each function module is only used for illustration, and in practical applications, the function distribution may be completed by different function modules according to needs, that is, an internal structure of a device is divided into different function modules, so as to complete all or part of the functions described above. In addition, the service fault analysis apparatus provided in the second embodiment of the present application and the service fault analysis method provided in the first embodiment of the present application belong to the same concept, and details of implementation processes thereof are referred to in the method embodiments and are not described herein again.
The embodiment of the service fault analysis apparatus according to the second embodiment of the present application may be applied to a computer device, such as a mobile terminal or a non-mobile terminal, and the embodiment of the apparatus may be implemented by software, or implemented by hardware, or implemented by a combination of hardware and software. The software implementation is taken as an example, and as a device in a logical sense, a processor in which the device is located processes a file reads corresponding computer program instructions in the nonvolatile memory into the memory to run. From a hardware perspective, the computer device may include a processor, a network interface, a memory, and a non-volatile memory, which are connected to each other via a data bus or in other known manners.
Please refer to fig. 10, which is a schematic structural diagram of a computer device according to a fourth embodiment of the present application. As shown in fig. 10, the computer device 16 may include: a processor 160, a memory 161, and a computer program 162 stored in the memory 161 and executable on the processor 160, such as: a program of a service failure analysis method; the steps in the first embodiment described above are implemented when the processor 160 executes the computer program 162.
The processor 160 may include one or more processing cores, among others. The processor 160 is connected to various components within the computer device 16 using various interfaces and lines to perform various functions of the computer device 16 and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 161 and calling up data within the memory 161. Alternatively, the processor 160 may be implemented in at least one hardware form of Digital Signal Processing (DSP), field-Programmable Gate Array (FPGA), programmable Logic Array (PLA). The processor 160 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the touch display screen; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 160, but may be implemented by a single chip.
The Memory 161 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 161 includes a non-transitory computer-readable medium. The memory 161 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 161 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch instructions, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 161 may optionally be at least one memory device located remotely from the processor 160.
The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are suitable for being loaded by a processor and executing the method steps of the foregoing embodiment, and a specific execution process may refer to specific descriptions of the foregoing embodiment, which is not described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules, so as to perform all or part of the functions described above. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. For the specific working processes of the units and modules in the system, reference may be made to the corresponding processes in the foregoing method embodiments, which are not described herein again.
In the above embodiments, the description of each embodiment has its own emphasis, and reference may be made to the related description of other embodiments for parts that are not described or recited in any embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described apparatus/terminal device embodiments are merely illustrative, and for example, a module or a unit may be divided into only one type of logic function, and another division manner may be provided in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium and used by a processor to implement the steps of the above-described embodiments of the method. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc.
The present invention is not limited to the above-described embodiments, and various modifications and variations of the present invention are intended to be included within the scope of the claims and the equivalent technology of the present invention if they do not depart from the spirit and scope of the present invention.

Claims (10)

1. A service fault analysis method is characterized by comprising the following steps:
receiving service fault information of an application program; the service fault information comprises service log information of an application program, fault time point information and a service fault model identifier;
acquiring a corresponding service fault log when a fault occurs according to the service log information and the fault time point information;
and inputting the service fault log into a service fault model corresponding to the service fault model identification to obtain a service fault analysis result.
2. The service failure analysis method according to claim 1, wherein:
the service log information comprises a service log compressed packet link;
the step of obtaining the service fault log corresponding to the fault according to the service log information and the fault time point information includes:
obtaining a service log compression packet according to the service log compression packet link;
unpacking the service log compressed packet to obtain service log information;
and acquiring a corresponding service fault log when a fault occurs according to the service log information and the fault time point information.
3. The service failure analysis method according to claim 2, wherein:
the step of obtaining the service fault log corresponding to the fault according to the service log information and the fault time point information includes:
dividing the service log information into a plurality of log slice files according to the life cycle of an application program;
and taking the optimal log slice as a service fault log according to the fault time point information.
4. The service failure analysis method according to claim 1, wherein:
before the step of receiving the service failure information of the application program, the method includes:
sending a request for downloading or updating each service fault model data to a server;
and storing the data of each service fault model fed back by the server to the local.
5. The service failure analysis method according to claim 4, wherein:
the step of inputting the service fault log into the service fault model corresponding to the service fault model identifier to obtain a service fault analysis result includes:
acquiring corresponding service fault model data from local according to the service fault model identification, and loading a corresponding service fault model according to the service fault model data;
and inputting the service fault log into the service fault model to obtain a service fault analysis result.
6. The service failure analysis method according to claim 1, wherein:
the step of receiving service failure information of the application program includes:
responding to the operation of accessing the service fault analysis system by a user, and displaying a service fault information input box of an application program;
and acquiring the service fault information input by the user in the service fault information input box.
7. The service failure analysis method according to any one of claims 1 to 6, wherein:
the service failure analysis result may include one or more of the following: the method comprises the following steps of generating reasons of service faults, processing the service faults and processing the contact person modes of the service faults.
8. A service failure analysis apparatus, comprising:
the service failure information receiving module is used for receiving the service failure information of the application program; the service fault information comprises service log information of an application program, fault time point information and a service fault model identifier;
a service fault log obtaining module, configured to obtain a corresponding service fault log when a fault occurs according to the service log information and the fault time point information;
and the service fault analysis result acquisition module is used for inputting the service fault log into a service fault model corresponding to the service fault model identification to acquire a service fault analysis result.
9. A computer device comprising a processor and a memory; characterized in that the memory stores a computer program adapted to be loaded by the processor and to execute the service failure analysis method according to any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the service failure analysis method according to any one of claims 1 to 7.
CN202211007400.6A 2022-08-22 2022-08-22 Service fault analysis method, device, medium and computer equipment Pending CN115357497A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211007400.6A CN115357497A (en) 2022-08-22 2022-08-22 Service fault analysis method, device, medium and computer equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211007400.6A CN115357497A (en) 2022-08-22 2022-08-22 Service fault analysis method, device, medium and computer equipment

Publications (1)

Publication Number Publication Date
CN115357497A true CN115357497A (en) 2022-11-18

Family

ID=84003222

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211007400.6A Pending CN115357497A (en) 2022-08-22 2022-08-22 Service fault analysis method, device, medium and computer equipment

Country Status (1)

Country Link
CN (1) CN115357497A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115834332A (en) * 2022-11-23 2023-03-21 中国联合网络通信集团有限公司 Fault processing method, server and system
JP7371845B1 (en) 2023-04-06 2023-10-31 17Live株式会社 Servers, methods and computer programs

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115834332A (en) * 2022-11-23 2023-03-21 中国联合网络通信集团有限公司 Fault processing method, server and system
JP7371845B1 (en) 2023-04-06 2023-10-31 17Live株式会社 Servers, methods and computer programs

Similar Documents

Publication Publication Date Title
US9992448B2 (en) Recording web conferences
US11601529B1 (en) Method and system of generating generic protocol handlers
CN115357497A (en) Service fault analysis method, device, medium and computer equipment
US9467347B2 (en) Systems and methods that utilize scalable vector graphics to provide web-based visualization of a device
CN103428525B (en) Internet video and the online query of TV programme and control method for playing back and system
CN111866537B (en) Information display method and device in live broadcast room, storage medium and electronic equipment
US20140143672A1 (en) System and method for function expandable collaboration screen system
US9996381B1 (en) Live application management workflow using metadata capture
CN113453030B (en) Audio interaction method and device in live broadcast, computer equipment and storage medium
AU2013213683B2 (en) A method and system of application development for multiple device client platforms
US10489179B1 (en) Virtual machine instance data aggregation based on work definition metadata
US20130254806A1 (en) System and Method for Displaying a Media Program Stream on Mobile Devices
CN113596508A (en) Virtual gift presenting method, device, medium and computer equipment of live broadcast room
CN112306887A (en) Program test distribution method and corresponding device, equipment and medium
CN114422821A (en) Live broadcast home page interaction method, device, medium and equipment based on virtual gift
CN112181678A (en) Service data processing method, device and system, storage medium and electronic device
US20130254822A1 (en) System for Creating and Displaying a Media Program Stream
CN114205366A (en) Cross-platform data synchronization method and device, equipment, medium and product thereof
CN113824979A (en) Live broadcast room recommendation method and device and computer equipment
CN112114927A (en) Interface notification message display method, device, equipment and storage medium
US20180349932A1 (en) Methods and systems for determining persona of participants by the participant use of a software product
CN116192829A (en) WEB-based remote multi-mode experiment teaching method, device, equipment and medium
CN113569089A (en) Information processing method, device, server, equipment, system and storage medium
CN103618793B (en) Browser Mission Monitor method, apparatus and system
CN111858260A (en) Information display method, device, equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination