CN112328568A - Service system log recording method and system based on SDK (software development kit) packet - Google Patents
Service system log recording method and system based on SDK (software development kit) packet Download PDFInfo
- Publication number
- CN112328568A CN112328568A CN202011212102.1A CN202011212102A CN112328568A CN 112328568 A CN112328568 A CN 112328568A CN 202011212102 A CN202011212102 A CN 202011212102A CN 112328568 A CN112328568 A CN 112328568A
- Authority
- CN
- China
- Prior art keywords
- service layer
- rest interface
- classes
- methods
- sdk
- 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.)
- Granted
Links
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- 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)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a service system log recording method and system based on an SDK packet, wherein the method comprises the following steps: carrying out first labeling on the classes and the methods obtained from the service layer through the SDK packet, assembling the classes and the methods to generate labeled objects, and storing the labeled objects in a redis cache; the gateway service layer intercepts the REST interface address from the front-end service layer, matches a corresponding labeled object from the redis cache through the REST interface address, and analyzes the matched labeled object to obtain an analysis result; and the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address, and assembles the analysis result, the REST interface entry and the REST interface exit into an operation log to be stored in the database. The service system log recording method and system based on the SDK package realize the log recording work of the service system in a plug-in SDK package mode, improve the reusability of log functions and reduce redundant codes. The method has the advantages that the log record is simplified, and meanwhile, the accuracy and comprehensiveness of the log are guaranteed.
Description
Technical Field
The invention relates to a service system log recording method and system based on an SDK packet.
Background
In order to search for problems more conveniently in a business system, an operation log is usually recorded when an application system is developed. In general, each service module needs to record a log according to an actual service management condition. This causes extra workload for the developer.
The existing methods for recording operation logs mainly include two types: firstly, recording logs in each module according to actual service conditions. The respective modules can record operation logs by themselves, but the operation logs are flexible, heavy in workload and capable of generating a large amount of redundant codes. And the recorded logs are recorded by developers of all modules, so that the style difference is large. Logging the system global operation in a filter or an interceptor. The operation logs are recorded in the filter or the interceptor, so that the workload is reduced, but the recorded information is not comprehensive enough.
Disclosure of Invention
In order to solve the defects of the prior art, the invention provides a service system log recording method and system based on an SDK packet, which can solve the problems.
A service system log recording method based on an SDK packet comprises the following steps:
carrying out first labeling on the classes and the methods obtained from the service layer through the SDK packet, assembling the classes and the methods to generate labeled objects, and storing the labeled objects in a redis cache;
the gateway service layer intercepts the REST interface address from the front-end service layer, and matches a corresponding labeled object from the redis cache through the REST interface address;
the gateway service layer analyzes the matched labeled object to obtain an analysis result;
the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address;
and the gateway service layer assembles the analysis result, the REST interface input parameter and the REST interface output parameter into an operation log and stores the operation log in a database.
Further, the specific method for performing first labeling on the classes and methods obtained from the service layer through the SDK package, assembling the labeled objects, and storing the labeled objects in the redis cache includes:
carrying out first labeling on the classes and the methods obtained from the business service layer;
scanning all classes with first labels and methods with the first labels in the classes;
analyzing the labels of the scanned classes and methods to obtain attributes labeled on the classes and methods;
acquiring an REST interface address corresponding to the method;
assembling the REST interface address and the attributes marked on the class and the method into a marked object;
and calling a redis cache and saving the annotation object into the redis cache.
Further, in the first labeling of the class and method obtained from the business service layer:
and performing WriteLog labeling on the classes and the methods acquired from the business service layer.
Further, a specific method for performing the first labeling on the class and the method obtained from the business service layer is as follows:
marking three attributes of name, operation and writeUser for the class and the method obtained from the service layer;
the name attribute is used for determining the module name;
the operation attribute is used for defining an operation name;
the writeUser attribute is used to define whether user information needs to be recorded.
Further, the specific method for intercepting the REST interface address from the front-end service layer by the gateway service layer is as follows:
the gateway service layer intercepts an REST interface request through a section;
and the gateway service layer intercepts the REST interface address corresponding to the REST interface request in a section.
Further, the specific method for the gateway service layer to obtain the REST interface entry and exit corresponding to the REST interface address includes:
the gateway service layer analyzes the intercepted parameters of the REST interface request and intercepts the REST interface access parameters;
and the gateway service layer forwards the REST interface request to the service layer, and after the service processing is finished, the gateway service layer acquires interface return information to obtain the REST interface reference.
A service system log recording system based on SDK packet comprises: the system comprises a front-end service layer, a gateway service layer, a service layer, an SDK packet, a redis cache and a database;
the SDK package is used for carrying out first labeling on the classes and the methods obtained from the service layer, assembling the classes and the methods to generate labeled objects and storing the labeled objects into a redis cache;
the gateway service layer is used for intercepting the REST interface address from the front-end service layer and matching a corresponding labeled object from the redis cache through the REST interface address;
the gateway service layer analyzes the matched labeled object to obtain an analysis result;
the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address;
and the gateway service layer assembles the analysis result, the REST interface input reference and the REST interface output reference into an operation log and stores the operation log in a database.
Further, the SDK package includes:
the marking module is used for carrying out first marking on the classes and the methods obtained from the business service layer;
the scanning module is used for scanning all classes with first labels and methods with the first labels in the classes, analyzing the labels of the scanned classes and methods to obtain attributes marked on the classes and methods, acquiring REST interface addresses corresponding to the methods, and assembling the REST interface addresses and the attributes marked on the classes and methods into marked objects;
and the calling module is used for calling the redis cache and storing the labeled object in the redis cache.
Further, the labeling module performs WriteLog labeling on the classes and methods obtained from the business service layer.
Further, the gateway service layer includes:
the interception module is used for intercepting the REST interface request through a section;
and the interception module is used for intercepting the REST interface address corresponding to the REST interface request in the section.
The service system log recording method and system based on the SDK package have the advantages that log recording work of the service system is achieved through the plug-in SDK package mode, reusability of log functions is improved, and redundant codes are reduced. The method has the advantages that the log record is simplified, and meanwhile, the accuracy and comprehensiveness of the log are guaranteed.
Drawings
Fig. 1 is a flowchart of a service system logging method based on SDK packets according to the present invention.
Detailed Description
The invention is described in detail below with reference to the figures and the embodiments.
Fig. 1 shows a service system log recording method based on SDK packet of the present invention, which mainly includes the following steps: step S1: and carrying out first labeling on the classes and the methods obtained from the service layer through the SDK packet, assembling the classes and the methods to generate a labeled object, and storing the labeled object in a redis cache. Step S2: and the gateway service layer intercepts the REST interface address from the front-end service layer, and matches a corresponding annotation object from the redis cache through the REST interface address. Step S3: and the gateway service layer analyzes the matched labeled object to obtain an analysis result. Step S4: and the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address. Step S5: and the gateway service layer assembles the analysis result, the REST interface input parameter and the REST interface output parameter into an operation log and stores the operation log in a database. Through the steps, the log recording work of the service system is realized in a plug-in sdk package mode, the reusability of the log function is improved, and redundant codes are reduced. The method has the advantages that the log record is simplified, and meanwhile, the accuracy and comprehensiveness of the log are guaranteed. The above method is specifically described below.
For step S1: and carrying out first labeling on the classes and the methods obtained from the service layer through the SDK packet, assembling the classes and the methods to generate a labeled object, and storing the labeled object in a redis cache.
The specific method for performing first labeling on the classes and methods obtained from the service layer through the SDK packet, assembling the classes and methods to generate labeled objects, and storing the labeled objects in the redis cache comprises the following steps:
s11: and carrying out first labeling on the classes and the methods obtained from the business service layer.
In the present application, in a first labeling of a class and a method obtained from a business service layer: and performing WriteLog labeling on the classes and the methods acquired from the business service layer. Subsequent scans are directed to classes and methods with WriteLog labels.
Further, a specific method for performing the first labeling on the class and the method obtained from the business service layer is as follows: and marking three attributes of name, operation and writeUser for the class and the method obtained from the service layer.
As described in Table one, the name attribute is used to define the module name. The operation attribute is used to define the operation name. The writeUser attribute is used to define whether user information needs to be recorded. Wherein the name attribute is a must fill attribute. When the label is added on the class name, the name attribute defines the name of the primary module, and when the label is loaded on the method, the name attribute defines the name of the secondary module. The primary module name and the secondary module name are assembled when logging. The operation attribute defines the name of the operation, for example: query, add, modify, delete, import, export, etc. The writeUser attribute is used for marking whether the user information needs to be recorded in the log, and the attribute is not set to indicate that the user information does not need to be recorded. When the writeUser attribute is "true", it indicates that user information needs to be recorded, and when it is "false", it indicates that user information does not need to be recorded.
Table-first labeled Attribute Specification
| Properties | Name (R) | Must fill in | Remarks for note |
| name | Name of module | Is that | Class (c): a first-level module; the method comprises the following steps: two-stage module |
| operation | Name of operation | Whether or not | Query, add, modify, delete, import, export, etc |
| writeUser | Whether to record the user | Whether or not | Recording true; false: not recording; |
s12: all classes with the first label and methods with the first label in the class are scanned. When the application service starts, the writeLog annotation scanner is added to the launch class. The main function is to automatically invoke the writeLog annotation scanner when the business service is started. It can be specified that the directory is scanned or that all classes are scanned. The case of scanning directories is not specified to scan all classes by default.
S13: and analyzing the scanned labels of the classes and the methods to obtain the attributes marked on the classes and the methods.
After all classes are obtained, filtering the classes with the writeLog labels from the obtained classes, analyzing the scanned classes with the writeLog labels, and obtaining all methods in the classes. And analyzing the method in the obtained method list, and further obtaining the method with the writeLog label on the method. These writeLog labels are parsed to obtain attributes labeled on classes and methods.
S14: and acquiring the REST interface address corresponding to the method.
And assembling the url on the class and the method into the REST interface address.
S15: and assembling the REST interface address and the attributes marked on the class and the method into a marked object.
S16: and calling a redis cache and saving the annotation object into the redis cache.
For step S2: and the gateway service layer intercepts the REST interface address from the front-end service layer, and matches a corresponding annotation object from the redis cache through the REST interface address.
The specific method for intercepting the REST interface address from the front-end service layer by the gateway service layer is as follows: and the gateway service layer intercepts the REST interface request through a section. And the gateway service layer intercepts the REST interface address corresponding to the REST interface request in a section.
And matching a corresponding label object with the same REST interface address from the redis cache through the intercepted REST interface address.
For step S3: and the gateway service layer analyzes the matched labeled object to obtain an analysis result.
And analyzing the obtained labeling object to obtain an analysis result. The analysis result contains the labeled information, namely the name attribute, the operation attribute and the writeUser attribute.
For step S4: and the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address.
The specific method for the gateway service layer to acquire REST interface entry and exit corresponding to the REST interface address is as follows:
and the gateway service layer analyzes the intercepted parameters of the REST interface request and intercepts the REST interface access parameters.
And the gateway service layer forwards the REST interface request to the service layer, and after the service processing is finished, the gateway service layer acquires interface return information to obtain the REST interface reference.
For step S5: and the gateway service layer assembles the analysis result, the REST interface input parameter and the REST interface output parameter into an operation log and stores the operation log in a database.
And the gateway service layer assembles an operation log according to the analyzed name attribute, operation attribute, writeUser attribute, REST interface input parameter and REST interface output parameter and stores the operation log in a database.
The invention also discloses a service system log recording system based on the SDK packet, which is used for realizing the service system log recording method based on the SDK packet. The service system log recording system based on the SDK packet comprises: the system comprises a front-end service layer, a gateway service layer, a service layer, an SDK package, a redis cache and a database.
The SDK package is used for carrying out first labeling on the classes and the methods obtained from the service layer, assembling the classes and the methods to generate a labeled object, and storing the labeled object in a redis cache. The gateway service layer is used for intercepting the REST interface address from the front-end service layer and matching a corresponding annotation object from the redis cache through the REST interface address. And the gateway service layer analyzes the matched labeled object to obtain an analysis result. And the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address. And the gateway service layer assembles the analysis result, the REST interface input reference and the REST interface output reference into an operation log and stores the operation log in a database.
As a preferred embodiment, the SDK package includes: the device comprises a marking module, a scanning module and a calling module.
The labeling module is used for carrying out first labeling on the classes and the methods obtained from the business service layer. The scanning module is used for scanning all classes with first labels and methods with the first labels in the classes, analyzing the labels of the scanned classes and methods to obtain attributes marked on the classes and methods, acquiring REST interface addresses corresponding to the methods, and assembling the REST interface addresses and the attributes marked on the classes and methods into marked objects. The calling module is used for calling the redis cache and storing the labeled object in the redis cache.
In a preferred embodiment, the annotation module performs WriteLog annotation on classes and methods obtained from the business service layer. Subsequent scans are directed to classes and methods with WriteLog labels. The specific method for carrying out the first labeling on the classes and the methods obtained from the business service layer comprises the following steps: and marking three attributes of name, operation and writeUser for the class and the method obtained from the service layer.
As a preferred embodiment, the gateway service layer includes: the device comprises an interception module and an interception module.
The interception module is used for intercepting the REST interface request through the section. And the interception module is used for intercepting the REST interface address corresponding to the REST interface request in the section.
The foregoing illustrates and describes the principles, general features, and advantages of the present invention. It should be understood by those skilled in the art that the above embodiments do not limit the present invention in any way, and all technical solutions obtained by using equivalent alternatives or equivalent variations fall within the scope of the present invention.
Claims (10)
1. A service system log recording method based on an SDK packet is characterized by comprising the following steps:
carrying out first labeling on the classes and the methods obtained from the service layer through the SDK packet, assembling the classes and the methods to generate labeled objects, and storing the labeled objects in a redis cache;
the gateway service layer intercepts an REST interface address from a front-end service layer, and matches the corresponding label object from the redis cache through the REST interface address;
the gateway service layer analyzes the matched labeled object to obtain an analysis result;
the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address;
and the gateway service layer assembles the analysis result, the REST interface input reference and the REST interface output reference into an operation log and stores the operation log in a database.
2. The SDK packet-based service system logging method of claim 1,
the specific method for performing first labeling and assembling on the classes and methods obtained from the service layer through the SDK packet to generate a labeled object and storing the labeled object in the redis cache comprises the following steps:
carrying out first labeling on the class and the method obtained from the business service layer;
scanning all classes with first labels and methods with the first labels in the classes;
analyzing the labels of the scanned classes and methods to obtain attributes labeled on the classes and methods;
acquiring the REST interface address corresponding to the method;
assembling the REST interface address and attributes marked on the class and the method into the marked object;
and calling a redis cache and storing the labeling object into the redis cache.
3. The SDK packet-based service system logging method of claim 2,
in the first labeling of the class and the method obtained from the business service layer:
and performing WriteLog labeling on the class and the method acquired from the service layer.
4. The SDK packet-based service system logging method of claim 2,
the specific method for carrying out the first labeling on the class and the method obtained from the business service layer comprises the following steps:
marking three attributes of name, operation and writeUser to the class and the method obtained from the service layer;
the name attribute is used for determining the module name;
the operation attribute is used for defining an operation name;
the writeUser attribute is used to define whether user information needs to be recorded.
5. The SDK packet-based service system logging method of claim 1,
the specific method for intercepting the REST interface address from the front-end service layer by the gateway service layer is as follows:
the gateway service layer intercepts the REST interface request through a section;
and the gateway service layer intercepts the REST interface address corresponding to the REST interface request in a section.
6. The SDK packet-based service system logging method of claim 5,
the specific method for the gateway service layer to acquire the REST interface entry and the REST interface exit corresponding to the REST interface address is as follows:
the gateway service layer analyzes the intercepted parameters of the REST interface request and intercepts the access parameters of the REST interface;
and the gateway service layer forwards the REST interface request to the service layer, and after the service processing is finished, the gateway service layer acquires interface return information to obtain the output of the REST interface.
7. A service system logging system based on SDK packets, comprising: the system comprises a front-end service layer, a gateway service layer, a service layer, an SDK packet, a redis cache and a database;
the SDK packet is used for carrying out first labeling on the classes and the methods obtained from the service layer, assembling the classes and the methods to generate a labeled object and storing the labeled object in the redis cache;
the gateway service layer is used for intercepting an REST interface address from the front-end service layer and matching the corresponding annotation object from the redis cache through the REST interface address;
the gateway service layer analyzes the matched labeled object to obtain an analysis result;
the gateway service layer also acquires REST interface entry and REST interface exit corresponding to the REST interface address;
and the gateway service layer assembles the analysis result, the REST interface input parameters and the REST interface output parameters into an operation log and stores the operation log in the database.
8. The SDK packet-based services system logging system of claim 7,
the SDK packet includes:
the marking module is used for carrying out first marking on the classes and the methods obtained from the business service layer;
the scanning module is used for scanning all classes with first labels and methods with the first labels in the classes, analyzing the labels of the scanned classes and methods to obtain attributes marked on the classes and methods, acquiring the REST interface address corresponding to the method, and assembling the REST interface address and the attributes marked on the classes and methods into the marked object;
and the calling module is used for calling the redis cache and storing the labeled object in the redis cache.
9. The SDK packet-based services system logging system of claim 8,
and the marking module carries out WriteLog marking on the class and the method acquired from the service layer.
10. The SDK packet-based services system logging system of claim 7,
the gateway service layer includes:
the interception module is used for intercepting the REST interface request through a section;
and the interception module is used for intercepting the REST interface address corresponding to the REST interface request in a section.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011212102.1A CN112328568B (en) | 2020-11-03 | 2020-11-03 | Service system log recording method and system based on SDK package |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011212102.1A CN112328568B (en) | 2020-11-03 | 2020-11-03 | Service system log recording method and system based on SDK package |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112328568A true CN112328568A (en) | 2021-02-05 |
| CN112328568B CN112328568B (en) | 2023-06-02 |
Family
ID=74323329
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011212102.1A Active CN112328568B (en) | 2020-11-03 | 2020-11-03 | Service system log recording method and system based on SDK package |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112328568B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113486370A (en) * | 2021-06-25 | 2021-10-08 | 杭州天宽科技有限公司 | Android log auditing system and method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160070894A1 (en) * | 2014-09-07 | 2016-03-10 | Michael Boodaei | Authentication method and system using password as the authentication key |
| CN108038039A (en) * | 2017-12-04 | 2018-05-15 | 泰康保险集团股份有限公司 | The method and micro services system of record log |
| CN108376181A (en) * | 2018-04-24 | 2018-08-07 | 丹阳飓风物流股份有限公司 | Log services platform based on ELK |
| CN109756364A (en) * | 2018-12-07 | 2019-05-14 | 成都四方伟业软件股份有限公司 | A kind of micro services performance optimization system and analysis method based on log analysis |
| US20200250172A1 (en) * | 2019-01-31 | 2020-08-06 | Salesforce.Com, Inc. | Scalable event sourcing datastore |
| CN111611320A (en) * | 2020-06-17 | 2020-09-01 | 天津异乡好居网络科技有限公司 | Method for counting data based on log service package and storage medium |
-
2020
- 2020-11-03 CN CN202011212102.1A patent/CN112328568B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160070894A1 (en) * | 2014-09-07 | 2016-03-10 | Michael Boodaei | Authentication method and system using password as the authentication key |
| CN108038039A (en) * | 2017-12-04 | 2018-05-15 | 泰康保险集团股份有限公司 | The method and micro services system of record log |
| CN108376181A (en) * | 2018-04-24 | 2018-08-07 | 丹阳飓风物流股份有限公司 | Log services platform based on ELK |
| CN109756364A (en) * | 2018-12-07 | 2019-05-14 | 成都四方伟业软件股份有限公司 | A kind of micro services performance optimization system and analysis method based on log analysis |
| US20200250172A1 (en) * | 2019-01-31 | 2020-08-06 | Salesforce.Com, Inc. | Scalable event sourcing datastore |
| CN111611320A (en) * | 2020-06-17 | 2020-09-01 | 天津异乡好居网络科技有限公司 | Method for counting data based on log service package and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 王建辉;李涛;: "基于Hive的支付SDK日志分析系统的设计研究", 计算机应用与软件 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113486370A (en) * | 2021-06-25 | 2021-10-08 | 杭州天宽科技有限公司 | Android log auditing system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112328568B (en) | 2023-06-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6694307B2 (en) | System for collecting specific information from several sources of unstructured digitized data | |
| US7668849B1 (en) | Method and system for processing structured data and unstructured data | |
| CN111259067B (en) | Method, device and equipment for realizing DAO interface based on Spring | |
| US7370028B2 (en) | Method of and system for providing namespace based object to XML mapping | |
| CN110377651B (en) | Batch data processing method, device, equipment and storage medium | |
| KR20030084245A (en) | Reversed Search Engine | |
| US6205576B1 (en) | Method and apparatus for identifying indirect messaging relationships between software entities | |
| CN111475694A (en) | Data processing method, device, terminal and storage medium | |
| CN112688810B (en) | Network asset information acquisition method, equipment and readable storage medium | |
| CN111008020A (en) | Method for analyzing logic expression into general query statement | |
| CN112287013A (en) | Data conversion method and adapter | |
| CN110716866B (en) | Code quality scanning method, device, computer equipment and storage medium | |
| CN113901083A (en) | Heterogeneous data source operation resource analysis positioning method and equipment based on multiple analyzers | |
| CN112328568B (en) | Service system log recording method and system based on SDK package | |
| CN110826057A (en) | Data processing path analysis method, computer device, and storage medium | |
| CN113626558B (en) | Intelligent recommendation-based field standardization method and system | |
| CN113868698A (en) | File desensitization method and equipment | |
| CN113407511A (en) | Log aggregation method, log aggregation equipment and computer program product | |
| CN113987337A (en) | Search method, system, equipment and storage medium based on componentized dynamic arrangement | |
| CN116795486A (en) | Analysis method and device for container mirror image file purification, storage medium and terminal | |
| CN114281875A (en) | Database adaptation device and method based on dynamic multiple data sources | |
| CN113050987B (en) | Method and device for generating interface document, storage medium and electronic equipment | |
| CN114157439A (en) | Vulnerability scanning method, computing device and recording medium | |
| CN114629807A (en) | Work order processing method, device and equipment | |
| CN112612477B (en) | Service implementation method, device, equipment and storage medium |
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 |