CN116610529A

CN116610529A - Buried point data acquisition method and device, electronic equipment and storage medium

Info

Publication number: CN116610529A
Application number: CN202310653528.8A
Authority: CN
Inventors: 易金晶; 姜柏青; 宁长来; 诸轶添
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-06-02
Filing date: 2023-06-02
Publication date: 2023-08-18

Abstract

The disclosure provides a method, a device, electronic equipment and a storage medium for acquiring buried point data, which can be applied to the technical field of cloud computing and the technical field of financial science and technology. The method for acquiring the buried point data comprises the following steps: in response to receiving a data acquisition request for a target service, invoking a first acquisition method to acquire first buried point data, wherein the first buried point data comprises data of the target service transmitted by a front end; invoking a second acquisition method to acquire second buried point data in the process of executing the target service, wherein the second buried point data comprises code parameter information generated by running the target service; storing a buried point document consisting of the first buried point data and the second buried point data to a cloud platform; and wherein the target service comprises custom annotations, the custom annotations comprising a first acquisition method and a second acquisition method.

Description

Buried point data acquisition method and device, electronic equipment and storage medium

Technical Field

The disclosure relates to the technical field of cloud computing and the technical field of financial science and technology, in particular to a method and a device for acquiring buried point data, electronic equipment and a storage medium.

Background

With the continuous development of internet technology, users can implement various business operations, such as financial transaction operations, using various services. In addition, the service provider can acquire buried point data generated in the service running process, analyze the buried point data and guarantee service safety or provide auxiliary services for users.

In the related art, front-end buried point data is generally obtained by using buried point software and web-end public service; or intercepting and analyzing the front-end request message through the interceptor to obtain the rear-end buried point data.

In the process of implementing the disclosed concept, the inventor finds that at least the following problems exist in the related art: collecting buried data through multiple data schemes can lead to the technical problems of high buried cost and high buried data acquisition cost.

Disclosure of Invention

In view of the above, the present disclosure provides a method, an apparatus, an electronic device, and a storage medium for acquiring buried point data.

According to a first aspect of the present disclosure, there is provided a method for acquiring buried point data, including:

in response to receiving a data acquisition request for a target service, invoking a first acquisition method to acquire first buried point data, wherein the first buried point data comprises data of the target service transmitted by a front end;

Invoking a second acquisition method to acquire second buried point data in the process of executing the target service, wherein the second buried point data comprises code parameter information generated by running the target service;

storing a buried point document consisting of the first buried point data and the second buried point data to a cloud platform; and

the target service comprises a custom annotation, and the custom annotation comprises a first acquisition method and a second acquisition method.

According to an embodiment of the disclosure, the second buried data includes an entry information and an exit information related to the target service, the entry information includes P entry names and P entry values, the entry names uniquely correspond to the entry values, and the exit information includes Q exit values; the second acquisition method comprises a first acquisition sub-method, a second acquisition sub-method and a third acquisition sub-method, wherein P is more than or equal to 1, and Q is more than or equal to 1;

in the process of executing the target service, invoking the second acquisition method to acquire the second embedded data includes:

calling a first acquisition sub-method to acquire P input names related to target service;

invoking a second acquisition sub-method to acquire P input parameter values related to the target service; and

and calling a third acquisition sub-method to acquire Q parameter values related to the target service.

According to the embodiment of the disclosure, the second buried point data further comprises class member variable information related to the target service, wherein the class member variable information comprises S class member variable names and S class member variable values, and the class member variable names uniquely correspond to the class member variable values; the second acquisition method also comprises a fourth acquisition sub-method, wherein S is more than or equal to 1;

and calling a fourth acquisition sub-method to acquire S class member variable names and S class member variable values related to the target service.

According to an embodiment of the present disclosure, the fourth obtaining sub-method is invoked to obtain S class member variable names and S class member variable values related to the target service, including:

calling a fourth acquisition sub-method to acquire a code execution object of the target service; and

based on the reflection mechanism, S class member variable names and S class member variable values are acquired according to the code execution object.

According to an embodiment of the present disclosure, wherein the first buried data includes at least one of: user behavior data, page performance data, and front-end operation error-reporting data.

According to the embodiment of the disclosure, the cloud platform is deployed with a distributed message service, and the cloud platform sends the embedded point document to the database through the distributed message service.

According to an embodiment of the present disclosure, after storing a buried point document composed of the first buried point data and the second buried point data to the cloud platform, the method further includes:

m buried point documents corresponding to M target services are obtained, M is more than or equal to 1, and the buried point documents come from a cloud platform or a database;

under the condition that the M buried point documents comprise first custom entry names and second custom entry names, acquiring first custom entry parameter values according to the first custom entry names, and acquiring second custom entry parameter values according to the second custom entry names, wherein the first custom entry names are used for representing user attributes, and the second custom entry names are used for representing service branch information; and

according to the first customized parameter and the second customized parameter, M target services are connected in series to form N service chains, wherein N is more than or equal to 1 and less than or equal to M.

According to an embodiment of the disclosure, a buried point document is stored to a cloud platform in a target format;

under the condition that the M buried point documents comprise first custom entry names and second custom entry names, acquiring first custom entry parameters according to the first custom entry names, and acquiring second custom entry parameters according to the second custom entry names, wherein the method comprises the following steps:

Under the condition that M buried point documents are determined to comprise a first custom parameter name and a second custom parameter name, generating a first call statement according to the first custom parameter name and a target grammar, wherein the target grammar is matched with a target format;

executing a first call statement to obtain a first custom parameter value;

generating a second call statement according to the second custom parameter name and the target grammar; and

executing the second call statement to obtain a second custom parameter value.

According to an embodiment of the present disclosure, according to a first customized parameter and a second customized parameter, M target services are connected in series into N service chains, including:

obtaining L target services with the same first custom parameter value from the M target services, wherein N is more than or equal to L and less than or equal to M; and

and according to the second customized parameter, connecting the L target services in series into N service chains.

A second aspect of the present disclosure provides an apparatus for acquiring buried point data, including:

the first acquisition module is used for calling a first acquisition method to acquire first buried point data in response to receiving a data acquisition request aiming at a target service, wherein the first buried point data comprises data of the target service transmitted by a front end;

The second acquisition module is used for calling a second acquisition method to acquire second buried point data in the process of executing the target service, wherein the second buried point data comprise code parameter information generated by running the target service;

the storage module is used for storing the buried point document formed by the first buried point data and the second buried point data to the cloud platform; and

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the above-described method of acquiring buried point data.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described method of acquiring buried point data.

The fifth aspect of the present disclosure also provides a computer program product, including a computer program, which when executed by a processor implements the above-mentioned method for acquiring buried point data.

In an embodiment of the present disclosure, since the target service includes a custom annotation including a first acquisition method and a second acquisition method, in response to receiving a data acquisition request for the target service, the first acquisition method is invoked to acquire first buried point data; in the process of executing the target service, a second acquisition method is called to acquire second buried point data; and storing the buried point document formed by the first buried point data and the second buried point data to a cloud platform, so that the first buried point data of the front end and the second buried point data of the rear end can be acquired simultaneously. According to the embodiment of the disclosure, the first buried point data and the second buried point data can be acquired at the same time, the technical problems that the buried point cost is high and the buried point data acquisition cost is high due to the fact that the buried point data are acquired through multiple data schemes are at least partially solved, the buried point cost can be reduced, and the more comprehensive buried point data can be acquired.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:

fig. 1 schematically illustrates an application scenario of a method of acquiring buried point data according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a method of acquiring buried point data according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow chart of a second method of buried data acquisition according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates a system architecture of a method of acquiring buried point data according to a specific embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow chart for concatenating M target services into N service chains, according to an embodiment of the disclosure;

FIG. 6 schematically illustrates a flow diagram for deriving N service chains from M target services, in accordance with a specific embodiment of the present disclosure;

fig. 7 schematically illustrates a block diagram of a structure of an acquisition apparatus of buried point data according to an embodiment of the present disclosure; and

fig. 8 schematically illustrates a block diagram of an electronic device adapted for a method of acquiring buried point data according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

It should be noted that, the method and the device for acquiring buried point data in the present disclosure may be used in the financial field, and may also be used in any field other than the financial field, such as the cloud computing technical field, the computer technical field, the information security technical field, etc., and the application field of the method and the device for acquiring buried point data in the present disclosure is not limited.

In the technical scheme of the disclosure, the related data (such as including but not limited to personal information of a user) are collected, stored, used, processed, transmitted, provided, disclosed, applied and the like, all conform to the regulations of related laws and regulations, necessary security measures are adopted, and the public welcome is not violated.

The processing of collecting, storing, using, processing, transmitting, providing, disclosing and applying the buried point data related to the present disclosure all conform to the rules of the relevant laws and regulations, necessary security measures are taken, and the public order is not violated.

For example, before acquiring buried data, a user is requested to acquire rights to the buried data. And acquiring buried point data under the permission of a user.

In the related art, the scheme for acquiring buried point data includes: and acquiring front-end buried point data by using buried point software and web-end public service. The embedded point scheme belongs to an integrated solution, aims at front-end embedded points, can acquire embedded point data of user behaviors, and cannot acquire back-end data of service operation. Alternatively, the method for acquiring the buried point data further includes: and introducing an interceptor jar packet, intercepting a request sent by the front end through the interceptor, and then obtaining a front end request message through analysis. The embedded point scheme aims at the embedded point of the rear end, and the front end user behavior data cannot be acquired.

In the process of implementing the disclosed concept, the inventor finds that at least the following problems exist in the related art: collecting buried data through multiple data schemes can lead to the technical problems of high buried cost and high buried data acquisition cost. In the related art, a scheme capable of simultaneously acquiring front-end buried point data and rear-end buried point data is lacking.

To at least partially solve the above technical problems, an embodiment of the present disclosure provides a method for acquiring buried point data, including: in response to receiving a data acquisition request for a target service, invoking a first acquisition method to acquire first buried point data, wherein the first buried point data comprises data of the target service transmitted by a front end; invoking a second acquisition method to acquire second buried point data in the process of executing the target service, wherein the second buried point data comprises code parameter information generated by running the target service; storing a buried point document consisting of the first buried point data and the second buried point data to a cloud platform; and wherein the target service comprises custom annotations, the custom annotations comprising a first acquisition method and a second acquisition method.

Fig. 1 schematically illustrates an application scenario of a method for acquiring buried point data according to an embodiment of the present disclosure.

As shown in fig. 1, an application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is a medium used to provide a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may interact with the server 105 through the network 104 using at least one of the first terminal device 101, the second terminal device 102, the third terminal device 103, to receive or send messages, etc. Various communication client applications, such as a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only) may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103.

The first terminal device 101, the second terminal device 102, the third terminal device 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by the user using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that, the method for acquiring buried point data provided in the embodiments of the present disclosure may be generally executed by the server 105. Accordingly, the device for acquiring the buried point data provided in the embodiments of the present disclosure may be generally disposed in the server 105. The method for acquiring buried point data provided by the embodiment of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105. Accordingly, the apparatus for acquiring buried point data provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105.

The method for acquiring buried point data provided by the embodiment of the present disclosure may also be executed by any one of the first terminal device 101, the second terminal device 102, and the third terminal device 103. Accordingly, the apparatus for acquiring buried point data provided in the embodiments of the present disclosure may be generally set in any one of the first terminal device 101, the second terminal device 102, and the third terminal device 103.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The method of acquiring point data of the disclosed embodiment will be described in detail below with reference to fig. 2 to 6 based on the scenario described in fig. 1.

Fig. 2 schematically illustrates a flowchart of a method of acquiring buried point data according to an embodiment of the present disclosure.

As shown in fig. 2, the method 200 includes operations S210 to S230.

In response to receiving a data acquisition request for a target service, a first acquisition method is invoked to acquire first buried point data in operation S210.

In operation S220, in the course of executing the target service, a second acquisition method is called to acquire second buried point data.

In operation S230, a buried point document composed of the first buried point data and the second buried point data is stored to the cloud platform.

According to embodiments of the present disclosure, the target services include various types, for example, services related to financial transaction classes, services related to interactive operations, and the like.

According to an embodiment of the present disclosure, the target service includes a custom annotation including a first acquisition method and a second acquisition method. Before or during the execution of the target service, the buried point data acquisition operation is realized by triggering a first acquisition method or a second acquisition method in the custom annotation.

According to an embodiment of the present disclosure, the first obtaining method and the second obtaining method may be defined in advance in a section class of the custom annotation. The first acquisition method is only used for acquiring first buried point data, namely front-end buried point data; the second acquisition method is only used for acquiring second buried point data, namely rear buried point data.

According to embodiments of the present disclosure, a Spring custom annotation and a facet-oriented programming (Aspect Oriented Programming, AOP) technique may be utilized to add a first acquisition method and a second acquisition method to a custom annotated facet class. The first acquisition method and the second acquisition method may be functional methods that perform specific operations, such as acquisition operations.

According to embodiments of the present disclosure, the data acquisition request may be a request generated by triggering a custom annotation of the target service prior to executing the target service.

According to an embodiment of the present disclosure, the first buried data includes data that is imported by the front-end into the target service. For example, the user can click a query button on a query page for querying user information. In the above case, the first buried data includes various data such as information of the current query page, operation time of clicking the query button by the user, and the like.

According to an embodiment of the present disclosure, the second buried data includes code parameter information generated by the execution target service. The second buried point data may be understood as rear-end buried point data acquired when the code for realizing the target service is run at the rear end.

For example, when the target service is a transaction service, the second embedded data includes a code return result that characterizes the success or failure of the transaction.

According to the embodiment of the disclosure, since the custom annotation is added in advance in the target service, in response to receiving the data acquisition request for the target service, a first acquisition method in the custom annotation is invoked and executed to acquire the first buried point data before the target service is executed. The execution result of the first acquisition method is the first buried point data. And calling and executing a second acquisition method in the custom annotation in the process of executing the target service so as to acquire second buried point data. The execution result of the second acquisition method is the second buried point data.

According to an embodiment of the present disclosure, a buried point document characterizes buried point data collected when a target service is invoked by the same service invocation request. When the same user invokes the same service at different times, the generation of the buried point documents is different. The service invocation request includes a request initiated via hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP), such as an HTTP request; alternatively, the request may be initiated via a remote procedure call protocol (Remote Procedure Call Protocol, RPC), such as an RPC request.

For example, the user initiates an HTTP request at 12 points invoking transaction service A, and the collected embedded data constitutes embedded document A' for transaction service A invoked at 12 points. The user initiates an HTTP request for calling the transaction service A at 18 points, and the collected buried data forms a buried document A aiming at the transaction service A called at 18 points. The buried point document a' is different from the buried point document a″.

Fig. 3 schematically illustrates a flow chart of a second buried data acquisition method according to an embodiment of the present disclosure.

As shown in fig. 3, the second buried data acquisition method 300 of this embodiment includes operations S321 to S323, which may be a specific embodiment of operation S220.

In operation S321, a first obtaining sub-method is invoked to obtain P reference names related to the target service.

In operation S322, a second acquisition sub-method is invoked to acquire P entry parameter values related to the target service.

In operation S323, a third acquiring sub-method is invoked to acquire Q out parameter values related to the target service.

According to an embodiment of the disclosure, the second buried data includes an entry information and an exit information related to the target service, the entry information includes P entry names and P entry values, the entry names uniquely correspond to the entry values, and the exit information includes Q exit values; the second acquisition method comprises a first acquisition sub-method, a second acquisition sub-method and a third acquisition sub-method, wherein P is more than or equal to 1, and Q is more than or equal to 1.

According to an embodiment of the present disclosure, the target service includes at least one internal function method by which the functions of the target service are commonly implemented. There are a plurality of call relations between at least one internal function method, each internal function method including at least one input parameter (input parameters) and at least one output parameter (output parameters).

According to embodiments of the present disclosure, an input is required when an internal function method is called, and an output of the internal function method may be understood as an output. The number of in-and out-going ginseng may be different. The parameter entering information comprises a parameter entering name and a parameter entering value, and the parameter exiting information comprises a parameter exiting name and a parameter exiting value.

According to an embodiment of the present disclosure, the target service includes at least one internal function method, whereby there may be P in-parameters and Q out-parameters for one target service.

According to an embodiment of the present disclosure, the first acquisition sub-method may be determined according to a Signature method. For example, the first acquisition sub-method may be Signature. The second acquisition sub-method may be determined from procedingJoinPoint. For example, the second acquisition sub-method may be joinopoint. The third acquisition sub-method may be procedingJoinPoint.processed (). Wherein, as a return result of the internal function method, the out-reference name may default to result.

According to embodiments of the present disclosure, entering may further include user-customized entering and exiting may further include user-customized exiting. For example, custom entry userID, branchID is used to characterize user attributes and service branch information, respectively. The custom out parameter name resFlag is used for representing the processing result of the target program block.

According to the embodiment of the disclosure, for the custom parameter entering and the custom parameter exiting, the user can also customize the method for acquiring the parameter value through the JSONPath grammar.

For example, for the custom entry name userID, the method for obtaining the custom entry value includes: and extracting the current user ID, such as currentUserID, from the paramMap parameter of the incoming call. For the custom out parameter name resFlag, the method for acquiring the custom in parameter value comprises the following steps: the processing result identification of the retCode program is fetched from the parameter.

According to an embodiment of the disclosure, the second buried point data further includes class member variable information related to the target service, the class member variable information including S class member variable names and S class member variable values, the class member variable names uniquely corresponding to the class member variable values; the second acquisition method also comprises a fourth acquisition sub-method, wherein S is more than or equal to 1;

in the process of executing the target service, invoking the second acquisition method to acquire the second embedded data includes: and calling a fourth acquisition sub-method to acquire S class member variable names and S class member variable values related to the target service.

According to an embodiment of the present disclosure, class member variables include variables related to traffic, temporary variables. It should be noted that, although the temporary variable exists only in the defined internal function method, the temporary variable may be used to assist the series call chain.

According to an embodiment of the present disclosure, invoking a fourth obtaining sub-method to obtain S class member variable names and S class member variable values related to a target service includes:

calling a fourth acquisition sub-method to acquire a code execution object of the target service; based on the reflection mechanism, S class member variable names and S class member variable values are acquired according to the code execution object.

According to the embodiment of the disclosure, the current instance is obtained through procedingJoinPoint, and the class member variable value of the current instance is obtained through reflection.

The embodiment of the disclosure not only can collect the first buried point data transmitted from the front end, but also can acquire class member variables inside the target service and the out-going parameters and the in-going parameters of the internal function method, can break the technical limitations of the existing buried point scheme, increases the collection dimension of the buried point data, and is beneficial to the subsequent safety analysis of the target service. In addition, when the first buried point data and the second buried point data are acquired, the embodiment of the disclosure can realize decoupling and isolation of the target service business function and the buried point acquisition function without modifying the business logic of the target service.

According to an embodiment of the present disclosure, the first buried data includes at least one of: user behavior data, page performance data, and front-end operation error-reporting data.

According to embodiments of the present disclosure, user behavior data is acquired as allowed by a user.

For example, when a user logs into a web page or application client, the user is requested to obtain the authority of the user behavior data. And acquiring user behavior data under the permission of a user.

According to an embodiment of the present disclosure, the user behavior data includes page behavior parameters such as a start time, an end time, a number of times the user performs the transaction operation, a number of times the user clicks the plurality of function modules, and the like.

According to embodiments of the present disclosure, the page performance data includes page rendering parameters, such as the location, shape, color, etc., of a plurality of operational keys in the page.

According to the embodiment of the disclosure, the front-end operation error-reporting data includes error-reporting content, error-reporting reasons, error-reporting time and the like displayed on the page.

According to an embodiment of the disclosure, a cloud platform is deployed with a distributed message service, and the cloud platform sends buried point documents to a database through the distributed message service.

According to embodiments of the present disclosure, the cloud Platform provides the target Service in the form of Platform-as-a-Service (PAAS). Thus, the cloud platform may also be referred to as a PAAS platform.

