CN110858163A

CN110858163A - Data processing method, device and machine readable medium

Info

Publication number: CN110858163A
Application number: CN201810962489.9A
Authority: CN
Inventors: 张国顺; 朱陈良
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Singapore Holdings Pte Ltd
Priority date: 2018-08-22
Filing date: 2018-08-22
Publication date: 2020-03-03

Abstract

The embodiment of the application discloses a data processing method, a data processing device and a data processing device, wherein the method specifically comprises the following steps: determining target calling information of at least one second service subsystem in the processing process of a user request by a first service subsystem according to a log of the first service subsystem; and displaying the target calling information. The target calling information displayed by the embodiment of the application can be checked and utilized by a user, and can be helpful for positioning the abnormity of the first service subsystem; in addition, the process of obtaining the target calling information according to the log of the first service subsystem can involve less operations, so that the target testing information can be quickly provided for a user, the testing cost can be reduced, and the testing efficiency can be improved.

Description

Data processing method, device and machine readable medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to a data processing method, apparatus, and machine-readable medium.

Background

With the development of internet technology, the scale of business systems such as service platforms, trading platforms, etc. depending on networks is gradually enlarged. Most of the current service systems adopt a distributed system, and the distributed system usually includes a plurality of service subsystems, and the types of the service subsystems may include: applications, middleware, databases, caches, etc. The communication mode between the service subsystems may specifically include: an RPC (Remote Procedure Call) mode and an asynchronous message mode. Wherein, RPC calls can generate nesting of one layer and one layer, and one message is issued and can be consumed by a plurality of applications.

In practical applications, in the process from the beginning of a user request to the end of the user request, multiple call relationships between service subsystems in a service system are generally required to be triggered. Which calling relationships among the multiple calling relationships will affect the processing performance of the user request, which will help to optimize the performance of the business system.

At present, a code test mode can be adopted to determine the call relationship between service subsystems in a service system. However, the code testing method usually requires a lot of testing cost and usually requires a certain technical threshold, thereby increasing the testing difficulty.

Disclosure of Invention

In view of the foregoing problems, an embodiment of the present application provides a data processing method, a data processing apparatus and a data processing apparatus to solve the problems in the related art.

In order to solve the above problem, an embodiment of the present application discloses a data processing method, including:

determining target calling information of at least one second service subsystem in the processing process of a user request by a first service subsystem according to a log of the first service subsystem;

and displaying the target calling information.

In order to solve the above problem, an embodiment of the present application further discloses a data processing apparatus, including:

the system comprises a target calling information determining module, a target calling information determining module and a target calling information determining module, wherein the target calling information determining module is used for determining target calling information of at least one second service subsystem in the processing process of a user request of a first service subsystem according to a log of the first service subsystem; and

and the target calling information display module is used for displaying the target calling information.

To solve the above problem, an embodiment of the present application further discloses an apparatus, which includes a memory, and one or more programs, where the one or more programs are stored in the memory, and configured to be executed by the one or more processors, and the one or more programs include instructions for:

and displaying the target calling information.

To address the above issues, one or more machine-readable media having instructions stored thereon, which when executed by one or more processors, cause an apparatus to perform one or more of the methods described above.

As can be seen from the foregoing, the data processing method, apparatus and machine-readable medium provided in the embodiments of the present application have at least the following advantages:

the embodiment of the application aims at a first service subsystem, determines target calling information of the first service subsystem to at least one second service subsystem in the processing process of a user request according to a log of the first service subsystem, and displays the target calling information. The target calling information can reflect the calling condition of the first service subsystem to the second service subsystem, namely the interaction condition between the first service subsystem and the external service subsystem, so that the displayed target calling information can be viewed and utilized by a user, and can be helpful for positioning the abnormality of the first service subsystem.

Moreover, the target calling information can be obtained according to the log of the first service subsystem, and the process of obtaining the target calling information according to the log of the first service subsystem can involve less operations, so that the target testing information can be quickly provided for a user, the testing cost can be reduced, and the testing efficiency can be improved.

In addition, the target calling information is visual, so that the technical threshold of a user can be reduced. The user of the embodiment of the application can comprise: developers, testers, even people unfamiliar with code, etc.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a block diagram of a data processing system according to an embodiment of the present application;

FIG. 2 is a flow chart of the steps of an embodiment of a data processing method of the present application;

FIG. 3 is an illustration of a test scenario in an embodiment of the present application;

FIG. 4 is an illustration of a browser request triggered invocation between service subsystems in an embodiment of the present application;

FIG. 5 is a block diagram of an embodiment of a data processing apparatus of the present application; and

fig. 6 is a schematic structural diagram of an apparatus according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

While the concepts of the present application are susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the description above is not intended to limit the application to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the application.

Reference in the specification to "one embodiment," "an embodiment," "a particular embodiment," or the like, means that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, where a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. In addition, it should be understood that items in the list included in the form "at least one of a, B, and C" may include the following possible items: (A) (ii) a (B) (ii) a (C) (ii) a (A and B); (A and C); (B and C); or (A, B and C). Likewise, a listing of items in the form of "at least one of a, B, or C" may mean (a); (B) (ii) a (C) (ii) a (A and B); (A and C); (B and C); or (A, B and C).

In some cases, the disclosed embodiments may be implemented as hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage media, which may be executed by one or more processors. A machine-readable storage medium may be implemented as a storage device, mechanism, or other physical structure (e.g., a volatile or non-volatile memory, a media disk, or other media other physical structure device) for storing or transmitting information in a form readable by a machine.

In the drawings, some structural or methodical features may be shown in a particular arrangement and/or ordering. Preferably, however, such specific arrangement and/or ordering is not necessary. Rather, in some embodiments, such features may be arranged in different ways and/or orders than as shown in the figures. Moreover, the inclusion of structural or methodical features in particular figures is not meant to imply that such features are required in all embodiments and that, in some embodiments, such features may not be included or may be combined with other features.

The embodiment of the application provides a data processing method, which specifically comprises the following steps: determining target calling information of at least one second service subsystem in the processing process of a user request by a first service subsystem according to a log of the first service subsystem; and displaying the target calling information.

In the embodiment of the present application, the service subsystem may refer to a functional system of the service system. The business system may include: service platforms, trading platforms, and the like. Types of service subsystems may include, but are not limited to: applications, middleware, databases, caches, storage, etc. Examples of applications may include: distributed service frameworks, user services, network services, and the like. The middleware may include: message middleware, and the like. It is to be understood that the embodiments of the present application are not limited to specific service subsystems.

The embodiment of the application can determine the target calling information of the first service subsystem to at least one second service subsystem in the processing process of the user request according to the log of the first service subsystem, and display the target calling information. Wherein the second service subsystem may be a service subsystem other than the first service subsystem; the target calling information can reflect the calling condition of the first service subsystem to the second service subsystem, namely the interaction condition between the first service subsystem and the external service subsystem, so that the displayed target calling information can be viewed and utilized by a user, and can be helpful for positioning the abnormality of the first service subsystem.

According to the method and the device for displaying the target calling information between the first service subsystem and the external second service subsystem, a user can quickly and conveniently check the interactive information between one service subsystem and the external service subsystem, and therefore the method and the device for displaying the target calling information between the first service subsystem and the external second service subsystem can provide convenient testing and debugging functions for page development and testing of the first service subsystem.

Referring to fig. 1, a schematic structural diagram of a data processing system according to an embodiment of the present application is shown, which may specifically include: a log device 101 and a data processing device 102. The log device 101 and the data processing device 102 may perform data interaction through a wireless network or a wired network.

Wherein the logging means 101 is configured to log for the first service subsystem. Alternatively, the log apparatus 101 may set a buried point for the first service subsystem, and in a case where the first service subsystem calls an external second service subsystem based on a user request, may collect call data related to the first service subsystem through the buried point, and record the call data and the runtime data of the first service subsystem to the log. Alternatively, the buried point may be a piece of code executed at a set point in time during execution of the first service subsystem.

Optionally, the call data may include: user request information, current system time, IP (Internet Protocol) address and port of the first service subsystem, and IP address and port of the called second service subsystem. Optionally, the call data may include: call parameters and/or call results. The calling parameter may be a parameter transferred to the second service subsystem by the first service subsystem in a process of calling the second service subsystem, and the calling result may refer to a result returned to the first service subsystem by the second service subsystem according to the calling parameter.

The runtime data may specifically include one of the following: the whole running time of the first service subsystem, the running time of the setting stage of the first service subsystem and the like. The setting stage can be determined by those skilled in the art according to the actual application requirements, and the specific setting stage is not limited in the embodiments of the present application.

The log device 101 may run on a server of the first service subsystem, and of course, the specific location of the log device 101 is not limited in this embodiment of the application.

The data processing device 102 may obtain a log of the first service subsystem from the log device 101, and determine, according to the log of the first service subsystem, target invocation information of the first service subsystem to at least one second service subsystem in a processing process of a user request; and displaying the target calling information.

According to an embodiment, the log means 101 may send the log to the data processing means 102 after the first service subsystem has performed the call to all the second service subsystems. According to another embodiment, the logging means 101 may send the log to the data processing means 102 after the first service subsystem has performed a call to a second service subsystem. It is to be understood that the embodiment of the present application is not limited to the specific manner in which the log device 101 sends the log to the data processing device 102.

The data processing apparatus 101 may be located above the test equipment. The data processing apparatus 101 may present the target call information on a page. Alternatively, the page may be a page of a browser. It can be understood that the embodiment of the present application does not impose a limitation on the specific display manner of the target call information.

Method embodiment

Referring to fig. 2, a flowchart illustrating steps of an embodiment of a data processing method according to the present application is shown, which may specifically include the following steps:

step 201, determining target calling information of a first service subsystem to at least one second service subsystem in a user request processing process according to a log of the first service subsystem;

and step 202, displaying the target calling information.

Steps 201 to 202 included in the method of the embodiment of the present application may be performed by a test apparatus. Of course, the specific implementation subject corresponding to the method of the embodiment of the present application is not limited.

In practical applications, the testing device may be a PC (personal computer), a smart phone, a tablet computer, or the like.

Referring to fig. 3, an illustration of a test scenario of an embodiment of the present application is shown, where a user equipment 301 may send a user request to a service system 302. For example, the user device 301 may receive a user request triggered by a tester and send the user request to the business system 302.

The service system 302 may include n service subsystems, where n is a natural number; the processing procedure of the user request can relate to the calling relation among a plurality of service subsystems, and a server of the service subsystem i (1 is less than or equal to i and less than or equal to n) is used for recording calling data of the service subsystems except the service subsystem i.

The test device 303 corresponds to one service subsystem, and assuming that the service subsystem corresponding to the test device 303 is a service subsystem j (j is greater than or equal to 1 and less than or equal to n), the test device 303 may obtain a log of the service subsystem j from a server of the service subsystem j, determine target calling information of the service subsystem j for at least one second service subsystem in a processing process of a user request according to the log of the service subsystem j, and display the target calling information.

In an alternative embodiment of the present application, the above method may be performed by a plug-in of a browser. And the plug-in of the browser is used for realizing the test function corresponding to the service subsystem j. And the plug-in can be dynamically loaded into the browser. The plug-in has the characteristic of dynamic loading, and can be dynamically loaded as required, for example, the plug-in can be dynamically loaded according to a trigger instruction of a user for the plug-in; the influence on the starting speed of the browser can be reduced. Of course, the above method is executed by a plug-in of the browser, only as an alternative embodiment, and actually, the above method may also be executed by a main program of the browser.

In step 201, the log of the first service subsystem may record related data of the first service subsystem. Optionally, the logged data may include: and under the condition that the first service subsystem calls the second service subsystem based on the user request, calling data collected through the buried point of the first service subsystem.

Of course, the logged data may include other data, such as runtime data of the first business subsystem, in addition to the call data described above.

Step 201 determines that the target invocation information of the first service subsystem to at least one second service subsystem in the processing process of the user request may specifically include: and extracting preset type information from the log of the first service subsystem as target calling information.

In an optional embodiment of the present application, the target call information may include:

information of a second service subsystem called by the first service subsystem; and/or

The order of the plurality of second service subsystems invoked by the first service subsystem.

The information of the second service subsystem may include, but is not limited to: name, type, service name, etc. The information of the second service subsystem may enable the user to know the condition of the second service subsystem.

The first service subsystem may correspond to a call time when the second service subsystem is called. The second service subsystems may be sequenced according to the sequence of the call time to obtain the sequence of the second service subsystems called by the first service subsystem.

The information and the sequence of the second service subsystem are beneficial to positioning the abnormity of the first service subsystem, and the performance of the service system can be optimized.

In an optional embodiment of the present application, the step 203 of displaying the target invocation information may specifically include: and sequentially displaying the information of the plurality of second service subsystems called by the first service subsystem according to the calling time sequence.

Referring to table 1, a schematic diagram of displaying target invocation information in the embodiment of the present application is shown, where target invocation information of a first service subsystem for at least one second service subsystem may be displayed for a certain user request; according to the sequence of the calling time from first to last, the second service subsystem called by the first service subsystem may sequentially include: the system comprises a service subsystem A, a service subsystem B, a service subsystem C and a service subsystem D. Specifically, the target call information may be presented according to the following fields: name, type, and service name of the business subsystem.

TABLE 1

It can be understood that the display manner shown in table 1 is only an example, and actually, a person skilled in the art may determine other display manners of the target call information according to the actual application requirement, for example, the display manner shown in table 2 may also be adopted, and for example, the call time corresponding to the second service subsystem may also be displayed.

TABLE 2

In another optional embodiment of the present application, the target call information may include:

the first service subsystem sends a calling parameter to the second service subsystem; and/or

And the first service subsystem receives the calling result from the second service subsystem.

The calling parameter can be a parameter transmitted to the second service subsystem by the first service subsystem in the process of calling the second service subsystem; the call result may refer to a result returned by the second service subsystem to the first service subsystem according to the call parameter. The calling parameters and calling results are helpful for positioning the abnormity of the first service subsystem, and the performance of the service system can be optimized.

Referring to table 3, a schematic diagram of presenting the target call information in the embodiment of the present application is shown, where the target call information may be presented according to the following fields: name, type, service name, calling parameters and calling results of the service subsystem.

TABLE 3

In an optional embodiment of the present application, the method may further include: displaying a test interface corresponding to the calling relation; the calling relationship may be a calling relationship between the first service subsystem and a second service subsystem called by the first service subsystem.

Referring to table 4, an illustration of presenting the target call information in the embodiment of the present application is shown, where the presentation of the target call information may be performed according to the following fields: name, type, service name and test interface of the service subsystem.

TABLE 4

Name of service subsystem	Type (B)	Service name	Test interface
				First service subsystem	Testing	Service S
Service subsystem A	Type 1	Service A	Test interface A
				Service subsystem B	Type 2	Service B	Test interface B
Service subsystem C	Type 3	Service C	Test interface C
				Service subsystem D	Type 4	Service D	Test interface D

The test interface is used for triggering a test corresponding to the calling relationship, namely for triggering a test of the first service subsystem to the corresponding second service subsystem. For example, the test interface a is used to trigger a test of a call relationship of the first service subsystem to the service subsystem a, that is, the first service subsystem may call the service subsystem a, and a corresponding test result may be returned.

In an optional embodiment of the present application, the test interface may include: MOCK (analog) test interface. And the MOCK (simulation) test interface is used for triggering the MOCK test corresponding to the calling relation.

The Mock test is a test method which is created by using a virtual object for some objects which are not easy to construct or easily obtained in the test process so as to be tested. By using the Mock test, the coupling of the front end and the rear end can be reduced in the application development process, so that front-end personnel do not need to wait for the data provided by the rear end and then debug, and the separation of the front end and the rear end and the parallel development of the front end and the rear end are realized.

For a person skilled in the art to better understand the embodiment of the present application, referring to fig. 4, an illustration of a call between service subsystems triggered by a browser request is shown, where the service subsystems may include: application A, user B, application C, application D, application F, application G, message server, and database. In fig. 4, the browser request may reach application a and trigger a call between the business subsystems, and arrow → may indicate the direction of the call, e.g., "application a → application B" indicates application a calls application B.

According to the embodiment of the application, the first layer calling link for calling the external system by the first service subsystem is collected and calculated in real time or at low calculation cost through data acquisition and calculation of one server of the first service subsystem to be tested, and the collected and calculated first layer calling link is output to the browser in a convenient plug-in mode, so that the calling relation of the breadth can be displayed at low cost and high efficiency, and the requirements of daily development and high-frequency testing and debugging of the test can be met.

In the case that attention needs to be paid to one service subsystem, the embodiment of the present application may use the service subsystem as a first service subsystem, determine a first layer call relationship corresponding to the first service subsystem according to a log of the first service subsystem, and display target call information corresponding to the first layer call relationship.

In the case that the first service subsystem is an application a, the first layer invocation relationship corresponding to the application a may sequentially include: therefore, in the embodiment of the present application, the information of the application B, the application C, and the message server may be sequentially displayed, and at least one of a call parameter, a call result, and a test interface corresponding to the called second service subsystem may also be displayed.

When the first service subsystem is application B, the first layer invocation relationship corresponding to application B may sequentially include: therefore, in the embodiment of the present application, the information of the application F and the information of the application G may be sequentially displayed, and at least one of a call parameter, a call result, and a test interface corresponding to the called second service subsystem may also be displayed.

In the case that the first service subsystem is application C, the first layer invocation relationship corresponding to application C may sequentially include: therefore, the application G in the embodiment of the present application may show information of the application G, and may also show at least one of a call parameter, a call result, and a test interface corresponding to the called application G.

When the first service subsystem is an application D, the first layer invocation relationship corresponding to the application D may sequentially include: therefore, the application G in the embodiment of the present application may show information of the application G, and may also show at least one of a call parameter, a call result, and a test interface corresponding to the called application G.

In the case that the first service subsystem is a message server, the first layer invocation relationship corresponding to the message server may sequentially include: therefore, in the embodiment of the present application, the information of the application C and the information of the application D may be sequentially displayed, and at least one of a call parameter, a call result, and a test interface corresponding to the called application C and the called application D may also be displayed.

When the first service subsystem is an application F, the first-layer call relationships corresponding to the application F may sequentially include: therefore, the embodiment of the application can display the information of the database and also can display at least one of the calling parameter, the calling result and the test interface corresponding to the called database.

When the first service subsystem is an application G, the first layer invocation relationship corresponding to the application G may sequentially include: therefore, the embodiment of the application can display the information of the database and also can display at least one of the calling parameter, the calling result and the test interface corresponding to the called database.

The embodiment of the application can be realized through a plug-in of a browser, and the plug-in can interact with a server of the first service subsystem through a preset interface so as to obtain a log of the first service subsystem through the preset interface; and the plug-in can calculate the data of the log of the first service subsystem to obtain the target calling information, and display the target calling information in the page of the browser. The target calling information displayed in the page of the browser enables a user to clearly see the calling sequence of the first service subsystem to the second service subsystem and input and output data, wherein the input data can comprise calling parameters, and the output data can comprise calling results. According to the embodiment of the application, the test can be performed based on the data of the log of the service subsystem, so that the target calling information serving as the test result can be displayed under the conditions of low test cost and high test efficiency, and the requirements of high-frequency white-box analysis and debugging in daily development and test can be met.

It should be noted that, a page of the browser may correspond to a page address, and the page of the browser may include: and page content corresponding to the page address. In the case where no user request is received, the page of the browser may include only: page content corresponding to the page address; and in case of receiving the kth (k is a natural number) user request, the page of the browser may include: the page content corresponding to the page address and the target calling information corresponding to the kth user request can be located on the upper portion of the page, and the target calling information corresponding to the kth user request can be located on the lower portion of the page. And when k is larger than 1, the target calling information can be sequentially displayed according to the sequence of the user requests, that is, the target calling information corresponding to the 1 st user request is positioned on the upper part of the target calling information corresponding to the 2 nd user request.

In addition, it should be noted that, in the embodiments of the present application, different plug-ins may be provided for the user to select and use, and one plug-in may correspond to one service subsystem.

To sum up, the data processing method according to the embodiment of the present application determines, for a first service subsystem, target invocation information for at least one second service subsystem in a processing process of a user request according to a log of the first service subsystem, and displays the target invocation information. The target calling information can reflect the calling condition of the first service subsystem to the second service subsystem, namely the interaction condition between the first service subsystem and the external service subsystem, so that the displayed target calling information can be viewed and utilized by a user, and can be helpful for positioning the abnormality of the first service subsystem.

It is noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the described order of acts, as some blocks may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.

The embodiment of the application also provides a data processing device.

Referring to fig. 5, a block diagram of a data processing apparatus according to an embodiment of the present application is shown, which may specifically include the following modules:

a target call information determining module 501, configured to determine, according to a log of a first service subsystem, target call information of the first service subsystem to at least one second service subsystem in a processing process of a user request; and

and a target calling information display module 502, configured to display the target calling information.

Optionally, the target call information may include:

Optionally, the apparatus is applied to a plug-in of a browser, that is, the module of the apparatus may be a module of the plug-in. Of course, the above device is applied to a plug-in of a browser, which is only an alternative embodiment, and actually, the module of the above device may also be a main program module of a browser.

Optionally, the apparatus may further include:

the test interface display module is used for displaying the test interface corresponding to the calling relationship; the calling relation is the calling relation between the first service subsystem and the second service subsystem called by the first service subsystem.

Optionally, the test interface may include: and the MOCK simulates a test interface.

Optionally, the logged data may include: and under the condition that the first service subsystem calls the second service subsystem based on the user request, calling data collected through the buried point of the first service subsystem.

To sum up, the data processing apparatus according to the embodiment of the present application determines, for a first service subsystem, target invocation information for at least one second service subsystem in a processing process of a user request according to a log of the first service subsystem, and displays the target invocation information. The target calling information can reflect the calling condition of the first service subsystem to the second service subsystem, namely the interaction condition between the first service subsystem and the external service subsystem, so that the displayed target calling information can be viewed and utilized by a user, and can be helpful for positioning the abnormality of the first service subsystem.

For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and the similar parts should be referred to each other.

An apparatus is also provided in an embodiment of the present application, comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors comprises instructions for:

and displaying the target calling information.

Optionally, the target call information may include:

Optionally, the program may include: a plug-in for a browser. The browser can comprise a main program, and the main program can load the plug-in program; or the plug-in may be installed and executed.

Optionally, the device is also configured to execute the one or more programs by the one or more processors including instructions for:

displaying a test interface corresponding to the calling relation; the calling relation is the calling relation between the first service subsystem and the second service subsystem called by the first service subsystem.

Embodiments of the application can be implemented as a system or apparatus employing any suitable hardware and/or software for the desired configuration. Fig. 6 schematically illustrates an example apparatus 1100 that may be used to implement various embodiments described herein.

For one embodiment, fig. 6 illustrates an example apparatus 1100, which apparatus 1100 may comprise: one or more processors 1102, a system control module (chipset) 1104 coupled to at least one of the processors 1102, a system memory 1106 coupled to the system control module 1104, a non-volatile memory (NVM)/storage 1108 coupled to the system control module 1104, one or more input/output devices 1110 coupled to the system control module 1104, and a network interface 1112 coupled to the system control module 1106. The system memory 1106 may include: instructions 1162, the instructions 1162 being executable by the one or more processors 1102.

The processor 1102 may include one or more single-core or multi-core processors, and the processor 1102 may include any combination of general-purpose or special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, the apparatus 1100 is capable of operating as a server, a target device, a wireless device, etc., as described in embodiments herein.

In some embodiments, the apparatus 1100 may include one or more machine-readable media (e.g., system memory 1106 or NVM/storage 1108) having instructions and one or more processors 1102 configured to execute the instructions, in conjunction with the one or more machine-readable media, to implement the modules included in the aforementioned apparatus to perform the actions described in embodiments of the present application.

System control module 1104 for one embodiment may include any suitable interface controller to provide any suitable interface to at least one of processors 1102 and/or any suitable device or component in communication with system control module 1104.

System control module 1104 for one embodiment may include one or more memory controllers to provide an interface to system memory 1106. The memory controller may be a hardware module, a software module, and/or a firmware module.

System memory 1106 for one embodiment may be used to load and store data and/or instructions 1162. For one embodiment, system memory 1106 may include any suitable volatile memory, such as suitable DRAM (dynamic random access memory). In some embodiments, system memory 1106 may include: double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).

System control module 1104 for one embodiment may include one or more input/output controllers to provide an interface to NVM/storage 1108 and input/output device(s) 1110.

NVM/storage 1108 for one embodiment may be used to store data and/or instructions 1182. NVM/storage 1108 may include any suitable non-volatile memory (e.g., flash memory, etc.) and/or may include any suitable non-volatile storage device(s), e.g., one or more Hard Disk Drives (HDDs), one or more Compact Disc (CD) drives, and/or one or more Digital Versatile Disc (DVD) drives, etc.

NVM/storage 1108 may include storage resources that are physically part of the device on which device 1100 is installed or may be accessible by the device and not necessarily part of the device. For example, NVM/storage 1108 may be accessed over a network via network interface 1112 and/or through input/output devices 1110.

Input/output device(s) 1110 for one embodiment may provide an interface for apparatus 1100 to communicate with any other suitable device, input/output devices 1110 may include communication components, audio components, sensor components, and so forth.

Network interface 1112 of one embodiment may provide an interface for device 1100 to communicate over one or more networks and/or with any other suitable device, and device 1100 may communicate wirelessly with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols, such as to access a communication standard-based wireless network, such as WiFi, 2G, or 3G, or a combination thereof.

For one embodiment, at least one of the processors 1102 may be packaged together with logic for one or more controllers (e.g., memory controllers) of the system control module 1104. For one embodiment, at least one of the processors 1102 may be packaged together with logic for one or more controllers of the system control module 1104 to form a System In Package (SiP). For one embodiment, at least one of the processors 1102 may be integrated on the same novelty as the logic of one or more controllers of the system control module 1104. For one embodiment, at least one of the processors 1102 may be integrated on the same chip with logic for one or more controllers of the system control module 1104 to form a system on a chip (SoC).

In various embodiments, the apparatus 1100 may include, but is not limited to: a computing device such as a desktop computing device or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.). In various embodiments, the apparatus 1100 may have more or fewer components and/or different architectures. For example, in some embodiments, device 1100 may include one or more cameras, keyboards, Liquid Crystal Display (LCD) screens (including touch screen displays), non-volatile memory ports, multiple antennas, graphics chips, Application Specific Integrated Circuits (ASICs), and speakers.

Wherein, if the display includes a touch panel, the display screen may be implemented as a touch screen display to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The present application also provides a non-transitory readable storage medium, where one or more modules (programs) are stored in the storage medium, and when the one or more modules are applied to an apparatus, the apparatus may be caused to execute instructions (instructions) of methods in the present application.

Provided in one example is an apparatus comprising: one or more processors; and, instructions in one or more machine-readable media stored thereon, which when executed by the one or more processors, cause the apparatus to perform a method as in embodiments of the present application, which may include: the method shown in fig. 2 or fig. 3 or fig. 4.

One or more machine-readable media are also provided in one example, having instructions stored thereon, which when executed by one or more processors, cause an apparatus to perform a method as in embodiments of the application, which may include: the method shown in fig. 2 or fig. 3 or fig. 4.

The data processing method, the data processing apparatus and the apparatus provided by the present application are introduced in detail above, and specific examples are applied herein to illustrate the principles and embodiments of the present application, and the descriptions of the above embodiments are only used to help understand the method and the core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A data processing method, comprising:

and displaying the target calling information.

2. The method of claim 1, wherein the target call information comprises:

3. The method of claim 1, wherein the target call information comprises:

4. The method of claim 1, wherein the method is performed by a plug-in to a browser.

5. The method according to any one of claims 1 to 4, further comprising:

6. The method of claim 5, wherein the test interface comprises: and the MOCK simulates a test interface.

7. The method of any of claims 1 to 4, wherein the logged data comprises: and under the condition that the first service subsystem calls the second service subsystem based on the user request, calling data collected through the buried point of the first service subsystem.

8. A data processing apparatus, comprising:

9. The apparatus of claim 8, wherein the target call information comprises:

10. The apparatus of claim 8, wherein the target call information comprises:

11. The apparatus of claim 8, wherein the apparatus is applied to a plug-in execution of a browser.

12. An apparatus comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors the one or more programs including instructions for:

and displaying the target calling information.

13. The apparatus of claim 12, wherein the target call information comprises:

14. The apparatus of claim 12, wherein the target call information comprises:

15. The apparatus of claim 12, wherein the program comprises: a plug-in for a browser.

16. The apparatus of any of claims 12-15, wherein the apparatus is also configured to execute the one or more programs by one or more processors includes instructions for:

17. The apparatus of claim 16, wherein the test interface comprises: and the MOCK simulates a test interface.

18. The apparatus of any of claims 12 to 15, wherein the logged data comprises: and under the condition that the first service subsystem calls the second service subsystem based on the user request, calling data collected through the buried point of the first service subsystem.

19. One or more machine-readable media having instructions stored thereon, which when executed by one or more processors, cause an apparatus to perform the method recited by one or more of claims 1-7.