WO2021179578A1

WO2021179578A1 - Business logic debugging method and apparatus, device, and computer-readable storage medium

Info

Publication number: WO2021179578A1
Application number: PCT/CN2020/118490
Authority: WO
Inventors: 张玉辰
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-03-12
Filing date: 2020-09-28
Publication date: 2021-09-16
Also published as: CN111506497B; CN111506497A

Abstract

Disclosed are a business logic debugging method and apparatus, a device, and a computer-readable storage medium. The method comprises: when a debugging request comprising a request header is detected, reading a target log level, a target encryption key, and a first encryption value corresponding to the debugging request; encrypting the target log level according to the target encryption key to generate a second encryption value; when the first encryption value matches the second encryption value, acquiring, according to the target log level, debugging data generated on the basis of a business logic corresponding to the debugging request, so as to debug the business logic on the basis of the debugging data.

Description

Business logic debugging method, device, equipment and computer readable storage medium

This application claims the priority of the Chinese patent application filed on March 12, 2020, with the application number 202010174165.6, titled "Business logic debugging method, device, equipment and computer-readable storage medium". The full text is hereby incorporated as refer to.

Technical field

This application mainly relates to the field of server technology, and specifically, to a method, device, device, and computer-readable storage medium for debugging business logic.

Background technique

With the development of network technology, more and more online service accesses are provided through business logic in the server. When a user accesses an online service, the access may be abnormal due to various reasons. At this time, the developer usually needs to troubleshoot the problem based on the log data generated by the business logic that provides the access.

At present, in order to fully reflect the functions of business logic, a mechanism is set up to generate log data for all aspects of business logic. Once an online service access exception occurs, the log data generated by the corresponding business logic is obtained for analysis. However, the inventor found that the analyzed log data is likely to contain data that is not related to abnormalities, which increases the amount of data analyzed, affects the efficiency of analysis, and brings data processing pressure to the normal access to the server; in addition, other non-relevant data Developers can also obtain or attack log data by constructing requests, which leads to the leakage of log data and brings risks to online services.

Technical solutions

The main purpose of this application is to provide a business logic debugging method, device, equipment, and computer readable storage medium, aiming to solve the low efficiency of log data analysis of business logic in the prior art, which affects server data processing and online services Security issues.

In order to achieve the above objective, this application provides a business logic debugging method, which includes the following steps:

When a debugging request is detected, the target log level, target encryption key, and first encryption value corresponding to the debugging request are read. The debugging request includes the target log level, target encryption key, and first encryption value. A request header corresponding to the encrypted value;

Encrypting the target log level according to the target encryption key to generate a second encrypted value;

When the first encrypted value matches the second encrypted value, the debugging data generated based on the business logic corresponding to the debugging request is collected according to the target log level, so as to compare the business based on the debugging data. Logic for debugging.

In addition, in order to achieve the above objective, this application also proposes a business logic debugging device, the business logic debugging device includes:

The reading module is used to read the target log level, target encryption key, and first encrypted value corresponding to the debugging request when a debugging request is detected, and the debugging request includes the target log level, The request header corresponding to the target encryption key and the first encryption value;

A generating module, configured to encrypt the target log level according to the target encryption key to generate a second encrypted value;

The debugging module is configured to collect debugging data generated based on the business logic corresponding to the debugging request according to the log level when the first encrypted value matches the second encrypted value, so as to be based on the debugging data Debug the business logic.

In addition, in order to achieve the above object, this application also proposes a business logic debugging device, the business logic debugging device includes: a memory, a processor, a communication bus, and a business logic debugging program stored on the memory;

The communication bus is used to realize the connection and communication between the processor and the memory;

The processor is used to execute the business logic debugging program to implement the following steps:

In addition, in order to achieve the above-mentioned object, the present application also provides a computer-readable storage medium that stores one or more programs, and the one or more programs can be used by one or more processors. Execute for:

In the business logic debugging method of this embodiment, when a debugging request including a request header corresponding to the target log level request, the target encryption key and the first encrypted data is detected, the target log level and target corresponding to the debugging request are read. The encryption key and the first encrypted value; and the target log level is encrypted by the target encryption key to generate the second encrypted value; if it is determined that the first encrypted value matches the second encrypted value, the collection is based on the target log level The debugging data generated by the business logic corresponding to the debugging request can be used to debug the business logic based on the debugging data. On the one hand, this application uses the consistency between the first encrypted value and the second encrypted value to promptly detect malicious acquisition or attack of log data by non-developers, avoid the leakage of log data, and facilitate the security of online services; On the other hand, by setting the target log level to collect debugging data, it avoids obtaining irrelevant data for analysis and affecting the server's data processing ability, which improves the accuracy and efficiency of analysis.

Description of the drawings

FIG. 1 is a schematic flowchart of the first embodiment of the business logic debugging method of the present application;

2 is a schematic diagram of functional modules of the first embodiment of the business logic debugging device of the present application;

FIG. 3 is a schematic diagram of the device structure of the hardware operating environment involved in the method of the embodiment of the present application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Embodiments of the present invention

It should be understood that the specific embodiments described here are only used to explain the present application, and are not used to limit the present application.

This application provides a business logic debugging method.

Please refer to FIG. 1, which is a schematic flowchart of a first embodiment of a business logic debugging method of this application. In this embodiment, the business logic debugging method includes:

Step S10: When a debugging request is detected, read the target log level, target encryption key, and first encryption value corresponding to the debugging request, and the debugging request includes the target log level and target encryption secret. The request header corresponding to the key and the first encrypted value;

The business logic debugging method of this application is applied to a server, and is suitable for the targeted collection of data generated by the business logic of the online service abnormality through the server, so as to facilitate analysis and debugging based on the collected data to find the cause of the abnormality. Considering that this embodiment debugs the abnormalities that occur in the process of providing online service access by the server, in order to avoid the impact of debugging on the normal user access, the server is provided with an external interface for external access in addition to an external interface dedicated for debugging. The internal interface; the request for triggering debugging and the data used for debugging are transmitted through the internal interface, while the normal access of the user is carried out through the external interface; the request initiated by the user is transmitted to the business logic for processing through the external interface, and the processing result Return to the user terminal through an external interface; this enables the distinction between debugging and normal access.

Further, in order to realize debugging by developers, a sending end that can communicate with the server is provided. The sending end can be a mobile terminal such as a mobile phone or a tablet computer, or a smart bracelet, a smart watch, etc. The wearable device can also be a fixed terminal such as a desktop computer. When the online service access is abnormal and the business logic needs to be debugged, the developer constructs a debug request through the sender and sends it to the server to request the data corresponding to the abnormality for debugging.

Understandably, the sending of the debugging request is based on the establishment of a communication connection between the server and the sending end. Therefore, before sending the debugging request to the server, a communication connection between the two needs to be established and the security of the communication must be ensured. Specifically, before step S10, it includes:

Step a1, receiving the communication connection request sent by the sending end corresponding to the debugging request, and performing identity verification on the sending end;

The developer sends a communication connection request to the server through the sender. After receiving the communication connection request, the server authenticates the sender in order to ensure the security of the communication. The identity verification can be carried out through the unique identifier of the sender, such as the MAC address of the sender (Media Access Control Address) or IMEI (International Mobile Equipment Identity, International Mobile Equipment Identity), etc. Before sending the communication connection request, the sender reads its own identifier of this type and adds it to the communication connection request before sending it; after receiving the communication connection request, the server reads the identifier in it. Or the sender only initiates a communication connection request. After receiving the communication connection request, the server returns a verification request for obtaining its identifier for identity verification to the sender, and the sender sends the identifier to the server according to the verification request. The server stores the identifier of the sender used for debugging in advance, and after obtaining the identifier of the sender, compares it with the pre-stored identifiers to determine whether the obtained identifier exists in the stored identifier; if If it exists, it is judged that the identity verification is successful, otherwise it is judged that the identity verification has failed, and the communication connection with the sender is refused.

Step a2: After the identity verification is successful, establish a communication connection with the sender for the sender to construct a request header, and send the debugging request based on the request header, wherein the request header is based on the request header. The target log level, the target encryption key, and the time point information of the request header construction are generated.

Further, after the server successfully authenticates the sender, a communication connection with the sender is established to realize data transmission between the sender and the server. In addition, in order to ensure that the data collected from the server is correlated with the access exception, the developer constructs the request header through the sender, so that the debugging request is sent to the server based on the request header to realize the communication between the two. The request header is used to inform the server about the information requested by the sender, such as the data type supported by the sender, which character set is supported, which compression format is supported, the language environment, which host is accessed, etc. When constructing the request header in this embodiment, the developer sets the target log level that needs to be collected and the target encryption key used to achieve encryption, and the sender sets the target log level, target encryption key, and the current time of the constructed request header. The point information is added to the request header to form a special header of the request header. If the constructed request header is X-Debug-Req: token, then the token is the special generated by the target log level, encryption key and time point information head.

It should be noted that in this embodiment, according to the severity of the abnormality reflected by the log data, the log data is divided into multiple target log levels, including at least five levels: FATAL, ERROR, WARN, INFO, and DEBUG; The actual situation of the exception sets the target log level of the log data that it needs to pull. If the actual condition of the abnormality is WARN level, the target log level can be set to WARN to pull log data with the target log level above WARN level, and avoid pulling log data that is not related to the abnormality. Processing efficiency. In addition, in order to avoid the malicious pull of log data by non-developers, resulting in the leakage of log data and affecting the security of online services, an encryption mechanism is set; the developer sets the target encryption key when constructing the request header to pass The target encryption key realizes the encryption processing of the target log level.

Furthermore, an encryption algorithm is preset in the sender. The encryption algorithm can be symmetric encryption such as DES, RC2, RC4, RC5 and Blowfish, or asymmetric encryption such as RSA, Rabin, DH, and ECC. Encryption can also be MD5 encryption, etc. After receiving the request header constructed by the developer, the sender encrypts the target log level through the encryption algorithm according to the target encryption key in the request header, and generates the first encrypted value; and the first encrypted value is combined with the target log level , The target encryption key and time point information are sent to the internal interface of the server as the information corresponding to the debugging request. When the internal interface of the server detects the debugging request, it reads the corresponding target log level, target encryption key, time point information, and first encrypted value to pass the time point information and the first encrypted value verification After that, the log data corresponding to the target log level is collected and returned to the sender.

Step S20: encrypt the target log level according to the target encryption key to generate a second encrypted value;

Further, the internal interface of the server is set with the same encryption algorithm as the sender. After reading the time point information, target log level, and target encryption key, the time point information is used to determine the current detection time and the time of the debugging request. Whether there is a large difference in the time to construct the request header, if it is large, it means that the time period between the construction time and the receiving time is longer, and there may be a risk of malicious attacks. Therefore, refuse to collect log data and return it to the sender. On the contrary, if there is not much difference between the two, it means that the time period between the construction time and the reception time is within a reasonable range and is a normal request. Then the target log level is encrypted by the target encryption key and the preset encryption algorithm. Obtain the second encrypted value. Based on the consistency between the first encrypted value and the second encrypted value, it is judged whether the data is subject to tampering attacks during transmission to the internal interface of the server.

Step S30: When the first encrypted value matches the second encrypted value, according to the target log level, collect debugging data generated based on the business logic corresponding to the debugging request, so as to pair the debugging data based on the debugging data. The business logic is debugged.

Furthermore, the generated second encrypted value is compared with the read first encrypted value to determine the consistency between the two; if the two are consistent, it is determined that the two match, the sender and the internal interface used The encryption algorithm is a preset algorithm. The target encryption key, target log level, and first encrypted value have not been tampered with during transmission; otherwise, it is determined that the first encrypted value and the second encrypted value do not match, and the data is being transmitted to the internal interface of the server After malicious tampering in the process, the debugging request is risky, and the log data is refused to be collected and returned to the sender. For debugging requests that match the first encrypted value and the second encrypted value without risk, the server collects the target log data corresponding to the target log level from the log data generated by the business logic triggered by the debugging request; at the same time obtains the business logic The response data and target log data are returned to the sending end as debugging data, so that developers can debug business logic based on the returned debugging data.

It should be noted that in order to avoid confusion between the collected target log data and the log data generated by external access, the server is provided with a buffer area dedicated to storing log data for debugging; this buffer area is used as a buffer area corresponding to the debugging request. And set up a regular cleaning mechanism. The server sends the collected target log data to the cache area, and detects the storage duration of each target log data previously stored in the cache area. When there is a target log data in each target log data, the storage duration is greater than the preset substantial When the duration threshold is set, a prompt message is output, prompting to clean up the target log data to free up storage space and facilitate subsequent storage of the target log data.

Further, based on the first embodiment of the business logic debugging method of the present application, a second real-time example of the business logic debugging method of the present application is proposed. In the second embodiment, the collection based on the target log level and the debugging The step of requesting the debugging data generated by the corresponding business logic to debug the business logic based on the debugging data includes:

Step S31: Adjust the default level of log data generated by the business logic corresponding to the debugging request according to the target log level, and collect the target corresponding to the adjusted default level from the log data generated by the business logic Log data;

Understandably, the log data generated by the business logic triggered by the debugging request is diverse to reflect abnormalities with different degrees of risk. Generally, log data corresponding to abnormalities that are small in risk and do not affect the use are not processed. The log data corresponding to the abnormality is processed only when the degree of danger of the abnormality is large and affects the use. In this embodiment, the log level of the log data that needs to be processed is set as the default level of the log data generated by the business logic. After the server reads the target log level, it compares it with the default level of the log data generated by the business logic. Compare and judge the consistency of the two. If they are consistent, it means that the log level of the log data returned by default meets the target log level required by the developer. From the log data generated by the business logic for the current debugging request, the target log data above the default level is directly obtained and returned to the sending end. . If the default level and the target log level are inconsistent, the default level is adjusted according to the target log level, and the default level is adjusted to the target log level, so as to collect and adjust the default log data from the log data generated by the business logic for the current debugging request. The target log data corresponding to the level is returned to the sender. For example, the default level of log data returned for each request is ERROR level, and the target log level required by the current debugging request characterization is DEBUG, the server adjusts the level returned by the log data to DEBUG to target the current debugging request Obtain the generated target log data above the DEBUG level.

Step S32, reading the response data generated by the business logic, and setting the target log data and the response data as debugging data;

Further, the business logic responds to the debugging request to generate response data. After obtaining the target log data generated by the business logic for the current debugging request that meets the target log level requirements, the response data is read, and the response data Set the debugging data together with the target log data to combine the two debugging to determine the cause of the service exception.

Step S33: Send the debugging data to the sending end corresponding to the debugging request, so as to debug the service logic based on the debugging data.

Furthermore, after the server generates the debugging data, it sends it to the sending end that initiates the debugging request, so that the developer who initiates the debugging request through the sending end can debug the business logic that caused the service exception based on the debugging data. Among them, in order to facilitate developers to distinguish between the response data in the debugging data and the target log data, a mechanism is provided to add the data size of the response data in the response header; specifically, the debugging data is sent to the sender corresponding to the debugging request. The steps include:

Step S331: Detect the data size of the response data, and add the data size to the response header of the business logic;

Furthermore, the data size of the response data generated by the business logic processing the debugging request is detected, and the detected data size is added to the response header of the business logic. Among them, the response header is used to notify the sender of information about the server, such as the model of the server, the compression format of the data, the length of the returned data, the language environment, and the type of the returned data to the sender.

Step S332: Send the debugging data according to the response header to distinguish target log data and response data in the debugging data based on the size of the data in the response header.

Further, the server returns the debugging data to the sending end that initiated the debugging request based on the generated response header, so that the developer can determine the response data and target log data in the debugging data according to the data size in the response header. For example, the response header: X-Ori-Content-Length: 100, which means that the data size of the response data is 100 bytes. The developer will intercept the first 100 bytes or the last 100 bytes from the returned debugging data according to the data size in the response header. One byte is used as the response data, and the rest is the target log data, and then the response data and target log data are combined to investigate the cause of the service exception.

In this embodiment, the target log data and response data generated by the business logic for the current debugging request are collected through the set target log level, and the two are distinguished by the data size of the response data, so as to realize the basis of the target log data and the response data. To debug. Because the collected target log data is the abnormally-related log data required by the developer, the collection of irrelevant log data is avoided, the amount of data processing is reduced, and the processing efficiency is improved; at the same time, the target log data is combined with the data size. The distinction of response data is conducive to the rapid distinction between the two and further improves the efficiency of data processing.

Further, based on the first or second embodiment of the business logic debugging method of the present application, a third real-time example of the business logic debugging method of the present application is proposed. In the third embodiment, when a debugging request is detected, read The steps of the target log level, the target encryption key and the first encryption value corresponding to the debugging request include:

Step S11, when a debugging request is detected, record the detection time point, and read the generation time point of the debugging request;

In this embodiment, before verifying the verification of the first encrypted value, the internal interface of the server also involves verification between the time when the developer constructs the request header and the time when the server detects the debugging request, that is, pass Secondary verification to ensure the security of the transmitted data. Specifically, when a debugging request is detected by the internal interface of the server, the time when the debugging request is detected is recorded as the detection time point, and the generation time point of the debugging request is read; wherein, the generation time point may be The time point information when constructing the request header can also be the time when the sender sends the debugging request.

Step S12, judging whether the time difference between the detection time point and the generation time point is within a preset time range;

Further, a preset time range representing the magnitude of the time difference is preset, and the detection time point and the generation time point are compared to obtain the time difference between the two. The obtained time difference is compared with the preset time range to determine whether the time difference is within the preset time range.

Step S13, if the time difference is within the preset time range, execute the step of reading the target log level, the target encryption key, and the first encryption value carried in the debugging request.

If the time difference is within the preset time range, it means that the time when the request header is constructed or the time when the sender sends the debugging request is not far from the time when the debugging request is detected, and the debugging request is reasonable. If the time difference is not within the preset time range, it means that the time when the request header is constructed or the time when the sender sends the debugging request is far from the time when the debugging request is detected. The debugging request may be risky but not risky. Debugging request for continued processing. For a reasonable debugging request, continue to read the target log level, target encryption key, and first encryption value corresponding to the debugging request to generate the second encryption value through the target log level and target encryption key, and pass the first encryption The consistency between the value and the second encrypted value is used to verify the security of the transmitted data.

Furthermore, the first encrypted value and the second encrypted value in this embodiment are related to time. Specifically, encrypting the target log level according to the target encryption key, and the step of generating the second encrypted value includes:

An encryption rule is determined according to the target encryption key, the encryption rule is invoked, and the target log level and the detection time point are encrypted based on the target encryption key to generate a second encrypted value.

In this embodiment, an encryption rule is used to characterize the encryption algorithm, and the corresponding relationship between the encryption key and the encryption rule is preset. The target encryption key set by the developer must exist in the corresponding relationship, otherwise the set target encryption key Invalid, in order to further prevent tampering by non-developers and ensure the security of encryption. In the process of generating the second encrypted value, the corresponding relationship between the encryption key and the encryption rule is called, and the corresponding encryption rule in the corresponding relationship is determined according to the read target encryption key, and then the corresponding encryption is called The rule encrypts the target log level and the detection time point with the target encryption key to generate a second encrypted value. It should be noted that the second encrypted value of this embodiment is related to time. Correspondingly, the first encrypted value is also related to time. The encryption rule corresponding to the target encryption key in the sender is called, and The set target log level and the time point information for constructing the request header are encrypted by the target encryption key to generate the first encrypted value. At this time, because the time corresponding to the generation of the first encrypted value and the second encrypted value is not exactly the same, the first encrypted value and the second encrypted value are not exactly the same; a certain threshold can be set, when the first encrypted value and the If the difference between the second encrypted values is within the threshold range, it is determined that the two match; if the difference between the two exceeds the threshold range, it is determined that the two do not match.

In this embodiment, the initial verification is performed through time first, and then the re-verification is performed through the first encrypted value and the second encrypted value, so that the security is better. At the same time, the factor of time is added to generate the first encrypted value and the second encrypted value, so that the first encrypted value and the second encrypted value generated each time have dynamic characteristics, which further ensures the security of data transmission.

In addition, please refer to FIG. 2. This application provides a business logic debugging device. In the first embodiment of the business logic debugging device of this application, the business logic debugging device includes:

The reading module 10 is used to read the target log level, the target encryption key and the first encrypted value corresponding to the debugging request when a debugging request is detected, and the debugging request includes information related to the target log level , The target encryption key and the request header corresponding to the first encryption value;

The generating module 20 is configured to encrypt the target log level according to the target encryption key to generate a second encrypted value;

The debugging module 30 is configured to collect debugging data generated based on the business logic corresponding to the debugging request according to the target log level when the first encrypted value matches the second encrypted value, so as to be based on the The debugging data debugs the business logic.

When a debugging request including a request header corresponding to the target log level request, the target encryption key, and the first encrypted data is detected, the reading module 10 reads the target log level, the target encryption key, and the first encrypted data corresponding to the debugging request. An encrypted value; and the generation module 20 encrypts the target log level with the target encryption key to generate a second encrypted value; if it is determined that the first encrypted value and the second encrypted value match, the debugging module 30 will, according to the target log level, Collect debugging data generated based on the business logic corresponding to the debugging request, so as to realize the debugging of the business logic based on the debugging data. On the one hand, this application uses the consistency between the first encrypted value and the second encrypted value to promptly detect malicious acquisition or attack of log data by non-developers, avoid the leakage of log data, and facilitate the security of online services; On the other hand, by setting the target log level to collect debugging data, it avoids obtaining irrelevant data for analysis and affecting the server's data processing ability, which improves the accuracy and efficiency of analysis.

Further, in another embodiment of the business logic debugging device of the present application, the debugging module further includes:

The collection unit is configured to adjust the default level of log data generated by the business logic corresponding to the debugging request according to the target log level, and collect the log data generated by the business logic corresponding to the adjusted default level Target log data;

A reading unit, configured to read the response data generated by the business logic, and set the target log data and the response data as debugging data;

The sending unit is configured to send the debugging data to the sending end corresponding to the debugging request, so as to debug the service logic based on the debugging data.

Further, in another embodiment of the service logic debugging apparatus of the present application, the sending unit is further configured to:

Detecting the data size of the response data, and adding the data size to the response header of the business logic;

The debugging data is sent according to the response header to distinguish target log data and response data in the debugging data based on the size of the data in the response header.

Further, in another embodiment of the business logic debugging device of the present application, the collection unit is further configured to:

The target log data is sent to a buffer area corresponding to the debugging request for buffering.

Further, in another embodiment of the business logic debugging apparatus of the present application, the reading module further includes:

The recording unit is used to record the detection time point when a debugging request is detected, and read the generation time point of the debugging request;

A judging unit, configured to judge whether the time difference between the detection time point and the generation time point is within a preset time range;

The execution unit is configured to execute the step of reading the target log level, the target encryption key, and the first encryption value carried in the debugging request if the time difference is within the preset time range.

Further, in another embodiment of the business logic debugging apparatus of the present application, the generating module further includes:

Further, in another embodiment of the business logic debugging device of the present application, the business logic debugging device further includes:

The receiving module is configured to receive the communication connection request sent by the sending end corresponding to the debugging request, and to perform identity verification on the sending end;

The establishment module is configured to establish a communication connection with the sending end after the identity verification is successful, so that the sending end can construct a request header and send the debugging request based on the request header, wherein the request header Generated based on the target log level, the target encryption key, and the time point information constructed by the request header.

Wherein, each virtual function module of the above-mentioned service logic debugging device is stored in the memory 1005 of the service logic debugging device shown in FIG. 3. When the processor 1001 executes the service logic debugging program, the function of each module in the embodiment shown in FIG. 2 is realized.

Referring to FIG. 3, FIG. 3 is a schematic diagram of the device structure of the hardware operating environment involved in the method of the embodiment of the present application.

The business logic debugging device of the embodiment of the present application may be a PC (personal computer, personal computer), or a terminal device such as a smart phone, a tablet computer, an e-book reader, and a portable computer.

As shown in FIG. 3, the service logic debugging device may include: a processor 1001, such as a CPU (Central Processing Unit, central processing unit), a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to implement connection and communication between the processor 1001 and the memory 1005. The memory 1005 may be a high-speed RAM (random Access memory, random access memory), can also be a stable memory (non-volatile memory), such as disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

Optionally, the service logic debugging equipment may also include user interfaces, network interfaces, cameras, RF (Radio Frequency, radio frequency) circuits, sensors, audio circuits, WiFi (Wireless Fidelity, wireless broadband) module and so on. The user interface may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface may also include a standard wired interface and a wireless interface. The optional network interface can include standard wired interface and wireless interface (such as WI-FI interface).

Those skilled in the art can understand that the structure of the business logic debugging device shown in FIG. 3 does not constitute a limitation on the business logic debugging device, and may include more or fewer components than shown in the figure, or a combination of certain components, or different components. The layout of the components.

As shown in FIG. 3, the memory 1005, which is a computer-readable storage medium, may include an operating system, a network communication module, and a business logic debugging program. The operating system is a program that manages and controls the hardware and software resources of the business logic debugging equipment, and supports the operation of the business logic debugging program and other software and/or programs. The network communication module is used to implement communication between various components in the memory 1005, and to communicate with other hardware and software in the business logic debugging device.

In the business logic debugging device shown in FIG. 3, the processor 1001 is used to execute the business logic debugging program stored in the memory 1005 to implement the steps in each embodiment of the foregoing business logic debugging method.

This application provides a computer-readable storage medium. The computer-readable storage medium may be non-volatile or volatile. The computer-readable storage medium stores one or more programs. Alternatively, one or more programs may also be executed by one or more processors to implement the steps in each embodiment of the foregoing service logic debugging method.

It should also be noted that in this article, the terms "including", "including" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements , And also include other elements not explicitly listed, or elements inherent to the process, method, article, or device. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or device that includes the element.

The serial numbers of the foregoing embodiments of the present application are for description only, and do not represent the superiority or inferiority of the embodiments.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product is stored in a computer-readable storage medium as described above (such as The ROM/RAM, magnetic disk, optical disk) includes several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the present application.

The above are only the preferred embodiments of this application, and do not limit the scope of this application. Under the concept of this application, equivalent structural transformations made using the content of the specification and drawings of this application, or directly/indirectly used in Other related technical fields are included in the scope of patent protection of this application.

Claims

A business logic debugging method, the business logic debugging method includes the following steps:

When a debugging request is detected, the target log level, target encryption key, and first encryption value corresponding to the debugging request are read. The debugging request includes the target log level, target encryption key, and first encryption value. A request header corresponding to the encrypted value;

Encrypting the target log level according to the target encryption key to generate a second encrypted value;

When the first encrypted value matches the second encrypted value, the debugging data generated based on the business logic corresponding to the debugging request is collected according to the target log level, so as to compare the business based on the debugging data. Logic for debugging.
The business logic debugging method of claim 1, wherein the debugging data generated based on the business logic corresponding to the debugging request is collected according to the target log level, so as to compare the business logic based on the debugging data. The steps for debugging include:

According to the target log level, adjust the default level of log data generated by the business logic corresponding to the debugging request, and collect target log data corresponding to the adjusted default level from the log data generated by the business logic;

Reading the response data generated by the business logic, and setting the target log data and the response data as debugging data;

The debugging data is sent to the sending end corresponding to the debugging request, so as to debug the business logic based on the debugging data.
3. The service logic debugging method according to claim 2, wherein the step of sending the debugging data to the sending end corresponding to the debugging request comprises:

Detecting the data size of the response data, and adding the data size to the response header of the business logic;

The debugging data is sent according to the response header to distinguish target log data and response data in the debugging data based on the size of the data in the response header.
3. The business logic debugging method according to claim 2, wherein after the step of collecting target log data corresponding to the adjusted default level comprises:

The target log data is sent to a buffer area corresponding to the debugging request for buffering.
5. The business logic debugging method of claim 1, wherein when a debugging request is detected, the step of reading the target log level, the target encryption key, and the first encryption value corresponding to the debugging request comprises:

When a debugging request is detected, record the detection time point, and read the generation time point of the debugging request;

Determine whether the time difference between the detection time point and the generation time point is within a preset time range;

If the time difference is within the preset time range, the step of reading the target log level, the target encryption key, and the first encryption value corresponding to the debugging request is performed.
5. The business logic debugging method of claim 5, wherein the step of encrypting the target log level according to the target encryption key, and generating a second encrypted value comprises:

An encryption rule is determined according to the target encryption key, the encryption rule is invoked, and the target log level and the detection time point are encrypted based on the target encryption key to generate a second encrypted value.
The business logic debugging method according to any one of claims 1 to 6, wherein when the debugging request is detected, the target log level, the target encryption key and the first encryption corresponding to the debugging request are read Before the numerical steps include:

Receiving the communication connection request sent by the sending end corresponding to the debugging request, and performing identity verification on the sending end;

After the identity verification is successful, a communication connection with the sender is established for the sender to construct a request header and send the debugging request based on the request header, wherein the request header is based on the target log The level, the target encryption key, and the time point information of the request header construction are generated.
A business logic debugging device, the business logic debugging device includes:

The reading module is used to read the target log level, target encryption key, and first encrypted value corresponding to the debugging request when a debugging request is detected, and the debugging request includes the target log level, The request header corresponding to the target encryption key and the first encryption value;

A generating module, configured to encrypt the target log level according to the target encryption key to generate a second encrypted value;

The debugging module is configured to collect debugging data generated based on the business logic corresponding to the debugging request according to the log level when the first encrypted value matches the second encrypted value, so as to be based on the debugging data Debug the business logic.
A business logic debugging device, wherein the business logic debugging device includes: a memory, a processor, a communication bus, and a business logic debugging program stored on the memory;

The communication bus is used to realize the connection and communication between the processor and the memory;

The processor is used to execute the business logic debugging program to implement the steps of the business logic debugging method:

When a debugging request is detected, the target log level, target encryption key, and first encryption value corresponding to the debugging request are read. The debugging request includes the target log level, target encryption key, and first encryption value. A request header corresponding to the encrypted value;

Encrypting the target log level according to the target encryption key to generate a second encrypted value;

When the first encrypted value matches the second encrypted value, the debugging data generated based on the business logic corresponding to the debugging request is collected according to the target log level, so as to compare the business based on the debugging data. Logic for debugging.
The business logic debugging device according to claim 9, wherein the processor executed by the processor collects debugging data generated based on the business logic corresponding to the debugging request according to the target log level, so as to be based on the debugging The steps of data debugging the business logic include:

According to the target log level, adjust the default level of log data generated by the business logic corresponding to the debugging request, and collect target log data corresponding to the adjusted default level from the log data generated by the business logic;

Reading the response data generated by the business logic, and setting the target log data and the response data as debugging data;

The debugging data is sent to the sending end corresponding to the debugging request, so as to debug the business logic based on the debugging data.
The service logic debugging device according to claim 10, wherein the step of sending the debugging data to the sending end corresponding to the debugging request performed by the processor comprises:

Detecting the data size of the response data, and adding the data size to the response header of the business logic;

The debugging data is sent according to the response header to distinguish target log data and response data in the debugging data based on the size of the data in the response header.
The business logic debugging device according to claim 10, wherein the step of collecting target log data corresponding to the adjusted default level afterwards comprises:

The target log data is sent to a buffer area corresponding to the debugging request for buffering.
The business logic debugging device according to claim 9, wherein when a debugging request is detected by the processor, it reads the target log level, the target encryption key, and the first log level corresponding to the debugging request. The steps to encrypt the value include:

When a debugging request is detected, record the detection time point, and read the generation time point of the debugging request;

Determine whether the time difference between the detection time point and the generation time point is within a preset time range;

If the time difference is within the preset time range, the step of reading the target log level, the target encryption key, and the first encryption value corresponding to the debugging request is performed.
The business logic debugging device according to claim 13, wherein the step of encrypting the target log level according to the target encryption key performed by the processor, and generating a second encrypted value comprises:

An encryption rule is determined according to the target encryption key, the encryption rule is invoked, and the target log level and the detection time point are encrypted based on the target encryption key to generate a second encrypted value.
A computer-readable storage medium, wherein a business logic debugging program is stored on the computer-readable storage medium, and the steps of the business logic debugging method are implemented when the business logic debugging program is executed by a processor:

When a debugging request is detected, the target log level, target encryption key, and first encryption value corresponding to the debugging request are read. The debugging request includes the target log level, target encryption key, and first encryption value. A request header corresponding to the encrypted value;

Encrypting the target log level according to the target encryption key to generate a second encrypted value;

When the first encrypted value matches the second encrypted value, the debugging data generated based on the business logic corresponding to the debugging request is collected according to the target log level, so as to compare the business based on the debugging data. Logic for debugging.
The computer-readable storage medium according to claim 15, wherein the business logic debugging program is implemented when the business logic debugging program is executed by the processor according to the target log level, and the business logic generated based on the business logic corresponding to the debugging request is collected The steps of debugging data to debug the business logic based on the debugging data include:

According to the target log level, adjust the default level of log data generated by the business logic corresponding to the debugging request, and collect target log data corresponding to the adjusted default level from the log data generated by the business logic;

Reading the response data generated by the business logic, and setting the target log data and the response data as debugging data;

The debugging data is sent to the sending end corresponding to the debugging request, so as to debug the business logic based on the debugging data.
16. The computer-readable storage medium according to claim 16, wherein the step of sending the debugging data to the sending end corresponding to the debugging request implemented when the business logic debugging program is executed by the processor comprises:

Detecting the data size of the response data, and adding the data size to the response header of the business logic;

The debugging data is sent according to the response header to distinguish target log data and response data in the debugging data based on the size of the data in the response header.
15. The computer-readable storage medium of claim 16, wherein the step of collecting target log data corresponding to the adjusted default level implemented when the business logic debugging program is executed by the processor comprises:

The target log data is sent to a buffer area corresponding to the debugging request for buffering.
The computer-readable storage medium according to claim 15, wherein when the debugging request is detected, the target log level corresponding to the debugging request is read when the debugging request is detected when the business logic debugging program is executed by the processor. , The steps of the target encryption key and the first encryption value include:

When a debugging request is detected, record the detection time point, and read the generation time point of the debugging request;

Determine whether the time difference between the detection time point and the generation time point is within a preset time range;

If the time difference is within the preset time range, the step of reading the target log level, the target encryption key, and the first encryption value corresponding to the debugging request is performed.
The computer-readable storage medium according to claim 19, wherein the execution of the business logic debugging program is implemented by the processor to encrypt the target log level according to the target encryption key to generate a second encryption The numerical steps include:

An encryption rule is determined according to the target encryption key, the encryption rule is invoked, and the target log level and the detection time point are encrypted based on the target encryption key to generate a second encrypted value.