According to an embodiment of the present disclosure, a server may call a first acquisition method to acquire first buried point data in response to receiving a data acquisition request for a target service; in the process of executing the target service, a second acquisition method is called to acquire second buried point data; and storing the buried point document formed by the first buried point data and the second buried point data to a cloud platform.

As a specific embodiment of the disclosure, an acquisition system may be further disposed on the terminal device, where the acquisition system acquires first buried point data and second buried point data, and stores a buried point document formed by the first buried point data and the second buried point data to the cloud platform.

For example, first buried point data and second buried point data are acquired through Fluentd, and a buried point document composed of the first buried point data and the second buried point data is stored to the cloud platform. Wherein Fluentd is an open-source general collection system, which can collect log or buried point data from multiple data sources. Fluentd uses JSON format to record journals or buried point data.

According to embodiments of the present disclosure, a distributed message service may be deployed in a target node of a cloud platform such that the cloud platform sends a buried point document to a database through the distributed message service. The distributed messaging service may be kafka.

For example, a kafka cluster and topic are configured in Fluentd nodes of the cloud platform, and the cloud platform can push the embedded point document to the kafka, and the embedded point document is stored to the database through the kafka.

Fig. 4 schematically illustrates a system architecture of a method for acquiring buried point data according to a specific embodiment of the present disclosure.

As shown in fig. 4, the system architecture 400 includes a server/acquisition system 401, a cloud platform 402, a distributed messaging service 403, a database 404, a first data analysis module 405, a second data analysis module 406, and a third data analysis module 407.

The server/acquisition system 401 may acquire the first buried point data and the second buried point data, and store a buried point document composed of the first buried point data and the second buried point data to the cloud platform 402. Cloud platform 402 may also transmit the embedded point document to distributed message service 403 such that distributed message service 403 stores the embedded point document in a subscription manner to database 404.

For example, database 404 may pull data corresponding to topic from kafka and store the buried point data in the form of a database.

According to an embodiment of the present disclosure, the first data analysis module 405, the second data analysis module 406, and the third data analysis module 407 may obtain the buried point data from the database 404 for data analysis.

For example, the first data analysis module 405 may perform a performance index analysis based on the first buried point data and/or the second buried point data; the second data analysis module 406 may perform user behavior analysis based on the first buried data; the third data analysis module 407 may perform security risk analysis according to the first buried point data and/or the second buried point data.

Fig. 5 schematically illustrates a flow chart for concatenating M target services into N service chains, according to an embodiment of the disclosure.

As shown in fig. 5, the flowchart 500 of the embodiment for concatenating M target services into N service chains includes operations S510 to S530. The operations S510 to S530 may be disposed after the operation S230.

In operation S510, M buried point documents corresponding to M target services are acquired, M being equal to or greater than 1.

In operation S520, in the case where it is determined that the M embedded documents include the first custom entry name and the second custom entry name, the first custom entry value is obtained according to the first custom entry name, and the second custom entry value is obtained according to the second custom entry name.

In operation S530, M target services are connected in series into N service chains according to the first customized input parameter value and the second customized input parameter value, wherein N is greater than or equal to 1 and less than or equal to M.

According to an embodiment of the present disclosure, for a plurality of target services belonging to a plurality of HTTP requests or a plurality of RPC requests, operations S210 to S230 are performed for each target service, and a buried point document may be corresponding, whereby the buried point document of the plurality of target services may be stored in the cloud platform. Then, the embedded point documents of the target services can be utilized to concatenate the target services belonging to the HTTP requests or the RPC requests into a call chain so as to analyze the business continuity and the security of the target services.

According to embodiments of the present disclosure, since the buried point document is stored to the cloud platform, the cloud platform may transmit the buried point document to the database. Thus, in operation S510, the buried point document may be from the cloud platform or from the database.

According to an embodiment of the present disclosure, a first custom entry is used to characterize a user attribute and a second custom entry is used to characterize service branch information. For example, the first custom entry name may be "user ID" or "userID", and the second custom entry name may be "service leg ID" or "brandchid".

According to an embodiment of the present disclosure, the embedded point document includes second embedded point data, which may include a first custom embedded name and a second custom embedded name. The first custom entry name and the second custom entry name may be added to the custom annotation by the user in advance, and in the process of executing operations S210 to S230, the first custom entry name, the first custom entry value, the second custom entry name, and the second custom entry name of the target service may be acquired. Thus, in the case that the buried point document is determined to include the first custom entry name and the second custom entry name, the collected first custom entry parameter value and the second custom entry parameter value can be determined.

According to an embodiment of the disclosure, a method for determining whether a buried point document includes a first custom entry name and a second custom entry name may be: determining whether the first custom entry name and the second custom entry name are included in the custom annotation of the target service.

According to embodiments of the present disclosure, multiple users can use the same or different services, and there is a correlation between functions provided by the multiple services. User attributes can be uniquely identified with the first custom entry and service branch information can be uniquely identified with the second custom entry. The first custom entry and the second custom entry may uniquely identify a current service used by the user. Therefore, according to the first customized parameter value and the second customized parameter value, M target services can be connected in series into N service chains.

In the related art, the traceId recorded by the log link is used for uniquely identifying the current log of the http micro-service, however, the traceId is generally a randomly generated number, so that the traceId can only be connected with a plurality of functions in a single http life cycle in series, services related to a plurality of life cycles cannot be connected in series, the subsequent security analysis needs to be manually participated, and the problems of high security analysis cost, easiness in occurrence of error and the like are caused.

In the embodiment of the disclosure, as the first custom parameter and the second custom parameter are uniquely related to the user and the service, a plurality of http requests or rpc requests can be connected in series with the target service of the http lifecycle, not only can the service chain of the function method level in the service be constructed, but also the service chain of the service level can be constructed, thereby reducing the security analysis cost and avoiding the problem of mistakes caused by introducing manpower.

According to the embodiment of the disclosure, the first custom entry name and the second custom entry name can form a service main key, and the first custom entry parameter value and the second custom entry parameter value form a key value of the service main key, so that M target services are connected in series into N service chains according to the key value.

According to an embodiment of the disclosure, a buried point document is stored to the cloud platform in a target format. For example, JSON format.

According to an embodiment of the present disclosure, in a case where it is determined that M embedded point documents include a first custom entry name and a second custom entry name, acquiring a first custom entry parameter value according to the first custom entry name, and acquiring a second custom entry parameter value according to the second custom entry name includes: under the condition that M buried point documents are determined to comprise a first custom parameter name and a second custom parameter name, generating a first call statement according to the first custom parameter name and a target grammar, wherein the target grammar is matched with a target format; executing a first call statement to obtain a first custom parameter value; generating a second call statement according to the second custom parameter name and the target grammar; and executing a second call statement to acquire a second custom parameter.

In accordance with an embodiment of the present disclosure, in the case where the target format is JSON format, the target syntax may be JSONPath syntax.

According to embodiments of the present disclosure, the call statement generated from the custom parameter name and the target grammar may be jsonpath. Read (json). Json represents the format of the buried point document. In the case where the custom parameter name is the first custom parameter name userID, the first call statement may be JSONPath. Read (json, userID). In the case where the custom parameter name is the second custom parameter name brandid, the second call statement may be jsonpath. Read (json, brandid).

According to an embodiment of the present disclosure, according to a first customized parameter and a second customized parameter, concatenating M target services into N service chains, including: obtaining L target services with the same first custom parameter value from the M target services, wherein N is more than or equal to L and less than or equal to M; and according to the second customized parameter, connecting the L target services in series into N service chains.

According to the embodiment of the disclosure, the first custom entry name is used for representing the user attribute, the second custom entry name is used for representing the service branch information, whether the user is the same user can be determined according to whether the first custom entry parameter value is the same, and the association relationship among the plurality of target services can be determined according to the first custom entry parameter value, so that the plurality of target services are connected in series into a plurality of service chains according to the association relationship among the plurality of target services.

According to an embodiment of the present disclosure, the association relationship between the plurality of target services includes a call relationship and a called relationship.

Fig. 6 schematically illustrates a flow diagram for deriving N service chains from M target services according to a specific embodiment of the present disclosure.

As shown in fig. 6, a flow chart 600 schematically illustrates a process of obtaining N service chains from M target services.

According to the embodiment of the disclosure, after the acquisition of the buried point data is completed, buried point documents of the M target services may be acquired from the cloud platform or the database. For example, the 1 st embedded point document 602_1, … of the 1 st target service 601_1 is determined, the M-th embedded point document 602_m, … of the M-th target service 601_m is determined, and the M-th embedded point document 602_m of the M-th target service 601_m is determined. The embedded point document may include first custom parameter information and second custom parameter information.

For example, the 1 st embedded point document 602_1 may include first custom parameter information 603_11 and second custom parameter information 603_12, the first custom parameter information 603_11 including a first custom parameter name userID and a first custom parameter value 1, the second custom parameter information 603_12 including a second custom parameter name brandedID and a second custom parameter value 11; …; the m-th embedded point document 602_m may include first custom parameter information 603_m1 and second custom parameter information 603_m2, the first custom parameter information 603_m1 includes a first custom parameter name userID and a first custom parameter value 1, and the second custom parameter information 603_m2 includes a second custom parameter name branchID and a second custom parameter value 1m; …; the mth buried point document 602_m may include first custom parameter information 603_m1 and second custom parameter information 603_m2, the first custom parameter information 603_m1 includes a first custom parameter name userID and a first custom parameter value 1, and the second custom parameter information 603_m2 includes a second custom parameter name brandid and a second custom parameter value 2.

Since the first custom parameter values of the M target services are the same and there is an association between the second custom parameter values of the first M target services, the first M target services may be concatenated into the service chain 1 604_1. In the case where there is no call relationship between the target service and other target services, a single target service may be used as a service chain, for example, the mth target service may be used as a service chain N604_n.

Fig. 7 schematically shows a block diagram of a structure of an acquisition apparatus of buried point data according to an embodiment of the present disclosure.

As shown in fig. 7, the buried point data acquisition apparatus 700 of this embodiment includes a first acquisition module 710, a second acquisition module 720, and a storage module 730.

The first obtaining module 710 is configured to invoke a first obtaining method to obtain first buried point data in response to receiving a data obtaining request for a target service, where the first buried point data includes data of the target service that is imported by a front end. In an embodiment, the first obtaining module 710 may be configured to perform the operation S210 described above, which is not described herein.

And a second acquisition module 720, configured to invoke a second acquisition method to acquire second embedded point data in a process of executing the target service, where the second embedded point data includes code parameter information generated by running the target service. In an embodiment, the second obtaining module 720 may be configured to perform the operation S220 described above, which is not described herein.

And the storage module 730 is configured to store a buried point document composed of the first buried point data and the second buried point data to the cloud platform. In an embodiment, the storage module 730 may be used to perform the operation S230 described above, which is not described herein.

According to an embodiment of the present disclosure, the target service includes a custom annotation including a first acquisition method and a second acquisition method.

According to an embodiment of the present disclosure, the second acquisition module 720 includes a first acquisition sub-module, a second acquisition sub-module, and a third acquisition sub-module.

The first acquisition sub-module is used for calling a first acquisition sub-method to acquire P parameter entries related to the target service. In an embodiment, the first obtaining sub-module may be used to perform the operation S321 described above, which is not described herein.

The second obtaining sub-module is used for calling a second obtaining sub-method to obtain P parameter values related to the target service. In an embodiment, the second obtaining sub-module may be used to perform the operation S322 described above, which is not described herein.

The third obtaining sub-module is used for calling a third obtaining sub-method to obtain Q parameter values related to the target service. In an embodiment, the third obtaining sub-module may be configured to perform the operation S323 described above, which is not described herein.

According to an embodiment of the present disclosure, the second obtaining module 720 further includes a fourth obtaining sub-module for invoking a fourth obtaining sub-method to obtain S class member variable names and S class member variable values related to the target service. The second buried point data further comprises class member variable information related to the target service, wherein the class member variable information comprises S class member variable names and S class member variable values, and the class member variable names and the class member variable values are uniquely corresponding; the second acquisition method also comprises a fourth acquisition sub-method, wherein S is more than or equal to 1.

According to an embodiment of the present disclosure, the fourth acquisition sub-module further includes a first acquisition unit and a second acquisition unit.

The first acquisition unit is used for calling a fourth acquisition sub-method to acquire a code execution object of the target service.

The second obtaining unit is used for obtaining S class member variable names and S class member variable values according to the code execution object based on the reflection mechanism.

According to an embodiment of the present disclosure, the buried point data acquisition apparatus 700 further includes a third acquisition module, a determination module, and a series module.

The third acquisition module is used for acquiring M buried point documents corresponding to M target services, wherein M is more than or equal to 1, and the buried point documents are from a cloud platform or a database. In an embodiment, the third obtaining module may be configured to perform the operation S510 described above, which is not described herein.

The determining module is used for obtaining a first custom entry parameter value according to the first custom entry parameter and obtaining a second custom entry parameter value according to the second custom entry parameter under the condition that the M buried point documents comprise the first custom entry parameter and the second custom entry parameter, wherein the first custom entry parameter is used for representing user attributes, and the second custom entry parameter is used for representing service branch information. In an embodiment, the determining module may be configured to perform the operation S520 described above, which is not described herein.

The series module is used for acquiring a first custom entry parameter value according to the first custom entry parameter and acquiring a second custom entry parameter value according to the second custom entry parameter under the condition that the M buried point documents comprise the first custom entry parameter and the second custom entry parameter, wherein the first custom entry parameter is used for representing user attributes, and the second custom entry parameter is used for representing service branch information. In an embodiment, the serial module may be used to perform the operation S530 described above, which is not described herein.

According to an embodiment of the present disclosure, the determining module includes a first generating sub-module, a first executing sub-module, a second generating sub-module, and a second executing sub-module.

The first generation sub-module is used for generating a first call statement according to the first custom parameter name and the target grammar when the M buried point documents are determined to comprise the first custom parameter name and the second custom parameter name, and the target grammar is matched with the target format.

The first execution submodule is used for executing the first call statement and acquiring a first custom parameter value.

The second generation sub-module is used for generating a second call statement according to the second custom parameter name and the target grammar.

The second execution submodule is used for executing a second call statement and acquiring a second custom parameter value.

According to an embodiment of the present disclosure, the series module includes a first series sub-module and a second series sub-module.

The first series submodule is used for acquiring L target services with the same first custom parameter value from M target services, wherein N is not less than L and not more than M.

The second serial submodule is used for connecting the L target services in series into N service chains according to the second customized parameter.

Any of the first acquisition module 710, the second acquisition module 720, and the storage module 730 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules, according to an embodiment of the present disclosure. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module.

According to embodiments of the present disclosure, at least one of the first acquisition module 710, the second acquisition module 720, and the storage module 730 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or in hardware or firmware, such as any other reasonable manner of integrating or packaging the circuitry, or in any one of or a suitable combination of any of the three. Alternatively, at least one of the first acquisition module 710, the second acquisition module 720, and the storage module 730 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

As shown in fig. 8, an electronic device 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 801 may also include on-board memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.

In the RAM 803, various programs and data required for the operation of the electronic device 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or the RAM 803. Note that the program may be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 800 may also include an input/output (I/O) interface 805, the input/output (I/O) interface 805 also being connected to the bus 804. The electronic device 800 may also include one or more of the following components connected to the input/output I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 802 and/or RAM 803 and/or one or more memories other than ROM 802 and RAM 803 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to perform the methods provided by embodiments of the present disclosure.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 801. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and installed in the form of a signal on a network medium, and/or from a removable medium 811 via a communication portion 809. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 801. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

While the foregoing is directed to embodiments of the present disclosure, other and further details of the invention may be had by the present application, it is to be understood that the foregoing description is merely exemplary of the present disclosure and that no limitations are intended to the scope of the disclosure, except insofar as modifications, equivalents, improvements or modifications may be made without departing from the spirit and principles of the present disclosure.

Claims

1. A buried point data acquisition method comprises the following steps:

in response to receiving a data acquisition request for a target service, invoking a first acquisition method to acquire first buried point data, wherein the first buried point data comprises data transmitted into the target service by a front end;

the target service comprises a custom annotation, and the custom annotation comprises the first acquisition method and the second acquisition method.

2. The method of claim 1, wherein the second buried data comprises entry information and exit information related to the target service, the entry information comprising P entry names and P entry values, the entry names uniquely corresponding to the entry values, the exit information comprising Q exit values; the second acquisition method comprises a first acquisition sub-method, a second acquisition sub-method and a third acquisition sub-method, wherein P is more than or equal to 1, and Q is more than or equal to 1;

the step of calling a second obtaining method to obtain second buried data in the process of executing the target service includes:

calling the first acquisition sub-method to acquire P parameter entries related to the target service;

Invoking the second acquisition sub-method to acquire P parameter values related to the target service; and

and calling the third acquisition sub-method to acquire Q parameter values related to the target service.

3. The method of claim 1, wherein the second embedded point data further comprises class member variable information associated with the target service, the class member variable information comprising S class member variable names and S class member variable values, the class member variable names uniquely corresponding to the class member variable values; the second acquisition method further comprises a fourth acquisition sub-method, wherein S is more than or equal to 1;

and calling the fourth acquisition sub-method to acquire S class member variable names and S class member variable values related to the target service.

4. The method of claim 3, wherein said invoking said fourth get sub-method to get S said class member variable names and S said class member variable values associated with said target service comprises:

invoking the fourth acquisition sub-method to acquire a code execution object of the target service; and

Based on a reflection mechanism, S class member variable names and S class member variable values are obtained according to the code execution object.

5. The method of claim 1, wherein the first buried data comprises at least one of: user behavior data, page performance data, and front-end operation error-reporting data.

6. The method of claim 1, wherein the cloud platform is deployed with a distributed messaging service through which the cloud platform sends the embedded point document to a database.

7. The method of claim 1 or 6, wherein after storing the buried point document composed of the first buried point data and the second buried point data to a cloud platform, further comprising:

m buried point documents corresponding to M target services are obtained, M is more than or equal to 1, and the buried point documents come from the cloud platform or the database;

under the condition that M buried point documents comprise first custom input parameter names and second custom input parameter names, acquiring first custom input parameter values according to the first custom input parameter names, and acquiring second custom input parameter values according to the second custom input parameter names, wherein the first custom input parameter names are used for representing user attributes, and the second custom input parameter names are used for representing service branch information; and

And according to the first customized input parameter value and the second customized input parameter value, M target services are connected in series to form N service chains, wherein N is more than or equal to 1 and less than or equal to M.

8. The method of claim 7, wherein the embedded point document is stored to the cloud platform in a target format;

under the condition that M buried point documents are determined to comprise first custom entry names and second custom entry names, acquiring first custom entry parameters according to the first custom entry names, and acquiring second custom entry parameters according to the second custom entry names, wherein the method comprises the following steps:

under the condition that M buried point documents are determined to comprise a first custom parameter name and a second custom parameter name, generating a first call statement according to the first custom parameter name and a target grammar, wherein the target grammar is matched with the target format;

executing the first call statement to acquire the first custom parameter value;

and executing the second call statement to acquire the second custom parameter value.

9. The method of claim 7, wherein the concatenating the M target services into N service chains according to the first custom entry parameter and the second custom entry parameter comprises:

Obtaining L target services with the same first customized input parameter value from M target services, wherein N is more than or equal to L and less than or equal to M; and

and according to the second customized parameter, connecting L target services in series to form the N service chains.

10. An acquisition device of buried point data, comprising:

the first acquisition module is used for calling a first acquisition method to acquire first buried point data in response to receiving a data acquisition request aiming at a target service, wherein the first buried point data comprises data transmitted into the target service by a front end;

the second acquisition module is used for calling a second acquisition method to acquire second embedded point data in the process of executing the target service, wherein the second embedded point data comprises code parameter information generated by running the target service;

the storage module is used for storing the buried point document formed by the first buried point data and the second buried point data to a cloud platform; and

11. An electronic device, comprising:

one or more processors;

Storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.

12. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1 to 9.

13. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 9.