WO2019136812A1

WO2019136812A1 - Electronic device, data calling log generation and query method, and storage medium

Info

Publication number: WO2019136812A1
Application number: PCT/CN2018/077629
Authority: WO
Inventors: 王丽
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-01-10
Filing date: 2018-02-28
Publication date: 2019-07-18
Also published as: CN108415925B; CN108415925A

Abstract

Disclosed are an electronic device, a data calling log generation and query method, and a storage medium. The method involves: after a data calling request sent by a service system is received, generating, according to a predetermined calling log identification code generation rule, a log identification code corresponding to a calling log generated when the data calling request is responded to, generating a mapping relationship between the calling log and the log identification code, and storing the mapping relationship in a predetermined database; and after a calling log query instruction carrying a log identification code parameter and sent by a user side is received, determining, according to the pre-stored mapping relationship between the calling log and the log identification code, a log identification code and a calling log corresponding to the log identification code parameter, and returning the determined calling log to the user side. The present invention improves data query efficiency, and reduces an exception handling time.

Description

Electronic device, data call log generation and query method and storage medium

This application claims the priority of the Chinese patent application filed on January 10, 2018, the Chinese Patent Office, the application number is 201810024107.8, and the invention name is "electronic device, data call log generation and query method and storage medium". The citations are incorporated herein by reference.

Technical field

The present application relates to the field of mutual data management, and in particular, to an electronic device, a data call log generation and query method, and a storage medium.

Background technique

The enterprise service management monitoring platform monitors the business call data of all business departments within the company in real time. Once abnormal data is found, it is necessary to query the call log of the abnormal data in time and perform exception processing according to the called call log. At present, the enterprise service governance monitoring platform locates and indexes the database by using the keyword and the storage time of the data to be queried (in minutes) to locate the call log of the abnormal data. This method of calling the log requires a minute of time. When the amount of data to be called is large, the response time of the query page is likely to occur, and even the failure of the query call log may occur, resulting in inefficient processing of the exception processing and wasting a lot of time.

Summary of the invention

In view of this, the present application provides an electronic device, a data generation log generation and query method, and a storage medium, which can improve the efficiency of data query.

First, in order to achieve the above object, a first aspect of the present application provides an electronic device, where the electronic device includes a memory and a processor connected to the memory, and the processor is configured to execute a data call log stored on the memory. Generating and querying a program that implements the following steps when the data call log generation and query program is executed by the processor:

A1. After receiving the request for invoking data sent by the service system, generating, according to the predetermined call log identifier generation rule, a log identifier corresponding to the call log generated when the request call data is generated;

A2. Generate a mapping relationship between the call log and the log identifier, and store the mapping relationship in a predetermined database.

A3. After receiving the call log query command with the log identifier parameter sent by the user end, determining a log corresponding to the log identifier parameter according to the mapping relationship between the pre-stored call log and the log identifier The identification code and the call log are returned, and the determined call log is returned to the client. .

In addition, to achieve the above object, the second aspect of the present application further provides a data call log generation and query method, where the method includes the following steps:

S1. After receiving the request for invoking data sent by the service system, generating a log identifier corresponding to the call log generated when the request is invoked according to the predetermined call log identifier generation rule;

S2. Generate a mapping relationship between the call log and the log identifier, and store the mapping relationship in a predetermined database.

S3. After receiving the call log query command with the log identifier parameter sent by the user end, determining a log corresponding to the log identifier parameter according to the mapping relationship between the pre-stored call log and the log identifier The identification code and the call log are returned, and the determined call log is returned to the client.

Further, in order to achieve the above object, the third aspect of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a data call log generation and query program, and the data call log generation and query program may be Executed by at least one processor to cause the at least one processor to perform the steps of the data call log generation and query method as described above.

Compared with the prior art, the electronic device, the data call log generation and query method and the storage medium proposed by the present application generate rules according to a predetermined call log identification code after receiving a request for calling data sent by the service system. Generating a log identifier corresponding to the call log generated when the data is invoked in response to the request; generating a mapping relationship between the call log and the log identifier, and storing the mapping relationship in a predetermined database. It ensures that the query response time is increased from the minute to the second by matching the log identification code when the query data is called, which improves the efficiency of data query and reduces the time of exception processing.

DRAWINGS

1 is a schematic diagram of an optional hardware architecture of an electronic device proposed by the present application;

2 is a schematic diagram of a program module of a data call log generation and query procedure in an embodiment of an electronic device of the present application;

3 is a flowchart of an implementation of an embodiment of a data call log generation and query method of the present application;

4 is a flow chart showing an implementation of another embodiment of the data call log generation and query method of the present application.

The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.

Detailed ways

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

It should be noted that the descriptions of "first", "second" and the like in the present application are for the purpose of description only, and are not to be construed as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. . Thus, features defining "first" or "second" may include at least one of the features, either explicitly or implicitly. In addition, the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. Nor is it within the scope of protection required by this application.

Referring to FIG. 1 , it is an optional hardware architecture diagram of the electronic device proposed by the present application. In this embodiment, the electronic device 10 may include, but is not limited to, the memory 11, the processor 12, and the network interface 13 being communicably connected to each other through the communication bus 14. It should be noted that FIG. 1 only shows the electronic device 10 having the components 11-14, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.

The memory 11 includes at least one type of computer readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (for example, SD or DX memory, etc.), a random access memory (RAM), and a static memory. Random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, and the like. In some embodiments, the memory 11 may be an internal storage unit of the electronic device 10, such as a hard disk or memory of the electronic device 10. In other embodiments, the memory 11 may also be an outsourced storage device of the electronic device 10, such as a plug-in hard disk equipped on the electronic device 10, a smart memory card (SMC), and a secure digital (Secure Digital, SD) ) cards, flash cards, etc. Of course, the memory 11 can also include both an internal storage unit of the electronic device 10 and an outsourced storage device thereof. In this embodiment, the memory 11 is generally used to store an operating system installed on the electronic device 10 and various types of application software, such as a data call log generation and query program. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.

Processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 12 is typically used to control the overall operation of the electronic device 10. In this embodiment, the processor 12 is configured to run program code or processing data stored in the memory 11, such as a running data call log generation and query program.

Network interface 13 may include a wireless network interface or a wired network interface, which is typically used to establish a communication connection between electronic device 10 and other electronic devices.

Communication bus 14 is used to implement a communication connection between components 11-13.

Figure 1 shows only the electronic device 10 with components 11-14 and data call log generation and query procedures, but it should be understood that not all illustrated components may be implemented, alternative implementations may be more or less Component.

Optionally, the electronic device 10 may further include a user interface (not shown in FIG. 1), and the user interface may include a display, an input unit such as a keyboard, wherein the user interface may further include a standard wired interface, a wireless interface, and the like.

Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED touch device, or the like. Further, the display may also be referred to as a display screen or display unit for displaying information processed in the electronic device 10 and a user interface for displaying visualizations.

In an embodiment, when the data call log generation and query program stored in the memory 11 is executed by the processor 12, the following operations are implemented:

A. After receiving the request for invoking data sent by the service system, generating a log identifier corresponding to the call log generated when the request is invoked according to the predetermined call log identifier generation rule;

B. Generate a mapping relationship between the call log and the log identifier, and store the mapping relationship in a predetermined database.

C. After receiving the call log query instruction with the log identifier parameter sent by the user end, determining a log corresponding to the log identifier parameter according to the mapping relationship between the pre-stored call log and the log identifier The identification code and the call log are returned, and the determined call log is returned to the client. .

In this embodiment, the request for invoking data sent by the service system may be triggered by the related staff by clicking an operation interface provided by the service system, and after receiving the request for calling the data, generating according to the predetermined log identification code. The rule generates a call log identifier corresponding to the request.

In this embodiment, the log identification code includes a system identification code, a first time, and a first request quantity;

The predetermined call log identifier generation rule may be, for example, a first time to obtain a request for receiving the call data, a predetermined system identification code corresponding to the service system; and statistics at the first time The first number of requests received within the call data; generating a log identification code including the first time, the system identification code, and the first number of requests.

In this embodiment, the first current time is in units of seconds.

In other embodiments of the present application, or the log identification code includes a system identification code, a second time, and a second request quantity;

The predetermined call log identifier generation rule may be, for example, a second time to obtain a request for receiving the call data, a predetermined system identification code corresponding to the service system, and the second time in minutes Calculating, in units, a second request quantity of the call data received in the second time of the second time; generating a call including the second time, the preset type coded information, and the second request quantity Log ID.

In other embodiments of the present application, the step C includes: after receiving the call log query instruction with the log identifier parameter sent by the user terminal, searching for the inclusion and the information from the predetermined database. a log identifier matching the log identifier parameter, where the log identifier parameter includes a system identification code and time information;

Calculating, according to the first request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface, the number of pages that the user interface needs to display and the log identification code respectively included in each page of the page;

And obtaining, according to the mapping relationship between the log identifier and the call log, a call log corresponding to the log identifier included in each page, and returning the obtained call log to the client.

Alternatively, the step C includes: after receiving the call log query command with the log identifier parameter sent by the user terminal, searching from the predetermined database includes the parameter of the log identifier a matching log identifier, the log identifier parameter including a system identification code and time information;

Calculating the number of pages that the user interface needs to display and the log identification code respectively included in each page according to the second request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface;

For example, in one embodiment, after receiving a query from 15:37 on October 12, 2017 to 15:38 on October 12, 2017, after the instruction of the log of ESG1 is called, the search is performed from the predetermined data. The outbound and time range information is 15:37 on October 12, 2017 - 15:38 on October 12, 2017, and the system identification code is ESG1 matching log ID ESG12017101215:370120 (indicating October 12, 2017) 15:37, the first request received 20 requests), ESG12017101215:372352 (representing the number of 52 requests received at 15:37 on October 12, 2017, 23rd), ESG12017101215:374434 (indicating October 2017) At 15:37 on the 12th, the 44th request received 34 requests), ESG12017101215:380324 (representing the number of 24 requests received at 15:38 on October 12, 2017), ESG12017101215:383355 (indicating 2017) At 15:38 on October 12, the 33rd request received 55 requests), ESG12017101215:385638 (indicating that on October 12, 2017, 15:38, 56th, received 38 requests), in this embodiment The predetermined number of data displayed on each page of the user interface is 30, and the number of pages to be displayed on the user interface is calculated to be 8, and the first page package The log IDs are ESG12017101215:370120 and ESG12017101215:372310 (indicating that the first page contains an identifier of 20 requests received on October 12, 2017 at 15:37, 1st second and 15 October 2017 15 Point 37 points and the number of 10 requests received in the 23rd second, and so on, can calculate the log identification code respectively included in each page of the user interface to be displayed. It can be seen from the embodiment that the stored log identifier is in seconds, so the response time of the query page can be increased from the minute level to the second level, and the implementation process is simple.

It can be seen from the above embodiments that the electronic device proposed by the present application generates a call log corresponding to the call data generated in response to the request according to a predetermined call log identification code generation rule after receiving the request for calling data sent by the service system. a log identifier; generating a mapping relationship between the call log and the log identifier, storing the mapping relationship in a predetermined database; receiving a call log with a log identifier parameter sent by the user end After the query is executed, the log identifier corresponding to the log identifier parameter and the call log are determined according to the mapping relationship between the pre-stored call log and the log identifier, and the determined call log is returned to the client. It ensures that the query response time is increased from the minute to the second by matching the log identification code when the query data is called, which improves the efficiency of data query and reduces the time of exception processing.

It should be further noted that the data call log generation and query program of the present application may be described by using a program module having the same function according to different functions implemented by each part thereof. Please refer to FIG. 2 , which is a schematic diagram of a program module for data call log generation and query procedure in an embodiment of the electronic device of the present application. In this embodiment, the data call log generation and query program may be divided into a generation module 201, a storage module 202, and a determination module 203 according to different functions implemented by the respective parts. As can be seen from the above description, the program module referred to in the present application refers to a series of computer program instruction segments capable of performing a specific function, which is more suitable than the program to describe the execution process of the data call log generation and query program in the electronic device 10. The functions or operation steps implemented by the generating module 201, the storage module 202, and the determining module 203 are all similar to the above, and are not described in detail herein, for example, where:

The generating module 201 is configured to: after receiving the request for calling data sent by the service system, generate a log identifier corresponding to the call log generated when the request is invoked according to the predetermined call log identifier generation rule;

The storage module 202 is configured to generate a mapping relationship between the call log and the log identifier, and store the mapping relationship in a predetermined database.

The determining module 203 is configured to: after receiving the call log query instruction with the log identifier parameter sent by the user end, determine the parameter of the log identifier according to the mapping relationship between the pre-stored call log and the log identifier Corresponding log identifier and call log, and return the determined call log to the client.

In addition, the present application also provides a data call log generation and query method. Referring to FIG. 3, it is an implementation flowchart of an embodiment of the data call log generation and query method of the present application. As shown in FIG. 3, the data is called. The log generation and query method includes the following steps:

Step S301, after receiving the request for invoking data sent by the service system, generating a log identifier corresponding to the call log generated when the request is invoked according to the predetermined call log identifier generation rule;

Step S302, generating a mapping relationship between the call log and the log identification code, and storing the mapping relationship in a predetermined database;

Step S303, after receiving the call log query instruction with the log identifier parameter sent by the user end, determining, according to the mapping relationship between the pre-stored call log and the log identifier, the log identifier parameter corresponding to the log identifier The log identifier and the call log are returned, and the determined call log is returned to the client.

In this embodiment, the first current time is in units of seconds.

Further, as shown in FIG. 4, it is an implementation flowchart of another embodiment of the data call log generation and query method of the present application. As shown in FIG. 4, in the implementation, the step S303 includes the following steps:

Step S401, after receiving the call log query instruction with the log identifier parameter sent by the user terminal, searching for the log identifier including the log identifier matching the log identifier from the predetermined database. The log identifier parameter includes a system identification code and time information;

Step S402, calculating, according to the first request quantity included in the log identification code and the number of data displayed on each page of the predetermined user interface, the number of pages that the user interface needs to display and the logs respectively included in each page of the page. Identifier;

Step S403: Acquire a call log corresponding to the log identifier included in each page according to the mapping relationship between the log identifier and the call log, and return the obtained call log to the client.

Alternatively, in another embodiment, the step S402 may be further replaced by calculating the user according to the second request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface. The number of pages that the interface needs to display and the log identification code (not shown in Figure 4) contained in each page.

For example, in one embodiment, after receiving a query from 15:37 on October 12, 2017 to 15:38 on October 12, 2017, after the instruction of the log of ESG1 is called, the search is performed from the predetermined data. The outbound and time range information is 15:37 on October 12, 2017 - 15:38 on October 12, 2017, and the system identification code is ESG1 matching log ID ESG12017101215:370120 (indicating October 12, 2017) 15:37, the first request received 20 requests),

ESG12017101215:372352 (representing the number of 52 requests received at 15:37 on October 12, 2017 at 23:37), ESG12017101215:374434 (representing the number of 34 requests received at 44:37 on October 12, 2017, 44 seconds) ), ESG12017101215:380324 (representing the number of 24 requests received at 15:38 on October 12, 2017, 3rd), ESG12017101215:383355 (indicating that on October 12, 2017, 15:38, 33rd, received 55) The number of requests), ESG12017101215:385638 (representing 38 requests for the number of requests received at 15:38 on October 12, 2017), in this embodiment, the predetermined number of data displayed per page of the user interface is 30. The number of pages that need to be displayed on the user interface is 8, and the log identifiers contained in the first page are ESG12017101215:370120 and ESG12017101215:372310 (indicating that the first page contains the identification code at 15 o'clock on October 12, 2017) The number of 20 requests received in the first second of 37 minutes and the number of 10 requests received in the 23rd second of 15:37 on October 12, 2017), and so on, can calculate each page to be displayed on the user interface. The log identifiers contained in the pages. It can be seen from the embodiment that the stored log identifier is in seconds, so the response time of the query page can be increased from the minute level to the second level, and the implementation process is simple.

It can be seen from the above embodiments that the data call log generation and query method proposed by the present application generates a response to the request according to a predetermined call log identification code generation rule after receiving a request for calling data sent by the service system. a log identifier corresponding to the generated call log; generating a mapping relationship between the call log and the log identifier, storing the mapping relationship in a predetermined database; and receiving the log identifier sent by the user end After the call parameter query instruction of the code parameter is used, the log identification code corresponding to the log identification code parameter and the call log are determined according to the mapping relationship between the pre-stored call log and the log identification code, and the determined call log is returned. Give the client. It ensures that the query response time is increased from the minute to the second by matching the log identification code when the query data is called, which improves the efficiency of data query and reduces the time of exception processing.

In addition, the present application further provides a computer readable storage medium, on which the data call log generation and query program is stored, and the data call log generation and query program is executed by the processor to:

After receiving the request for invoking data sent by the service system, generating, according to the predetermined call log identifier generation rule, a log identifier corresponding to the call log generated when the request call data is generated;

Generating a mapping relationship between the call log and the log identifier, and storing the mapping relationship in a predetermined database;

After receiving the call log query command with the log identifier parameter sent by the user end, determining the log identifier corresponding to the log identifier parameter according to the mapping relationship between the pre-stored call log and the log identifier And calling the log, and returning the determined call log to the client.

The specific embodiment of the computer readable storage medium of the present application is substantially the same as the foregoing embodiments of the electronic device and the data call log generation and query method, and is not described herein.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

The above is only a preferred embodiment of the present application, and is not intended to limit the scope of the patent application, and the equivalent structure or equivalent process transformations made by the specification and the drawings of the present application, or directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of this application.

Claims

An electronic device, comprising: a memory, and a processor coupled to the memory, the processor configured to execute a data call log generation and query program stored on the memory, the data call The log generation and query program is implemented by the processor to implement the following steps:

A1. After receiving the request for invoking data sent by the service system, generating, according to the predetermined call log identifier generation rule, a log identifier corresponding to the call log generated when the request call data is generated;

A2. Generate a mapping relationship between the call log and the log identifier, and store the mapping relationship in a predetermined database.

A3. After receiving the call log query command with the log identifier parameter sent by the user end, determining a log corresponding to the log identifier parameter according to the mapping relationship between the pre-stored call log and the log identifier The identification code and the call log are returned, and the determined call log is returned to the client.
The electronic device according to claim 1, wherein the log identification code comprises a system identification code, a first time, and a first number of requests, and the step A3 comprises:

After receiving the call log query command with the log identifier parameter sent by the client, searching for the log identifier including the log identifier parameter from the predetermined database, The log identification code parameter includes a system identification code and time information;

Calculating, according to the first request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface, the number of pages that the user interface needs to display and the log identification code respectively included in each page of the page;

And obtaining, according to the mapping relationship between the log identifier and the call log, a call log corresponding to the log identifier included in each page, and returning the obtained call log to the client.
The electronic device according to claim 1, wherein the log identification code comprises a system identification code, a second time, and a second number of requests, and the step A3 comprises:

After receiving the call log query command with the log identifier parameter sent by the client, searching for the log identifier including the log identifier parameter from the predetermined database, The log identification code parameter includes a system identification code and time information;

Calculating the number of pages that the user interface needs to display and the log identification code respectively included in each page according to the second request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface;

And obtaining, according to the mapping relationship between the log identifier and the call log, a call log corresponding to the log identifier included in each page, and returning the obtained call log to the client.
The electronic device according to claim 1, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.
The electronic device according to claim 2, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.
The electronic device according to claim 3, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.
The electronic device according to claim 1, wherein the predetermined call log identification code generation rule comprises:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.
The electronic device according to claim 2, wherein the predetermined call log identification code generation rule comprises:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.
The electronic device according to claim 3, wherein the predetermined call log identification code generation rule comprises:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.
A data call log generation and query method, characterized in that the method comprises the following steps:

S1. After receiving the request for invoking data sent by the service system, generating a log identifier corresponding to the call log generated when the request is invoked according to the predetermined call log identifier generation rule;

S2. Generate a mapping relationship between the call log and the log identifier, and store the mapping relationship in a predetermined database.

S3. After receiving the call log query command with the log identifier parameter sent by the user end, determining a log corresponding to the log identifier parameter according to the mapping relationship between the pre-stored call log and the log identifier The identification code and the call log are returned, and the determined call log is returned to the client.
The data call log generation and query method according to claim 10, wherein the log identification code comprises a system identification code, a first time, and a first number of requests, and the step S3 comprises:

After receiving the call log query command with the log identifier parameter sent by the client, searching for the log identifier including the log identifier parameter from the predetermined database, The log identification code parameter includes a system identification code and time information;

Calculating, according to the first request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface, the number of pages that the user interface needs to display and the log identification code respectively included in each page of the page;

And obtaining, according to the mapping relationship between the log identifier and the call log, a call log corresponding to the log identifier included in each page, and returning the obtained call log to the client.
The data call log generation and query method according to claim 10, wherein the log identification code comprises a system identification code, a second time, and a second number of requests, and the step S3 comprises:

After receiving the call log query command with the log identifier parameter sent by the client, searching for the log identifier including the log identifier parameter from the predetermined database, The log identification code parameter includes a system identification code and time information;

Calculating the number of pages that the user interface needs to display and the log identification code respectively included in each page according to the second request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface;

And obtaining, according to the mapping relationship between the log identifier and the call log, a call log corresponding to the log identifier included in each page, and returning the obtained call log to the client.
The data call log generation and query method according to claim 10, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.

Alternatively, the predetermined call log identifier generation rule includes:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.
The data call log generation and query method according to claim 11, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.

Alternatively, the predetermined call log identifier generation rule includes:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.
The data call log generation and query method according to claim 12, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.

Alternatively, the predetermined call log identifier generation rule includes:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.
A computer readable storage medium storing a data call log generation and query program, the data call log generation and query program being executable by at least one processor to cause the at least one processor Perform the following steps:

After receiving the request for invoking data sent by the service system, generating, according to the predetermined call log identifier generation rule, a log identifier corresponding to the call log generated when the request call data is generated;

Generating a mapping relationship between the call log and the log identifier, and storing the mapping relationship in a predetermined database;

After receiving the call log query command with the log identifier parameter sent by the user end, determining the log identifier corresponding to the log identifier parameter according to the mapping relationship between the pre-stored call log and the log identifier And calling the log, and returning the determined call log to the client.
The storage medium according to claim 16, wherein the log identification code comprises a system identification code, a first time, and a first request quantity, and the received log identification code parameter sent by the user end After the log query command is invoked, the log identifier and the log corresponding to the log identifier parameter are determined according to the mapping relationship between the pre-stored call log and the log identifier, and the determined call log is returned to the log log. User-side steps, including:

After receiving the call log query command with the log identifier parameter sent by the client, searching for the log identifier including the log identifier parameter from the predetermined database, The log identification code parameter includes a system identification code and time information;

Calculating, according to the first request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface, the number of pages that the user interface needs to display and the log identification code respectively included in each page of the page;

And obtaining, according to the mapping relationship between the log identifier and the call log, a call log corresponding to the log identifier included in each page, and returning the obtained call log to the client.
The storage medium according to claim 16, wherein the log identification code comprises a system identification code, a second time, and a second number of requests, wherein the receipt of the log identification code parameter sent by the user end After the log query command is invoked, the log identifier and the log corresponding to the log identifier parameter are determined according to the mapping relationship between the pre-stored call log and the log identifier, and the determined call log is returned to the log log. User-side steps, including:

After receiving the call log query command with the log identifier parameter sent by the client, searching for the log identifier including the log identifier parameter from the predetermined database, The log identification code parameter includes a system identification code and time information;

Calculating the number of pages that the user interface needs to display and the log identification code respectively included in each page according to the second request quantity included in the log identifier and the number of data displayed on each page of the predetermined user interface;

And obtaining, according to the mapping relationship between the log identifier and the call log, a call log corresponding to the log identifier included in each page, and returning the obtained call log to the client.
The storage medium of claim 16, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.

Alternatively, the predetermined call log identifier generation rule includes:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.
The storage medium of claim 17, wherein the predetermined call log identification code generation rule comprises:

Acquiring a first time of receiving the request for the call data and a predetermined system identification code corresponding to the service system, wherein the first time is in seconds;

And counting a first request quantity of the call data received in the first time, and generating a log identification code including the first time, the system identification code, and the first request quantity.

Alternatively, the predetermined call log identifier generation rule includes:

Acquiring a second time of receiving the request for invoking data and a predetermined system identification code corresponding to the service system, wherein the second time is in minutes;

And respectively counting the second request quantity of the call data received in the second time in the second time, and generating a log identification code including the second time, the system identification code, and the second request quantity.