CN112181696B - Abnormality information processing method, apparatus, and storage medium - Google Patents
Abnormality information processing method, apparatus, and storage medium Download PDFInfo
- Publication number
- CN112181696B CN112181696B CN202010900314.2A CN202010900314A CN112181696B CN 112181696 B CN112181696 B CN 112181696B CN 202010900314 A CN202010900314 A CN 202010900314A CN 112181696 B CN112181696 B CN 112181696B
- Authority
- CN
- China
- Prior art keywords
- abnormal
- abnormality
- prompt information
- type
- exception
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application provides an abnormal information processing method, equipment and a storage medium. In some embodiments of the present application, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not; if the system has an abnormal condition, according to the abnormal type of the abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type, the system abnormal processing efficiency is high, and the user experience is good.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a method, an apparatus, and a storage medium for processing abnormal information.
Background
At present, parameter verification is carried out everywhere in codes, various abnormal conditions can be encountered by a system in the running process, some abnormal conditions need background processing and are sent to a page to prompt a user, but the system does not process the abnormal conditions. Therefore, the system has poor efficiency of exception handling and poor user experience.
Disclosure of Invention
Aspects of the present application provide an anomaly information processing method, apparatus, and storage medium, which are used to improve the efficiency of system anomaly processing and improve user experience.
The embodiment of the application provides an abnormal information processing method, which is applicable to a server and comprises the following steps:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result;
if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
The embodiment of the application provides an abnormal information processing method, which is applicable to a service end and comprises the following steps:
responding to the input operation of a configuration user on an abnormal type, and acquiring the abnormal type;
and responding to the operation of configuring the abnormal prompt information of the abnormal type by the configuration user, and establishing a mapping relation between the abnormal type and the abnormal prompt information.
The embodiment of the application provides a server, which comprises: a memory and a processor;
the memory is used for storing one or more computer instructions;
the processor is configured to execute the one or more computer instructions to:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result;
if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
Embodiments of the present application provide a computer-readable storage medium storing a computer program that, when executed by one or more processors, causes the one or more processors to perform acts comprising:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result;
if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
In some embodiments of the present application, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not; if the system has an abnormal condition, according to the abnormal type of the abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type, the system abnormal processing efficiency is high, and the user experience is good.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
FIG. 1 is a schematic diagram of an exception information handling system according to an exemplary embodiment of the present application;
FIG. 2a is a flowchart illustrating an exception information processing method according to an exemplary embodiment of the present application;
FIG. 2b is a flowchart illustrating an exception information processing method according to an exemplary embodiment of the present application;
fig. 3 is a schematic structural diagram of a server according to an exemplary embodiment of the present application;
fig. 4 is a schematic structural diagram of a service end according to an exemplary embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
At present, parameter verification is carried out everywhere in codes, various abnormal conditions can be encountered by a system in the running process, some abnormal conditions need background processing and are sent to a page to prompt a user, but the system does not process the abnormal conditions. Therefore, the system has poor efficiency of exception handling and poor user experience.
Aiming at the technical problems, in some embodiments of the present application, a server receives user operation data sent by a user terminal; performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not; if the system has an abnormal condition, according to the abnormal type of the abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type, the system abnormal processing efficiency is high, and the user experience is good.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
Fig. 1 is a schematic diagram of an exception information processing system 10 according to an exemplary embodiment of the present application. As shown in fig. 1, the abnormality information processing system 10 includes a plurality of service terminals 10a, a service terminal 10b, and a user terminal 10c. Wherein, a plurality of service terminals 10a, user terminals 10c and a service terminal 10b establish communication connection.
In this embodiment, the service terminals 10a, the user terminal 10c and the service terminal 10b may be connected wirelessly or by wires. Optionally, the multiple service ends 10a and the user terminal 10c may use WIFI, bluetooth, infrared, and other communication modes to establish communication connection with the service end 10b, or the multiple service ends 10a and the user terminal 10c may also establish communication connection with the service end 10b through a mobile network. The network system of the mobile network may be any one of 2G (GSM), 2.5G (GPRS), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS), 4G (LTE), 4g+ (lte+), wiMax, etc.
In this embodiment, the service end 10a is configured to obtain an exception type in response to an input operation of the configuration user on the exception type; and responding to the operation of configuring the abnormal prompt information of the abnormal type by the configuration user, and establishing a mapping relation between the abnormal type and the abnormal prompt information. The service end 10a includes an electronic display screen, which may be a computer device or a handheld device, and its implementation forms may be various, for example, smart phones, personal computers, tablet computers, smart speakers, etc.
In this embodiment, the user terminal 10c is configured to display the abnormal prompt information for viewing by a user. The user terminal 10c includes an electronic display screen, which may be a computer device or a handheld device, and may be implemented in various manners, for example, a smart phone, a personal computer, a tablet computer, a smart speaker, etc.
In this embodiment, the server 10b performs parameter verification and exception handling by using an exception handling component. In the present embodiment, the implementation form of the server 10b is not limited, and for example, the server 10b may be a conventional server, a cloud host, a virtual center, or the like. The server 10b mainly includes a processor, a hard disk, a memory, a system bus, and the like, and a general computer architecture type.
It should be noted that, the information processing system 10 encapsulates the parameter verification and the exception processing corresponding to the service end 10a into a jar packet to form an exception handling component. The exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process. Different service end 10a may introduce these jar packets into respective code files, and then may directly use the classes and attributes and methods in these jar packets. Codes among different service ends are more unified and normative, and parameter verification and exception handling of the whole system are classified as exception handling components for handling, so that the method is more convenient.
Parameter verification is a common problem, and user input needs to be verified in both front-end and background, so that correctness of system data is guaranteed. The exception handling component performs parameter verification and exception handling; when the parameter verification fails, a specific reason for the failure of the parameter verification needs to be sent to the corresponding service end 10 a. Abnormal conditions of the system include business anomalies and system anomalies, business anomalies including, but not limited to, the following: the user name or password is wrong when logging in, and the account number is registered when newly creating a user; system anomalies include, but are not limited to, the following: system crash, call failure between services, database exception and memory overflow.
In this embodiment, the configuration user needs to establish a mapping relationship between the anomaly type and the anomaly prompt information through the service end 10 a. An alternative embodiment is that, in response to an input operation of an abnormality type by a configuration user, the abnormality type is acquired; and responding to the operation of configuring the abnormal prompt information of the abnormal type by the configuration user, and establishing a mapping relation between the abnormal type and the abnormal prompt information. For example, when the parameter verification fails, detailed prompt information is given to the user according to the reason that the parameter verification fails; when the business is abnormal, such as user name or password error during login, account number is registered during newly-built user, and the abnormal information should give the user accurate prompt information as far as possible, for example, "user name input error", "password input error", "account number is registered", etc.; in the event of a system failure, such as a system crash, a failure in call between services, a database exception, and a memory overflow, the system exception may prompt the user for a prompt such as "system exception, please contact with an administrator", and the like, without specific prompts, because the user will not care whether the service is abnormal or the database is abnormal, but the background log should record detailed error stack information at this time, so as to facilitate the operation and maintenance or the developer to locate the problem.
In this embodiment, the user performs an operation through the user terminal 10c to generate user operation data, and the user terminal 10c sends the user operation data to the server 10b; after receiving the user operation data sent by the user terminal 10c, the server 10b performs parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter verification result is that the verification is passed, continuously monitoring whether the system has an abnormal condition, and if the system has the abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition. And if the parameter verification result is that the verification is not passed, sending verification abnormality prompt information to the corresponding service end.
In the above embodiment, if the system has an abnormal situation, according to the abnormal type of the abnormal situation, a corresponding abnormal prompt message is sent to the service end corresponding to the abnormal type.
Optionally, if the system has system abnormality, intercepting the system abnormality by using an abnormality processing component; determining an abnormality type corresponding to the system abnormality and first abnormality prompt information corresponding to the abnormality type; and sending first abnormality prompt information to a service end corresponding to an abnormality type corresponding to the system abnormality. In addition, the server 10b may also send the first abnormal prompting information to the user terminal used by the user, so that the user can view the first abnormal prompting information.
Optionally, if the system has a business abnormality, capturing the business abnormality by using an abnormality processing component; determining an abnormal type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormal type; and sending second abnormality prompt information to a service end corresponding to the abnormality type corresponding to the system abnormality. In addition, the server 10b may also send the first abnormal prompting information to the user terminal used by the user, so that the user can view the first abnormal prompting information.
In the above embodiment, for the case that the first exception does not call the exception handling component to perform exception handling, the exception handling component needs to actively capture the exception by using the exception handling component to perform handling. One way that may be implemented is that the server 10b monitors whether the first exception is handled by the exception handling component; if not, capturing a first exception by using the exception handling component, and processing the first exception by using the exception handling component; wherein the first anomaly is any one of the anomalies.
In the embodiment of the system, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not; if the system has an abnormal condition, according to the abnormal type of the abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type, the system abnormal processing efficiency is high, and the user experience is good.
In addition to the above-described exception information processing system 10, some embodiments of the present application also provide an exception information processing method, which may be implemented depending on the above-described exception information processing system 10, but is not limited to the exception information processing system 10 provided by the above-described embodiments.
From the perspective of the server, fig. 2a is a schematic flow chart of an anomaly information processing method according to an exemplary embodiment of the present application. As shown in fig. 2a, the method comprises:
s211: receiving user operation data sent by a user terminal;
s212: performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter verification result is that the verification is passed, step S213 is executed, and if the parameter verification result is that the verification is not passed, step S214 is executed;
s213: continuously monitoring whether the system has an abnormal condition, and executing S215 if the system has the abnormal condition;
s214: sending parameter verification exception prompt information to a corresponding service end;
s215: and sending corresponding abnormal prompt information to a service end corresponding to the abnormal type according to the abnormal type of the abnormal condition.
From the service side perspective, fig. 2b is a schematic flow chart of an anomaly information processing method according to an exemplary embodiment of the present application. As shown in fig. 2b, the method comprises:
s221: responding to the input operation of the configuration user on the abnormal type, and acquiring the abnormal type;
s222: and responding to the operation of configuring the abnormal prompt information of the abnormal type by the configuration user, and establishing a mapping relation between the abnormal type and the abnormal prompt information.
In this embodiment, the service end is configured to respond to an input operation of the configuration user on the exception type, and obtain the exception type; and responding to the operation of configuring the abnormal prompt information of the abnormal type by the configuration user, and establishing a mapping relation between the abnormal type and the abnormal prompt information. The service end comprises an electronic display screen, which can be a computer device or a handheld device, and can be realized in various modes, such as a smart phone, a personal computer, a tablet personal computer, a smart sound box and the like.
In this embodiment, the user terminal is configured to display the abnormal prompt information for the user to view. The user terminal comprises an electronic display screen, which can be a computer device or a handheld device, and can be realized in various modes, such as a smart phone, a personal computer, a tablet personal computer, a smart sound box and the like.
In this embodiment, the server uses the exception handling component to perform parameter verification and handling of the exception condition. In this embodiment, the implementation form of the server is not limited, and for example, the server may be a conventional server, a cloud host, a virtual center, or other server devices. The server side mainly comprises a processor, a hard disk, a memory, a system bus and the like, and a general computer architecture type.
It should be noted that, the information processing system 10 encapsulates the parameter verification and the exception processing corresponding to the service end into a jar packet to form an exception handling component. The exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process. Different service ends can introduce the jar packets into respective code files, and then can directly use the classes, attributes and methods in the jar packets. Codes among different service ends are more unified and normative, and parameter verification and exception handling of the whole system are classified as exception handling components for handling, so that the method is more convenient.
Parameter verification is a common problem, and user input needs to be verified in both front-end and background, so that correctness of system data is guaranteed. The exception handling component performs parameter verification and exception handling; when the parameter verification fails, a specific reason for the failure of the parameter verification needs to be sent to the corresponding service end. Abnormal conditions of the system include business anomalies and system anomalies, business anomalies including, but not limited to, the following: the user name or password is wrong when logging in, and the account number is registered when newly creating a user; system anomalies include, but are not limited to, the following: system crash, call failure between services, database exception and memory overflow.
In this embodiment, the configuration user needs to establish a mapping relationship between the anomaly type and the anomaly prompt information through the service end. An alternative embodiment is that, in response to an input operation of an abnormality type by a configuration user, the abnormality type is acquired; and responding to the operation of configuring the abnormal prompt information of the abnormal type by the configuration user, and establishing a mapping relation between the abnormal type and the abnormal prompt information. For example, when the parameter verification fails, detailed prompt information is given to the user according to the reason that the parameter verification fails; when the business is abnormal, such as user name or password error during login, account number is registered during newly-built user, and the abnormal information should give the user accurate prompt information as far as possible, for example, "user name input error", "password input error", "account number is registered", etc.; in the event of a system failure, such as a system crash, a failure in call between services, a database exception, and a memory overflow, the system exception may prompt the user for a prompt such as "system exception, please contact with an administrator", and the like, without specific prompts, because the user will not care whether the service is abnormal or the database is abnormal, but the background log should record detailed error stack information at this time, so as to facilitate the operation and maintenance or the developer to locate the problem.
In this embodiment, a user performs an operation through a user terminal, generates user operation data, and the user terminal sends the user operation data to a server; after receiving user operation data sent by a user terminal, the server side performs parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter verification result is that the verification is passed, continuously monitoring whether the system has an abnormal condition, and if the system has the abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition. And if the parameter verification result is that the verification is not passed, sending verification abnormality prompt information to the corresponding service end.
In the above embodiment, if the system has an abnormal situation, according to the abnormal type of the abnormal situation, a corresponding abnormal prompt message is sent to the service end corresponding to the abnormal type.
Optionally, if the system has system abnormality, intercepting the system abnormality by using an abnormality processing component; determining an abnormality type corresponding to the system abnormality and first abnormality prompt information corresponding to the abnormality type; and sending first abnormality prompt information to a service end corresponding to an abnormality type corresponding to the system abnormality. In addition, the server side can also send the first abnormal prompt information to the user terminal used by the user so as to enable the user to check the first abnormal prompt information.
Optionally, if the system has a business abnormality, capturing the business abnormality by using an abnormality processing component; determining an abnormal type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormal type; and sending second abnormality prompt information to a service end corresponding to the abnormality type corresponding to the system abnormality. In addition, the server side can also send the first abnormal prompt information to the user terminal used by the user so as to enable the user to check the first abnormal prompt information.
In the above embodiment, for the case that the first exception does not call the exception handling component to perform exception handling, the exception handling component needs to actively capture the exception by using the exception handling component to perform handling. One implementation way is that the server monitors whether to process the first exception by using the exception processing component; if not, capturing a first exception by using the exception handling component, and processing the first exception by using the exception handling component; wherein the first anomaly is any one of the anomalies.
In the embodiment of the method, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not; if the system has an abnormal condition, according to the abnormal type of the abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type, the system abnormal processing efficiency is high, and the user experience is good.
It should be noted that, the execution subjects of each step of the method provided in the above embodiment may be the same device, or the method may also be executed by different devices. For example, the execution subject of step S211 to step S213 may be the device a; for another example, the execution subject of steps S211 and S212 may be the device a, and the execution subject of step S213 may be the device B; etc.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations such as S211, S212, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.
Fig. 3 is a schematic structural diagram of a server according to an exemplary embodiment of the present application. As shown in fig. 4, the server includes: a memory 301 and a processor 302. In addition, the server also includes necessary components such as a power supply component 303 and a communication component 304.
The memory 301 is used for storing a computer program, and may be configured to store other various data to support operations on a server side. Examples of such data include instructions for any application or method operating on a server.
The memory 301 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
A communication component 304 for data transmission with other devices.
A processor 302, executable computer instructions stored in memory 301, for: receiving user operation data sent by a user terminal; performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not; if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition; the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
Optionally, if the system has an abnormal situation, the processor 302 is specifically configured to, according to an abnormal type of the abnormal situation, send corresponding abnormal prompt information to a service end corresponding to the abnormal type: if the system is abnormal, intercepting the system abnormality by using an abnormality processing component; determining an abnormality type corresponding to the system abnormality and first abnormality prompt information corresponding to the abnormality type; and sending first abnormality prompt information to a service end corresponding to an abnormality type corresponding to the system abnormality.
Optionally, the processor 302 may be further configured to: and sending the first abnormal prompt information to a user terminal used by the user so as to enable the user to check the first abnormal prompt information.
Optionally, if the system has an abnormal situation, when the processor 302 sends corresponding abnormal prompt information to the service end corresponding to the abnormal type according to the abnormal type of the abnormal situation, the processor is specifically configured to: if the system has the business abnormality, capturing the business abnormality by using an abnormality processing component; determining an abnormal type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormal type; and sending second abnormality prompt information to a service end corresponding to the abnormality type corresponding to the system abnormality.
Optionally, the processor 302 may be further configured to: and sending the second abnormal prompt information to a user terminal used by the user so as to enable the user to check the second abnormal prompt information.
Optionally, the processor 302 may be further configured to: monitoring whether the first exception is processed by using an exception processing component; if not, capturing a first exception by using the exception handling component, and processing the first exception by using the exception handling component; wherein the first anomaly is any one of the anomalies.
Optionally, the processor 302 may be further configured to: and sending the parameter verification result and the abnormal condition to a monitoring platform so as to monitor the parameter verification result and the abnormal condition by the monitoring platform.
Accordingly, embodiments of the present application also provide a computer-readable storage medium storing a computer program. The computer-readable storage medium stores a computer program, which when executed by one or more processors, causes the one or more processors to perform the steps in the method embodiment of fig. 2 a.
Fig. 4 is a schematic structural diagram of a service end according to an exemplary embodiment of the present application. As shown in fig. 4, the service end includes: a memory 401 and a processor 402. In addition, the service end further comprises necessary components such as a power supply component 403, a communication component 404 and the like.
The memory 401 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
A communication component 404 for data transmission with other devices.
A processor 402, executable computer instructions stored in memory 401, for: responding to the input operation of the configuration user on the abnormal type, and acquiring the abnormal type; and responding to the operation of configuring the abnormal prompt information of the abnormal type by the configuration user, and establishing a mapping relation between the abnormal type and the abnormal prompt information.
Accordingly, embodiments of the present application also provide a computer-readable storage medium storing a computer program. The computer-readable storage medium stores a computer program, which when executed by one or more processors, causes the one or more processors to perform the steps in the method embodiment of fig. 2 b.
The communication assembly of fig. 3 and 4 described above is configured to facilitate wired or wireless communication between the device in which the communication assembly is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as a mobile communication network of WiFi,2G, 3G, 4G/LTE, 5G, etc., or a combination thereof. In one exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
The power supply assembly of fig. 3 and 4 provides power to the various components of the device in which the power supply assembly is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.
In the embodiment of the method, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result; if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not; if the system has an abnormal condition, according to the abnormal type of the abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type, the system abnormal processing efficiency is high, and the user experience is good.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.
Claims (8)
1. An anomaly information processing method suitable for a server side is characterized by comprising the following steps:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result;
if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition;
the system comprises an exception handling component, a parameter checking component, an exception handling component and a system management component, wherein the exception handling component is packaged with exception handling classes, attributes and methods and is used for checking parameters and carrying out centralized handling on exception conditions in the working process of the system;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition, wherein the method comprises the following steps:
if the system has the business abnormality, capturing the business abnormality by using an abnormality processing component;
determining an abnormality type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormality type;
and sending second abnormality prompt information to a service end corresponding to the abnormality type corresponding to the system abnormality.
2. The method of claim 1, wherein if the system has an abnormal situation, sending corresponding abnormality prompt information to a service end corresponding to the abnormal situation according to the abnormal type of the abnormal situation, including:
if the system has system abnormality, intercepting the system abnormality by using an abnormality processing component;
determining an abnormality type corresponding to the system abnormality and first abnormality prompt information corresponding to the abnormality type;
and sending the first abnormality prompt information to a service end corresponding to an abnormality type corresponding to the system abnormality.
3. The method according to claim 2, wherein the method further comprises:
and sending first abnormal prompt information to a user terminal used by a user so as to enable the user to check the first abnormal prompt information.
4. The method according to claim 1, wherein the method further comprises:
and sending second abnormal prompt information to a user terminal used by the user so as to enable the user to check the second abnormal prompt information.
5. The method according to claim 1, wherein the method further comprises:
monitoring whether the first exception is processed by using an exception processing component;
if not, capturing a first exception by using an exception handling component, and processing the first exception by using the exception handling component;
wherein the first anomaly is any one of the anomalies.
6. The method according to claim 1, wherein the method further comprises:
and sending the parameter verification result and the abnormal condition to a monitoring platform so that the monitoring platform can monitor the parameter verification result and the abnormal condition.
7. A server, comprising: a memory and a processor;
the memory is used for storing one or more computer instructions;
the processor is configured to execute the one or more computer instructions to:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result;
if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition;
the system comprises an exception handling component, a parameter checking component, an exception handling component and a system management component, wherein the exception handling component is packaged with exception handling classes, attributes and methods and is used for checking parameters and carrying out centralized handling on exception conditions in the working process of the system;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition, wherein the method comprises the following steps:
if the system has the business abnormality, capturing the business abnormality by using an abnormality processing component;
determining an abnormality type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormality type;
and sending second abnormality prompt information to a service end corresponding to the abnormality type corresponding to the system abnormality.
8. A computer-readable storage medium storing a computer program, which when executed by one or more processors causes the one or more processors to perform acts comprising:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the established exception handling assembly to generate a parameter verification result;
if the parameter check result is that the test passes, continuing to monitor whether the system has abnormal conditions or not;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition;
the system comprises an exception handling component, a parameter checking component, an exception handling component and a system management component, wherein the exception handling component is packaged with exception handling classes, attributes and methods and is used for checking parameters and carrying out centralized handling on exception conditions in the working process of the system;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal condition according to the abnormal type of the abnormal condition, wherein the method comprises the following steps:
if the system has the business abnormality, capturing the business abnormality by using an abnormality processing component;
determining an abnormality type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormality type;
and sending second abnormality prompt information to a service end corresponding to the abnormality type corresponding to the system abnormality.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010900314.2A CN112181696B (en) | 2020-08-31 | 2020-08-31 | Abnormality information processing method, apparatus, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010900314.2A CN112181696B (en) | 2020-08-31 | 2020-08-31 | Abnormality information processing method, apparatus, and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112181696A CN112181696A (en) | 2021-01-05 |
| CN112181696B true CN112181696B (en) | 2023-05-12 |
Family
ID=73924984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010900314.2A Active CN112181696B (en) | 2020-08-31 | 2020-08-31 | Abnormality information processing method, apparatus, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181696B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112764956B (en) * | 2021-01-14 | 2024-01-12 | 网宿科技股份有限公司 | Database exception handling system, database exception handling method and device |
| CN115795387A (en) * | 2022-10-27 | 2023-03-14 | 圣名科技(广州)有限责任公司 | Sensor work abnormity monitoring method and device, storage medium and electronic equipment |
| CN116821000B (en) * | 2023-08-30 | 2023-12-12 | 天津租赁资产交易中心股份有限公司 | Method for processing abnormal operation of user feedback application |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6170067B1 (en) * | 1997-05-13 | 2001-01-02 | Micron Technology, Inc. | System for automatically reporting a system failure in a server |
| CN102043682A (en) * | 2011-01-27 | 2011-05-04 | 中国农业银行股份有限公司 | Workflow exception handing method and system |
| CN102937930A (en) * | 2012-09-29 | 2013-02-20 | 重庆新媒农信科技有限公司 | Application program monitoring system and method |
| CN103269384A (en) * | 2013-06-14 | 2013-08-28 | 福建伊时代信息科技股份有限公司 | Rich client abnormality processing method, processing device and processing system |
| CN106610890A (en) * | 2015-10-21 | 2017-05-03 | 北京国双科技有限公司 | Exception processing method and apparatus |
| CN109344046A (en) * | 2018-08-09 | 2019-02-15 | 北京奇艺世纪科技有限公司 | A kind of data processing method, device, medium and electronic equipment |
| CN109726081A (en) * | 2019-01-02 | 2019-05-07 | 深圳壹账通智能科技有限公司 | Method, apparatus, computer equipment and the storage medium of service exception processing |
| CN110149343A (en) * | 2019-05-31 | 2019-08-20 | 国家计算机网络与信息安全管理中心 | A kind of abnormal communications and liaison behavioral value method and system based on stream |
| CN110166297A (en) * | 2019-05-22 | 2019-08-23 | 平安信托有限责任公司 | O&M method, system, equipment and computer readable storage medium |
| US10394691B1 (en) * | 2017-10-05 | 2019-08-27 | Tableau Software, Inc. | Resolution of data flow errors using the lineage of detected error conditions |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9354963B2 (en) * | 2014-02-26 | 2016-05-31 | Microsoft Technology Licensing, Llc | Service metric analysis from structured logging schema of usage data |
| CN108121633B (en) * | 2016-11-30 | 2021-08-17 | 北京国双科技有限公司 | Abnormity capturing method and device |
| CN109257196A (en) * | 2017-07-12 | 2019-01-22 | 阿里巴巴集团控股有限公司 | A kind of abnormality eliminating method and equipment |
| CN110187993A (en) * | 2019-05-14 | 2019-08-30 | 广州欧科信息技术股份有限公司 | A kind of processing method of misoperation, system, electronic equipment and storage medium |
-
2020
- 2020-08-31 CN CN202010900314.2A patent/CN112181696B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6170067B1 (en) * | 1997-05-13 | 2001-01-02 | Micron Technology, Inc. | System for automatically reporting a system failure in a server |
| CN102043682A (en) * | 2011-01-27 | 2011-05-04 | 中国农业银行股份有限公司 | Workflow exception handing method and system |
| CN102937930A (en) * | 2012-09-29 | 2013-02-20 | 重庆新媒农信科技有限公司 | Application program monitoring system and method |
| CN103269384A (en) * | 2013-06-14 | 2013-08-28 | 福建伊时代信息科技股份有限公司 | Rich client abnormality processing method, processing device and processing system |
| CN106610890A (en) * | 2015-10-21 | 2017-05-03 | 北京国双科技有限公司 | Exception processing method and apparatus |
| US10394691B1 (en) * | 2017-10-05 | 2019-08-27 | Tableau Software, Inc. | Resolution of data flow errors using the lineage of detected error conditions |
| CN109344046A (en) * | 2018-08-09 | 2019-02-15 | 北京奇艺世纪科技有限公司 | A kind of data processing method, device, medium and electronic equipment |
| CN109726081A (en) * | 2019-01-02 | 2019-05-07 | 深圳壹账通智能科技有限公司 | Method, apparatus, computer equipment and the storage medium of service exception processing |
| CN110166297A (en) * | 2019-05-22 | 2019-08-23 | 平安信托有限责任公司 | O&M method, system, equipment and computer readable storage medium |
| CN110149343A (en) * | 2019-05-31 | 2019-08-20 | 国家计算机网络与信息安全管理中心 | A kind of abnormal communications and liaison behavioral value method and system based on stream |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112181696A (en) | 2021-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112181696B (en) | Abnormality information processing method, apparatus, and storage medium | |
| US8655336B1 (en) | Remote issue logging and reporting of mobile station issues and diagnostic information to manufacturer | |
| US20180364975A1 (en) | Voice user interface for data access control | |
| CN109857404B (en) | SDK interface packaging method and device, storage medium and electronic equipment | |
| CN110932918B (en) | Log data acquisition method and device and storage medium | |
| CN108121633B (en) | Abnormity capturing method and device | |
| CN110650503B (en) | Network access method, device, system and computer readable storage medium | |
| CN104346560A (en) | Security authentication method and security authentication device | |
| CN106339273A (en) | Application program restoration method, terminal and server | |
| CN112187616A (en) | Message sending method, device and storage medium | |
| CN104639498A (en) | Fingerprint matching method, device and system | |
| CN111263377B (en) | Network configuration method, device, equipment and system and distribution network testing method and system | |
| CN108322917B (en) | Wireless network access fault positioning method, device, system and storage medium | |
| CN114356434B (en) | Page loading method, device, apparatus, storage medium and program product | |
| CN111628927A (en) | Mail management method and device, storage medium and electronic terminal | |
| WO2018231656A1 (en) | Voice user interface for device and component control | |
| CN115102775A (en) | Charging pile risk detection method, device and system | |
| CN109982315B (en) | Log uploading method and related equipment | |
| CN114465867A (en) | Server maintenance method and device, storage medium and processor | |
| CN112286796A (en) | Software testing method, device and storage medium | |
| CN111190761B (en) | Log output method and device, storage medium and electronic equipment | |
| CN110336712B (en) | Method and device for capturing empty packet by mobile terminal, storage medium and mobile terminal | |
| CN109388917B (en) | Hardware equipment authentication method, device, equipment and storage medium | |
| CN114553608A (en) | Method and device for accessing cloud platform | |
| CN113934552A (en) | Method and device for determining function code, storage medium and electronic 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 |