CN112437152A - Crash processing method and device, electronic equipment and storage medium - Google Patents
Crash processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112437152A CN112437152A CN202011311143.6A CN202011311143A CN112437152A CN 112437152 A CN112437152 A CN 112437152A CN 202011311143 A CN202011311143 A CN 202011311143A CN 112437152 A CN112437152 A CN 112437152A
- Authority
- CN
- China
- Prior art keywords
- crash
- target
- client
- service node
- determining
- 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.)
- Granted
Links
Images
Classifications
-
- 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/52—Network services specially adapted for the location of the user terminal
-
- 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/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
- H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
-
- 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/0677—Localisation of faults
-
- 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/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
The application discloses a crash processing method and device, electronic equipment and a storage medium, and relates to the field of application programs. The specific implementation scheme is as follows: determining M clients with target crash events; obtaining a crash identification set based on the identification information of the M clients; determining that the target crash event is related to the target service node under the condition that the crash identification set is matched with the client identification set corresponding to the target service node; the client identification set comprises identification information of N clients accessing the target service node. According to the technical scheme, the processing efficiency of the crash event can be improved.
Description
Technical Field
The application relates to the technical field of computers, in particular to the field of application programs.
Background
In the early development of Application programs (apps), a single service architecture was generally adopted, a single service system provides services, and all services are operated in an independent service system.
With the continuous development of the mobile internet, the types of apps are more and more, and the functions are more and more complex. Complex function realization on the App client requires support of multiple business services. Based on the structure, the App service architecture is developed into a multi-service system architecture. Under the multi-service system architecture, a service complete set is split into a plurality of independent services according to service types, and a plurality of parallel service systems provide services.
Under the multi-service system architecture, when a client crashes, analysis and repair are required to be performed on a plurality of service systems respectively.
Disclosure of Invention
The application provides a crash processing method and device, electronic equipment and a storage medium.
According to an aspect of the present application, there is provided a crash processing method, including:
determining M clients with target crash events; wherein M is a positive integer;
obtaining a crash identification set based on the identification information of the M clients;
determining that the target crash event is related to the target service node under the condition that the crash identification set is matched with the client identification set corresponding to the target service node; the client identification set comprises identification information of N clients accessing the target service node, wherein N is a positive integer.
According to another aspect of the present application, there is provided a crash processing apparatus including:
the client determining module is used for determining M clients with target crash events; wherein M is a positive integer;
the set determining module is used for obtaining a crash identification set based on the identification information of the M clients;
the relevant determining module is used for determining that the target crash event is relevant to the target service node under the condition that the crash identification set is matched with the client identification set corresponding to the target service node; the client identification set comprises identification information of N clients accessing the target service node, wherein N is a positive integer.
According to another aspect of the present application, there is provided an electronic device including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the methods provided by the embodiments of the present application.
According to another aspect of the present application, there is provided a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform a method provided by embodiments of the present application.
According to the technical scheme, whether the target crash event is related to the target service node or not can be determined. Therefore, the service node related to the target crash event can be positioned, and the processing efficiency of the crash event is improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present application, nor do they limit the scope of the present application. Other features of the present application will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a schematic diagram of a crash handling method according to one embodiment of the application;
FIG. 2 is a schematic diagram of a crash handling method according to another embodiment of the application;
FIG. 3 is a diagram illustrating an exemplary application of the crash handling method of the present application;
FIG. 4 is a schematic diagram of a crash processing apparatus according to one embodiment of the application;
FIG. 5 is a schematic diagram of a crash processing apparatus according to another embodiment of the present application;
FIG. 6 is a block diagram of an electronic device for implementing a crash handling method of an embodiment of the application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
FIG. 1 shows a schematic diagram of a crash handling method according to one embodiment of the application. As shown in fig. 1, the method includes:
step S11, determining M clients with the target crash event; wherein M is a positive integer;
step S12, obtaining a crash identification set based on the identification information of the M clients;
step S13, determining that the target crash event is related to the target service node under the condition that the crash identification set is matched with the client identification set corresponding to the target service node; the client identification set comprises identification information of N clients accessing the target service node, wherein N is a positive integer.
The above method may be performed by a monitoring server. The monitoring server may be connected to at least one service node of an App (Application, Application program) monitored by the monitoring server, and collect, for each service node of the at least one service node, identification information of each client accessing the service node to obtain a client identification set corresponding to each service node. The monitoring server can also be connected with at least one client of the App to determine the client with the target crash event. Wherein, each service node comprises a target service node. The service node may be a service system, or may be a service interface included in the service system.
For example, M clients with a target crash event may be determined based on crash information reported by the clients.
The crash information reported by the client may include identification information of the client, crash environment information, crash details, and the like. The identification information of the client may include an ID (Identity Document), a name, and the like of the client. Crash environment information can include client version, business service version, operating system type, and the like. Crash details can include crash start time, duration, and the like.
The target crash event may include any pending crash event, such as a crash event occurring within a predetermined time period, a crash event related to a business service system updating a business service version, a crash event with an increased crash rate, and the like. And analyzing the collected crash information to determine M clients with the target crash event.
For example, in step S12, the identification information of M clients may be used as an element in the crash identification set, so as to obtain a crash identification set; or selecting identification information of L clients from the identification information of the M clients, and taking the identification information of the L clients as elements in the crash identification set to obtain the crash identification set, wherein L is a positive integer less than or equal to M.
For example, a preset matching algorithm may be used to perform matching analysis on the crash identifier set and the client identifier set corresponding to the target service node.
The matching algorithm may determine, based on a predetermined rule, whether the crash identifier set matches the client identifier set corresponding to the target service node, for example, determine whether the crash identifier set matches the client identifier set corresponding to the target service node according to whether the number of the same identifier information in the crash identifier set and the client identifier set corresponding to the target service node is greater than a threshold, whether the ratio of the number in the crash identifier set is greater than a threshold, whether the ratio of the number in the client identifier set is greater than a threshold, or the like.
The matching algorithm may also include a data model trained using historical data, and the data model may output a determination result of whether the crash identifier set and the client identifier set are matched according to the input crash identifier set and the client identifier set.
In the embodiment of the application, under the condition that the crash identifier set is matched with the client identifier set corresponding to the target service node, the target crash event is determined to be related to the target service node. Therefore, the service node related to the target crash event can be positioned, and the processing efficiency of the crash event is improved.
For example, under the condition that the App adopts a multi-service system architecture, if the App client crashes, a service system related to the crash can be located in the multiple service systems, and the crash problem is analyzed and repaired for the related service systems. By improving the processing efficiency, the loss can be stopped in time, and the expansion of the influence surface of the crash phenomenon caused by the crash of more clients is avoided.
For example, in a case where it is determined that the target crash event is related to the target service node, the business service version of the target service node may be rolled back, and in a case where the crash rate decreases after rolling back, it is determined that the target crash event is related to the updated business service version of the target service node.
In an exemplary embodiment, as shown in fig. 2, the crash handling method may further include:
step S21, receiving the identification information sent by the target service node; the identification information is obtained by the target service node from the received access request of the client;
step S22, based on the identification information sent by the target service node, updating the client identification set corresponding to the target service node.
In practical application, each service node in a link of a client and each service system for data interaction can be embedded. The client sends an access request containing the identification information of the client to a certain business service system, and a service node through which the access request of the client passes obtains the identification information of the client from the access request and sends the identification information of the client to the monitoring server. And the monitoring server adds the received identification information to a client identification set corresponding to the service node to update the client identification set.
For example, the business service system of the App monitored by the monitoring server includes a weather service system, a city location service system, and the like. And a certain client sends an access request to the weather service system, wherein the access request comprises the identification information and the coordinate information of the client. After receiving the access request, the weather service system needs to call the city location service system to determine the city where the client is located, and when the weather service system sends the access request to the city location service system, the access request passes through the weather service system and the city location service system. And the weather service system and the city positioning service system respectively acquire the identification information of the client from the access request and send the identification information to the monitoring server. And the monitoring server respectively adds the identification information of the client to a client identification set corresponding to the weather service system and a client identification set corresponding to the city positioning service system.
According to the exemplary embodiment, since the target service node acquires the identification information of the client in the access request and sends the identification information to the monitoring server, the monitoring server can acquire the identification information of the client accessing the target service node in a full amount and accurately. The method is beneficial to accurately determining whether the target crash event is related to the target service node.
In an exemplary embodiment, in step S11, the determining M clients with the target crash event includes:
clustering the received crash information of the client to obtain K crash information sets corresponding to K crash events; wherein K is a positive integer;
and determining M clients with the target crash event based on the crash information set corresponding to the target crash event in the K crash events.
In practical application, when a client crashes, the client uploads crash information to the monitoring server, and the monitoring server clusters the crash information according to crash environment information and crash details in the crash information, so that the crash information with the same or similar crash situation is in the same crash information set. For each crash information set obtained by clustering, a crash event corresponding to the set can be determined according to the crash information in the set, for example, a crash caused by updating of a service version, a crash caused by an operating environment, and the like.
Illustratively, a crash caused by a business service system, such as a crash caused by a business service version update, may be determined as a target crash event. And determining M clients with the target crash event based on the crash information set corresponding to the target crash event.
According to the embodiment, the received collapse information of the client is clustered, so that the target collapse event and the client corresponding to the target collapse event can be determined more accurately, the analysis and repair of the target collapse event are more targeted, and the collapse processing effect is improved.
In an exemplary embodiment, the determining M clients with the target crash event in step S11 may include:
and under the condition that the collapse rate corresponding to the target collapse event is greater than a preset threshold value, determining M clients with the target collapse event.
In practical application, the received crash information of the client can be clustered, and after a crash information set corresponding to the target crash event is obtained through clustering, the crash rate of the target crash event is determined based on the crash information set. For example, the collapse rate is determined based on the number of clients corresponding to the collapse information in the collapse information set and the total number of clients. And if the collapse rate is overlarge, determining M clients with the target collapse event to process the target collapse event.
According to the embodiment, the processing of the target crash event is triggered when the crash rate is greater than the preset threshold, so that unnecessary resource consumption can be avoided, and the processing efficiency of the crash event to be processed is improved.
In an exemplary embodiment, the crash handling method further comprises:
determining the time range of the target crash event based on the crash information of the M clients in which the target crash event occurs;
determining a target time range based on the time range within which the target crash event occurred;
and determining the service node which updates the service version of the business in the target time range as a target service node.
For example, in the case that the target crash event is related to the service version update, the time range of the target crash event may be determined, for example, after 10:00, based on the crash occurrence time in the crash information of the client. A time range, e.g., 9:45-10:00, whose duration before the time range in which the target crash event occurred is equal to a predetermined value is determined as the target time range. And determining the service node which updates the service version of the business in the target time range as a target service node. Alternatively, the number of target service nodes may be plural.
According to the embodiment, the range of the target service node is reduced to the service node which updates the service version of the business within the target time range by using the crash information, so that the service node related to the target crash event can be quickly positioned on the basis, and the crash processing efficiency is improved.
As an example, the target service node is a traffic service system. And determining whether the target crash event is related or not by taking the business service system as a unit can improve the positioning efficiency.
As another example, the target service node is a service interface included in the business service system. Whether the target crash event is related or not is determined by taking the service interface as a unit, and after the related service interface is positioned, the efficiency of analyzing and repairing the problem of the crash can be improved.
Fig. 3 is a schematic diagram illustrating an application example of the crash handling method of the present application. In this application example, the monitoring server is configured with a crash processing system, and as shown in fig. 3, the system includes a client identifier generation module 310, an identifier collection management module 320, a crash information collection module 330, and a service crash location module 340.
The client ID generation module 310 is configured to allocate an ID to the client 350, where the allocation may be dynamically allocated to the client 350 through an API (Application Programming Interface) Interface, or provide an SDK (Software Development Kit) for the client 350 when the client 350 downloads and installs, so that the client 350 obtains the ID based on the SDK. The client 350 carries the parameter in the access request to indicate its identity in the subsequent interaction process with each service system.
The identification collection management module 320 is used for collecting the access condition of the client to the business service system. Because the client carries the ID of the client in the process of interacting with each service system, the ID of the client runs through the whole link of the client and each service system for data interaction. When the access request of the client passes through the link node, the link node sends the information of the link node and the ID of the client to the identifier collection management module 320, and the identifier collection management module 320 is responsible for storing and summarizing the information and generating a client identifier set corresponding to each link node.
For example, the client 350 initiates an access request 1 to the business service system 361, and the business service system 361 needs to call the business service system 362, the business service system 363, and the like to cooperatively process the access request 1, so that the access request 1 passes through the business service systems 361 to 363. The service systems 361 to 363 acquire the ID of the client 350 from the access request 1, and report the ID collection management module 320. For another example, the client 350 initiates an access request N to the service system 364, and the service system 364 obtains the ID of the client 350 from the access request N and reports to the identifier collection management module 320. The identifier collection management module 320 updates the client identifier sets 371 to 374 corresponding to the service systems 361 to 364, respectively, based on the IDs reported by the service systems 361 to 364, respectively.
It should be noted that, here, the link node is taken as an example of the business service system, in other examples, the link node may also refine service interfaces included in the business service system to collect a set of client identifiers corresponding to each service interface.
The crash information collection module 330 is configured to provide an API interface, and is configured to receive crash information reported by the client 350 when the client 350 crashes, where the crash information includes crash environment information, crash details, and an ID of the client. The client 350 is pre-configured with a relevant SDK, and based on the SDK, when a crash occurs, relevant information is uploaded to a corresponding API interface of the crash information collection module 330. The crash information collection module obtains a crash identifier set 380 based on the reported crash information.
The service crash location module 340 is used for quickly locating a service system and a service version causing crash, and the specific method is as follows: firstly, a crash identifier set 380 obtained by the crash information collection module 330 is obtained, then, a matching algorithm is used to perform matching analysis on the crash identifier set 380 and each of the client identifier sets 371 to 374 in the identifier collection management module 320, and when the crash identifier set 380 is matched with a certain client identifier set, a service system corresponding to the client identifier set is determined as a problem service system, so that a problem service system 391 and a problem service system 392 are obtained. The business service system that may cause the crash is quickly located to a small extent. Then, the real reason of the crash can be further determined by means of analysis or version rollback, and the problem can be repaired.
In summary, the method provided in the embodiment of the present application determines that the target crash event is related to the target service node when the crash identifier set matches the client identifier set corresponding to the target service node. Therefore, the service node related to the target crash event can be positioned, and the processing efficiency of the crash event is improved.
As the implementation of the method, the application also provides a crash processing device. FIG. 4 shows a schematic diagram of a crash processing apparatus according to one embodiment of the application. As shown in fig. 4, the crash processing apparatus includes:
a client determining module 410, configured to determine M clients where the target crash event occurs; wherein M is a positive integer;
a set determining module 420, configured to obtain a crash identifier set based on the identifier information of the M clients;
a correlation determination module 430, configured to determine that the target crash event is correlated with the target service node when the crash identifier set matches with the client identifier set corresponding to the target service node; the client identification set comprises identification information of N clients accessing the target service node, wherein N is a positive integer.
Illustratively, as shown in fig. 5, the crash processing apparatus further includes:
an identifier receiving module 510, configured to receive identifier information sent by a target service node; the identification information is obtained by the target service node from the received access request of the client;
the set updating module 520 is configured to update the client identifier set corresponding to the target service node based on the identifier information sent by the target service node.
Illustratively, as shown in fig. 5, the client determining module 410 includes:
the clustering unit 411 is configured to cluster the received crash information of the client to obtain K crash information sets corresponding to the K crash events; wherein K is a positive integer;
the determining unit 412 is configured to determine, based on a crash information set corresponding to a target crash event in the K crash events, K clients that have the target crash event.
Illustratively, the client determining module is configured to determine M clients with the target crash event when a crash rate corresponding to the target crash event is greater than a preset threshold.
Illustratively, as shown in fig. 5, the crash processing apparatus further includes:
a crash time determining module 530, configured to determine a time range in which the target crash event occurs based on the crash information of the M clients in which the target crash event occurs;
a target time determination module 540, configured to determine a target time range based on a time range in which the target crash event occurs;
and a node determining module 550, configured to determine, as the target service node, the service node whose service version is updated within the target time range.
Illustratively, the target service node is a business service system or a service interface included in the business service system.
The crash processing device provided by the embodiment of the application can realize the crash processing method provided by the embodiment of the application, and has corresponding beneficial effects.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 6 is a block diagram of an electronic device according to the crash processing method in the embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 6, the electronic apparatus includes: one or more processors 601, memory 602, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 6, one processor 601 is taken as an example.
The memory 602 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by the at least one processor to cause the at least one processor to perform the crash handling method provided herein. The non-transitory computer-readable storage medium of the present application stores computer instructions for causing a computer to perform the crash processing method provided by the present application.
The memory 602, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the crash processing methods in the embodiments of the present application (e.g., the client determination module 410, the set determination module 420, and the correlation determination module 430 shown in fig. 4). The processor 601 executes various functional applications and data processing of the server by running non-transitory software programs, instructions and modules stored in the memory 602, that is, implementing the crash processing method in the above method embodiment.
The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the electronic device by the crash processing method, and the like. Further, the memory 602 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 602 optionally includes memory located remotely from the processor 601, and these remote memories may be connected to the crash processing method's electronic device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the crash handling method may further include: an input device 603 and an output device 604. The processor 601, the memory 602, the input device 603 and the output device 604 may be connected by a bus or other means, and fig. 6 illustrates the connection by a bus as an example.
The input device 603 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device of the crash handling method, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointer, one or more mouse buttons, a track ball, a joystick, or other input device. The output devices 604 may include a display device, auxiliary lighting devices (e.g., LEDs), and tactile feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computing programs (also known as programs, software applications or code) include machine instructions for a programmable processor, and may be implemented using a high-level procedural and/or object-oriented programming language, and/or assembly/machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server) or that includes a middleware component (e.g., an application server) or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service expansibility in the traditional physical host and Virtual Private Server (VPS) service. The server may also be a server of a distributed system, or a server incorporating a blockchain.
According to the technical scheme of the embodiment of the application, whether the target crash event is related to the target service node or not can be determined. Therefore, the service node related to the target crash event can be positioned, and the processing efficiency of the crash event is improved.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present application can be achieved, and the present invention is not limited herein.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (14)
1. A crash handling method, comprising:
determining M clients with target crash events; wherein M is a positive integer;
obtaining a crash identification set based on the identification information of the M clients;
determining that the target crash event is related to a target service node when the crash identifier set is matched with a client identifier set corresponding to the target service node; the client identification set comprises identification information of N clients accessing the target service node, wherein N is a positive integer.
2. The method of claim 1, further comprising:
receiving identification information sent by the target service node; the identification information is obtained by the target service node from the received access request of the client;
and updating the client identification set corresponding to the target service node based on the identification information sent by the target service node.
3. The method of claim 1 or 2, wherein the determining M clients at which a target crash event occurs comprises:
clustering the received crash information of the client to obtain K crash information sets corresponding to K crash events; wherein K is a positive integer;
and determining M clients with the target crash event based on the crash information set corresponding to the target crash event in the K crash events.
4. The method of claim 1 or 2, wherein the determining M clients at which a target crash event occurs comprises:
and determining M clients with the target crash event when the crash rate corresponding to the target crash event is greater than a preset threshold.
5. The method of claim 1 or 2, further comprising:
determining a time range of the target crash event based on crash information of the M clients in which the target crash event occurs;
determining a target time range based on the time range within which the target crash event occurred;
and determining the service node which updates the service version of the business in the target time range as the target service node.
6. The method according to any of claims 1 or 2, wherein the target service node is a business service system or a service interface comprised by a business service system.
7. A crash processing apparatus, comprising:
the client determining module is used for determining M clients with target crash events; wherein M is a positive integer;
the set determining module is used for obtaining a crash identification set based on the identification information of the M clients;
a correlation determination module, configured to determine that the target crash event is correlated with a target service node when the crash identifier set matches a client identifier set corresponding to the target service node; the client identification set comprises identification information of N clients accessing the target service node, wherein N is a positive integer.
8. The apparatus of claim 7, further comprising:
the identification receiving module is used for receiving the identification information sent by the target service node; the identification information is obtained by the target service node from the received access request of the client;
and the set updating module is used for updating the client identifier set corresponding to the target service node based on the identifier information sent by the target service node.
9. The apparatus of claim 7 or 8, wherein the client determination module comprises:
the clustering unit is used for clustering the received crash information of the client to obtain K crash information sets corresponding to the K crash events; wherein K is a positive integer;
and the determining unit is used for determining the K clients with the target crash event based on the crash information set corresponding to the target crash event in the K crash events.
10. The apparatus of claim 7 or 8, wherein the client determining module is configured to determine M clients that have the target crash event when a crash rate corresponding to the target crash event is greater than a preset threshold.
11. The apparatus of claim 7 or 8, further comprising:
the crash time determining module is used for determining the time range of the target crash event based on the crash information of the M clients in which the target crash event occurs;
a target time determination module for determining a target time range based on a time range within which the target crash event occurred;
and the node determining module is used for determining the service node which updates the service version in the target time range as the target service node.
12. The apparatus according to any of claims 7 or 8, wherein the target service node is a business service system or a service interface included in a business service system.
13. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.
14. A non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011311143.6A CN112437152B (en) | 2020-11-20 | 2020-11-20 | Crash processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011311143.6A CN112437152B (en) | 2020-11-20 | 2020-11-20 | Crash processing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112437152A true CN112437152A (en) | 2021-03-02 |
| CN112437152B CN112437152B (en) | 2022-05-17 |
Family
ID=74693173
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011311143.6A Active CN112437152B (en) | 2020-11-20 | 2020-11-20 | Crash processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112437152B (en) |
Citations (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6810493B1 (en) * | 2000-03-20 | 2004-10-26 | Palm Source, Inc. | Graceful recovery from and avoidance of crashes due to notification of third party applications |
| CN202093513U (en) * | 2011-03-30 | 2011-12-28 | 中国工商银行股份有限公司 | Bulk data processing system |
| CN102427480A (en) * | 2011-12-31 | 2012-04-25 | 北京新媒传信科技有限公司 | Application access method in a plurality of application service platform systems |
| CN102546708A (en) * | 2010-12-27 | 2012-07-04 | 阿里巴巴集团控股有限公司 | Plug-in obtaining method and system as well as relevant devices |
| EP2633665A2 (en) * | 2010-12-14 | 2013-09-04 | Apple Inc. | Real-time or near real-time streaming with compressed playlists |
| CN103684833A (en) * | 2012-09-21 | 2014-03-26 | 成都勤智数码科技股份有限公司 | Efficient terminal alarm processing method |
| WO2014075599A1 (en) * | 2012-11-15 | 2014-05-22 | Tencent Technology (Shenzhen) Company Limited | Method, device and system for processing client environment data |
| CN104199749A (en) * | 2014-09-17 | 2014-12-10 | 百度在线网络技术（北京）有限公司 | Crash information processing method and crash information processing device |
| CN104601370A (en) * | 2014-12-15 | 2015-05-06 | 四川长虹电器股份有限公司 | Information processing method and cloud server |
| CN104965775A (en) * | 2015-04-23 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Reconstruction method for application software fault site, server, and terminal |
| CN105827459A (en) * | 2016-05-09 | 2016-08-03 | 腾讯科技（深圳）有限公司 | Method and device for calling maintenance center by intelligent device |
| CN107239381A (en) * | 2017-06-07 | 2017-10-10 | 北京奇虎科技有限公司 | The processing method of crash info, apparatus and system |
| CN107947973A (en) * | 2017-11-17 | 2018-04-20 | 深圳泉眼体育运营管理有限公司 | Application crashes Notification Method, system, mobile terminal and server |
| CN108134692A (en) * | 2017-12-18 | 2018-06-08 | 上海斐讯数据通信技术有限公司 | A kind of fault handling method and system based on mark figure |
| CN108287769A (en) * | 2018-02-28 | 2018-07-17 | 腾讯科技（深圳）有限公司 | A kind of information processing method and device |
| CN109032909A (en) * | 2018-07-18 | 2018-12-18 | 携程旅游信息技术（上海）有限公司 | Processing method, system, equipment and the storage medium of application crash log |
| CN109324965A (en) * | 2018-09-18 | 2019-02-12 | 郑州云海信息技术有限公司 | A kind of automated testing method that monitoring flock causes client to be collapsed |
| CN109669795A (en) * | 2018-12-14 | 2019-04-23 | 麒麟合盛网络技术股份有限公司 | Crash info processing method and processing device |
| CN110083472A (en) * | 2019-03-19 | 2019-08-02 | 深圳壹账通智能科技有限公司 | Application crashes processing method, device, computer equipment and storage medium |
| CN110399246A (en) * | 2019-07-30 | 2019-11-01 | 腾讯科技（深圳）有限公司 | Program restorative procedure and device |
| CN110675079A (en) * | 2019-09-30 | 2020-01-10 | 腾讯科技（深圳）有限公司 | Fault data processing method and device and computer equipment |
| CN111416857A (en) * | 2020-03-16 | 2020-07-14 | 广州市百果园信息技术有限公司 | Client crash processing method, device, system, equipment and storage medium |
| US20200334102A1 (en) * | 2019-04-16 | 2020-10-22 | Dell Products L.P. | Systems And Methods For Preventing Client Application Crashes Due To Operating System Updates |
-
2020
- 2020-11-20 CN CN202011311143.6A patent/CN112437152B/en active Active
Patent Citations (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6810493B1 (en) * | 2000-03-20 | 2004-10-26 | Palm Source, Inc. | Graceful recovery from and avoidance of crashes due to notification of third party applications |
| EP2633665A2 (en) * | 2010-12-14 | 2013-09-04 | Apple Inc. | Real-time or near real-time streaming with compressed playlists |
| CN102546708A (en) * | 2010-12-27 | 2012-07-04 | 阿里巴巴集团控股有限公司 | Plug-in obtaining method and system as well as relevant devices |
| CN202093513U (en) * | 2011-03-30 | 2011-12-28 | 中国工商银行股份有限公司 | Bulk data processing system |
| CN102427480A (en) * | 2011-12-31 | 2012-04-25 | 北京新媒传信科技有限公司 | Application access method in a plurality of application service platform systems |
| CN103684833A (en) * | 2012-09-21 | 2014-03-26 | 成都勤智数码科技股份有限公司 | Efficient terminal alarm processing method |
| WO2014075599A1 (en) * | 2012-11-15 | 2014-05-22 | Tencent Technology (Shenzhen) Company Limited | Method, device and system for processing client environment data |
| CN104199749A (en) * | 2014-09-17 | 2014-12-10 | 百度在线网络技术（北京）有限公司 | Crash information processing method and crash information processing device |
| CN104601370A (en) * | 2014-12-15 | 2015-05-06 | 四川长虹电器股份有限公司 | Information processing method and cloud server |
| CN104965775A (en) * | 2015-04-23 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Reconstruction method for application software fault site, server, and terminal |
| CN105827459A (en) * | 2016-05-09 | 2016-08-03 | 腾讯科技（深圳）有限公司 | Method and device for calling maintenance center by intelligent device |
| CN107239381A (en) * | 2017-06-07 | 2017-10-10 | 北京奇虎科技有限公司 | The processing method of crash info, apparatus and system |
| CN107947973A (en) * | 2017-11-17 | 2018-04-20 | 深圳泉眼体育运营管理有限公司 | Application crashes Notification Method, system, mobile terminal and server |
| CN108134692A (en) * | 2017-12-18 | 2018-06-08 | 上海斐讯数据通信技术有限公司 | A kind of fault handling method and system based on mark figure |
| CN108287769A (en) * | 2018-02-28 | 2018-07-17 | 腾讯科技（深圳）有限公司 | A kind of information processing method and device |
| CN109032909A (en) * | 2018-07-18 | 2018-12-18 | 携程旅游信息技术（上海）有限公司 | Processing method, system, equipment and the storage medium of application crash log |
| CN109324965A (en) * | 2018-09-18 | 2019-02-12 | 郑州云海信息技术有限公司 | A kind of automated testing method that monitoring flock causes client to be collapsed |
| CN109669795A (en) * | 2018-12-14 | 2019-04-23 | 麒麟合盛网络技术股份有限公司 | Crash info processing method and processing device |
| CN110083472A (en) * | 2019-03-19 | 2019-08-02 | 深圳壹账通智能科技有限公司 | Application crashes processing method, device, computer equipment and storage medium |
| US20200334102A1 (en) * | 2019-04-16 | 2020-10-22 | Dell Products L.P. | Systems And Methods For Preventing Client Application Crashes Due To Operating System Updates |
| CN110399246A (en) * | 2019-07-30 | 2019-11-01 | 腾讯科技（深圳）有限公司 | Program restorative procedure and device |
| CN110675079A (en) * | 2019-09-30 | 2020-01-10 | 腾讯科技（深圳）有限公司 | Fault data processing method and device and computer equipment |
| CN111416857A (en) * | 2020-03-16 | 2020-07-14 | 广州市百果园信息技术有限公司 | Client crash processing method, device, system, equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| CHQJ_163: "理解和分析App崩溃报告(译)", 《HTTPS://BLOG.CSDN.NET/CHQJ_163/ARTICLE/DETAILS/90375723》 * |
| ZIQIANG ZHOU: "Research and Implementation of Mobile Application Security Detection Combining Static and Dynamic", 《2018 10TH INTERNATIONAL CONFERENCE ON MEASURING TECHNOLOGY AND MECHATRONICS AUTOMATION (ICMTMA)》 * |
| 轩轩笔记: "应用崩溃时搜集信息并发送到服务端", 《HTTPS://BLOG.CSDN.NET/U010047390/ARTICLE/DETAILS/54406269?LOCATIONNUM=9&FPS=1》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112437152B (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110570217B (en) | Cheating detection method and device | |
| CN111694646A (en) | Resource scheduling method and device, electronic equipment and computer readable storage medium | |
| CN109672722B (en) | Data deployment method and device, computer storage medium and electronic equipment | |
| CN111880914A (en) | Resource scheduling method, resource scheduling apparatus, electronic device, and storage medium | |
| CN112925651A (en) | Application resource deployment method, device, electronic equipment and medium | |
| CN111506401B (en) | Automatic driving simulation task scheduling method and device, electronic equipment and storage medium | |
| CN111586126A (en) | Method, device and equipment for pre-downloading small program and storage medium | |
| CN111625195A (en) | Method and device for server capacity expansion | |
| US10601954B2 (en) | Sandboxing requests for web services | |
| CN112351042B (en) | Attack flow calculation method and device, electronic equipment and storage medium | |
| CN112565356A (en) | Data storage method and device and electronic equipment | |
| CN111782341B (en) | Method and device for managing clusters | |
| CN111831752A (en) | Distributed database space arrangement method, device, equipment and storage medium | |
| CN110995687B (en) | Cat pool equipment identification method, device, equipment and storage medium | |
| CN111782147A (en) | Method and apparatus for cluster scale-up | |
| CN111767149A (en) | Scheduling method, device, equipment and storage equipment | |
| CN112437152B (en) | Crash processing method and device, electronic equipment and storage medium | |
| CN112069137A (en) | Method and device for generating information, electronic equipment and computer readable storage medium | |
| CN111796940A (en) | Resource allocation method and device and electronic equipment | |
| CN111597026B (en) | Method and device for acquiring information | |
| CN113821232A (en) | Model updating method and device | |
| CN112532483A (en) | Test method, test device, electronic equipment and storage medium | |
| CN113778973A (en) | Data storage method and device | |
| CN112346512A (en) | Time synchronization method and device | |
| CN111639116A (en) | Data access connection session protection method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |