CN113608955B - Log recording method, device, equipment and storage medium - Google Patents
Log recording method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113608955B CN113608955B CN202110742084.6A CN202110742084A CN113608955B CN 113608955 B CN113608955 B CN 113608955B CN 202110742084 A CN202110742084 A CN 202110742084A CN 113608955 B CN113608955 B CN 113608955B
- Authority
- CN
- China
- Prior art keywords
- data
- operation function
- function
- log
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 230000006870 function Effects 0.000 claims abstract description 313
- 238000012986 modification Methods 0.000 claims abstract description 81
- 230000004048 modification Effects 0.000 claims abstract description 79
- 238000007781 pre-processing Methods 0.000 claims abstract description 52
- 238000012805 post-processing Methods 0.000 claims abstract description 45
- 238000012544 monitoring process Methods 0.000 claims description 40
- 238000012545 processing Methods 0.000 claims description 36
- 230000006399 behavior Effects 0.000 claims description 22
- 238000001914 filtration Methods 0.000 claims description 18
- 238000013519 translation Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 10
- 238000013507 mapping Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 7
- 238000011161 development Methods 0.000 abstract description 14
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 230000008901 benefit Effects 0.000 description 7
- 230000009471 action Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 101100297540 Oryza sativa subsp. japonica PHP5 gene Proteins 0.000 description 1
- 101100123444 Schizosaccharomyces pombe (strain 972 / ATCC 24843) hap5 gene Proteins 0.000 description 1
- 230000003542 behavioural effect Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000002650 habitual effect Effects 0.000 description 1
- 230000004807 localization Effects 0.000 description 1
- 239000003607 modifier Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000008719 thickening Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Library & Information Science (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a log recording method, a log recording device, log recording equipment and a storage medium, wherein the log recording method comprises the following steps: configuring a target operation function to be monitored in a filter and configuring a target field in an interpreter; acquiring pre-processing data and post-processing data corresponding to a target operation function through a filter; and recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data and the target field configured in the interpreter. In the method, a developer does not need to know specific details of log records, does not need to maintain related interfaces of the log, only needs to complete configuration through a unified configuration interface, and has low learning cost, high development efficiency and low error rate. And the log and the service are decoupled and are not mutually influenced, so that the maintainability of the program is improved. And the log data of the query is intuitively displayed according to the time axis, and the displayed log data are text data interpreted by an interpreter, so that the readability is high. Modification data can be highlighted, and log query efficiency is improved.
Description
Technical Field
The application belongs to the technical field of data processing, and particularly relates to a log recording method, device, equipment and storage medium.
Background
The function of the operation log is to record all operations of the operator in the application. The operation log is used for recording the time, content and the like of each operation of the operator. Recording operation logs is important for problem backtracking, behavior pursuit, error localization, data statistics, etc.
Currently, some log recording methods are provided in the related art, and one method is to record user-defined information using a log framework, and store the recorded information to a file, a database or a cloud. However, the method is mainly aimed at problem investigation and tracking of developers, business staff cannot view the logs through a panel generally, and the data format for displaying the logs is not intuitive. The other method is to nest the log record behavior in the business codes of each layer, so that the custom scene required by the business can be realized. However, the log record is tightly coupled with the service, a developer needs to develop a set of log while developing the service, the work is repeated, complicated and easy to make mistakes, and once the main structure of the log is changed, all program codes need to be modified, so that the maintenance is not easy.
Disclosure of Invention
The application provides a log recording method, device, equipment and storage medium, a developer does not need to know specific details of log recording, does not need to maintain a log related interface, only needs to complete related configuration, and has the advantages of low learning cost, high development efficiency and low error rate. And the log and the service are decoupled and are not mutually influenced, so that the maintainability of the program is improved.
An embodiment of a first aspect of the present application provides a logging method, including:
configuring a target operation function to be monitored in a filter and configuring a target field in an interpreter;
acquiring pre-processing data and post-processing data corresponding to the target operation function through the filter;
and recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data and the target field configured in the interpreter.
In some embodiments of the present application, the configuring, in the filter, a target operation function to be monitored includes:
configuring function names of target operation functions to be monitored in filtering parameters of a behavior function included in a filter;
generating a monitoring detail array corresponding to the target operation function according to the function name, the logic type, the service primary key, the additional information, the class name of the callback function and the callback function name of the target operation function;
and configuring the monitoring detail array in the monitoring object parameters of the behavior function.
In some embodiments of the present application, the configuring the target field in the interpreter includes:
configuring one or more target fields in a defined field function included in the interpreter;
And configuring corresponding translation text for each target field.
In some embodiments of the present application, the acquiring, by the filter, pre-processing data and post-processing data of the target operating function before processing includes:
receiving a data modification request, and determining a first operation function to be executed in response to the data modification request;
determining whether the first operating function is configured in the filter;
if yes, acquiring a monitoring detail array of the first operation function from monitoring object parameters of the behavior function in the filter;
and acquiring pre-processing data before executing the first operation function and post-processing data after executing the first operation function according to the acquired monitoring detail array.
In some embodiments of the present application, the determining whether the first operation function is configured in the filter includes:
acquiring a function name of the first operation function;
acquiring function names of all target operation functions included in the filtering parameters of the behavior function in the filter;
and if the function name included in the filtering parameter contains the function name of the first operation function, determining that the first operation function is configured in the filtering.
In some embodiments of the present application, the acquiring, according to the acquired listening detail array, pre-processing data before executing the first operation function and post-processing data after executing the first operation function includes:
obtaining the class name and callback function name of the callback function corresponding to the first operation function from the monitoring detail array;
calling a callback function corresponding to the first operation function according to the obtained class name and the callback function name;
acquiring pre-processing data aimed at by the data modification request before executing the first operation function through a callback function corresponding to the first operation function;
after the first operation function is executed, the processed data corresponding to the data modification request is obtained through a callback function corresponding to the first operation function.
In some embodiments of the present application, the recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data, and a target field configured in the interpreter includes:
if the pre-processing data is different from the post-processing data, judging whether a target field configured in the interpreter contains a modified field corresponding to the pre-processing data and the post-processing data;
If yes, generating log data corresponding to the target operation function executed this time, and storing the log data into a database, wherein the log data comprises a logic type corresponding to the target operation function, a business primary key, the pre-processing data, the post-processing data and corresponding modification time;
and if the modified field is not configured in the interpreter or the data before processing is the same as the data after processing, not recording the log data corresponding to the execution of the target operation function.
In some embodiments of the present application, the method further comprises:
receiving a log query request, wherein the log query request comprises a logic type and a service primary key corresponding to a target operation function to be queried;
according to the logic type and the service primary key, acquiring all log data corresponding to the target operation function to be queried from the database;
respectively translating the target fields included in each piece of acquired log data through the mapping relation between the target fields configured in the interpreter and the translation text;
displaying all the translated log data.
In some embodiments of the present application, the displaying all log data acquired includes:
Creating a time axis corresponding to the target operation function to be queried according to the modification time included in each piece of acquired log data;
mapping and arranging each log data and the modification time corresponding to the log data on the time axis respectively;
and displaying the time axis and each arranged log data.
In some embodiments of the present application, the method further comprises:
determining modification data corresponding to the pre-processing data and the post-processing data included in the log data;
marking the modified data in the data before processing and the data after processing according to a preset marking mode;
and displaying the marked data before processing and the marked data after processing.
An embodiment of a second aspect of the present application provides a logging device, including:
the configuration module is used for configuring a target operation function to be monitored in the filter and configuring a target field in the interpreter;
the acquisition module is used for acquiring the pre-processing data and the post-processing data corresponding to the target operation function through the filter;
and the log recording module is used for recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data and the target field configured in the interpreter.
An embodiment of a third aspect of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the computer program to implement the method of the first aspect.
An embodiment of the fourth aspect of the present application provides a computer readable storage medium having stored thereon a computer program for execution by a processor to implement the method of the first aspect.
The technical scheme provided in the embodiment of the application has at least the following technical effects or advantages:
in the embodiment of the application, the log data of the target operation function can be recorded by configuring the target operation function to be monitored in the filter and configuring the target field to be concerned in the interpreter, so that a developer does not need to know the specific details of the log recording process, does not need to maintain the query interface of the log, only needs to complete configuration operation through a unified configuration interface, and has the advantages of low learning cost, high development efficiency and reduction of error rate. And the log record is decoupled from the specific service, so that the log and the specific service are not mutually influenced, and the maintainability of the service program is improved. And all the log data of the query are intuitively displayed according to a time axis when the log is queried, and the displayed log data are text data subjected to text interpretation by an interpreter, so that the readability is high. And the modified data can be marked and highlighted during display, so that a user can directly review the modified data, and the efficiency of a query person is greatly improved.
Additional aspects and advantages of the application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the application.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to designate like parts throughout the figures.
In the drawings:
FIG. 1 is a flow chart of a logging method according to an embodiment of the present application;
FIG. 2 is another flow chart of a logging method provided by an embodiment of the present application;
FIG. 3 is a schematic diagram showing log query results according to an embodiment of the present application;
FIG. 4 is a schematic diagram illustrating a log record and query flow according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a log recording device according to an embodiment of the present application;
FIG. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure;
Fig. 7 shows a schematic diagram of a storage medium according to an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
It is noted that unless otherwise indicated, technical or scientific terms used herein should be given the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs.
A logging method, apparatus, device and storage medium according to embodiments of the present application are described below with reference to the accompanying drawings.
Some methods for logging exist in the related art, such as using a log framework to record user-defined information, and storing the recorded information in a file, a database or a cloud. However, the method is mainly aimed at problem investigation and tracking of developers, business staff cannot view the logs through a panel generally, and the data format for displaying the logs is not intuitive. In another way, the logging behavior is nested in the business code of each layer, so that the custom scene required by the business can be realized. However, the log record is tightly coupled with the service, a developer needs to develop a set of log while developing the service, the work is repeated, complicated and easy to make mistakes, and once the main structure of the log is changed, all program codes need to be modified, so that the maintenance is not easy. And the method is that all requests are recorded through an item system interceptor, similar to an access log of the nginx, the access log can be unified, and service decoupling is performed, but only request data is recorded, the request data cannot be bound with a service main key, data mixing cannot be performed for service customization, and the method is also not intuitive.
Based on the problems existing in the related art, the embodiment of the application provides a log recording method, which can realize the log data of the target operation function by configuring the target operation function to be monitored in a filter and configuring the target field to be concerned in an interpreter, so that a developer does not need to know the specific details of the log recording process and maintain the query interface of the log, and the development efficiency is greatly improved. And the log record is decoupled from the specific service, so that the log and the specific service are not mutually influenced, and the maintainability of the service program is improved. And all log data of the query are intuitively displayed according to a time axis when the log is queried, and the displayed log data are text data subjected to text interpretation by an interpreter, so that the readability is high, the display interface is simpler, and the efficiency of the query personnel is greatly improved.
Referring to fig. 1, the method specifically includes the steps of:
step 101: the target operation function to be monitored is configured in the filter, and the target field is configured in the interpreter.
The embodiment of the application is realized by adopting a preset development framework and a preset database, wherein the preset development framework can be a YII framework or a YII2.0 framework and the like, the YII framework or the YII2.0 framework is a web application development framework of PHP5 (hypertext preprocessor) with high performance, and a developer can add business logic on the basis of the generated code framework to rapidly complete the development of an application. The preset database can be a mysql database or an sqlserver database, etc. The embodiment of the application completes the collection of the log data by utilizing a new characteristic component, a behavior, a component, an event and the like in a preset development framework. And storing the collected log data into a preset database, and providing a log query service based on the data stored in the database.
The above-mentioned preset components of the development framework include a filter and an interpreter, and the embodiment of the application provides a unified data operation interface for a developer based on the development framework, through which the developer can perform configuration operation on the filter and the interpreter, and monitor a target operation function in a specific service program through the configured filter and the configured interpreter, so as to record corresponding log data when monitoring data modification operation corresponding to the target operation function.
Specifically, the function name of the target operation function to be monitored is configured in the filtering parameters of the behavior function included in the filter. Determining the logic type of the target operation function, wherein the logic type is divided in a factory mode when a business program is developed, and the logic type comprises a plurality of types such as clients, users, orders and the like. And determining a service main key corresponding to the target operation function, wherein the service main key can be a unique identifier of the target operation function, and the unique identifier can be a character string which is set during development and is used for uniquely identifying the target operation function. Additional information required for monitoring the target operating function is determined, and the additional information can be an operator identifier and the like. And determining the class name of the callback function corresponding to the target operation function and the name of the callback function. And then generating a monitoring detail array corresponding to the target operation function according to the function name of the target operation function, the logic type, the service primary key, the additional information, the class name of the callback function and the callback function name, wherein the monitoring detail array comprises the function name of the target operation function, the logic type, the service primary key, the additional information, the class name of the callback function and the callback function name. The listening detail array is then configured in a listening object parameter of a behavioural function.
Since most of the services are not in a single table structure, but one-to-many or many-to-many associated data, a complete view needs to be implemented in the listening detail, and continuous table query of all data needs to be implemented in the callback function, and associated translation is performed. For example, if a common city of a customer is queried, and assuming that there are three table structures, a master table, a customer_related_city city table, and a city table, the related query uses the name of the city table as a result, a target customer is first searched from the customer table, and a city identifier managed by the target customer is searched from the customer_related_city city table according to the target customer, for example, 123. And then searching a target city corresponding to the city identifier, such as Beijing city, from the city table according to the searched city identifier (such as 123).
To facilitate an understanding of the above-described process of configuring a filter, an example is described below in connection with the configuration code of the filter.
In the above configuration code, behavir () is a behavior function in the filter, only is a filtering parameter, and function names of target operation functions to be monitored are configured in the filtering parameter only. The switch_switches are monitoring object parameters, monitoring details of target operation functions to be monitored are configured in the monitoring object parameters switch_switches, and the monitoring details are specifically configured in the form of arrays, wherein one array corresponds to one target operation function. The above code example configures the interception detail arrays corresponding to the target operation functions save-user and change-status in the interception object parameter snapshot_switches respectively. The number of parameters included in each monitoring detail array is the same as the meaning represented by each parameter. Taking a monitoring detail array corresponding to the target operation function save-USER as an example for explanation, wherein a first parameter 'save-USER' in the monitoring detail array is the function name of the target operation function save-USER, and a second parameter LogsConstants is the logic type to which LOG_USER belongs, and the logic type is the USER type. The third parameter 'id' is the business primary key. The fourth parameter 'created_by' is additional information, which is operator information here. The fifth parameter 'app\modules\user\user business' is the class name of the callback function, and the sixth parameter 'getuserinnfobyid' is the callback function name.
The filter parameter may be configured with function names of one or more target operation functions, and accordingly, the monitor object parameter may be configured with a monitor detail array corresponding to the one or more target operation functions. According to the method, a filter is added in the behavior to monitor the target operation function, and the service code and the operation log system are stripped off, so that the decoupling effect is achieved. And the self-defined callback function realizes bottom processing, so that the log recording becomes more flexible.
In the embodiment of the application, the configurable field display is provided through the interpreter, and when the service data fields are very numerous, the service personnel may only care about a few important fields, and the fields such as age, sex and the like are not cared for, but too many fields are filled with views to disturb the field of view, so that only the fields needed by people are configured, and the data can be simpler and tidy.
For the configuration of the interpreter, one or more target fields are configured in a defined field function included in the interpreter, and corresponding translation text is configured for each target field. The target field is a field focused by a user, and after the target operation function carries out data modification processing, if the content of the target field changes, the content of the target field before and after modification is required to be stored as log data corresponding to the target operation function.
In order to facilitate an understanding of the configuration process of the above-described interpreter, the following description is made in connection with codes.
In the configuration code of the interpreter, defined words () is a defined field function, in which each target field is configured in the form of an array of keys= > value, a key is an original target field of the target field, and a value is a translation text corresponding to the target field. The translation text corresponding to the target field username in the code is 'name'.
After the filter and the interpreter are configured in the above manner, the configured target operation function can be monitored in real time, and the corresponding log data is recorded through the following operations in steps 102 and 103.
Step 102: and acquiring the pre-processing data and the post-processing data corresponding to the target operation function through a filter.
The embodiment of the application provides a unified data modification interface for a user, when a data modification request submitted by the user is received through the data modification interface, a first operation function required to be executed in response to the data modification request is determined, and whether the first operation function is configured in a filter or not is determined, namely whether the first operation function is configured as a target operation function required to be monitored or not. Specifically, the function names of the first operation function are acquired, and the function names of all target operation functions included in the filter parameters of the behavior function in the filter, that is, all function names configured in the filter parameter only included in the behavior function behavir () in the code example in step 101 are acquired. And judging whether all function names configured in the filtering parameters contain function names of the first operation function required to be executed in response to the current data modification request. If the target operation function is included, determining that the first operation function is configured in the filtering, namely the first operation function is the target operation function needing to be monitored. If not, it is determined that the first operation function is not the target operation function to be monitored.
If the first operation function is the target operation function to be monitored, according to the function name of the first operation function, acquiring a monitoring detail array of the first operation function from the monitoring object parameters of the behavior function in the filter, that is, acquiring a monitoring detail array corresponding to the first operation function from the monitoring object parameters snapshot_switches in the code example in the step 101. And acquiring the pre-processing data before executing the first operation function and the post-processing data after executing the first operation function according to the acquired monitoring detail array.
According to the embodiment of the application, the collection before modification operation before the modification and the collection after modification operation after the modification are set, and the callback functions corresponding to the target operation functions are automatically called by the collection before modification and the collection after modification, so that data before and after data modification of the target operation functions are automatically collected. Specifically, when it is determined that a first operation function corresponding to a current data modification request needs to be monitored, before-modification collection operation before modification is triggered, after a monitoring detail array corresponding to the first operation function is obtained, a class name and a callback function name of a callback function corresponding to the first operation function are obtained from the monitoring detail array, and the callback function corresponding to the first operation function is called according to the obtained class name and callback function name. And acquiring the pre-processing data aimed at by the data modification request before executing the first operation function through the callback function corresponding to the first operation function, and storing the pre-processing data in the old variable container. Then, in response to the current data modification request, the first operation function is executed to perform data modification. Judging whether the data modification is successful or not after the data modification is carried out, if not, prompting the reason of the failure modification to the user, and ending the operation. And if the modification is successful, triggering a modified collection operation after action, and automatically calling a callback function of the first operation function to acquire processed data corresponding to the data modification request according to the class name and the callback function name of the callback function of the first operation function. And store the processed data in a new variable container.
Step 103: and recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data and the target field configured in the interpreter.
The pre-processing data and post-processing data before and after execution of the target processing function are collected in step 102, and then it is determined whether the pre-processing data stored in the old variable container and the post-processing data stored in the new variable container are identical. If the data are the same, the data are not changed before and after the target operation function is executed, so that logging is not needed. If the data before and after the execution of the target operation function is judged to be changed, further judging whether the target field configured in the interpreter contains modified fields corresponding to the data before and after the processing. And if so, generating log data corresponding to the current execution target operation function according to the logic type, the service primary key, the collected data before and after processing and the recorded modification time of the target operation function, and storing the log data into a database. The log data comprises a logic type, a business main key, pre-processing data, post-processing data and corresponding modification time corresponding to the target operation function.
The table structure of the database is simple, and a single table can be completed. The unique identification of the logic type and the service primary key is needed, the processed data stored in the original old variable container is serialized on the old_data field, and the processed data stored in the new variable container is serialized on the new_data field. Some other fields may be appended such as creator, creation time, etc.
If the modified fields corresponding to the pre-processing data and the post-processing data are not configured in the interpreter, the modified fields of the execution target operation function are not concerned by the user, so that the log data corresponding to the execution target operation function is not recorded.
In order to facilitate understanding of the above logging process, a specific description will be given below with reference to the accompanying drawings. As shown in fig. 2, S1: the target operation function to be monitored is configured in the filter, and the target field is configured in the interpreter. S2: and receiving a data modification request submitted by a user through a unified data modification interface, and determining a first operation function required to be executed in response to the data modification request. S3: judging whether the first operation function is configured as a target operation function to be monitored in the filter, if not, executing a step S4, and if so, executing a step S5. S4: and (3) not monitoring the first operation function, executing the first operation function and ending the operation. S5: triggering and collecting operation before modification, and calling a callback function corresponding to a first operation function to acquire pre-processing data before data modification according to the class name and the callback function name of the callback function corresponding to the first operation function of the filter, and storing the pre-processing data in an old variable container. S6: a first operational function is performed. S7: triggering a modified collection operation after action, and automatically calling a callback function of the first operation function to acquire processed data corresponding to the data modification request. And store the processed data in a new variable container. S8: judging whether the pre-processing data stored in the old variable container and the post-processing data stored in the new variable container are the same, if so, executing step S9, and if not, executing step S10. S9: and (5) the log record is not needed, and the operation is ended. S10: judging whether the target field configured in the interpreter contains a modified field corresponding to the pre-processing data and the post-processing data, if so, executing step S11, and if not, executing step S12. S11: generating log data corresponding to the current execution target operation function, and storing the log data into a database. S12: and (5) not recording log data corresponding to the current execution target operation function, and ending the operation.
Through the method, each target operation function to be monitored is monitored in real time, and log data corresponding to the target operation function is stored in a database. Based on the database, a unified log query interface is provided for a user, the user can submit a log query request through the log query interface, and the log query request carries a logic type and a business primary key corresponding to a target operation function to be queried so as to query all log data corresponding to the target operation function. Or the log query request may include a time period to be queried so as to query all log data of the target operation function in the time period to be queried for the modification time of the modification data.
After receiving a log query request submitted by a user through a log query interface, acquiring all log data corresponding to a target operation function to be queried from a database according to a logic type and a service primary key included in the log query request, and translating target fields included in each acquired log data respectively through a mapping relation between target fields configured in an interpreter and translation texts, namely replacing the target fields included in each log data acquired from the database with the translation texts corresponding to the target fields configured in the interpreter. Displaying all the translated log data. And the target field is translated through the interpreter and then displayed, so that the readability of the log data is improved.
In order to more intuitively display the log data, before displaying all the obtained log data, the embodiment of the application creates a time axis corresponding to the target operation function to be queried according to the modification time included in each obtained log data, where the time axis includes an axis and the modification time of each log data marked on the axis according to a preset time sequence, and the preset time sequence may be arranged according to a time sequence from front to back or from back to front. And mapping and arranging each log data and the modification time corresponding to the log data on the time axis respectively. And finally displaying the time axis and each arranged log data. The log data is displayed in a time axis mode, so that a user can intuitively see the history track of data modification, and the user can conveniently and quickly look up the log data.
The embodiment of the application can also perform format display on the log data, namely, the data such as the data before processing, the data after processing and the like included in the log data are displayed according to preset layout typesetting, for example, a first row displays a user identifier, a second row sequentially displays the data before processing and the data after processing, and the like.
In other embodiments of the present application, the log data includes pre-processing data and modified data corresponding to the post-processing data; marking the modified data in the pre-processing data and the post-processing data according to a preset marking mode, wherein the preset marking mode can be thickening, underlining and the like of the modified data, or can be highlighting and the like of the modified data by adopting a preset color. Displaying the marked data before processing and the marked data after processing.
The modified data is marked and displayed in a preset marking mode, so that a user can quickly look up the modified data, the time for the user to look up the log data is saved, and the looking up efficiency is improved.
Fig. 3 is a schematic diagram of a log query result, where the left side is a time axis, the right side is log data corresponding to a modification time arrangement marked on the time axis, a modifier identifier is displayed in a first row in the log data, modified fields are sequentially displayed in a second row, the content of the field before modification and the content of the field after modification, a gray part is modification data, and modification data displayed in the gray part in practical application can be highlighted with colors such as yellow, red and the like.
In order to further understand the above-described logging and query logging process, a description is provided below with reference to the accompanying drawings. As shown in fig. 4, when a user needs to modify data, the user submits a request, filters an operation function required to be executed by the request through a filter, and if the operation function required to be executed is configured as a target operation function required to be monitored in the filter, triggers a before action, automatically invokes a callback function to perform multi-table associated translation, queries detail data before modification, and puts the detail data into an old container. And then executing the operation function required to be executed by the request to process, judging whether the data modification is successful or not, if so, prompting the failure reason, and terminating the operation. If successful, triggering after action, automatically calling callback function to make multi-table association translation, inquiring the modified detail data and placing the detail data into new container. And judging whether the new container is changed compared with the data in the old container, and if the new container is not changed, skipping and not recording. If the change occurs, judging whether fields corresponding to the pre-modification detail data and the post-modification detail data are configured in the interpreter through the interpreter, if not, skipping and not recording. If so, the collected data is stored in a database. If the user inquires the log through the unified inquiry interface, acquiring log data from the database through the interpreter, translating the fields in the acquired log array into a translation text with strong readability through the interpreter, and then displaying the log data to the user.
The embodiment of the application unifies log interface classes, such as providing a unified configuration interface, a unified data modification interface, a unified log query interface and the like. The log operation interface is provided to standardize the log format, so that the log is convenient to maintain and inherit, and the development amount is reduced. And the modified content is highlighted by adopting a time axis mode, and the data is as clear as possible. And moreover, the log data is displayed more humanized and visualized. The original data is changed into habitual readable language by means of interpretation and formatting, so that the efficiency of quickly extracting the data is improved.
In the embodiment of the application, the log data of the target operation function can be recorded by configuring the target operation function to be monitored in the filter and configuring the target field to be concerned in the interpreter, so that a developer does not need to know the specific details of the log recording process, does not need to maintain the query interface of the log, only needs to complete configuration operation through a unified configuration interface, and has the advantages of low learning cost, high development efficiency and reduction of error rate. And the log record is decoupled from the specific service, so that the log and the specific service are not mutually influenced, and the maintainability of the service program is improved. And all the log data of the query are intuitively displayed according to a time axis when the log is queried, and the displayed log data are text data subjected to text interpretation by an interpreter, so that the readability is high. And the modified data can be marked and highlighted during display, so that a user can directly review the modified data, and the efficiency of a query person is greatly improved.
The embodiment of the application also provides a logging device, which is used for executing the logging method provided by any one of the embodiments. Referring to fig. 5, the apparatus includes:
a configuration module 201, configured to configure a target operation function to be monitored in a filter and configure a target field in an interpreter;
an obtaining module 202, configured to obtain pre-processing data and post-processing data corresponding to the target operation function through a filter;
the log recording module 203 is configured to record log data corresponding to the target operation function according to the pre-processing data, the post-processing data and the target field configured in the interpreter.
A configuration module 201, configured to configure a function name of a target operation function to be monitored in a filtering parameter of a behavior function included in a filter; generating a monitoring detail array corresponding to the target operation function according to the function name, the logic type, the service primary key, the additional information, the class name of the callback function and the callback function name of the target operation function; and configuring the monitoring detail array in the monitoring object parameters of the behavior function.
A configuration module 201, configured to configure one or more target fields in a defined field function included in the interpreter; a corresponding translation text is configured for each target field.
An obtaining module 202, configured to receive a data modification request, and determine a first operation function that needs to be executed in response to the data modification request; determining whether a first operating function is configured in the filter; if yes, acquiring a monitoring detail array of the first operation function from monitoring object parameters of the behavior function in the filter; and acquiring the pre-processing data before executing the first operation function and the post-processing data after executing the first operation function according to the acquired monitoring detail array.
An obtaining module 202, configured to obtain a function name of a first operation function; obtaining function names of all target operation functions included in filtering parameters of the behavior functions in the filter; and if the function name included in the filtering parameter contains the function name of the first operation function, determining that the first operation function is configured in the filtering.
The obtaining module 202 is configured to obtain, from the monitoring detail array, a class name of a callback function and a callback function name corresponding to the first operation function; calling a callback function corresponding to the first operation function according to the acquired class name and callback function name; acquiring pre-processing data aimed at by a data modification request before executing a first operation function through a callback function corresponding to the first operation function; after the first operation function is executed, the processed data corresponding to the data modification request is obtained through a callback function corresponding to the first operation function.
The log recording module 203 is configured to determine whether the target field configured in the interpreter includes a modified field corresponding to the pre-processing data and the post-processing data if the pre-processing data is different from the post-processing data; if yes, generating log data corresponding to the current execution target operation function, and storing the log data into a database, wherein the log data comprises a logic type, a business primary key, pre-processing data, post-processing data and corresponding modification time corresponding to the target operation function; if the modified field is not configured in the interpreter or the data before processing is the same as the data after processing, the log data corresponding to the current execution target operation function is not recorded.
The apparatus further comprises: the log query module is used for receiving a log query request, wherein the log query request comprises a logic type and a service main key corresponding to a target operation function to be queried; according to the logic type and the business primary key, acquiring all log data corresponding to the target operation function to be queried from a database; respectively translating the target fields included in each piece of acquired log data through the mapping relation between the target fields configured in the interpreter and the translation text; displaying all the translated log data.
The log query module is used for creating a time axis corresponding to the target operation function to be queried according to the modification time included in each piece of acquired log data; mapping and arranging each log data and the modification time corresponding to the log data on the time axis respectively; and displaying the time axis and each log data after arrangement.
The log query module is used for determining modification data corresponding to the pre-processing data and the post-processing data included in the log data; marking the modified data in the data before and after processing according to a preset marking mode; displaying the marked data before processing and the marked data after processing.
The log recording device provided by the above embodiment of the present application and the log recording method provided by the embodiment of the present application have the same beneficial effects as the method adopted, operated or implemented by the application program stored therein, because of the same inventive concept.
The embodiment of the application also provides electronic equipment for executing the log recording method. Referring to fig. 6, a schematic diagram of an electronic device according to some embodiments of the present application is shown. As shown in fig. 6, the electronic device 6 includes: a processor 800, a memory 801, a bus 802 and a communication interface 803, the processor 800, the communication interface 803 and the memory 801 being connected by the bus 802; the memory 801 stores a computer program executable on the processor 800, and the processor 800 executes a logging method according to any one of the foregoing embodiments of the present application when the computer program is executed.
The memory 801 may include a high-speed random access memory (RAM: random Access Memory), and may further include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. The communication connection between the device network element and the at least one other network element is achieved through at least one communication interface 803 (which may be wired or wireless), the internet, a wide area network, a local network, a metropolitan area network, etc. may be used.
Bus 802 may be an ISA bus, a PCI bus, or an EISA bus, among others. The buses may be classified as address buses, data buses, control buses, etc. The memory 801 is configured to store a program, and the processor 800 executes the program after receiving an execution instruction, and the logging method disclosed in any of the foregoing embodiments of the present application may be applied to the processor 800 or implemented by the processor 800.
The processor 800 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the methods described above may be performed by integrated logic circuitry in hardware or instructions in software in processor 800. The processor 800 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 801, and the processor 800 reads information in the memory 801 and performs the steps of the above method in combination with its hardware.
The electronic device provided by the embodiment of the application and the log recording method provided by the embodiment of the application have the same beneficial effects as the method adopted, operated or realized by the electronic device and the log recording method provided by the embodiment of the application due to the same inventive concept.
The present embodiment also provides a computer readable storage medium corresponding to the logging method provided in the foregoing embodiment, referring to fig. 7, the computer readable storage medium is shown as an optical disc 30, on which a computer program (i.e. a program product) is stored, where the computer program, when executed by a processor, performs the logging method provided in any of the foregoing embodiments.
It should be noted that examples of the computer readable storage medium may also include, but are not limited to, a phase change memory (PRAM), a Static Random Access Memory (SRAM), a Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a flash memory, or other optical or magnetic storage medium, which will not be described in detail herein.
The computer readable storage medium provided by the above embodiments of the present application and a logging method provided by the embodiments of the present application have the same advantageous effects as the method adopted, operated or implemented by the application program stored therein, because of the same inventive concept.
It should be noted that:
in the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the present application may be practiced without these specific details. In some instances, well-known structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the application, various features of the application are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the application and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the following schematic diagram: i.e., the claimed application requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this application.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the present application and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.
The foregoing is merely a preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (13)
1. A method of logging, comprising:
configuring a target operation function to be monitored in a filter and configuring a target field in an interpreter;
acquiring pre-processing data and post-processing data corresponding to the target operation function through the filter;
recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data and a target field configured in the interpreter;
The method for obtaining the pre-processing data and the post-processing data corresponding to the target operation function through the filter comprises the following steps:
filtering an operation function required to be executed by the data modification request through the filter, and calling a callback function to inquire detail data before modification if the operation function required to be executed is configured as a target operation function required to be monitored in the filter; and processing the operation function required to be executed by executing the request, and calling the callback function to inquire the modified detail data under the condition that the modification is successful.
2. The method according to claim 1, wherein configuring the target operation function to be monitored in the filter includes:
configuring function names of target operation functions to be monitored in filtering parameters of a behavior function included in a filter;
generating a monitoring detail array corresponding to the target operation function according to the function name, the logic type, the service primary key, the additional information, the class name of the callback function and the callback function name of the target operation function;
and configuring the monitoring detail array in the monitoring object parameters of the behavior function.
3. The method of claim 1, wherein configuring the target field in the interpreter comprises:
Configuring one or more target fields in a defined field function included in the interpreter;
and configuring corresponding translation text for each target field.
4. The method according to claim 2, wherein the acquiring, by the filter, pre-processing data and post-processing data of the target operating function before processing, comprises:
receiving a data modification request, and determining a first operation function to be executed in response to the data modification request;
determining whether the first operating function is configured in the filter;
if yes, acquiring a monitoring detail array of the first operation function from monitoring object parameters of the behavior function in the filter;
and acquiring pre-processing data before executing the first operation function and post-processing data after executing the first operation function according to the acquired monitoring detail array.
5. The method of claim 4, wherein the determining whether the first operating function is configured in the filter comprises:
acquiring a function name of the first operation function;
acquiring function names of all target operation functions included in the filtering parameters of the behavior function in the filter;
And if the function name included in the filtering parameter contains the function name of the first operation function, determining that the first operation function is configured in the filter.
6. The method of claim 4, wherein the obtaining pre-processing data before executing the first operation function and post-processing data after executing the first operation function based on the obtained listening detail array comprises:
obtaining the class name and callback function name of the callback function corresponding to the first operation function from the monitoring detail array;
calling a callback function corresponding to the first operation function according to the obtained class name and the callback function name;
acquiring pre-processing data aimed at by the data modification request before executing the first operation function through a callback function corresponding to the first operation function;
after the first operation function is executed, the processed data corresponding to the data modification request is obtained through a callback function corresponding to the first operation function.
7. The method according to any one of claims 1-6, wherein the recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data, and a target field configured in the interpreter includes:
If the pre-processing data is different from the post-processing data, judging whether a target field configured in the interpreter contains a modified field corresponding to the pre-processing data and the post-processing data;
if yes, generating log data corresponding to the target operation function executed this time, and storing the log data into a database, wherein the log data comprises a logic type corresponding to the target operation function, a business primary key, the pre-processing data, the post-processing data and corresponding modification time;
and if the modified field is not configured in the interpreter or the data before processing is the same as the data after processing, not recording the log data corresponding to the execution of the target operation function.
8. The method of claim 7, wherein the method further comprises:
receiving a log query request, wherein the log query request comprises a logic type and a service primary key corresponding to a target operation function to be queried;
according to the logic type and the service primary key, acquiring all log data corresponding to the target operation function to be queried from the database;
respectively translating the target fields included in each piece of acquired log data through the mapping relation between the target fields configured in the interpreter and the translation text;
Displaying all the translated log data.
9. The method of claim 8, wherein displaying all log data after translation comprises:
creating a time axis corresponding to the target operation function to be queried according to the modification time included in each piece of acquired log data;
mapping and arranging each log data and the modification time corresponding to the log data on the time axis respectively;
and displaying the time axis and each arranged log data.
10. The method according to claim 8 or 9, characterized in that the method further comprises:
determining modification data corresponding to the pre-processing data and the post-processing data included in the log data;
marking the modified data in the data before processing and the data after processing according to a preset marking mode;
and displaying the marked data before processing and the marked data after processing.
11. A logging device, comprising:
the configuration module is used for configuring a target operation function to be monitored in the filter and configuring a target field in the interpreter;
the acquisition module is used for acquiring the pre-processing data and the post-processing data corresponding to the target operation function through the filter;
The log recording module is used for recording log data corresponding to the target operation function according to the pre-processing data, the post-processing data and the target field configured in the interpreter;
the acquisition module is used for filtering the operation function required to be executed by the data modification request through the filter, and calling a callback function to inquire the detail data before modification if the operation function required to be executed is configured as the target operation function required to be monitored in the filter; and processing the operation function required to be executed by executing the request, and calling the callback function to inquire the modified detail data under the condition that the modification is successful.
12. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor runs the computer program to implement the method of any one of claims 1-10.
13. A computer readable storage medium having stored thereon a computer program, wherein the program is executed by a processor to implement the method of any of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110742084.6A CN113608955B (en) | 2021-06-30 | 2021-06-30 | Log recording method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110742084.6A CN113608955B (en) | 2021-06-30 | 2021-06-30 | Log recording method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113608955A CN113608955A (en) | 2021-11-05 |
| CN113608955B true CN113608955B (en) | 2024-01-26 |
Family
ID=78337101
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110742084.6A Active CN113608955B (en) | 2021-06-30 | 2021-06-30 | Log recording method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113608955B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090065A (en) * | 2021-11-26 | 2022-02-25 | 北京神州数字科技有限公司 | Method and system for recording data difference before and after modification |
| CN115114256A (en) * | 2022-07-27 | 2022-09-27 | 济南浪潮数据技术有限公司 | Operation log management method, device, equipment and readable storage medium |
| CN115544050A (en) * | 2022-11-29 | 2022-12-30 | 明度智云(浙江)科技有限公司 | Operation log recording method, device, equipment and storage medium |
| CN117407369B (en) * | 2023-12-14 | 2024-05-28 | 宁德时代新能源科技股份有限公司 | Operation log recording method and device and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102929920A (en) * | 2012-09-19 | 2013-02-13 | 北京奇虎科技有限公司 | Web-information-extraction-based monitoring method and device for software updating information |
| CN104182435A (en) * | 2013-05-24 | 2014-12-03 | 三星Sds株式会社 | System and method for searching information based on data missing mark |
| CN105426292A (en) * | 2015-10-29 | 2016-03-23 | 网易（杭州）网络有限公司 | Game log real-time processing system and method |
| WO2021012489A1 (en) * | 2019-07-22 | 2021-01-28 | 平安科技（深圳）有限公司 | Telephone platform log query method, terminal device, storage medium and apparatus |
| CN112395157A (en) * | 2020-11-13 | 2021-02-23 | 广州至真信息科技有限公司 | Audit log obtaining method and device, computer equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090132607A1 (en) * | 2007-11-16 | 2009-05-21 | Lorenzo Danesi | Techniques for log file processing |
| JP5581309B2 (en) * | 2008-03-24 | 2014-08-27 | スー カン，ミン | Information processing method for broadcast service system, broadcast service system for implementing the information processing method, and recording medium related to the information processing method |
-
2021
- 2021-06-30 CN CN202110742084.6A patent/CN113608955B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102929920A (en) * | 2012-09-19 | 2013-02-13 | 北京奇虎科技有限公司 | Web-information-extraction-based monitoring method and device for software updating information |
| CN104182435A (en) * | 2013-05-24 | 2014-12-03 | 三星Sds株式会社 | System and method for searching information based on data missing mark |
| CN105426292A (en) * | 2015-10-29 | 2016-03-23 | 网易（杭州）网络有限公司 | Game log real-time processing system and method |
| WO2021012489A1 (en) * | 2019-07-22 | 2021-01-28 | 平安科技（深圳）有限公司 | Telephone platform log query method, terminal device, storage medium and apparatus |
| CN112395157A (en) * | 2020-11-13 | 2021-02-23 | 广州至真信息科技有限公司 | Audit log obtaining method and device, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 杨杰.如何构建简易、高效、实用的网络运行监控系统.网络安全技术与应用.2004,(第10期),47-49. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113608955A (en) | 2021-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113608955B (en) | Log recording method, device, equipment and storage medium | |
| CN112099768B (en) | Business process processing method and device and computer readable storage medium | |
| CN111061733B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| AU2009238294A1 (en) | Data transformation based on a technical design document | |
| US9910870B2 (en) | System and method for creating data models from complex raw log files | |
| CN114625732A (en) | Query method and system based on Structured Query Language (SQL) | |
| JP2016126788A (en) | Cross column-searching relational database table | |
| CN112084167B (en) | A permission filtering method, device and storage medium | |
| CA3021720A1 (en) | System and method for cognitive troubleshooting assistance | |
| DE102008005083A1 (en) | Retrieve case-based closure information from archive records | |
| CN111414410A (en) | Data processing method, device, equipment and storage medium | |
| US7698277B2 (en) | Query processor, query processor elements and a method of establishing such a query processor and query processor elements and a domain processor | |
| CN116450890A (en) | Graph data processing method, device and system, electronic equipment and storage medium | |
| CN115629763A (en) | Target code generation method and NPU instruction display method and device | |
| EP1909170A1 (en) | Method and system for automatically generating a communication interface | |
| CN114116745A (en) | Interface change identification and display method, device, equipment and medium | |
| JP3914081B2 (en) | Access authority setting method and structured document management system | |
| CN113918606A (en) | Log query method and device | |
| CN112765197A (en) | Data query method and device, computer equipment and storage medium | |
| CN117827902A (en) | Service data processing method, device, computer equipment and storage medium | |
| US11977473B2 (en) | Providing a pseudo language for manipulating complex variables of an orchestration flow | |
| CN110737642B (en) | Database information analysis method, database information analysis device, computer device and storage medium | |
| GB2528697A (en) | Generating a database structure from a scanned drawing | |
| CN112861060A (en) | Page creating method and device, computer equipment and storage medium | |
| CN112905558A (en) | Report system implementation method and system based on database configuration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240510 Address after: 100102 room 1201, 12 / F, building 8, yard 34, Chuangyuan Road, Chaoyang District, Beijing Patentee after: Beijing new oxygen world wide Technology Consulting Co.,Ltd. Country or region after: China Address before: 100102 room 901, 9 / F, room 1001, 10 / F, building 8, yard 34, Chuangyuan Road, Chaoyang District, Beijing Patentee before: Beijing New Oxygen Technology Co.,Ltd. Country or region before: China |
|
| TR01 | Transfer of patent right |