CN110704378A - Log recording method and log recording system - Google Patents
Log recording method and log recording system Download PDFInfo
- Publication number
- CN110704378A CN110704378A CN201910940739.3A CN201910940739A CN110704378A CN 110704378 A CN110704378 A CN 110704378A CN 201910940739 A CN201910940739 A CN 201910940739A CN 110704378 A CN110704378 A CN 110704378A
- Authority
- CN
- China
- Prior art keywords
- log
- data
- log recording
- database table
- database
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 230000008859 change Effects 0.000 claims abstract description 29
- 230000008569 process Effects 0.000 claims abstract description 17
- 238000012544 monitoring process Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 12
- 230000000737 periodic effect Effects 0.000 claims description 6
- 238000013500 data storage Methods 0.000 abstract description 3
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
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/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- 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
- G06F11/3079—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 the data filtering being achieved by reporting only the changes of the monitored data
-
- 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
Abstract
The invention provides a log recording method and a log recording system, comprising the following steps: converting data consisting of a database table name, a data row ID, a log recording timestamp, an operation type and updated data row content into a json format, and storing the json format by adopting a txt file; when the database table changes, only the changed data rows are stored into the corresponding folders according to the corresponding log storage paths; and the log recording module displays the data of the same data row ID according to the history change process. The advantages are that: (1) when the database table of the tracked record changes, only the changed data rows are recorded, and other data rows which are not changed are not recorded, so that the space occupation condition of data storage can be obviously reduced, and the storage burden of a system is reduced; (2) and hierarchical storage is realized, and the data display efficiency is improved. (3) The decoupling from the service is realized, and the field and logic change of the service system does not have any influence on the log record.
Description
Technical Field
The invention belongs to the technical field of log recording, and particularly relates to a log recording method and a log recording system.
Background
With the development of the internet, a large number of data tables are involved in operation and maintenance of many enterprises and public institutions, and modification operations such as adding, modifying or deleting the data tables are required to be performed frequently. In the prior art, when the content of a certain data table changes, the changed data table is simply recorded, and the data table before the change is not stored. This approach has the following problems: in the operation and maintenance process, the change condition of the data table cannot be traced, so that many problems in the operation and maintenance process are difficult to solve. For example, for the data table a, after the content of the data table a is changed, the data table a is assumed to be changed, and if the data table a and the data table a' are simply stored, when the data table is changed for multiple times, multiple versions of the data table may be stored, which results in a large amount of storage space being occupied.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a log recording method and a log recording system, which can effectively solve the problems.
The technical scheme adopted by the invention is as follows:
the invention provides a log recording method, which comprises the following steps:
step 1, a database table is composed of a plurality of data rows; each of the data lines has a unique corresponding data line ID; each database table has a unique corresponding database table name;
step 2, establishing a list which does not need to be subjected to log recording, and putting the database names which do not need to be subjected to log recording into the list;
step 3, when the system uses the storage function, judging whether the table name of the database needing to be stored is in the table list, if not, executing step 4; if yes, skipping a log recording module and not performing log recording processing;
step 4, the log recording module performs log recording processing, including:
step 4.1, the log recording module converts data composed of database table names, data row IDs, log recording timestamps, operation types and updated data row contents into json format according to data change instructions submitted during storage, the data row IDs of all data rows stored at this time and the updated row contents, and stores the json format by adopting txt files; the file name of the txt file is a log record timestamp;
step 4.2, the log recording module pre-establishes a log storage root directory, then searches the log storage root directory, and judges whether a first-level folder named by the database table name exists in the log storage root directory; if not, executing step 4.3; if so, executing step 4.4;
4.3, the log recording module establishes a first-level folder named by the database table name in the log storage root directory, and then executes the step 4.4;
step 4.4, the log recording module opens the first-level folder named by the database table name, judges whether the first-level folder named by the database table name comprises a second-level folder named by the data row ID, and if the first-level folder does not comprise the second-level folder named by the data row ID, the step 4.5 is executed; if so, performing step 4.6;
step 4.5, the log recording module establishes a second-level folder named by the data row ID in a first-level folder named by the database table name, and then executes step 4.6;
step 4.6, the log recording module writes the txt file obtained in the step 4.1 into a second-level folder named by the data line ID;
therefore, the database table is tracked, and when the database table changes, only the changed data rows are stored into the corresponding folders according to the corresponding log storage paths;
step 5, the windows monitoring service module carries out periodic monitoring scanning on each folder under the log storage root directory, and when a newly written txt file is scanned, a database table name, a data row ID, a log recording time stamp, an operation type and updated data row contents corresponding to the newly written txt file are written into a database log table;
step 6, when the log recording module receives a display request of the change process of the data row of a certain data table, the log recording module searches the database log table and associates all log records corresponding to the data row ID of the same data table; and then, analyzing each log record according to the sequence of the log record time stamps, and displaying the data corresponding to the same data line ID according to the history change process.
Preferably, the method further comprises the following steps:
and the windows monitoring service module monitors the valid period of the txt document in each folder under the log storage root directory, the default valid period is two months, and the txt document exceeding the valid period is automatically deleted.
Preferably, in step 4, the operation types include an addition operation type, a modification operation type and a deletion operation type.
The present invention also provides a log recording system, comprising:
the table list establishing module is used for establishing a table list which does not need to be subjected to log recording and placing the table name of the database which does not need to be subjected to log recording into the table list;
the judging module is used for judging whether the table name of the database needing to be stored is in the table list when the system uses the storing function, and if so, skipping the log recording module and not performing log recording processing; if not, calling the logging module;
a log recording module, configured to perform log recording processing, and specifically configured to:
step 4.1, the log recording module converts data composed of database table names, data row IDs, log recording timestamps, operation types and updated data row contents into json format according to data change instructions submitted during storage, the data row IDs of all data rows stored at this time and the updated row contents, and stores the json format by adopting txt files; the file name of the txt file is a log record timestamp;
step 4.2, the log recording module pre-establishes a log storage root directory, then searches the log storage root directory, and judges whether a first-level folder named by the database table name exists in the log storage root directory; if not, executing step 4.3; if so, executing step 4.4;
4.3, the log recording module establishes a first-level folder named by the database table name in the log storage root directory, and then executes the step 4.4;
step 4.4, the log recording module opens the first-level folder named by the database table name, judges whether the first-level folder named by the database table name comprises a second-level folder named by the data row ID, and if the first-level folder does not comprise the second-level folder named by the data row ID, the step 4.5 is executed; if so, performing step 4.6;
step 4.5, the log recording module establishes a second-level folder named by the data row ID in a first-level folder named by the database table name, and then executes step 4.6;
step 4.6, the log recording module writes the txt file obtained in the step 4.1 into a second-level folder named by the data line ID;
therefore, the database table is tracked, and when the database table changes, only the changed data rows are stored into the corresponding folders according to the corresponding log storage paths;
the windows monitoring service module is used for carrying out periodic monitoring scanning on each folder under the log storage root directory, and writing a database table name, a data row ID, a log recording timestamp, an operation type and updated data row contents corresponding to a newly written txt file into a database log table whenever the newly written txt file is scanned;
the logging module is further configured to: when the log recording module receives a display request of a change process of a data row of a certain data table, the log recording module searches the database log table and associates all log records corresponding to the data row ID of the same data table; and then, analyzing each log record according to the sequence of the log record time stamps, and displaying the data corresponding to the same data line ID according to the history change process.
The log recording method and the log recording system provided by the invention have the following advantages:
(1) when the database table of the tracked record changes, only the changed data rows are recorded, and other data rows which are not changed are not recorded, so that the space occupation condition of data storage can be obviously reduced, and the storage burden of a system is reduced;
(2) the changed data lines are converted into json format, and are stored in an appointed storage path in a txt file, so that the same data line is stored in the same second-level folder; and the second-level folders corresponding to all the rows in the same database table are stored in the same first-level folder, so that hierarchical storage is realized, the change condition of the same data row in the same database table can be quickly associated, the display of the change process of the data row is facilitated, and the data display efficiency is improved.
(3) The decoupling from the service is realized, and the field and logic change of the service system does not have any influence on the log record.
Drawings
Fig. 1 is a schematic flow chart of a log recording method provided by the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantageous effects solved by the present invention more clearly apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention provides a log recording method, which comprises the following steps with reference to fig. 1:
step 1, a database table is composed of a plurality of data rows; each of the data lines has a unique corresponding data line ID; each database table has a unique corresponding database table name;
it should be emphasized here that, for a certain data line, even if it is subjected to a modify operation or a delete operation, its data line ID remains unchanged. The delete operation here is a logical delete.
Step 2, establishing a list which does not need to be subjected to log recording, and putting the database names which do not need to be subjected to log recording into the list;
step 3, when the system uses the storage function, judging whether the table name of the database needing to be stored is in the table list, if not, executing step 4; if yes, skipping a log recording module and not performing log recording processing;
step 4, the log recording module performs log recording processing, including:
step 4.1, the log recording module converts data composed of database table names, data row IDs, log recording timestamps, operation types and updated data row contents into json format according to data change instructions submitted during storage, the data row IDs of all data rows stored at this time and the updated row contents, and stores the json format by adopting txt files; the file name of the txt file is a log record timestamp;
and the timestamp is used for recording, so that the data change of the whole set of service data operated at the same time can be uniformly inquired through the timestamp.
The txt text and json approach is extremely efficient and faster than the rest of the xml or database log analysis.
The operation types comprise an addition operation type, a modification operation type and a deletion operation type.
Step 4.2, the log recording module pre-establishes a log storage root directory, then searches the log storage root directory, and judges whether a first-level folder named by the database table name exists in the log storage root directory; if not, executing step 4.3; if so, executing step 4.4;
4.3, the log recording module establishes a first-level folder named by the database table name in the log storage root directory, and then executes the step 4.4;
step 4.4, the log recording module opens the first-level folder named by the database table name, judges whether the first-level folder named by the database table name comprises a second-level folder named by the data row ID, and if the first-level folder does not comprise the second-level folder named by the data row ID, the step 4.5 is executed; if so, performing step 4.6;
step 4.5, the log recording module establishes a second-level folder named by the data row ID in a first-level folder named by the database table name, and then executes step 4.6;
step 4.6, the log recording module writes the txt file obtained in the step 4.1 into a second-level folder named by the data line ID;
therefore, the database table is tracked, and when the database table changes, only the changed data rows are stored into the corresponding folders according to the corresponding log storage paths;
in the step, the corresponding folder is named directly by the database table ID and the data row ID, so that management is facilitated, and the folder is convenient for a windows monitoring service module to quickly scan in the later period.
Step 5, the windows monitoring service module carries out periodic monitoring scanning on each folder under the log storage root directory, and when a newly written txt file is scanned, a database table name, a data row ID, a log recording time stamp, an operation type and updated data row contents corresponding to the newly written txt file are written into a database log table;
step 6, when the log recording module receives a display request of the change process of the data row of a certain data table, the log recording module searches the database log table and associates all log records corresponding to the data row ID of the same data table; and then, analyzing each log record according to the sequence of the log record time stamps, and displaying the data corresponding to the same data line ID according to the history change process.
And the windows monitoring service module monitors the valid period of the txt document in each folder under the log storage root directory, the default valid period is two months, and the txt document exceeding the valid period is automatically deleted. Therefore, the timeliness of file storage is automatically maintained, and the maintenance of human intervention is reduced. And the log record failure is notified by an automatic alarm mail.
The present invention also provides a log recording system, comprising:
the table list establishing module is used for establishing a table list which does not need to be subjected to log recording and placing the table name of the database which does not need to be subjected to log recording into the table list;
the judging module is used for judging whether the table name of the database needing to be stored is in the table list when the system uses the storing function, and if so, skipping the log recording module and not performing log recording processing; if not, calling the logging module;
a log recording module, configured to perform log recording processing, and specifically configured to:
step 4.1, the log recording module converts data composed of database table names, data row IDs, log recording timestamps, operation types and updated data row contents into json format according to data change instructions submitted during storage, the data row IDs of all data rows stored at this time and the updated row contents, and stores the json format by adopting txt files; the file name of the txt file is a log record timestamp;
step 4.2, the log recording module pre-establishes a log storage root directory, then searches the log storage root directory, and judges whether a first-level folder named by the database table name exists in the log storage root directory; if not, executing step 4.3; if so, executing step 4.4;
4.3, the log recording module establishes a first-level folder named by the database table name in the log storage root directory, and then executes the step 4.4;
step 4.4, the log recording module opens the first-level folder named by the database table name, judges whether the first-level folder named by the database table name comprises a second-level folder named by the data row ID, and if the first-level folder does not comprise the second-level folder named by the data row ID, the step 4.5 is executed; if so, performing step 4.6;
step 4.5, the log recording module establishes a second-level folder named by the data row ID in a first-level folder named by the database table name, and then executes step 4.6;
step 4.6, the log recording module writes the txt file obtained in the step 4.1 into a second-level folder named by the data line ID;
therefore, the database table is tracked, and when the database table changes, only the changed data rows are stored into the corresponding folders according to the corresponding log storage paths;
the windows monitoring service module is used for carrying out periodic monitoring scanning on each folder under the log storage root directory, and writing a database table name, a data row ID, a log recording timestamp, an operation type and updated data row contents corresponding to a newly written txt file into a database log table whenever the newly written txt file is scanned;
the logging module is further configured to: when the log recording module receives a display request of a change process of a data row of a certain data table, the log recording module searches the database log table and associates all log records corresponding to the data row ID of the same data table; and then, analyzing each log record according to the sequence of the log record time stamps, and displaying the data corresponding to the same data line ID according to the history change process.
The log recording method and the log recording system provided by the invention have the following advantages:
(1) when the database table of the tracked record changes, only the changed data rows are recorded, and other data rows which are not changed are not recorded, so that the space occupation condition of data storage can be obviously reduced, and the storage burden of a system is reduced;
(2) the changed data lines are converted into json format, and are stored in an appointed storage path in a txt file, so that the same data line is stored in the same second-level folder; and the second-level folders corresponding to all the rows in the same database table are stored in the same first-level folder, so that hierarchical storage is realized, the change condition of the same data row in the same database table can be quickly associated, the display of the change process of the data row is facilitated, and the data display efficiency is improved.
(3) The decoupling from the service is realized, and the field and logic change of the service system does not have any influence on the log record.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements should also be considered within the scope of the present invention.
Claims (4)
1. A method of logging, comprising the steps of:
step 1, a database table is composed of a plurality of data rows; each of the data lines has a unique corresponding data line ID; each database table has a unique corresponding database table name;
step 2, establishing a list which does not need to be subjected to log recording, and putting the database names which do not need to be subjected to log recording into the list;
step 3, when the system uses the storage function, judging whether the table name of the database needing to be stored is in the table list, if not, executing step 4; if yes, skipping a log recording module and not performing log recording processing;
step 4, the log recording module performs log recording processing, including:
step 4.1, the log recording module converts data composed of database table names, data row IDs, log recording timestamps, operation types and updated data row contents into json format according to data change instructions submitted during storage, the data row IDs of all data rows stored at this time and the updated row contents, and stores the json format by adopting txt files; the file name of the txt file is a log record timestamp;
step 4.2, the log recording module pre-establishes a log storage root directory, then searches the log storage root directory, and judges whether a first-level folder named by the database table name exists in the log storage root directory; if not, executing step 4.3; if so, executing step 4.4;
4.3, the log recording module establishes a first-level folder named by the database table name in the log storage root directory, and then executes the step 4.4;
step 4.4, the log recording module opens the first-level folder named by the database table name, judges whether the first-level folder named by the database table name comprises a second-level folder named by the data row ID, and if the first-level folder does not comprise the second-level folder named by the data row ID, the step 4.5 is executed; if so, performing step 4.6;
step 4.5, the log recording module establishes a second-level folder named by the data row ID in a first-level folder named by the database table name, and then executes step 4.6;
step 4.6, the log recording module writes the txt file obtained in the step 4.1 into a second-level folder named by the data line ID;
therefore, the database table is tracked, and when the database table changes, only the changed data rows are stored into the corresponding folders according to the corresponding log storage paths;
step 5, the windows monitoring service module carries out periodic monitoring scanning on each folder under the log storage root directory, and when a newly written txt file is scanned, a database table name, a data row ID, a log recording time stamp, an operation type and updated data row contents corresponding to the newly written txt file are written into a database log table;
step 6, when the log recording module receives a display request of the change process of the data row of a certain data table, the log recording module searches the database log table and associates all log records corresponding to the data row ID of the same data table; and then, analyzing each log record according to the sequence of the log record time stamps, and displaying the data corresponding to the same data line ID according to the history change process.
2. The logging method of claim 1, further comprising:
and the windows monitoring service module monitors the valid period of the txt document in each folder under the log storage root directory, the default valid period is two months, and the txt document exceeding the valid period is automatically deleted.
3. The logging method of claim 1, wherein in step 4, the operation types comprise an add operation type, a modify operation type and a delete operation type.
4. A logging system, comprising:
the table list establishing module is used for establishing a table list which does not need to be subjected to log recording and placing the table name of the database which does not need to be subjected to log recording into the table list;
the judging module is used for judging whether the table name of the database needing to be stored is in the table list when the system uses the storing function, and if so, skipping the log recording module and not performing log recording processing; if not, calling the logging module;
a log recording module, configured to perform log recording processing, and specifically configured to:
step 4.1, the log recording module converts data composed of database table names, data row IDs, log recording timestamps, operation types and updated data row contents into json format according to data change instructions submitted during storage, the data row IDs of all data rows stored at this time and the updated row contents, and stores the json format by adopting txt files; the file name of the txt file is a log record timestamp;
step 4.2, the log recording module pre-establishes a log storage root directory, then searches the log storage root directory, and judges whether a first-level folder named by the database table name exists in the log storage root directory; if not, executing step 4.3; if so, executing step 4.4;
4.3, the log recording module establishes a first-level folder named by the database table name in the log storage root directory, and then executes the step 4.4;
step 4.4, the log recording module opens the first-level folder named by the database table name, judges whether the first-level folder named by the database table name comprises a second-level folder named by the data row ID, and if the first-level folder does not comprise the second-level folder named by the data row ID, the step 4.5 is executed; if so, performing step 4.6;
step 4.5, the log recording module establishes a second-level folder named by the data row ID in a first-level folder named by the database table name, and then executes step 4.6;
step 4.6, the log recording module writes the txt file obtained in the step 4.1 into a second-level folder named by the data line ID;
therefore, the database table is tracked, and when the database table changes, only the changed data rows are stored into the corresponding folders according to the corresponding log storage paths;
the windows monitoring service module is used for carrying out periodic monitoring scanning on each folder under the log storage root directory, and writing a database table name, a data row ID, a log recording timestamp, an operation type and updated data row contents corresponding to a newly written txt file into a database log table whenever the newly written txt file is scanned;
the logging module is further configured to: when the log recording module receives a display request of a change process of a data row of a certain data table, the log recording module searches the database log table and associates all log records corresponding to the data row ID of the same data table; and then, analyzing each log record according to the sequence of the log record time stamps, and displaying the data corresponding to the same data line ID according to the history change process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910940739.3A CN110704378A (en) | 2019-09-30 | 2019-09-30 | Log recording method and log recording system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910940739.3A CN110704378A (en) | 2019-09-30 | 2019-09-30 | Log recording method and log recording system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110704378A true CN110704378A (en) | 2020-01-17 |
Family
ID=69196938
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910940739.3A Pending CN110704378A (en) | 2019-09-30 | 2019-09-30 | Log recording method and log recording system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110704378A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115373950A (en) * | 2022-10-26 | 2022-11-22 | 北京芯可鉴科技有限公司 | Industrial personal computer and data monitoring system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070179961A1 (en) * | 2002-07-15 | 2007-08-02 | Fabio Gava | Hierarchical storage |
| CN103870560A (en) * | 2014-03-06 | 2014-06-18 | 上海爱数软件有限公司 | Log managing method for cluster |
| CN104572781A (en) * | 2013-10-29 | 2015-04-29 | 中国银联股份有限公司 | Method and device for generating transaction log |
| CN106383852A (en) * | 2016-08-30 | 2017-02-08 | 中国民生银行股份有限公司 | Docker container-based log acquisition method and apparatus |
| CN109492012A (en) * | 2018-10-31 | 2019-03-19 | 厦门安胜网络科技有限公司 | A kind of method, apparatus and storage medium of data real-time statistics and retrieval |
| CN110019239A (en) * | 2017-12-29 | 2019-07-16 | 百度在线网络技术（北京）有限公司 | Storage method, device, electronic equipment and the storage medium of reported data |
-
2019
- 2019-09-30 CN CN201910940739.3A patent/CN110704378A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070179961A1 (en) * | 2002-07-15 | 2007-08-02 | Fabio Gava | Hierarchical storage |
| CN104572781A (en) * | 2013-10-29 | 2015-04-29 | 中国银联股份有限公司 | Method and device for generating transaction log |
| CN103870560A (en) * | 2014-03-06 | 2014-06-18 | 上海爱数软件有限公司 | Log managing method for cluster |
| CN106383852A (en) * | 2016-08-30 | 2017-02-08 | 中国民生银行股份有限公司 | Docker container-based log acquisition method and apparatus |
| CN110019239A (en) * | 2017-12-29 | 2019-07-16 | 百度在线网络技术（北京）有限公司 | Storage method, device, electronic equipment and the storage medium of reported data |
| CN109492012A (en) * | 2018-10-31 | 2019-03-19 | 厦门安胜网络科技有限公司 | A kind of method, apparatus and storage medium of data real-time statistics and retrieval |
Non-Patent Citations (1)
| Title |
|---|
| （美）格雷（GRAY，J）, 华中科技大学出版社 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115373950A (en) * | 2022-10-26 | 2022-11-22 | 北京芯可鉴科技有限公司 | Industrial personal computer and data monitoring system |
| CN115373950B (en) * | 2022-10-26 | 2023-01-24 | 北京芯可鉴科技有限公司 | Industrial personal computer and data monitoring system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110347662B (en) | Multi-center medical data structure standardization system based on universal data model | |
| US11567736B2 (en) | Systems and methods for providing an instant communication channel within integrated development environments | |
| US7831676B1 (en) | Method and system for handling email | |
| US9171310B2 (en) | Search term hit counts in an electronic discovery system | |
| US20030037114A1 (en) | System, method and apparatus for updating electronic mail recipient lists | |
| US10642870B2 (en) | Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software | |
| CN109871392B (en) | Slow sql real-time data acquisition method under distributed application system | |
| CN104375928A (en) | Abnormal log management method and system | |
| US10055704B2 (en) | Workflow provision with workflow discovery, creation and reconstruction by analysis of communications | |
| US8738768B2 (en) | Multiple destinations for mainframe event monitoring | |
| CN114327678A (en) | Real-time data processing system and method supporting multiple engines | |
| CN104317601A (en) | Method and system for developing file interfaces | |
| US10459942B1 (en) | Sampling for preprocessing big data based on features of transformation results | |
| US20080235045A1 (en) | Workflow management system | |
| CN110704378A (en) | Log recording method and log recording system | |
| Zondergeld et al. | FAIR, safe and high-quality data: The data infrastructure and accessibility of the YOUth cohort study | |
| US20200201861A1 (en) | Application tracing system | |
| US10572458B2 (en) | Method and apparatus of collecting and reporting database application incompatibilities | |
| CN111352982A (en) | Manpower extraction analysis system based on big data | |
| CN107004036B (en) | Method and system for searching logs containing a large number of entries | |
| CN113010208B (en) | Version information generation method, device, equipment and storage medium | |
| CN116301985A (en) | Code scanning method, device, computer equipment and storage medium | |
| CN115033639A (en) | Method and related device for generating relation graph for data sharing among clusters | |
| CN112347066B (en) | Log processing method and device, server and computer readable storage medium | |
| JP2013235408A (en) | Log management system, log management server, and program |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200117 |
|
| RJ01 | Rejection of invention patent application after publication |