CN105099735B - A kind of method and system for obtaining magnanimity more detailed logging - Google Patents
A kind of method and system for obtaining magnanimity more detailed logging Download PDFInfo
- Publication number
- CN105099735B CN105099735B CN201410190188.0A CN201410190188A CN105099735B CN 105099735 B CN105099735 B CN 105099735B CN 201410190188 A CN201410190188 A CN 201410190188A CN 105099735 B CN105099735 B CN 105099735B
- Authority
- CN
- China
- Prior art keywords
- log
- positioning
- service
- server
- message
- 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 24
- 238000004458 analytical method Methods 0.000 claims abstract description 61
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 101001091385 Homo sapiens Kallikrein-6 Proteins 0.000 description 1
- 102100034866 Kallikrein-6 Human genes 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a kind of methods for obtaining magnanimity more detailed logging, and location-server is set on daily record generation server, the described method includes：Daily record generation server is sent to log analysis platform according to the positioning service generation business more detailed logging that location-server provides and positioning message daily record, and by positioning message daily record；After the corresponding positioning message daily record of log analysis platform inquiry business mark, positioning message daily record is sent to each daily record and generates server；Log pointer position, offset and message identifier of the log analysis platform in positioning message daily record obtain the corresponding more detailed logging of service identification.The invention also discloses a kind of systems for obtaining magnanimity more detailed logging.
Description
Technical Field
The present invention relates to a service processing technology, and in particular, to a method and system for acquiring a large number of detailed logs.
Background
With frequent Operation of services in a service Operation Support System (BOSS) and increasingly complex service processing processes, the number of service detailed logs for service acceptance through a service Support network is increased rapidly, so that service detailed log files are more and more huge, and the space of a disk is seriously insufficient; when business query is carried out, a log generation server needs to be logged to check detailed logs, and specific logs can be located through screening, searching and manual checking processes; therefore, when massive log file data are collected, huge network broadband resources are occupied, and the use of other system functions is influenced; the log can not be automatically inquired and filtered completely, huge manpower is wasted, and the working efficiency is reduced.
Disclosure of Invention
In view of this, embodiments of the present invention are expected to provide a method and a system for acquiring massive detailed logs, so that a large amount of log contents do not need to be stored on a server, and required detailed logs can be queried and acquired without manually filtering the log contents.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
the embodiment of the invention provides a method for acquiring massive detailed logs, wherein a positioning server is arranged on a log generation server, and the method comprises the following steps: the log generation server generates a service detailed log and a positioning message log according to the positioning service provided by the positioning server, and sends the positioning message log to a log analysis platform; after the log analysis platform inquires the positioning message log corresponding to the service identifier, sending the positioning message log to each log generation server; and the log analysis platform acquires the service detailed log according to the log pointer position, the offset and the message identifier in the positioning message log.
Preferably, before the log analysis platform sends the location message log to each log generation server, the method further includes: and the log analysis platform stores the positioning message log corresponding to the service identifier.
Preferably, the log generating server generates a service detail log and a positioning packet log according to a positioning service provided by the positioning server, and sends the positioning packet log to the log analysis platform, including: when the service is in progress, the log generation server calls a service application program and a positioning server, and generates a service detailed log and a positioning message log according to a positioning service provided by the positioning server; and the positioning server sends the positioning message log to a log analysis platform.
Preferably, the positioning message log comprises: log pointer location, offset, and message identification.
Preferably, the service detail log is: the first character of the service detail log is the next character of the log pointer position, and the number of characters between the last character of the service detail log and the first character of the service detail log is equal to the offset.
The embodiment of the invention provides a system for acquiring massive detailed logs, which comprises: the log generation server comprises a positioning server and is used for generating a service detailed log and a positioning message log according to positioning service provided by the positioning server and sending the positioning message log to a log analysis platform;
the log analysis platform comprises an acquisition server and a network server; wherein,
the acquisition server is used for inquiring the positioning message logs corresponding to the service identifiers and sending the positioning message logs to each log generation server;
and the network server is used for acquiring the service detailed log according to the log pointer position, the offset and the message identifier in the positioning message log.
Preferably, the log analysis platform further includes a database, configured to store a location packet log corresponding to the service identifier.
Preferably, the log generating server generates a service detail log and a positioning packet log according to a positioning service provided by the positioning server, and sends the service detail log and the positioning packet log to the log analysis platform, and includes: when the service is in progress, the log generation server calls a service application program and a positioning server, and generates a service detailed log and a positioning message log according to a positioning service provided by the positioning server; and the positioning server sends the positioning message log to a log analysis platform.
Preferably, the positioning message log obtained by the collecting server includes: log pointer location, offset, and message identification.
Preferably, the service detail log obtained by the network server is: the first character of the service detail log is the next character of the log pointer position, and the number of characters between the last character of the service detail log and the first character of the service detail log is equal to the offset.
According to the method and the system for acquiring massive detailed logs, the log generation server is provided with the positioning server, and generates the service detailed logs and the positioning message logs and sends the service detailed logs and the positioning message logs to the log analysis platform; after the log analysis platform inquires the positioning message log corresponding to the service identifier, sending the positioning message log to each log generation server; the log analysis platform acquires a detailed log corresponding to the service identifier according to the log pointer position, the offset and the message identifier in the positioning message log; therefore, the positioning information of the same service can be automatically gathered, a large amount of log contents do not need to be stored on the server, and only simple message data need to be stored to inform the specific pointer position and offset; the log content is not required to be manually filtered, and when a user needs to obtain the corresponding detailed log, the required detailed log can be inquired and obtained; the influence of network bandwidth on other systems is reduced, and human resources are saved.
Drawings
FIG. 1 is a schematic diagram of a basic flow of a method for acquiring massive detailed logs according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a basic flow of a log generation server generating a detailed log and a positioning message log and sending the detailed log and the positioning message log to a log analysis platform according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a detailed processing flow of a method for acquiring massive detailed logs according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a system composition structure for acquiring a large number of detailed logs according to an embodiment of the present invention.
Detailed Description
In the embodiment of the invention, a positioning server is arranged on a log generation server, the log generation server generates a service detailed log and a positioning message log according to a positioning service provided by the positioning server, and sends the positioning message log to a log analysis platform; after the log analysis platform inquires the positioning message log corresponding to the service identifier, sending the positioning message log to each log generation server; and the log analysis platform acquires a detailed log corresponding to the service identifier according to the log pointer position, the offset and the message identifier in the positioning message log.
Here, the log analysis platform obtains a detailed log corresponding to the service identifier according to the log pointer position, the offset and the message identifier in the positioning message log, and specifically includes: the log analysis platform searches the name of a positioning service fuzzy matching file in the positioning message log to obtain a query file; and acquiring a detailed log corresponding to the service identifier according to the log pointer position, the offset and the message identifier in the query file.
The basic flow of the method for acquiring massive detailed logs in the embodiment of the invention, as shown in fig. 1, comprises the following steps:
step 101, setting a positioning server on a log generation server;
the positioning server is a program with a positioning function.
102, a log generation server generates a service detailed log and a positioning message log according to a positioning service provided by a positioning server, and sends the positioning message log to a log analysis platform;
specifically, a basic flow of generating a service detailed log and a positioning message log by the log generation server and sending the positioning message log to the log analysis platform is shown in fig. 2, and includes the following steps:
step 1a, when a service is in progress, a log generation server calls a service application program and a positioning server, and generates a service detailed log and a positioning message log according to a positioning service provided by the positioning server;
here, the file name of the service detail log is: MDLOG < application identification > < YYYYMMDDHH24MISS >; wherein,
the application identifier is an eight-digit number, YYYY is the year of the occurrence of the service, MM is the month of the occurrence of the service, DD is the date of the occurrence of the service, and HH24MISS is the time of the occurrence of the service;
each field in the service detail log is separated by a field separator, and the field separator is a character '|'; the three fields of the pointer position, the offset and the service identifier in the service detail log are separated by characters ',' and a plurality of records of the same service identifier are separated by characters ':'; the character symbol set in the service detail log adopts GBK coding; wherein, the data length field defines the maximum length and data type of the field;
here, the description of some fields in each field included in the service detail log is specifically shown in table 1:
TABLE 1
Here, the location message log includes, but is not limited to: the name of the positioning service fuzzy matching file and the application identification corresponding to the positioning service matching are matched; wherein, the content of the positioning message log starts with a character '<' and ends with a character '>';
table 2 is a description of a part of fields included in the positioning message log, as shown in table 2:
TABLE 2
Here, since one service may need to call a plurality of applications, and the plurality of applications may be deployed on a plurality of different log generation servers, in this embodiment, the log generation servers are distributed.
And step 1b, the positioning server outputs a positioning message log of the current service.
Step 1c, the positioning server sends the positioning message log to a log analysis platform according to a reliable queue program used by the log analysis platform;
here, the reliable queue program is a message middleware written by using a C + + programming language by adopting an Apache server software authorization mechanism; the functions realized by the reliable queue program comprise: providing multi-queue and multi-priority message forwarding service for a log analysis platform, supporting transaction operation, supporting Java and Hypertext Preprocessor (PHP) clients, supporting Secure Socket Layer (SSL) encryption and user privileges, and supporting Time To Live (TTL) timestamps; wherein the forwarding service can be message forwarding among a plurality of message middleware; the message may be in binary form or in text form.
Step 1d, a reliable queue program of a log analysis platform receives and stores a positioning message log of a service;
here, the log analysis platform stores the received positioning message log into a database of the log analysis platform.
103, the log analysis platform inquires a positioning message log corresponding to the service identifier and sends the positioning message log to each log generation server;
here, the log analysis platform queries all positioning message logs corresponding to the service identifier through a database;
further, the log generation server corresponding to the application program called by the service is searched in a corresponding table of the application identifier and the log generation server existing in the log analysis platform.
Step 104, the log analysis platform acquires a service detailed log according to the position of a log pointer, the offset and the message identifier in the positioning message log;
specifically, the log analysis platform searches the name of a positioning service fuzzy matching file in the positioning message log on a log generation server according to a preset detailed log storage directory to obtain a query file;
the query file comprises: log pointer location, offset, and message identification;
the latter character of the log pointer position is the first character of the service detail log, and the number of characters between the last character of the service detail log and the first character of the service detail log is equal to the offset.
The detailed flow of the method for acquiring massive detailed logs in the embodiment of the invention, as shown in fig. 3, includes the following steps:
step 201, setting a positioning server on a log generation server;
the positioning server is a program with a positioning function.
Step 202, the log generation server generates a service detail log and a positioning message log according to a positioning service provided by the positioning server, and sends the positioning message log to a log analysis platform;
specifically, the processing flow of the log generation server generating the service detailed log and the positioning message log and sending the positioning message log to the log analysis platform is the same as the processing flow in fig. 2, and is not repeated here;
here, since one service may need to call a plurality of applications, and the plurality of applications may be deployed on a plurality of different log generation servers, in this embodiment, the log generation servers are distributed.
Step 203, the log analysis platform inquires the positioning message log corresponding to the service identifier and sends the positioning message log to each log generation server;
here, the log analysis platform queries all positioning message logs corresponding to the service identifier through a database;
taking an example where two applications are invoked for a transaction, the first application identifier is: 49918011, the second application is identified as: 49915111, respectively;
obtaining a positioning message log of the first application by querying a database: <11|499151110210170004108159|1|49918011|8712_20131113075919255|30000222|0,797,1:797,849,1.1:1646,1082,1.1:2728,1205,1.2:3933,432,1.2:4365,379,1: >;
8712_20131113075919255 is the name of the positioning service fuzzy matching file in the positioning message log;
obtaining the positioning message log of the second application by querying the database: <11|499151110210170004108159|1|49915111|2552_20131113065342596|30000345|162641,1012,:163653,795,1:164448,377,1:164825,706';
wherein 2552_20131113065342596 blurs the name of the matching file for the location service in the location message log.
Step 204, the log analysis platform searches a log generation server corresponding to the first application and a log generation server corresponding to the second application;
here, a log generation server corresponding to the first application and a log generation server corresponding to the second application are searched in a correspondence table of an existing application identifier and the log generation server in the log analysis platform;
specifically, the first application identifier is: 49918011, respectively; the found log generation server network Protocol (Internet Protocol, IP) corresponding to the first application is: 10.46.154.216, respectively;
the second application identification is: 49915111, respectively; the IP of the log generation server corresponding to the second application is found as follows: 10.46.154.241.
step 205, the log analysis platform searches the name of the positioning service fuzzy matching file in the positioning message log to obtain a query file;
here, the log analysis platform searches the names of the positioning service fuzzy matching files in the positioning message logs on a log generation server corresponding to the first application and a log generation server corresponding to the second application to obtain query files;
specifically, the first application identifier is used for searching a file name: 8712_20131113075919255, the obtained query file name is: MDLog _49918011_ BSSP _ SFC-8712_20131113075919255, Dat, where the file has four positioning message logs, the contents of the four positioning message logs are: 0,797,1:797,849,1.1:1646,1082,1.1:2728,1205,1.2.
Step 206, the log analysis platform obtains a service detailed log according to the log pointer position, the offset and the message identifier in the query file;
the latter character of the log pointer position is the first character of the service detail log, and the number of characters between the last character of the service detail log and the first character of the service detail log is equal to the offset;
specifically, the first pointer position is 0,797,1, the message identifier is 1, the file is opened, starting from the first character, and counting to the 797 th character is finished, and the file is a detailed log of the first pointer position;
the second pointer position is 797,849,1.1, the message identifier is 1.1, the file is opened, the file is calculated from the 798 th character to the 849 th character, and the file is a detailed log of the second pointer position;
the third pointer position is 1646,1082,1.1, the message identifier is 1.1, the file is opened, the detail log of the third pointer position is obtained from the 1647 th character, the calculation is completed by the 1082 th character;
the fourth pointer position is 2728,1205,1.2, the message identifier is 1.2, the file is opened, starting at 2729 characters, counting to 1205 characters ending as a detailed log of the fourth pointer position.
In order to implement the method for acquiring massive detailed logs, an embodiment of the present invention further provides a system for acquiring massive detailed logs, where a composition structure of the system, as shown in fig. 4, includes a log generation server 10 and a log analysis platform 20; wherein,
the log generating server 10 comprises a positioning server, and is configured to generate a service detail log and a positioning message log according to a positioning service provided by the positioning server, and send the positioning message log to the log analyzing platform 20;
here, since one service may need to call a plurality of applications, and the plurality of applications may be deployed on a plurality of different log generation servers, in this embodiment, the log generation servers are distributed.
A log analysis platform 20, including a collection server 20a, a database 20b and a network server 20 c; wherein,
the acquisition server 20a is configured to send the positioning message log to each log generation server after querying the positioning message log corresponding to the service identifier;
the database 20b is used for storing a positioning message log corresponding to the service identifier;
and the network server 20c is configured to search the log pointer position, the offset and the message identifier in the positioning message log, and obtain a service detail log according to the search result.
Further, the log generating server 10 generates a service detail log and a positioning message log according to a positioning service provided by a positioning server, and sends the positioning message log to the log analyzing platform 20, including:
when a service is in progress, the log generation server 10 calls a service application program and a positioning server, and generates a service detailed log and a positioning message log according to a positioning service provided by the positioning server;
the location server sends the location message log to the log analysis platform 20.
Further, the file name of the detailed log generated by the log generation server 10 is: MDLOG < application identification > < YYYYMMDDHH24MISS >; wherein,
the application identifier is an eight-digit number, YYYY is the year the service occurred, MM is the month the service occurred, DD is the date the service occurred, HH24MISS is the time the service occurred.
Further, the positioning message log obtained by the collecting server 20b includes: log pointer location, offset, and message identification.
Further, the service detail log obtained by the network server 20c is: the first character of the service detail log is the next character of the log pointer position, and the number of characters between the last character of the service detail log and the first character of the service detail log is equal to the offset.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (10)
1. A method for obtaining a mass of detailed logs is characterized in that a positioning server is arranged on a log generation server; the method further comprises the following steps:
the log generation server generates a service detailed log and a positioning message log according to the positioning service provided by the positioning server, and sends the positioning message log to a log analysis platform;
after the log analysis platform inquires the positioning message log corresponding to the service identifier, sending the positioning message log to each log generation server;
and the log analysis platform acquires the service detailed log according to the log pointer position, the offset and the message identifier in the positioning message log.
2. The method for obtaining massive detailed logs according to claim 1, wherein before the log analysis platform sends the positioning message logs to each log generation server, the method further comprises:
and the log analysis platform stores the positioning message log corresponding to the service identifier.
3. The method for obtaining massive detailed logs according to claim 1, wherein the log generating server generates the service detailed logs and the positioning message logs according to a positioning service provided by a positioning server, and sends the positioning message logs to a log analyzing platform, comprising:
when the service is in progress, the log generation server calls a service application program and a positioning server, and generates a service detailed log and a positioning message log according to a positioning service provided by the positioning server;
and the positioning server sends the positioning message log to a log analysis platform.
4. The method for obtaining massive detailed logs according to claim 1, wherein the positioning the message log comprises: log pointer location, offset, and message identification.
5. The method for obtaining massive detailed logs according to claim 1, wherein the service detailed logs are:
the first character of the service detail log is the next character of the log pointer position, and the number of characters between the last character of the service detail log and the first character of the service detail log is equal to the offset.
6. A system for obtaining a mass of detailed logs, the system comprising: the system comprises a log generation server and a log analysis platform; wherein,
the log generation server comprises a positioning server and is used for generating a service detailed log and a positioning message log according to positioning service provided by the positioning server and sending the positioning message log to a log analysis platform;
the log analysis platform comprises an acquisition server and a network server; wherein,
the acquisition server is used for sending the positioning message logs to each log generation server after inquiring the positioning message logs corresponding to the service identifiers;
and the network server is used for acquiring the service detailed log according to the log pointer position, the offset and the message identifier in the positioning message log.
7. The system for obtaining massive detailed logs according to claim 6, wherein the log analysis platform further comprises a database for storing the positioning message log corresponding to the service identifier.
8. The system for acquiring massive detailed logs according to claim 6, wherein the log generation server generates the service detailed logs and the positioning message logs according to the positioning service provided by the positioning server, and sends the service detailed logs and the positioning message logs to the log analysis platform, and the system comprises:
when the service is in progress, the log generation server calls a service application program and a positioning server, and generates a service detailed log and a positioning message log according to a positioning service provided by the positioning server;
and the positioning server sends the positioning message log to a log analysis platform.
9. The system for acquiring massive detailed logs according to claim 6, wherein the positioning message log acquired by the acquisition server comprises: log pointer location, offset, and message identification.
10. The system for acquiring massive detailed logs according to claim 6, wherein the service detailed logs acquired by the network server are:
the first character of the service detail log is the next character of the log pointer position, and the number of characters between the last character of the service detail log and the first character of the service detail log is equal to the offset.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410190188.0A CN105099735B (en) | 2014-05-07 | 2014-05-07 | A kind of method and system for obtaining magnanimity more detailed logging |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410190188.0A CN105099735B (en) | 2014-05-07 | 2014-05-07 | A kind of method and system for obtaining magnanimity more detailed logging |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105099735A CN105099735A (en) | 2015-11-25 |
| CN105099735B true CN105099735B (en) | 2018-05-22 |
Family
ID=54579361
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410190188.0A Active CN105099735B (en) | 2014-05-07 | 2014-05-07 | A kind of method and system for obtaining magnanimity more detailed logging |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105099735B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108234166A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | A kind of data processing method and management equipment |
| CN108712363B (en) * | 2018-03-22 | 2021-04-20 | 新华三信息安全技术有限公司 | Log encryption and decryption method |
| CN113055760A (en) * | 2019-12-26 | 2021-06-29 | 中兴通讯股份有限公司 | Log processing method, device, equipment and storage medium |
| CN111897834A (en) * | 2020-08-12 | 2020-11-06 | 网易（杭州）网络有限公司 | Log searching method and device and server |
| CN114844923A (en) * | 2022-04-26 | 2022-08-02 | 湖北华宝智通科技有限公司 | Internet of vehicles service quality detection system and method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101594252A (en) * | 2009-06-01 | 2009-12-02 | 中兴通讯股份有限公司 | A kind of massive logs storage management system and method |
| CN102724063A (en) * | 2012-05-11 | 2012-10-10 | 北京邮电大学 | Log collection server, data packet delivering and log clustering methods and network |
| CN103064933A (en) * | 2012-12-24 | 2013-04-24 | 华为技术有限公司 | Data query method and system |
| CN103532754A (en) * | 2013-10-12 | 2014-01-22 | 北京首信科技股份有限公司 | System and method for high-speed memory and distributed type processing of massive logs |
-
2014
- 2014-05-07 CN CN201410190188.0A patent/CN105099735B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101594252A (en) * | 2009-06-01 | 2009-12-02 | 中兴通讯股份有限公司 | A kind of massive logs storage management system and method |
| CN102724063A (en) * | 2012-05-11 | 2012-10-10 | 北京邮电大学 | Log collection server, data packet delivering and log clustering methods and network |
| CN103064933A (en) * | 2012-12-24 | 2013-04-24 | 华为技术有限公司 | Data query method and system |
| CN103532754A (en) * | 2013-10-12 | 2014-01-22 | 北京首信科技股份有限公司 | System and method for high-speed memory and distributed type processing of massive logs |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105099735A (en) | 2015-11-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105099735B (en) | A kind of method and system for obtaining magnanimity more detailed logging | |
| JP6599538B2 (en) | Method and apparatus for identifying application information in network traffic | |
| CN108400909B (en) | Traffic statistical method, device, terminal equipment and storage medium | |
| US20180287920A1 (en) | Intercepting application traffic monitor and analyzer | |
| US9210090B1 (en) | Efficient storage and flexible retrieval of full packets captured from network traffic | |
| CN106533838B (en) | Service characteristic time sequence data packet acquisition method facing cloud platform | |
| CN109783426A (en) | Acquire method, apparatus, computer equipment and the storage medium of data | |
| CN107547310B (en) | User behavior correlation analysis method and system based on bypass audit equipment | |
| CN105045905B (en) | A kind of log maintenance method and system based on full-text search | |
| CN112463772B (en) | Log processing method and device, log server and storage medium | |
| US10387370B2 (en) | Collecting test results in different formats for storage | |
| CN104378234A (en) | Cross-data-center data transmission processing method and system | |
| CN106326280B (en) | Data processing method, device and system | |
| CN108322495B (en) | Method, device and system for processing resource access request | |
| CN111224894A (en) | Traffic collection marking method and system for iOS device | |
| CN111737222A (en) | Message queue data packet storage and retrieval method based on one-to-many request response model | |
| US20130311655A1 (en) | Systems and methods for collecting and storing network traffic data | |
| CN110677396A (en) | Security policy configuration method and device | |
| CN109309587A (en) | A kind of log collection method and system | |
| CN110688354B (en) | Analysis method of slow log file in database, terminal and storage medium | |
| CN114338600B (en) | Equipment fingerprint selection method and device, electronic equipment and medium | |
| CN105184559B (en) | A kind of payment system and method | |
| CN110198227B (en) | Log file processing method and device, storage medium and electronic device | |
| CN113395367B (en) | HTTPS service identification method and device, storage medium and electronic equipment | |
| US10545798B2 (en) | Resegmenting chunks of data for efficient load balancing across indexers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |