CN113835921A - Method, device, equipment and storage medium for processing interface service exception - Google Patents
Method, device, equipment and storage medium for processing interface service exception Download PDFInfo
- Publication number
- CN113835921A CN113835921A CN202111155389.3A CN202111155389A CN113835921A CN 113835921 A CN113835921 A CN 113835921A CN 202111155389 A CN202111155389 A CN 202111155389A CN 113835921 A CN113835921 A CN 113835921A
- Authority
- CN
- China
- Prior art keywords
- interface
- abnormal
- data
- emergency
- calling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
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/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a method, a device, equipment and a storage medium for processing interface service abnormity, wherein the method comprises the following steps: monitoring a first interface calling event to collect first abnormal data corresponding to an abnormal service interface, wherein the first interface calling event is an event generated when a client requests target data from a server end by calling the service interface, reading a configuration file, and if first interface information of an emergency interface configured for the abnormal service interface is acquired, requesting corresponding same target data from the server end by calling the emergency interface according to the first interface information; and reporting the first abnormal data to a server side. The method and the device realize emergency treatment of the client side on the interface abnormity. The fault tolerance rate of the access server is improved, and the compatibility and the support under an abnormal scene are improved, so that the customer experience is improved, and the customer retention is increased.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing an interface service exception.
Background
For various types of software, particularly for large projects, the number of users is very large, and a large number of users are in use in each time period, if an interface provided by a server side is abnormal and there is no emergency temporary measure, a large number of clients cannot use software or APPs directly, and service loss and client loss are caused.
In order to ensure that a client can normally operate software to obtain a service or access a page when an abnormal condition occurs, a monitoring notification of the abnormal condition needs to be quickly received so as to summon a corresponding developer to quickly locate and repair the problem. However, from the problem discovery to the problem solution, a large amount of development labor investment is usually required to configure and collect the problem, the method is uncertain, the problem of the interface can not be timely and effectively discovered and solved every time, and the rush repair time cannot be guaranteed.
Disclosure of Invention
The method aims to solve the technical problems that in the prior art, when an interface is abnormally called, the positioning and the problem solving are not timely and the efficiency is low. The application provides a method, a device, equipment and a storage medium for processing interface service abnormity, and mainly aims to realize monitoring and emergency processing of the interface abnormity by a client, and accelerate the efficiency of abnormity positioning and debugging by reporting abnormal data.
In order to achieve the above object, the present application provides a method for processing an interface service exception, where the method includes:
monitoring a first interface calling event to collect first abnormal data corresponding to an abnormal service interface, wherein the first interface calling event is an event occurring when a client requests target data from a server end by calling the service interface, and the first abnormal data comprises: at least one of an error reporting webpage address, a version number of a client, a type of a terminal device where the client is located, system information of a system used by the terminal device, a unique identifier of an abnormal service interface, abnormal prompt information and a timestamp of occurrence of an abnormality;
reading a configuration file, and if first interface information of an emergency interface configured for an abnormal service interface is acquired, calling the emergency interface to request corresponding same target data from a server side according to the first interface information;
and reporting the first abnormal data to a server side.
In addition, to achieve the above object, the present application further provides an apparatus for processing an interface service exception, including:
the first monitoring module is configured to monitor a first interface call event to collect first abnormal data corresponding to an abnormal service interface, where the first interface call event is an event occurring when a client requests a server for target data by calling the service interface, and the first abnormal data includes: at least one of an error reporting webpage address, a version number of a client, a type of a terminal device where the client is located, system information of a system used by the terminal device, a unique identifier of an abnormal service interface, abnormal prompt information and a timestamp of occurrence of an abnormality;
the emergency interface calling module is used for reading the configuration file, and if first interface information of an emergency interface configured for the abnormal service interface is acquired, the emergency interface is called to request corresponding same target data from the server side according to the first interface information;
and the first reporting module is used for reporting the first abnormal data to the server side.
To achieve the above object, the present application further provides a computer device, which includes a memory, a processor and computer readable instructions stored on the memory and executable on the processor, wherein the processor executes the computer readable instructions to perform the steps of the method for handling an interface service exception as described in any one of the preceding claims.
To achieve the above object, the present application further provides a computer readable storage medium having computer readable instructions stored thereon, which, when executed by a processor, cause the processor to execute the steps of the method for handling an interface service exception as any one of the above.
According to the method, the device, the equipment and the storage medium for processing the interface service abnormity, the client can monitor and emergently process the interface abnormity only by simply configuring some parameters and then packaging and constructing. By reporting the abnormal data, the efficiency of abnormal positioning and debugging is accelerated. Through the switching of the emergency interface, the response delay caused by the abnormity of the service interface is reduced, and the interruption of data in the client is also reduced. The high fault tolerance of the client side for accessing the server side is guaranteed to a certain extent in the production environment, the compatibility and support under an abnormal scene are improved to a great extent, the customer experience is improved, and the customer retention is increased.
Drawings
Fig. 1 is an application scenario diagram of a processing method for an interface service exception in an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for handling an interface service exception according to an embodiment of the present application;
FIG. 3 is a block diagram illustrating an exemplary embodiment of a device for handling an interface service exception;
fig. 4 is a block diagram of an internal structure of a computer device according to an embodiment of the present application.
The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The method for processing the interface service exception provided by the application can be applied to a processing system of the interface service exception shown in fig. 1. The system for processing the interface service exception comprises the terminal device 110 and the server 120. Terminal device 110 and server 120 are connected via a network. The terminal device 110 may specifically be a desktop terminal or a mobile terminal, and the mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a notebook computer, a portable wearable device, and the like. The server 120 may be implemented as a stand-alone server or a server cluster composed of a plurality of servers.
The terminal device 110 monitors a first interface call event to collect first abnormal data corresponding to an abnormal service interface, where the first interface call event is an event occurring when a client requests target data from the server 120 by calling the service interface, and the first abnormal data includes: at least one of an error reporting webpage address, a version number of the client, a model of the terminal device 110 where the client is located, system information of a system used by the terminal device 110, a unique identifier of an abnormal service interface, abnormal prompt information and a timestamp of occurrence of an abnormality; the terminal device 110 reads the configuration file, and if first interface information of an emergency interface configured for the abnormal service interface is acquired, the emergency interface is called to request the server 120 for corresponding same target data according to the first interface information; the terminal device 110 reports the first abnormal data to the server 120. Wherein the client is installed in the terminal device 110.
Fig. 2 is a flowchart illustrating a processing method for an interface service exception according to an embodiment of the present application. Referring to fig. 2, the method is described as applied to the client installed in the terminal device in fig. 1. The method for processing the interface service exception comprises the following steps S100-S300.
S100: monitoring a first interface calling event to collect first abnormal data corresponding to an abnormal service interface, wherein the first interface calling event is an event occurring when a client requests target data from a server end by calling the service interface, and the first abnormal data comprises: at least one of an error reporting webpage address, a version number of the client, a model of the terminal device where the client is located, system information of a system used by the terminal device, a unique identifier of an abnormal service interface, abnormal prompt information and a timestamp of occurrence of an abnormality.
Specifically, the present embodiment is specifically applied to a client installed in a terminal device. Before the client of the APP is on-line, a developer embeds the code of an interface service exception handling tool (a plug-in) into the code of the client. The codes are installed and stored in the local of the terminal equipment used by the user along with the client side of the APP when the client side of the APP downloads and installs the codes, so that the client side of the APP has the function of automatically realizing the interface service exception handling.
The specific steps of introducing the interface service exception handling tool into the client comprise: in the development process before the client of the APP is on line, a command line is operated in a development computer where the client is located, a project root directory is located, and a command is executed: npmpas-oot-error-tools-D, add the tool or plug-in to the framework project. Positioning a project root directory, executing a command construction command: npm run pa-oot-error-tools. And after the execution is finished, the client carries an interface service exception handling tool.
An interface service exception handling tool is run under the root directory of the project. The purpose of the positioning is to enable the tool to execute under the root directory of the item, i.e. to do processing around the code under the directory.
Monitoring a first interface calling event corresponding to a first interface request sent by a client to a server through a service interface; if the interface return data corresponding to the first interface request is not received within a certain time length or the abnormal prompt information returned by the server is received, the service interface is marked as an abnormal service interface, and the first abnormal data corresponding to the abnormal service interface is collected. For example, the request may be for more than 1 minute without receiving interface return data or an error code (e.g., type 500 code or 404, etc.).
The first interface request is an interface calling request sent by a client to request target data from a server. The first interface calling event comprises the steps that the client sends an interface request to the server, receives data returned by the server and the like.
An APP may have multiple versions, different versions can be compatible with different terminal devices, different compatible computer systems are different, and based on compatibility of a client, interface calling in different operating environments may have different calling effects. Therefore, the version of the client, the model of the terminal device where the client is located, and the operating system are all factors that affect the normal invocation of the interface.
The purpose of the client-side requesting the target data from the server-side is to access the webpage of the server, and if the target data is not requested, the webpage of the server cannot be accessed, so that the error-reported webpage address corresponding to the interface calling failure can be obtained.
The exception prompt information includes an error reporting code, which is a response code returned by the server based on the interface call request of the client, for example, the error reporting codes 502 and 404.
S200: and reading the configuration file, and if first interface information of an emergency interface configured for the abnormal service interface is acquired, calling the emergency interface to request corresponding same target data from the server side according to the first interface information.
Specifically, the configuration file is a configuration file of the interface service exception handling tool, which configures a mapping relationship between a service interface and a corresponding emergency interface, and one service interface may be configured with one or more emergency interfaces or may not be configured with an emergency interface. The emergency interfaces corresponding to different service interfaces can be shared. The purpose of calling the emergency interface is the same as that of calling the corresponding service interface, and the purpose is to request the same target data. The service interface is an interface which is preferentially used by the client side for accessing the server side, and the emergency interface is a standby interface used under the condition that the corresponding service interface is abnormal in calling. And preferentially calling the service interface, and if the service interface fails to be called, trying to call the corresponding emergency interface to request the same target data.
If one abnormal service interface corresponds to a plurality of emergency interfaces, the emergency interfaces are called by calling the priority, and one emergency interface is failed to call the next emergency interface until one emergency interface is successfully called.
Of course, the switching between the abnormal service interface and the emergency interface can be started after the abnormal service interface is tried to be called repeatedly for the preset time and the calling fails.
S300: and reporting the first abnormal data to a server side.
Specifically, the first abnormal data may be reported to the server end immediately after being collected, or all the collected first abnormal data may be reported to the server end after accumulating for a period of time. The first abnormal data can be reported through a special abnormal reporting interface or an emergency interface. The first abnormal data are reported to the server side, and the server side also supports the operation of the interface monitoring system, so that the interface monitoring side can acquire the first abnormal data from the server side in real time and display the first abnormal data on computer equipment provided with the interface monitoring system, and operation and maintenance personnel can conveniently and quickly locate problems.
According to the embodiment, the client can perform emergency treatment on the interface abnormity only by simply configuring some parameters in the configuration file and then packaging and constructing the parameters. There is no need for a developer to separately write code for a project. The temporary emergency treatment function can be realized for small companies and small-sized projects, and a large amount of human resources are not required to be invested to develop and test the function. The project of the client side keeps high fault tolerance in a production environment, the compatibility and support of the project under an abnormal scene are greatly improved, especially for the access of a front-end page, the interruption of a webpage is reduced, the customer experience is improved, and the customer retention is increased.
In one embodiment, the method further comprises:
monitoring a second interface calling event to collect second abnormal data corresponding to the abnormal emergency interface, wherein the second interface calling event is an event generated when the client calls the emergency interface;
and reporting the second abnormal data to a server side.
Specifically, if the abnormal service interface is configured with the emergency interface, a second interface call event corresponding to the call of the emergency interface is monitored while the emergency interface is called, so as to collect second abnormal data of the abnormal emergency interface. The second anomaly data includes: at least one of an error reporting webpage address, a version number of the client, a model of the terminal device where the client is located, system information of a system used by the terminal device, a unique identifier of an abnormal emergency interface, abnormal prompt information and a timestamp of occurrence of an abnormality.
The second abnormal data can be reported to the server end immediately after being collected, and can also be reported to the server end in a unified way after accumulating for a period of time. For example, second abnormal data corresponding to the abnormal service interface is collected and cached to the local, the corresponding abnormal reporting interface is called every fourth preset time, and the cached and unreported second abnormal data is reported to the server side. The second abnormal data can be reported through a special abnormal reporting interface or through the next emergency interface to be called of the abnormal service interface. The second abnormal data are reported to the server side, and the server side also supports the operation of the interface monitoring system, so that the interface monitoring side can acquire the second abnormal data from the server side in real time and display the second abnormal data on computer equipment provided with the interface monitoring system, and operation and maintenance personnel can conveniently and quickly locate problems.
In addition, the reporting of the first abnormal data and the second abnormal data has no mutual exclusivity and absolute sequence, and the first abnormal data and the second abnormal data can be reported after meeting the reporting condition.
In one embodiment, the step S200 of requesting the same corresponding target data from the server by calling the emergency interface according to the first interface information includes:
if the emergency interfaces configured by the abnormal service interface comprise at least two emergency interfaces, selecting an emergency interface without a history calling record or an emergency interface with the minimum response time length from the emergency interfaces as a target emergency interface, wherein the emergency interface with the minimum response time length is acquired according to the history calling record,
the target emergency interface is called to request the corresponding same target data from the server side,
after listening for the second interface call event, the method further comprises:
acquiring the response time length corresponding to the target emergency interface,
and performing associated storage by taking the first interface information of the target emergency interface and the corresponding response time as the historical calling record of the target emergency interface.
In particular, since the emergency interface of the same service interface may be multiple, and may exist in the server side of different geographic locations. For the client, if the IP requested by the interface is far from the IP region provided by the server, delay of interface response may be brought, resulting in slow response time and affecting the client experience. Therefore, selecting an appropriate panic interface from a plurality of panic interfaces is also key to optimizing interface invocation.
If a service interface has a plurality of emergency interfaces to select, a target emergency interface is selected to use according to certain rules. Specifically, if the emergency interfaces configured for the abnormal service interface include at least two emergency interfaces, and the response time lengths of the emergency interfaces with the historical call records in the emergency interfaces are all greater than the response threshold value, the emergency interface without the historical call records in the emergency interfaces is selected as the target emergency interface, and if all the emergency interfaces in the emergency interfaces have the historical call records, that is, the emergency interfaces which are not called do not exist, the emergency interface with the historical call records and the minimum response time length is selected as the target emergency interface. And if the emergency interface comprises the emergency interface with the history calling record and the response time length less than or equal to the response threshold, selecting the emergency interface with the response time length less than or equal to the response threshold and the minimum response time length from the emergency interfaces as the target emergency interface. That is, select the non-invoked panic interface or select the invoked panic interface with the smallest response duration.
And calling the target emergency interface to send an emergency interface request to the server side. After the emergency interface request is called, a second interface calling event corresponding to the emergency interface request is monitored, so that the sending time of the emergency interface request is recorded, interface return data returned after the server end responds to the emergency interface request is received, the receiving time of the interface return data is recorded, and the response time corresponding to the target emergency interface is obtained according to the sending time and the receiving time.
And storing or updating the response time length of the called emergency interface, and taking the response time length as a basis for selecting the emergency interface when the emergency interface is called next time.
In one embodiment, step S300 specifically includes the following steps:
calling the emergency interface to request the server end for the corresponding same target data, reporting the first abnormal data to the server end through the emergency interface,
or the like, or, alternatively,
reading the configuration file to obtain the second interface information of the abnormal reporting interface,
and calling the corresponding abnormal reporting interface to report the first abnormal data to the server side according to the second interface information.
And if the abnormal service interface is configured with an emergency interface, the emergency interface is called to automatically initiate an interface request again to request target data from the server, and simultaneously, the first abnormal data is carried in the interface request and reported to the server side, or the same emergency interface is used for respectively requesting the target data and uploading the abnormal data, so that interface resources can be saved, and the pressure of the server can be reduced.
In addition, whether the abnormal service interface has an emergency interface or not, the abnormal data can be reported to the server side through the abnormal reporting interface. The abnormal reporting interface is configured in the configuration file in advance. The exception reporting interface may be configured as a shared interface.
In one embodiment, the method further comprises:
if the abnormal service interface is not configured with the emergency interface, calling the abnormal service interface to try to request the target data from the server again;
step S300 specifically includes the following steps:
if the abnormal service interface is not configured with the emergency interface, counting the normal calling times and the abnormal calling times of all the called times of the abnormal service interface in a first preset time, acquiring the calling parameters called by the abnormal service interface each time and interface return data returned by the server side,
classifying the abnormal service interface into one of a temporary service abnormal interface, a long-term service abnormal interface, an entry parameter abnormal interface and a response overtime interface according to the normal calling frequency, the abnormal calling frequency, the entry parameter called each time and interface return data returned by the server end,
reading the configuration file to obtain the second interface information of the abnormal reporting interface,
and calling an abnormal reporting interface to report the first abnormal data and the classification association of the abnormal service interface to the server side according to the second interface information.
Specifically, if the abnormal service interface is not configured with the emergency interface, the abnormal service interface is tried to be called again to request the same target data from the server side.
Whether the service interface is called for the first time or is called again after abnormal calling, the first interface calling event of the service interface is monitored. In addition, the service interface may be invoked multiple times without the panic interface.
The client side can extract the called input parameters and the interface return data according to the corresponding interface calling data called by the interface each time, and count the normal calling times and the abnormal calling times of the service interface. If the called parameters of the abnormal service interface are the same in each time within the first preset time, and calling abnormality and calling normality exist in all the times of calling, the abnormal service interface is judged to be a temporary service abnormal interface. For example, within a first preset time, if the same entry parameter is the same when the same interface calls the abnormal service interface again after the error is reported for the first time, and if the error is not reported after multiple times of error reporting, the abnormal service interface is defined as a temporary service abnormal interface. The abnormality is generally caused by instability of the server, and if the abnormality does not occur frequently, the operation and maintenance personnel can not do the abnormality.
If the abnormal service interface is abnormal when being called every time within the first preset time length and the called access parameters are not all the same, the abnormal service interface is judged to be a long-term service abnormal interface. For example, if the same interface is in an error reporting state regardless of the change of the input parameter, or if the error reporting code 404 is received, the abnormal service interface is defined as a long-term service abnormal interface. The abnormality is generally caused by the downtime of the server, and needs to be handled by operation and maintenance personnel in an emergency, such as restarting the server, maintaining hardware, and the like.
If the called entry parameters of the abnormal service interface in the first preset time length are not completely the same, and the calling is abnormal and normal in all the called entries, the abnormal service interface is judged to be the entry parameter abnormal interface. For example, if the same interface is within the first preset time period and the entry parameter changes, sometimes the return interface does not report an error, and sometimes the return interface reports an error, the service interface is defined as an entry parameter abnormal interface. The exception may be caused by an inappropriate call entering and calling mode used by a calling party or call under the condition that an interface server is incompatible with various scenes, and the exception needs to be checked by a developer and repaired as appropriate.
And if the abnormal service interface cannot receive interface return data returned by the server end every time the abnormal service interface is called within the first preset time, judging that the abnormal service interface is a response overtime interface. For example, in multiple calls, if the service interface does not receive data returned by the server within a specified time after the request is sent, the service interface is defined as a response timeout interface. The exception may be caused by slow data processing at the server or excessively long processing time caused by continuous calling of a plurality of underlying systems. It may also be that the client network is slow, but the amount of data returned is huge. Operation and maintenance personnel and troubleshooting are required to find problems.
If the interface calling data is not preprocessed to realize the classification of the abnormal service interfaces, the first abnormal data is directly reported, a large amount of manpower is needed for data analysis at the interface monitoring end corresponding to the server end to obtain an error rule, a large amount of time is wasted, and the repair time is greatly increased. In addition, if the analysis is performed at the server, when an error occurs, the server needs to bear huge computation consumption, which may affect the resource utilization of the normal service. Therefore, the embodiment classifies the abnormal service interfaces by analyzing at the client, thereby not only reducing the operation overhead of the server, but also providing preliminary abnormal judgment and analysis for the operation and maintenance personnel by classification, and facilitating the quick positioning of the operation and maintenance personnel and solving the problem of abnormal interfaces.
In addition, the step S100 of collecting the first abnormal data corresponding to the abnormal service interface includes: and collecting first abnormal data corresponding to the abnormal service interface and caching the first abnormal data to the local.
In order to avoid frequent error reporting, the interface is frequently requested to upload data. The configuration file is provided with an interval time for automatically reporting the exception, namely a second preset time length, so that the throttling of the uploading frequency is realized. Step S300 specifically includes: and reporting the cached and unreported first abnormal data to the server end every second preset time interval.
The abnormal service interface without the emergency interface can be called for many times, and in the process of calling for many times, the first abnormal data corresponding to each calling can be cached locally. If the same error occurs repeatedly, the repeated recording of the first abnormal data wastes memory. Therefore, the local client performs deduplication processing on the same first abnormal data corresponding to the same abnormal service interface, and increases the number of times of repeated occurrence of the abnormality in the corresponding first abnormal data. And reporting the first abnormal data which is not reported and is cached locally to the server end through the abnormal reporting interface every second preset time interval, so that intelligent throttling reporting of the abnormal data is realized. For example, if the second preset time duration is set to be 5 seconds, the first abnormal data is cached within 5 seconds, and after 5 seconds, all the first abnormal data is reported once. The first exception data reported each time may include first exception data of multiple exception service interfaces. And the abnormal data reported each time may also include second abnormal data of the emergency interface.
Of course, if the abnormal service interface is configured with the emergency interface, the first abnormal data of the abnormal service interface is sent to the server together with the emergency interface calling request when the emergency interface is called, and the server does not need to wait for the second preset time.
Because the classification of the abnormal service interfaces needs to comprehensively judge interface call data called for multiple times, the first abnormal data reported each time may include part of the first abnormal data of the multiple abnormal service interfaces and does not necessarily carry the classification of the abnormal service interfaces. And marking the first abnormal data which are not reported according to the classification of the abnormal service interface after the classification of the abnormal service interface is determined, so that the first abnormal data carrying the classification of the abnormal service interface are associated and reported to the server side.
In a specific embodiment, if the abnormal service interface is tried to be called repeatedly for a preset time and fails to be called, then switching between the abnormal service interface and the emergency interface is started, classifying the abnormal service interface configured with the emergency interface according to the method, and reporting the first abnormal data and the classification association to the server side.
In one embodiment, the method further comprises:
reading the configuration file to determine a cache interface in the service interface, a corresponding cache field and cache retention time;
intercepting and calling interface return data of a normal cache interface, and extracting corresponding cache fields and field values from the intercepted interface return data;
caching the cache field and the corresponding field value as cache data of a cache interface to the local, and setting a cache validity period for the cache data according to the corresponding cache retention time;
and returning the intercepted interface return data to the corresponding caller, wherein the caller is the caller which triggers the calling of the cache interface in the client.
Specifically, in order to deal with the following situations, the interface return data needs to be cached, and is used for temporary emergency use or performance optimization, and the pressure on the server side is relieved:
when the server side cannot provide an emergency interface, the client side can temporarily use the locally cached historical request data to ensure that part of the interactive functions are normally used;
when the client network is suddenly abnormal, such as entering a no-signal area, the client can temporarily use the locally cached historical request data to ensure that part of the interactive functions are normally used;
and when the data returned by the same interface is almost unchanged, the service interface is called again to acquire the data from the server side once every third preset time, and the local cache is updated according to the acquired data. The locally cached data is preferentially used when the interface is not called.
Js determines a service interface set as a cache interface among the service interfaces through the configuration file config. The monitored service interfaces are more than one, the cache interfaces belong to the service interfaces, a part of the service interfaces are set as cache interfaces in the configuration file, and the interface return data of the cache interfaces hardly change. The cache retention time period, that is, the third preset time period, is specifically set according to the actual situation, and for example, may be set to 10 minutes or 5 minutes, and the like, but is not limited thereto.
When monitoring the interface calling event of the service interface, monitoring an interface request sent by the client to the server, and if the interface calling is normal, monitoring interface return data returned by the server. Therefore, if the service interface belongs to the cache interface, the interception processing of interface return data is carried out on the cache interface, the correctness of the interface return data is verified, after the correctness is verified, part of data in the interface return data is cached in the local of the terminal equipment, and then the interface return data is returned to the calling party. Therefore, the data can be directly called from the local next time without repeatedly calling the interface, the response is faster, the frequent calling of the interface is reduced, and the response pressure of the server side is relieved. Since the interface return data may include more fields of data, some fields of data are frequently changed, and some fields of data are not substantially changed, the embodiment caches the data of the fields that are not frequently changed. In addition, due to the fact that the valid period is set, if the expiration time is up, the interface is called again to obtain the latest data from the server side and cache the latest data to the local side, and synchronization of the data of the local side and the server side is guaranteed.
In one embodiment, the method further comprises:
reading the configuration file to obtain a use scene of cache data corresponding to the cache interface;
if the use scene is calling abnormity, calling corresponding cache data from local if the cache interface is calling abnormity;
if the use scene is not limited to calling exception, the corresponding cache data is preferentially called from the local before the cache interface is called.
In particular, the configuration file sets when the cached data is used. And if the use scene of the cache data is used when the call exception occurs, using the local cache data under the condition that the call cache interface is abnormal.
If the cache interface is configured with an emergency interface, when the cache interface is abnormally called, the local cache data can be called first, and if the cache data cannot be called locally, the emergency interface is called again. And if the emergency interface is normally called, updating the local cache data of the cache interface according to the interface return data of the emergency interface.
If the cache interface is configured with an emergency interface, the emergency interface can be called first when the cache interface is abnormally called, and then the local cache data is called if the emergency interface is abnormally called.
If the use scene is not limited to calling abnormity, the cache data is preferably called from the local before the cache interface is called, if the cache data cannot be called locally, the cache interface is called again, and if the cache interface is called abnormally, the emergency interface is called again.
A service interface can be configured as a cache interface and can also be configured as an emergency interface, and when the service interface calls, uses local cache data and calls the emergency interface, priority setting can be carried out according to actual conditions.
According to the embodiment, interface calling to the server side is further reduced through caching data, and the response pressure of the server side is reduced. Meanwhile, the cache data plays a certain role in dealing with temporary emergencies.
According to the method and the device, the abnormal data can be automatically collected to switch the emergency interface, and part of target data can be automatically cached to the local part, so that the normal access of the client to the server is guaranteed to a certain extent under the emergency temporary emergency condition, the access delay caused by the abnormal calling of the service interface is reduced, and the user experience is improved.
In addition, the collected abnormal data is rich and contains the information of interface abnormality, so that developers can quickly locate problems and quickly process generated abnormality, the abnormal data is used as the basis for analyzing the generated abnormal event data to analyze common abnormal scenes, the problems generated in the follow-up process are avoided, and valuable data resources are provided.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
FIG. 3 is a block diagram illustrating an exemplary embodiment of a device for handling an interface service exception; referring to fig. 3, the apparatus includes:
the first monitoring module 100 is configured to monitor a first interface call event to collect first abnormal data corresponding to an abnormal service interface, where the first interface call event is an event occurring when a client requests a server for target data by calling the service interface, and the first abnormal data includes: at least one of an error reporting webpage address, a version number of a client, a type of a terminal device where the client is located, system information of a system used by the terminal device, a unique identifier of an abnormal service interface, abnormal prompt information and a timestamp of occurrence of an abnormality;
the emergency interface calling module 200 is configured to read the configuration file, and if first interface information of an emergency interface configured for the abnormal service interface is acquired, according to the first interface information, call the emergency interface to request the server for corresponding same target data;
the first reporting module 300 is configured to report the first abnormal data to the server.
In one embodiment, the apparatus further comprises:
the second monitoring module is used for monitoring a second interface calling event to collect second abnormal data corresponding to the abnormal emergency interface, wherein the second interface calling event is an event generated when the client calls the emergency interface;
and the second reporting module is used for reporting the second abnormal data to the server side.
The first reporting module and the second reporting module may be the same reporting module or different reporting modules.
In one embodiment, the emergency interface calling module 200 specifically includes:
the emergency interface selection unit is used for selecting an emergency interface without a historical calling record or an emergency interface with the minimum response time length as a target emergency interface if the emergency interfaces configured by the abnormal service interface comprise at least two emergency interfaces, wherein the emergency interface with the minimum response time length is acquired according to the historical calling record,
and the emergency interface calling unit is used for calling the target emergency interface to request the corresponding same target data from the server side.
The device also includes:
a response time length obtaining module for obtaining the response time length corresponding to the target emergency interface,
and the calling record storage module is used for performing associated storage by taking the first interface information of the target emergency interface and the corresponding response time as the historical calling record of the target emergency interface.
In one embodiment, the first reporting module 300 specifically includes:
a first sub-reporting unit, which is used for calling the emergency interface to request the same corresponding target data from the server and reporting the first abnormal data to the server through the emergency interface,
and/or the presence of a gas in the gas,
the first reporting module 300 specifically includes:
a reporting interface information obtaining unit for reading the configuration file to obtain the second interface information of the abnormal reporting interface,
and the second sub-reporting unit is used for calling the corresponding abnormal reporting interface according to the second interface information to report the first abnormal data to the server side.
In one embodiment, the apparatus further comprises:
the repeated calling module is used for calling the abnormal service interface to try to request the target data from the server again if the emergency interface is not configured on the abnormal service interface;
the first reporting module 300 specifically includes:
the data analysis unit is used for counting the normal calling times and the abnormal calling times of the abnormal service interface in all the called times within a first preset time length if the emergency interface is not configured on the abnormal service interface, acquiring the calling parameters called by the abnormal service interface each time and interface return data returned by the server end,
a classification unit for classifying the abnormal service interface into one of a temporary service abnormal interface, a long-term service abnormal interface, a parameter abnormal interface and a response overtime interface according to the normal calling frequency, the abnormal calling frequency, the called parameter and the interface return data returned by the server end,
a reporting interface information obtaining unit for reading the configuration file to obtain the second interface information of the abnormal reporting interface,
and the third sub-reporting unit is used for calling the abnormal reporting interface to report the first abnormal data and the classification association of the abnormal service interface to the server side according to the second interface information.
In one embodiment, the apparatus further comprises:
the first cache information acquisition module is used for reading the configuration file to determine a cache interface in the service interface, a corresponding cache field and cache retention time;
the intercepting module is used for intercepting interface return data of the normal cache interface and extracting corresponding cache fields and field values from the intercepted interface return data;
the cache module is used for caching the cache field and the corresponding field value to the local as cache data of the cache interface, and setting a cache validity period for the cache data according to the corresponding cache retention time;
and the data transmission module is used for returning the intercepted interface return data to the corresponding caller, and the caller is the caller which triggers the calling of the cache interface in the client.
In one embodiment, the apparatus further comprises:
the second cache information acquisition module is used for reading the configuration file to acquire a use scene of cache data corresponding to the cache interface;
the first cache calling module is used for calling corresponding cache data from local if the calling of the cache interface is abnormal if the use scene is calling abnormity;
and the second cache calling module is used for calling the corresponding cache data from the local preferentially before calling the cache interface if the use scene is not limited to calling exception.
Wherein the meaning of "first" and "second" in the above modules/units is only to distinguish different modules/units, and is not used to define which module/unit has higher priority or other defining meaning. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not explicitly listed or inherent to such process, method, article, or apparatus, and such that a division of modules presented in this application is merely a logical division and may be implemented in a practical application in a further manner.
For the specific definition of the processing device for the interface service exception, reference may be made to the above definition of the processing method for the interface service exception, and details are not described here again. The modules in the processing device for the interface service exception can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
Fig. 4 is a block diagram of an internal structure of a computer device according to an embodiment of the present application. The computer device may specifically be the terminal device in fig. 1. As shown in fig. 4, the computer apparatus includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory includes a storage medium and an internal memory. The storage medium may be a nonvolatile storage medium or a volatile storage medium. The storage medium stores an operating system and may also store computer readable instructions which, when executed by the processor, may cause the processor to implement a method of handling interface service exceptions. The internal memory provides an environment for the operating system and execution of computer readable instructions in the storage medium. The internal memory may also have computer readable instructions stored therein, which when executed by the processor, may cause the processor to perform a method for handling interface service exceptions. The network interface of the computer device is used for communicating with an external server through a network connection. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
In one embodiment, a computer device is provided, which includes a memory, a processor, and computer readable instructions (e.g., a computer program) stored on the memory and executable on the processor, and when the processor executes the computer readable instructions, the steps of the method for processing an interface service exception in the above embodiments are implemented, for example, steps S100 to S300 shown in fig. 2 and other extensions of the method and related steps. Alternatively, the processor executes the computer readable instructions to implement the functions of the modules/units of the interface service exception handling apparatus in the above embodiments, such as the functions of the modules 100 to 300 shown in fig. 3. To avoid repetition, further description is omitted here.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable gate array (FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, the processor being the control center of the computer device and the various interfaces and lines connecting the various parts of the overall computer device.
The memory may be used to store computer readable instructions and/or modules, and the processor may implement various functions of the computer apparatus by executing or executing the computer readable instructions and/or modules stored in the memory and invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, video data, etc.) created according to the use of the cellular phone, etc.
The memory may be integrated in the processor or may be provided separately from the processor.
Those skilled in the art will appreciate that the architecture shown in fig. 4 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer readable storage medium is provided, on which computer readable instructions are stored, and when executed by a processor, the computer readable instructions implement the steps of the method for processing an interface service exception in the above embodiments, such as the steps S100 to S300 shown in fig. 2 and the extensions of other extensions and related steps of the method. Alternatively, the computer readable instructions, when executed by the processor, implement the functions of each module/unit of the processing apparatus for interface service exception in the above embodiments, such as the functions of the modules 100 to 300 shown in fig. 3. To avoid repetition, further description is omitted here.
It will be understood by those of ordinary skill in the art that all or part of the processes of the methods of the embodiments described above may be implemented by instructing associated hardware to implement computer readable instructions, which may be stored in a computer readable storage medium, and when executed, may include processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method 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, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments. Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present application may be substantially or partially embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.
Claims (10)
1. A method for handling an interface service exception, the method comprising:
monitoring a first interface call event to collect first abnormal data corresponding to an abnormal service interface, wherein the first interface call event is an event occurring when a client requests target data from a server by calling the service interface, and the first abnormal data comprises: at least one of an error reporting webpage address, a version number of the client, a machine type of a terminal device where the client is located, system information of a system used by the terminal device, a unique identifier of the abnormal service interface, abnormal prompt information and an abnormal timestamp;
reading a configuration file, and if first interface information of an emergency interface configured for the abnormal service interface is acquired, calling the emergency interface to request corresponding same target data from the server side according to the first interface information;
and reporting the first abnormal data to the server side.
2. The method of claim 1, further comprising:
monitoring a second interface calling event to collect second abnormal data corresponding to an abnormal emergency interface, wherein the second interface calling event is an event generated when the client calls the emergency interface;
and reporting the second abnormal data to the server side.
3. The method according to claim 2, wherein the requesting the server side for the corresponding same target data by calling the emergency interface according to the first interface information includes:
if the emergency interfaces configured by the abnormal service interface comprise at least two emergency interfaces, selecting an emergency interface without a historical call record or an emergency interface with the minimum response time length from the emergency interfaces as a target emergency interface, wherein the emergency interface with the minimum response time length is acquired according to the historical call record,
calling the target emergency interface to request corresponding same target data from the server;
after the listening for the second interface call event, the method further comprises:
acquiring the response time length corresponding to the target emergency interface,
and performing associated storage by taking the first interface information of the target emergency interface and the corresponding response time as a historical calling record of the target emergency interface.
4. The method according to claim 1, wherein the reporting the first abnormal data to the server side includes:
calling the emergency interface to request the same corresponding target data from the server side and reporting the first abnormal data to the server side through the emergency interface;
or the like, or, alternatively,
reading the configuration file to obtain the second interface information of the abnormal reporting interface,
and calling a corresponding abnormal reporting interface to report the first abnormal data to the server side according to the second interface information.
5. The method of claim 1 or 4, further comprising:
if the abnormal service interface is not configured with an emergency interface, calling the abnormal service interface to try to request the target data from the server again;
the reporting the first abnormal data to the server side includes:
if the abnormal service interface is not configured with an emergency interface, counting the normal calling times and the abnormal calling times of all the called times of the abnormal service interface in a first preset time, acquiring the calling parameters called by the abnormal service interface each time and interface return data returned by the server side,
classifying the abnormal service interface according to the normal calling times, the abnormal calling times, the called entry parameter each time and interface return data returned by the server, wherein the classification is one of a temporary service abnormal interface, a long-term service abnormal interface, an entry parameter abnormal interface and a response timeout interface,
reading the configuration file to obtain the second interface information of the abnormal reporting interface,
and calling the abnormal reporting interface to report the first abnormal data and the classification association of the abnormal service interface to the server side according to the second interface information.
6. The method of claim 1, further comprising:
reading the configuration file to determine a cache interface in the service interface, a corresponding cache field and cache retention time;
intercepting interface return data calling a normal cache interface, and extracting corresponding cache fields and field values from the intercepted interface return data;
caching the cache field and the corresponding field value to the local as cache data of the cache interface, and setting a cache validity period for the cache data according to the corresponding cache retention time;
and returning the intercepted interface return data to a corresponding caller, wherein the caller is the caller which triggers the calling of the cache interface in the client.
7. The method of claim 6, further comprising:
reading the configuration file to obtain a use scene of cache data corresponding to the cache interface;
if the use scene is abnormal, if the cache interface is abnormal, the corresponding cache data is called locally;
if the use scene is not limited to calling exception, the corresponding cache data is preferentially called from the local before the cache interface is called.
8. An apparatus for handling an interface service exception, the apparatus comprising:
a first monitoring module, configured to monitor a first interface call event to collect first abnormal data corresponding to an abnormal service interface, where the first interface call event is an event occurring when the client requests a server for target data by calling the service interface, and the first abnormal data includes: at least one of an error reporting webpage address, a version number of the client, a machine type of a terminal device where the client is located, system information of a system used by the terminal device, a unique identifier of the abnormal service interface, abnormal prompt information and an abnormal timestamp;
the emergency interface calling module is used for reading a configuration file, and if first interface information of an emergency interface configured for the abnormal service interface is acquired, the emergency interface is called to request corresponding same target data from the server side according to the first interface information;
and the first reporting module is used for reporting the first abnormal data to the server side.
9. A computer device comprising a memory, a processor and computer readable instructions stored on the memory and executable on the processor, wherein the processor when executing the computer readable instructions performs the steps of the method of handling interface service exceptions of any of claims 1-7.
10. A computer readable storage medium having computer readable instructions stored thereon, which when executed by a processor, cause the processor to perform the steps of the method of handling interface service exceptions of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111155389.3A CN113835921A (en) | 2021-09-29 | 2021-09-29 | Method, device, equipment and storage medium for processing interface service exception |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111155389.3A CN113835921A (en) | 2021-09-29 | 2021-09-29 | Method, device, equipment and storage medium for processing interface service exception |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113835921A true CN113835921A (en) | 2021-12-24 |
Family
ID=78967675
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111155389.3A Pending CN113835921A (en) | 2021-09-29 | 2021-09-29 | Method, device, equipment and storage medium for processing interface service exception |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113835921A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114419756A (en) * | 2022-01-30 | 2022-04-29 | 重庆长安汽车股份有限公司 | Method and system for dynamically capturing abnormal scene of whole vehicle |
| CN115292081A (en) * | 2022-08-10 | 2022-11-04 | 朴道征信有限公司 | Information sending method, information sending device, electronic equipment, medium and computer program product |
| CN115499291A (en) * | 2022-09-14 | 2022-12-20 | 平安壹钱包电子商务有限公司 | Method and device for processing service zero-drop alarm information and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107343091A (en) * | 2017-06-27 | 2017-11-10 | 努比亚技术有限公司 | Data reporting method and system |
| CN109766204A (en) * | 2018-12-13 | 2019-05-17 | 平安普惠企业管理有限公司 | Intelligent trouble processing method, device, equipment and readable storage medium storing program for executing |
| CN110445637A (en) * | 2019-07-05 | 2019-11-12 | 深圳壹账通智能科技有限公司 | Event-monitoring method, system, computer equipment and storage medium |
-
2021
- 2021-09-29 CN CN202111155389.3A patent/CN113835921A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107343091A (en) * | 2017-06-27 | 2017-11-10 | 努比亚技术有限公司 | Data reporting method and system |
| CN109766204A (en) * | 2018-12-13 | 2019-05-17 | 平安普惠企业管理有限公司 | Intelligent trouble processing method, device, equipment and readable storage medium storing program for executing |
| CN110445637A (en) * | 2019-07-05 | 2019-11-12 | 深圳壹账通智能科技有限公司 | Event-monitoring method, system, computer equipment and storage medium |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114419756A (en) * | 2022-01-30 | 2022-04-29 | 重庆长安汽车股份有限公司 | Method and system for dynamically capturing abnormal scene of whole vehicle |
| CN114419756B (en) * | 2022-01-30 | 2023-05-16 | 重庆长安汽车股份有限公司 | Method and system for dynamically capturing abnormal scene of whole vehicle |
| CN115292081A (en) * | 2022-08-10 | 2022-11-04 | 朴道征信有限公司 | Information sending method, information sending device, electronic equipment, medium and computer program product |
| CN115292081B (en) * | 2022-08-10 | 2023-10-20 | 朴道征信有限公司 | Information sending method, device, electronic equipment and medium |
| CN115499291A (en) * | 2022-09-14 | 2022-12-20 | 平安壹钱包电子商务有限公司 | Method and device for processing service zero-drop alarm information and storage medium |
| CN115499291B (en) * | 2022-09-14 | 2024-04-02 | 平安壹钱包电子商务有限公司 | Processing method and device for service zero-drop alarm information and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112910945B (en) | Request link tracking method and service request processing method | |
| CN113835921A (en) | Method, device, equipment and storage medium for processing interface service exception | |
| CN111708749B (en) | Operation log recording method and device, computer equipment and storage medium | |
| WO2020147419A1 (en) | Monitoring method and apparatus, computer device and storage medium | |
| CN107451040B (en) | Method and device for positioning fault reason and computer readable storage medium | |
| CN108845910A (en) | Monitoring method, device and the storage medium of extensive micro services system | |
| WO2019051948A1 (en) | Method, apparatus, server, and storage medium for processing monitoring data | |
| CN111930472B (en) | Code debugging method and device, electronic equipment and storage medium | |
| CN107357731A (en) | Process produces monitoring, analysis and the processing method of core dump problems | |
| CN114363144B (en) | Fault information association reporting method and related equipment for distributed system | |
| CN114745295A (en) | Data acquisition method, device, equipment and readable storage medium | |
| CN111147310A (en) | Log tracking processing method, device, server and medium | |
| CN111240976A (en) | Software testing method and device, computer equipment and storage medium | |
| US10915510B2 (en) | Method and apparatus of collecting and reporting database application incompatibilities | |
| CN112564980A (en) | Service monitoring method and system based on micro-service architecture | |
| CN117389830A (en) | Cluster log acquisition method and device, computer equipment and storage medium | |
| CN113190286B (en) | MES system, loading method, terminal and medium for dynamically and remotely loading functional plug-ins | |
| CN115729727A (en) | Fault repairing method, device, equipment and medium | |
| CN111309557B (en) | Monitoring method, device, equipment and medium for multiple operating systems | |
| JP7305641B2 (en) | Methods and systems for tracking application activity data from remote devices and generating corrective behavior data structures for remote devices | |
| CN114090268B (en) | Container management method and container management system | |
| CN115220992A (en) | Interface change monitoring method and device, computer equipment and storage medium | |
| CN114385498A (en) | Performance test method, system, computer equipment and readable storage medium | |
| CN112306723B (en) | Operation information acquisition method and device applied to applet | |
| CN113326052A (en) | Method and device for upgrading service component, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |