CN115248735A

CN115248735A - Log data output control method, device, equipment and storage medium

Info

Publication number: CN115248735A
Application number: CN202210836087.0A
Authority: CN
Inventors: 林波
Original assignee: Hangzhou Tuya Information Technology Co Ltd
Current assignee: Hangzhou Tuya Information Technology Co Ltd
Priority date: 2022-07-15
Filing date: 2022-07-15
Publication date: 2022-10-28

Abstract

The invention discloses a log data output control method, a device, equipment and a storage medium. The method comprises the following steps: sending the calling method of the target RN component to a primary container layer through a front-end service layer; sending the calling method to a native plug-in layer through the native container layer for calling the target RN component; outputting, by the native container layer, log data associated with the target RN component based on the log burial point information. The technical scheme of the embodiment of the invention can ensure the integrity of the log data associated with the RN assembly and improve the problem positioning efficiency.

Description

Log data output control method, device, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a log data output control method, apparatus, device, and storage medium.

Background

ReactNative is one of the currently popular cross-platform mobile application development frameworks, referred to as RN for short. When the RN is used for application development, data interaction between a front end and an application native end is often involved, and the guarantee of the accuracy of the part of data is very important for the normal operation of the application.

In order to facilitate problem location when a problem occurs in data interaction between the front end and the application native end, a developer usually adds a large amount of log data output methods in an application program, and the log data output methods depend on the understanding of the developer on the application program, so that some key log data are easy to miss. When the application runs and has a problem, log data needs to be exported first, data checking is carried out in the log data, accuracy of data transmission of the front end and the application native end is difficult to judge visually, and problem positioning efficiency is low.

Disclosure of Invention

The invention provides a log data output control method, a log data output control device, log data output control equipment and a log data output control storage medium, and aims to solve the problems of log data omission and low problem positioning efficiency.

According to an aspect of the present invention, there is provided a log data output method, the method including:

sending the calling method of the target RN component to a primary container layer through a front-end service layer;

sending the calling method to a native plug-in layer through the native container layer for calling the target RN component;

outputting, by the native container layer, log data associated with the target RN component based on the log burial point information.

According to another aspect of the present invention, there is provided a log data output apparatus including:

the first calling method sending module is used for sending the calling method of the target RN component to the native container layer through the front-end business layer;

a second calling method sending module, configured to send the calling method to a native plug-in layer through the native container layer, and configured to call the target RN component;

a log data output module, configured to output, by the native container layer, log data associated with the target RN component based on the log burial point information.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the log data output method according to any of the embodiments of the present invention.

According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement the log data output method according to any one of the embodiments of the present invention when the computer instructions are executed.

According to the technical scheme, the calling method of the target RN component is sent to the primary container layer through the front-end service layer, the calling method is further sent to the primary plug-in layer through the primary container layer and is used for calling the target RN component, finally, log data associated with the target RN component is output through the primary container layer based on the log embedded point information, and the log data is output on the primary container layer, so that the problem that log data are easy to miss due to the fact that a developer is dependent on embedding points on the front-end service layer or the primary plug-in layer is solved, log data are only output by the primary container layer according to interaction between the front-end service layer and the primary plug-in layer, other disordered logs are eliminated, and the problem positioning efficiency when the interaction occurs is improved.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1a is a flowchart of a log data output method according to an embodiment of the present invention;

FIG. 1b is a diagram of a cross-platform mobile application development system architecture suitable for use in accordance with an embodiment of the present invention;

FIG. 2a is a flowchart of a log data output method according to a second embodiment of the present invention;

FIG. 2b is a flowchart of problem location according to the second embodiment of the present invention;

FIG. 2c is a flowchart for problem location according to the second embodiment of the present invention;

FIG. 3 is a flowchart of a log data output method according to a third embodiment of the present invention;

fig. 4 is a schematic structural diagram of a log data output apparatus according to a fourth embodiment of the present invention;

fig. 5 is a schematic structural diagram of an electronic device implementing the log data output method according to the embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in other sequences than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example one

Fig. 1a is a flowchart of a log data output method according to an embodiment of the present invention, where the present embodiment is applicable to an RN log output situation at a native container layer, and the method may be applied to a cross-platform mobile application development system.

FIG. 1b is an architecture diagram of a cross-platform mobile application development system, including a front-end business layer T1, a native container layer T2, and a native plug-in layer T3. The front-end service layer T1 includes a plurality of service modules for implementing corresponding functions, for example, a service module B1, a service module B2, and the like. The native plug-in layer T3 includes a plurality of plug-in modules, for example, including a plug-in module P1, a plug-in module P2, and the like, and each plug-in module includes a plurality of RN components for providing different functions. In the process of implementing the corresponding function of each service module, the front-end service layer T1 needs to call the RN component in the native plug-in layer T3 through the native container layer T2. The native container layer T2 is configured to, after receiving the method for the front-end application layer T1 to invoke the target RN component, forward the method to a plug-in module in the native plug-in layer T3 that includes the target RN component, so as to complete the invocation of the RN component.

The log data output method according to the present embodiment may be performed by a log data output apparatus, which may be implemented in hardware and/or software, and may be configured in various general-purpose computing devices. As shown in fig. 1a, the method comprises:

and S110, sending the calling method of the target RN component to a native container layer through a front-end business layer.

In the embodiment of the invention, in order to realize the specific function in the front-end service layer, the target RN component in the native plug-in layer needs to be called through the front-end service layer. Specifically, the calling method of the target RN component needs to be sent to the native container layer, so as to instruct the native container layer to forward the calling method to the native plug-in layer to call the target RN component. The calling method of the target RN component needs to include information such as an identifier of the target RN component and an identifier of a plug-in module to which the target RN component belongs.

In a specific example, the front-end service layer includes service modules B1 and B2, where the service module B1 needs to call a target RN component in the process of implementing its corresponding function, and the target RN component is provided by a plug-in module P1 in the native plug-in layer. And sending the calling method of the target RN component to the native container layer through the service module B1 in the front-end service layer, and indicating the native container layer to determine a target plug-in module containing the target RN component in the native plug-in layer, namely the plug-in module P1, according to the calling method, and forwarding the calling method to the target plug-in module in the native plug-in layer.

And S120, sending the calling method to a native plug-in layer through a native container layer, and calling the target RN component.

In the embodiment of the invention, after the native container layer receives the calling method sent by the front-end service layer, the calling method needs to be forwarded to the native plug-in layer to call the template RN component. Specifically, after receiving the calling method of the target RN component, the native container layer parses the calling method to obtain a calling method associated with the target RN component and a target plugin module to which the target RN component belongs, and finally forwards the calling method to the target plugin module in the native plugin layer, where the calling method is used to instruct the target plugin module to execute the target RN component included in the target RN module.

In a specific example, after receiving a calling method sent by a front-end service layer, a native container layer parses the calling method, and obtains an identifier a of a target RN component that the calling method needs to call, and an identifier P1 of a target plug-in module to which the RN component belongs. The native container layer needs to forward the calling method to the plug-in module P1 in the native plug-in layer for instructing the plug-in module P1 to execute the logic of the target RN component.

And S130, outputting log data associated with the target RN component based on the log buried point information through the native container layer.

The log buried point information is used as a basis for log output and is used for providing information such as the position of the output log, events of the output log, the format of the output log and the like. For example, the output format of the log data, for example, jason format output, may be preset in the log burial point information.

If the point is directly embedded in the front-end service layer or the native plug-in layer according to the understanding of the developer on the service, the problem of log omission easily occurs. For example, in the front-end service layer, the developer considers that the service module B1 is a key module and the service module B2 is a non-key module, so that log embedding is performed on a plurality of events in the service module B1, and embedding is not performed in the service module B2, which easily causes log omission, and if a problem occurs in data interaction between the subsequent service module B2 and the native plug-in layer, the problem cannot be accurately located according to log data.

In the embodiment of the invention, in order to avoid the problem of log omission, the log embedding is directly carried out on the native container layer, and after the native container layer receives the calling method sent by the front-end service layer, the calling method is forwarded to the corresponding plug-in module in the native plug-in layer, the log data is printed at the same time, and the printed log data is written into the database. On the one hand, the front-end service layer and the native plug-in layer can perform data interaction through the native container layer, log data printing is performed on the native container layer, and omission of interaction logs can be avoided. On the other hand, the interactive log of the front-end service layer and the native plug-in layer can be written into a designated database and isolated from log data in other services, so that the uniqueness of the log data can be ensured, and the rapid positioning can be conveniently carried out through the log data when the subsequent interactive problem occurs.

In addition, an output format of the log data can be preset in the native container layer, the log data interacted between the front-end service layer and the native plug-in layer are output in the native container layer in a uniform format, and the uniform format of the log data and the integrity of the log data can be ensured. Illustratively, the log data is output uniformly in a Jason format.

Example two

Fig. 2a is a flowchart of a log data output method according to a second embodiment of the present invention, which is further detailed on the basis of the above embodiment, and provides a specific step of outputting, by a native container layer, log data associated with a target RN component based on the buried point information of the log, and a specific step after outputting the log data associated with the target RN component. As shown in fig. 2a, the method comprises:

s210, sending the calling method of the target RN component to a native container layer through a front-end business layer.

And S220, sending the calling method to a native plug-in layer through a native container layer for calling the target RN component.

And S230, outputting log data associated with the target RN component based on a log format in the log buried point information through the native container layer.

In the embodiment of the invention, after receiving the calling method sent by the front-end service layer, the native container layer needs to forward the method to the corresponding plug-in module in the native container layer, and simultaneously, the log data of the calling target RN component needs to be output according to the log format specified in the log embedded point information, so that the log data associated with the RN component can be ensured to be output in a uniform format, and data searching and problem positioning are facilitated. Illustratively, the preset log format in the log buried point information is Jason format.

S240, broadcasting the log data through the native container layer, and storing the log data into a log database by the indication interface construction module.

When the program operation is in a problem in the prior art, the processing procedure is shown in fig. 2 b. Firstly, a log file needs to be uploaded aiming at the operation problem, a developer can download the log file, and after the log file is downloaded, log screening is carried out in a large number of log files according to the problems, so that log analysis is carried out aiming at the screened logs, and finally the problems are positioned and solved according to the log analysis result. The problem positioning process needs to download log files and screen logs related to problems in a large batch of logs, so that the workload is high, and the problem positioning efficiency is low.

In the embodiment of the invention, in order to facilitate log data viewing and problem positioning, the cross-platform mobile application development system further provides an interface construction module for constructing a log display interface based on log data output by the native container layer, so as to realize visualization of the log data.

In the embodiment of the invention, the native container layer also broadcasts log data after outputting the log according to the preset log format. After receiving the broadcast sent by the native container layer, the interface construction module stores the log data into a log database, so that the log data can be read in time when problems occur subsequently. The log database is a proprietary database used for storing the log data output by the native container layer, that is, the log data stored in the log database is all the log data associated with the RN component. When the interaction between the front-end service layer and the native plug-in layer has a problem, the log database can be used for searching related log data, and the problem positioning efficiency is improved.

And S250, responding to the access of the log data display interface entry through the interface construction module, reading log data from the log database, and constructing a log data display interface based on the log data.

In an embodiment of the present invention, the interface construction module provides a log data display interface entry, which may be in the form of a network link. When the log data display interface inlet is accessed, the interface construction module reads related log data from the log database and constructs a log data display interface based on the log data. Developers or other operation and maintenance personnel can obtain the visual log data display interface by accessing the log data display interface inlet, so that obscure and unintelligible log data can be displayed in a shallow and understandable mode.

Certainly, in order to further facilitate the positioning of the developer, the log data display interface can also provide functions of log screening, data searching and the like, so that the efficiency of screening available information in a large amount of log data is improved.

Optionally, the log data display interface provides at least one of functions of log data screening, log data searching, log data sharing and log data copying.

In this optional embodiment, the log data display interface provides at least one of functions of log data screening, log data searching, log data analysis, log data copying, and the like. The log data screening can be performed through log printing time, data fields or events to which the data belong; the log data search can be carried out by screening the log printing time, data field cooperation and data belonging events; the log data analysis can be to analyze the access condition of the user or to analyze the user behavior, etc.

Based on the log data output method provided by the embodiment of the invention, if a problem occurs in the running of a program, the processing process is as shown in fig. 2c, firstly, the log data display interface is entered according to the access entry provided by the interface construction module, and then the log is screened based on the functions of log data screening or searching and the like provided by the log data display interface, and the log analysis is performed, so that the problem is positioned and solved according to the log analysis result. Compared with the scheme that log files are downloaded firstly and then log screening is carried out on a large number of log files in the prior art, the method and the device have the advantages that interactive log data of the front-end service layer and the native plug-in layer are output in a centralized mode on the native container layer, a smaller log range is defined, a log data display interface is provided, and compared with the mode of downloading the log files, log data screening and analysis are carried out on the visual interface, so that the problem positioning efficiency is further improved.

According to the technical scheme of the embodiment of the invention, the log data with the set format is output based on the log format in the log buried point information, so that the log data format can be ensured to be uniform, the log data can be conveniently recorded and managed, the log data display interface is constructed based on the log data through the interface construction module, the log data can be displayed in a shallow display and easy-to-understand mode, and the related logs can be conveniently and quickly positioned when problems occur.

EXAMPLE III

Fig. 3 is a flowchart of a log data output method according to a third embodiment of the present invention, which is further detailed on the basis of the foregoing embodiments, and provides specific steps of sending a calling method to a native plug-in layer through a native container layer for calling a target RN component, and after outputting log data associated with the target RN component. As shown in fig. 3, the method includes:

and S310, sending the calling method of the target RN component to a primary container layer through a front-end business layer.

S320, determining a target plug-in module to which the target RN component belongs in the calling method through the native container layer.

In the embodiment of the invention, after receiving the calling method of the target RN component sent by the front-end service layer, the native container layer analyzes the calling method and determines the target plug-in module to which the target RN component belongs in the calling method. Specifically, after receiving the calling method of the target RN component, the native container layer reads the calling parameter in the calling method, and the calling specifically includes the identifier of the target RN component and the identifier of the target plug-in module to which the target RN component belongs.

In a specific example, after receiving the calling method sent by the front-end service layer, the native container layer parses the calling method, and obtains that a target RN component included in the calling method is a component a, and a plugin module to which the component a belongs is a plugin module P1.

S330, sending the calling method to a target plug-in module in the native plug-in layer for calling the target RN assembly in the target plug-in module.

In the embodiment of the invention, the native container layer forwards the calling method to the target plug-in module in the native plug-in layer for calling the target RN component in the target plug-in module. Specifically, after determining that the plug-in module to which the target RN component belongs in the calling method is the plug-in module P1, the native container layer forwards the calling method to the plug-in module P1, so that the plug-in module P1 executes the logic of the target RN component included therein, thereby implementing the corresponding function.

And S340, outputting log data associated with the target RN component based on the log buried point information through the native container layer.

And S350, uploading the log data to a cloud end through a native container layer to indicate the cloud end to construct a log data display page based on the log data.

In this embodiment, besides the interface construction module constructing the visual interface of the log data, the native container layer can upload the log data to the cloud server after receiving the output log data, so as to construct a log data display interface at the cloud, thereby improving the log data display range and easy acquirability.

Optionally, after outputting the log data associated with the target RN component, the method further includes:

executing the target RN component through the native plug-in layer, and feeding back an execution result to the native container layer;

outputting, by the native container layer, log data associated with the RN component based on the log burial point information.

In this alternative embodiment, a specific step after outputting log data associated with the target RN component is provided: and the front-end service layer sends the calling method of the target RN component to the native plug-in layer through the native container layer, and after the RN component is called, the native plug-in layer executes corresponding logic of the target RN component to obtain an execution result. Further, the native plug-in layer feeds back the execution result to the native container layer, and the native container layer determines the target service module associated with the execution result according to the identifier of the target service module included in the feedback information, and finally feeds back the execution result to the target service module in the front-end service layer. Meanwhile, the native container layer outputs log data corresponding to the execution result of the RN component based on the log embedded point information. By carrying out log dotting on the native container layer, the interactive process between the front-end service layer and the native plug-in layer can be ensured to output corresponding logs, and log omission is avoided. And the log format is preset in the native container layer, so that the unification of the log format can be realized, and the management and the positioning of log data are facilitated.

According to the technical scheme, the log data associated with the target RN component is output on the basis of the log embedded point information through the native container layer, the log data is output on the native container layer, the problem of log data omission is solved, the native container layer only outputs the log data aiming at the interaction between the front-end service layer and the native plug-in layer, other disordered logs are eliminated, and the problem positioning efficiency when the interaction has problems is improved. Furthermore, the log is uploaded to the cloud after the log is output, the cloud is instructed to construct a log data display interface, log data can be visually acquired at the cloud, and problem location is facilitated.

Example four

Fig. 4 is a schematic structural diagram of a log data output apparatus according to a fourth embodiment of the present invention.

As shown in fig. 4, the apparatus includes:

a first calling method sending module 410, configured to send a calling method of a target RN component to a native container layer through a front-end service layer;

a second calling method sending module 420, configured to send the calling method to a native plug-in layer through the native container layer, so as to call the target RN component;

a log data output module 430, configured to output, through the native container layer, log data associated with the target RN component based on the log burial point information.

Optionally, the log data output module 430 is specifically configured to:

outputting, by the native container layer, log data associated with the target RN component based on a log format in log burial point information.

Optionally, the log data output device further includes:

the log data broadcasting module is used for broadcasting the log data through the native container layer after outputting the log data associated with the target RN component, and is used for indicating the interface construction module to store the log data into a log database;

and the display interface construction module is used for responding to the access of a log data display interface inlet through the interface construction module, reading log data from the log database and constructing a log data display interface based on the log data.

Optionally, the log data display interface provides at least one of functions of log data screening, log data searching, log data sharing, and log data copying.

Optionally, the second calling method sending module 420 is specifically configured to:

determining a target plug-in module to which a target RN component in the calling method belongs through the native container layer;

and sending the calling method to a target plug-in module in a native plug-in layer for calling a target RN component in the target plug-in module.

Optionally, the log data output device further includes:

and the log data uploading module is used for uploading the log data to a cloud end through the native container layer after the log data associated with the target RN component is output, so as to instruct the cloud end to construct a log data display page based on the log data.

Optionally, the log data output device further includes:

an execution result feedback module, configured to execute the target RN component through a native plug-in layer after outputting log data associated with the target RN component, and feed back an execution result to the native container layer;

and the feedback log output module is used for outputting log data associated with the RN component based on the log embedded point information through the native container layer.

The log data output device provided by the embodiment of the invention can execute the log data output method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

EXAMPLE five

FIG. 5 illustrates a schematic diagram of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 5, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

Processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The processor 11 performs the various methods and processes described above, such as the log data output method.

In some embodiments, the log data output method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the log data output method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the log data output method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, 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), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.

It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A log data output method, comprising:

sending the calling method of the target native interaction RN component to a native container layer through a front-end service layer;

2. The method of claim 1, wherein outputting, by the native container layer, log data associated with the target RN component based on log burial point information comprises:

3. The method of claim 1, further comprising, after outputting log data associated with the target RN component:

broadcasting the log data through the native container layer, and indicating an interface construction module to store the log data into a log database;

and responding to the access of a log data display interface inlet through the interface construction module, reading log data from the log database, and constructing a log data display interface based on the log data.

4. The method of claim 3, wherein the log data presentation interface provides at least one of log data screening, log data searching, log data sharing, and log data replication functions.

5. The method of claim 1, wherein sending the calling method to a native plug-in layer through the native container layer for calling the target RN component comprises:

6. The method of claim 1, further comprising, after outputting log data associated with the target RN component:

uploading the log data to a cloud through the native container layer to instruct the cloud to construct a log data display page based on the log data.

7. The method of any of claims 1-6, further comprising, after outputting log data associated with the target RN component:

executing the target RN component through a native plug-in layer, and feeding back an execution result to the native container layer;

outputting, by the native container layer, log data associated with the RN component based on log burial point information.

8. A log data output apparatus, comprising:

9. An electronic device, characterized in that the electronic device comprises:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the log data output method of any one of claims 1-7.

10. A computer-readable storage medium storing computer instructions for causing a processor to implement the log data output method of any one of claims 1 to 7 when executed.