Data storage and monitoring method, device, electronic device and storage medium

Abstract

The present application provides a data storage and monitoring method, device, electronic device and storage medium, which use a distributed log storage service to receive and partition the latest test data from different test boards to form a test log, share the log data with a log monitoring terminal through a WEB API, and the log monitoring terminal monitors and displays the log data in real time, thereby solving the performance pressure of a single process processing a large amount of test data and the problem that multiple people cannot view the log at the same time. The method can independently store the log data generated by a large amount of equipment under test and monitor the logs generated by any object under test in real time. All module programs can be executed independently, which has the advantages of low operating pressure, high stability, and the ability to connect to the customer's information system and convenient use by customers.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data storage and monitoring method, device, electronic device and storage medium. Background Art

[0002] In the field of semiconductor testing, a semiconductor test device will integrate a large number of test boards and can measure a large number of objects under test (ranging from 1000 to 10000) at the same time. A large number of test logs will be generated during the test process. The storage and real-time monitoring of a large number of test logs bring huge operation and storage pressure to the test system software. For example, when using Yangtze Memory UFS3.0 to test 500 devices under test (DUT) at the same time, the test log traffic can reach 300Mbps. If 1000 devices under test DUT are tested at the same time on UFS4.0, the storage of test log data will exceed the upper limit of the write speed of a mechanical hard disk. This brings huge pressure to the test software system and also puts high demands on the server configuration equipped with the test system. At the same time, for the test log system, during the customer's use, it is also necessary to support viewing the test log of any device under test DUT at any time (generally only viewing the latest part), which also poses a great challenge to the test software system. In traditional designs, a log service process is responsible for receiving a large amount of test data from multiple test boards and also supports displaying the logs of the device under test (DUT) that customers are concerned about. This leads to the following problems:

[0003] The system is under great pressure to run and has high stability risks. It is inconvenient for customers to use. Customers are usually in their own offices, and the test machines are in the factory. If they want to view logs, they must use a remote desktop. Since logs can only be viewed using a remote desktop, only one person can view them at a time. It does not support docking with customers' own information systems. In industry, many customers require equipment to be docked with their own information systems, and logs may also need to be displayed on the customer's information system. With this traditional solution, logs can only be displayed on the interface of the log service. When the number of DUTs tested is higher and the system pressure is higher, it is impossible to use distributed technology to solve the problem, and the only option is to increase the single-host configuration to solve the problem. Summary of the invention

[0004] The present application provides a data storage and monitoring method, device, electronic device and storage medium, which use a distributed log storage service and a log data sharing solution based on a WEB API to share logs with a log monitoring terminal, thereby solving the performance pressure of a single process processing a large amount of test data and the problem that multiple people cannot view logs at the same time. The method can independently store the log data generated by a large amount of devices under test and monitor the logs generated by any object under test in real time. All module programs can be executed independently, which has the advantages of low operating pressure, high stability, ability to connect to the customer's information system, and convenience for customers.

[0005] Other purposes and advantages of the present invention can be further understood from the technical features disclosed in the present invention.

[0006] To achieve one, part or all of the above purposes or other purposes, the present invention provides a data storage and monitoring method, device, electronic device and storage medium.

[0007] A data storage and monitoring method, comprising:

[0008] The receiving and storing module receives and stores the latest test data from different test boards to form test log data;

[0009] The monitoring terminal module sends query requests to the shared service module in real time based on the user's business query needs;

[0010] The shared service module pushes the requested test log data to the receiving and storage module through the message push module based on the query request;

[0011] The receiving and storing module uploads the corresponding test log data to the shared service module, and the shared service module caches the test log data for query by the monitoring terminal module;

[0012] The monitoring terminal queries the test log data cached by the shared service module through the WEBAPI and displays it in real time.

[0013] The receiving and storing module starts multiple instances according to the pre-established corresponding relationship to respectively receive the test data from different test boards and store the test data in partitions to the hard disk. The test data contents of the different test boards are similar.

[0014] The pre-established corresponding relationship is to group the test boards according to the data volume of the test data, and the receiving and storage module manages different test boards according to the grouping of the test boards and starts multiple instances.

[0015] The test log text content is the relevant test data of the operation of different test boards, including one or more combinations of several items of information such as test process, time, date, flow, status, inspection results, etc.

[0016] The monitoring terminal module continuously sends query requests to the shared service module. If the query request is not sent within a timeout period, the receiving and storage module will stop uploading the corresponding test log data to the shared service module.

[0017] Any query request will be pushed to the receiving and storage module through the message push module. The receiving and storage module determines whether to upload the test log to the shared service module based on the pre-established correspondence. If so, the monitored log information of the user of the current request is generated and uploaded to the shared service module; if not, the monitoring terminal module continues to send query requests to the shared service module based on the user's business query requirements.

[0018] The receiving and storage module determines whether to upload the test log based on the established corresponding relationship: the test data is grouped according to its attribution, and the receiving and storage module determines whether the test data type of the query request belongs to a group of test objects managed by itself. If so, the test data of the query request is pushed, otherwise it is not processed.

[0019] The specific process of the query request is: the monitoring terminal module calls the application programming interface of the shared service module to query the test log, and the shared service module is responsible for data transfer and does not store data.

[0020] The monitored test log information is added and displayed in sequence on the log display interface of the monitoring terminal. The monitoring terminal module is responsible for real-time monitoring and does not store data.

[0021] When the monitoring terminal module is closed, the continuous monitoring process ends.

[0022] A data storage and monitoring device, comprising:

[0023] Receiving and storage module, used for receiving, partitioning, storing and pushing test data from different test boards;

[0024] A shared service module, used for caching the test data pushed by the receiving and storage module and providing query to the monitoring terminal module;

[0025] A monitoring terminal module, used to query the shared service module for the test data, monitor in real time and display the test data on a page for users to view;

[0026] Message push module, used for real-time push of necessary status.

[0027] An electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the data storage and monitoring method as claimed in any one of claims 1 to 8 are implemented.

[0028] A non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of any of the above-mentioned data storage and monitoring methods.

[0029] Compared with the prior art, the beneficial effects of the present invention mainly include:

[0030] 1. This application uses a distributed log storage service and a log data sharing solution based on the WEB API to share logs with the log monitoring terminal, solving the performance pressure of a single process processing a large amount of test data, and at the same time solving the problem that multiple people cannot view logs at the same time. It can independently store the log data generated by a large number of devices under test and monitor the logs generated by any object under test in real time.

[0031] 2. All module programs of this application can be executed independently, which simplifies the complexity of program writing, can be connected to the customer's information system, and can more easily meet the customer's on-site customization needs. It has the advantages of low operating pressure, high stability, and easy customer use.

[0032] In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the specific embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0034] Figure 1 A flowchart of a data storage and monitoring method provided in an embodiment of the present application.

[0035] Figure 2 A schematic diagram of the module operation of a data storage and monitoring method provided in an embodiment of the present application.

[0036] Figure 3 A schematic diagram of the structure of a data storage and monitoring device provided in an embodiment of the present application.

[0037] Figure 4 A schematic diagram of the physical structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The above and other technical contents, features and effects of the present invention will be clearly presented in the following detailed description of a preferred embodiment with reference to the drawings. The directional terms mentioned in the following embodiments, such as up, down, left, right, front or back, etc., are only referenced to the directions of the attached drawings. Therefore, the directional terms used are used to illustrate and not to limit the present invention.

[0039] The present invention provides a data storage and monitoring method, device, electronic device and storage medium, which use a distributed log storage service and a log data sharing solution based on a WEB API to share logs with a log monitoring terminal, thereby solving the performance pressure of a single process processing a large amount of test data and the problem that multiple people cannot view logs at the same time. The method can independently store the log data generated by a large amount of devices under test and monitor the logs generated by any object under test in real time.

[0040] The following will describe the various embodiments of the present application in detail with reference to the accompanying drawings. However, it will be appreciated by those skilled in the art that in the various embodiments of the present application, many technical details are provided in order to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solution claimed in the present application can be implemented.

[0041] Example 1

[0042] This embodiment 1 provides a data storage and monitoring method, such as Figure 1 A data storage and monitoring method shown includes:

[0043] Step 1: The receiving and storage module S receives and partitions the latest test data of the device under test DUT from different test boards to form a test log; the receiving and storage module S caches the latest test data of the device under test DUT in this service process;

[0044] Step 2: The user performs a designated viewing service operation, and the monitoring terminal module M makes a query request to the shared service module A; the monitoring terminal module M calls the application programming interface API of the shared service module A to query the test log of the device under test DUT;

[0045] Step 3: The shared service module A pushes the test data requirements of the device under test DUT to the receiving and storage module S through the message push module P;

[0046] Step 4: Any query request will be pushed to the receiving and storage module S through module P. After analysis, if the receiving and storage module S manages the data, it will push the test data of the device under test DUT to module A; otherwise, no processing will be done; the shared service module A caches the test data of the device under test DUT for query by the monitoring terminal module M, and the monitored test log information is added and displayed in sequence on the log display interface of the monitoring terminal;

[0047] Step 5: Repeat the above steps 2-4 to achieve real-time monitoring of the test data of the device under test DUT by the monitoring terminal module M and display the test log; close the monitoring terminal module, and the continuous monitoring process ends.

[0048] The receiving and storing module S starts receiving multiple copies of test data from different test boards according to the pre-established corresponding relationship, and stores the test data in partitions to the hard disk.

[0049] Here are some examples:

[0050] {

[0051] Example 1 accepts the test log data of test boards B1, B2, B3, and B4;

[0052] Example 2 accepts the test log data of test boards B5, B6, B7, and B8;

[0053] Example 3 accepts the test log data of test boards B9, B10, B11, and B12; ......

[0054] B1 is used to test DUT 1-40

[0055] B2 is used to test DUT 41-80

[0056] B3 is used to test DUT 81-120

[0057] B4 is used to test DUT 121-160

[0058] B5 is used to test DUT 161-200 ......

[0059] }

[0060] The monitoring terminal module M arbitrarily starts a plurality of test data for monitoring different test boards according to the pre-established corresponding relationship.

[0061] The receiving and storage module S starts multiple copies according to the pre-established correspondence, and the shared service module A starts one copy to be responsible for data transfer. The shared service module A does not store data, and the test data of the DUT that is not currently monitored will not be pushed from S to A, so as to save traffic and reduce the data processing volume of the shared service module A port, save the traffic consumption of the server processing resources, reduce the computing power investment, and also reduce the traffic of the terminal equipment and the processing resources of the log monitoring system, reducing the overall log monitoring operation and maintenance costs. Since the shared service module A port transmits a small amount of data, it can also reduce the packet loss rate to a certain extent, effectively improving the monitoring efficiency.

[0062] The monitoring terminal module M starts multiple copies at will, and the monitoring terminal module M needs to continuously send query requests to the shared service module A, and the receiving and storage module S will transmit the required data to the shared service module A. When the monitoring terminal module M times out and no longer sends query requests to the shared service module A, the receiving and storage module S will stop transmitting data to the shared service module A. The timeout time of 10 seconds is a good preset time in this embodiment, and there are other preset times in some embodiments. It is feasible to preset the time according to different actual application situations.

[0063] Since the monitoring terminal module M needs to be connected to the customer system, it can only monitor in real time and does not have storage and retrieval functions. For example, the business page 1 of the monitoring terminal module M is opened at 08:45:00 am on 2020.11.03, and can only monitor the test data at 08:45:00 am on 2020.11.03 in real time. Past data cannot be retrieved. Past data can only be found in the receiving and storage module S.

[0064] like Figure 2 Shown is a module operation diagram of a data storage and monitoring method provided in an embodiment of the present application.

[0065] The present invention is further described below by a specific embodiment:

[0066] like Figure 2 As shown, in a test machine in the semiconductor field, there are many sets of test equipment, each of which tests several devices under test (DUTs). Each device under test (DUT) has its own log information, which all need to be collected and stored on the server. At the same time, it is also necessary to support real-time viewing of the log information of any device under test (DUT) during testing.

[0067] The test board B1 is responsible for testing the DUTs B1-1, B1-2, B1-3, etc., and the test board B2 is responsible for testing the DUTs B2-1, B2-2, B2-3, etc.;

[0068] The text content of the log file is the DUT operation related data, including one or more combinations of several information such as the test process, test time, test date, test flow, test status, inspection results, etc. The test log file stores more information and the test time is longer. The following is a list of test log data:

[0069] “

[0070] [2023-11-11 11:11:25.112]Start test TestItem1

[0071] [2023-11-11 11:11:25.118]nop_request failed 0xFF

[0072] [2023-11-11 11:11:25.234]ufs_nop_request result failed

[0073] [2023-11-11 11:11:25.246]ufs_dut_reset pass

[0074] [2023-11-11 11:11:25.356]ufs_hardware_reset result pass

[0075] [2023-11-11 11:11:31.560]nop_request pass

[0076] [2023-11-11 11:11:31.561]ufs_reset_enable result pass

[0077] [2023-11-11 11:11:31.663]nop_request pass

[0078] [2023-11-11 11:11:31.663]End test TestItem1,result pass ......

[0079] ”

[0080] In this specific implementation, the content of the DUT operation-related data in the test log is relatively repetitive, and the receiving and storage module S has already performed large-scale storage of all test data. Therefore, the monitoring terminal module M in this embodiment only needs real-time monitoring and no storage.

[0081] Start the instances S1 and S2 of the receiving and storage module S, upload the log data of B1 to S1, and upload the log data of B2 to S2;

[0082] For example, the log content of a DUTB1-1 of B1 is as follows:

[0083] [2023-11-11 11:11:11.111]TestItem1 start.

[0084] The log data transmitted from B1 to S1 is as follows:

[0085] {

[0086] "dut": "B1-1",

[0087] "text": "[2023-11-11 11:11:11.111]TestItem1 start."

[0088] }

[0089] Start the instance A1 of the shared service module A, the instance P1 of the message push module P, and the instances M1 and M2 of the monitoring terminal module M;

[0090] After receiving the log data transmitted from B1 to S1, the receiving and storage module S1 writes the log to the ${LogPath} / B1-1.log file and caches it in the memory of S1;

[0091] In this specific implementation, in order to solve the problem of limited cached data, after receiving more logs, the previous cache will be deleted. Generally, the maximum number of cached logs can be set, for example, 100.

[0092] Set the monitoring terminal module M1 to monitor the log data of B1-1, and the monitoring terminal module M2 to monitor the log of B2-3;

[0093] The monitoring terminal module M1 requests the shared service module A1 for the log data of B1-1. Since the monitoring terminal module M1 has not yet displayed any logs of B1-1, the log data requested here is the log data from time 0 (i.e., 1970-01-01 08:00:00) to the current time;

[0094] The shared service module A1 pushes the log requirements of B1-1 to the receiving and storage modules S1 and S2 through the message push module P1;

[0095] Receiving and storage module S1 finds that the log of B1-1 is managed by itself, so it uploads the log of B1-1 to the shared service module A1. Receiving and storage module S2 does not have the log of B1-1 and does not process it.

[0096] The format of the logs uploaded here is the same as that of the logs uploaded by B1, as follows:

[0097] {

[0098] "dut": "B1-1",

[0099] "text": "[2023-11-11 11:11:11.111]TestItem1 start."

[0100] }

[0101] After receiving the log data from the receiving and storing module S1, the shared service module A1 caches the log for query by the monitoring terminal module M1;

[0102] For example, if the time when the log is received is 1699672272583 (i.e. 2023-11-11 11:11:12.583), the recorded data is as follows:

[0103] {

[0104] "dut": "B1-1",

[0105] "text": "[2023-11-11 11:11:11.111]TestItem1 start."

[0106] "time":1699672272583

[0107] }

[0108] The monitoring terminal module M1 requests the shared service module A1 for the log data of B1-1. Since the monitoring terminal module M1 has not yet displayed any logs of B1-1, the log data still requested here is the log data from time 0 (i.e., 1970-01-01 08:00:00) to the current time;

[0109] The shared service module A1 feeds back the log data of B1-1 to the monitoring terminal module M1, and the shared service module A1 continues to push the log requirements of B1-1 to the receiving and storage modules S1 and S2;

[0110] Here, logs can be returned to the monitoring terminal module M1. The returned data is as follows:

[0111] {

[0112] "dut": "B1-1",

[0113] "text":"[2023-11-11 11:11:11.111]TestItem1 start."

[0114] "time":1699672272583

[0115] }

[0116] At this time, the latest log time obtained by the monitoring terminal module M1 is 1699672272583, and the time range of the next log query by the monitoring terminal module M1 is updated to the log data from 1699672272583 to the current time;

[0117] The receiving and storage module S1 continues to push the log data of B1-1 to the shared service module A1;

[0118] The monitoring terminal module M1 continuously monitors the log data of B1-1, and the receiving and storage module S1 continuously uploads the corresponding log data to the shared service module A1, so that the monitoring terminal module M1 can continuously obtain the corresponding log data;

[0119] The monitoring terminal module M2 requests the shared service module A1 for the log data of B2-3;

[0120] The shared service module A1 pushes the log requirements of B2-3 to the storage modules S1 and S2 through the message push module P1;

[0121] Storage module S1 finds that the log of B2-3 is not managed by itself, so it does not process it. Storage module S2 finds that the log of B2-3 is managed by itself, so it uploads the log of B2-3 to the shared service module A1.

[0122] The monitoring terminal module M2 continues to request the log data of B2-3 from the shared service module A1;

[0123] The shared service module A1 feeds back the log data of B2-3 to the monitoring terminal module M2, and the shared service module A1 continues to push the log requirements of B2-3 to the storage modules S1 and S2 at the same time;

[0124] The storage module S2 continues to push the log data of B2-3 to the shared service module A1;

[0125] As long as the monitoring terminal module M2 continues to monitor the log data of B2-3, the storage module S2 will continue to upload the corresponding log data to the shared service module A1, and the monitoring terminal module M2 can continue to obtain the corresponding log data;

[0126] Close the monitoring terminal module M1 and stop requesting the log data of (B1-1);

[0127] The shared service module A1 no longer pushes the log data requirements of B1-1;

[0128] The storage module S1 stops uploading the log data of B1 - 1 to the shared service module A1 , and the monitoring process ends.

[0129] It should be understood that, although the steps in each flow chart involved in the above-described embodiment are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a portion of the steps in each flow chart involved in the above-described embodiment may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0130] Example 2

[0131] Embodiment 2 provides a data storage and monitoring device, such as Figure 3 The figure is a schematic diagram of the structure of a data storage and monitoring device provided in an embodiment of the present application, including:

[0132] The receiving and storage module S is used to receive, partition, store and push test data from different test boards. The log receiving and storage module S is a data receiving and storage module based on the TCP protocol. It receives test data from the test board. Since a large number of test boards are integrated in the test machine, a large amount of data comes from different boards. The amount of data on each board is relatively small, so this module can start multiple instances according to demand, receive test data from different test boards, and store them on the hard disk.

[0133] The shared service module A is used to cache the test data pushed by the receiving and storage modules, and is queried by the monitoring terminal module. The log sharing service module A is a log data sharing service based on the WEB API. When someone needs to view the log of a device under test DUT, the log receiving and storage service will push the log of the device under test DUT to the log sharing service, while the test log data of the device under test DUT that no one has viewed will not be pushed over. Since the test system tests a large number of devices under test DUT, generally more than 1,000, but the number of people who view the log is limited, generally no more than 10 people will view the log at the same time, and no more than 20 people at most, so only a small number of the large number of test logs need to be viewed by users through the log sharing service.

[0134] The monitoring terminal module M is used to query the shared service module for test data, monitor in real time and display the test data on the page for users to view. The log monitoring terminal module M is a UI program, which can be a WEB front-end page, a client, or a console program. This module is used to view the log data of the device under test DUT. When the user needs to view the test log of the specified device under test DUT, the module will request the log data from the log sharing service and then display it on the page.

[0135] The message push module P is used to push the necessary status in real time. The message push module P is used to push the components of each module status in real time. When the log monitoring module needs to view the test log of the device under test DUT object DUT1, it will query the test log of the device under test DUT1 from the log sharing service module, and this demand will be pushed to the log receiving and storage module through this module, and then the log receiving and storage module will push the log of the device under test DUT1 to the log sharing service module, and then the log monitoring terminal module can query the test log data of the device under test DUT1.

[0136] Example 3

[0137] This embodiment 3 provides an electronic device capable of implementing the above method, such as Figure 4 Shown is a schematic diagram of the physical structure of an electronic device provided in an embodiment of the present application.

[0138] like Figure 4 As shown, the electronic device may include: a processor 510, a communication interface 520, a memory 530, and a communication bus 540. The processor 510, the communication interface 520, and the memory 530 communicate with each other through the communication bus 540. The processor 510 may call the logic instructions in the memory 530, and the logic instructions in the memory 530 may be implemented in the form of software function units and may be stored in a computer-readable storage medium when sold or used as an independent product.

[0139] Example 4

[0140] This embodiment 4 provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the computer can execute the above method.

[0141] Based on such understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., various media that can store program codes.

[0142] Based on this understanding, the above-mentioned technical solution can essentially or contribute to the existing technology in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of various embodiments or certain parts of the embodiments.

[0143] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A data storage and monitoring method, characterized in that: include: The receiving and storing module receives and stores the latest test data from different test boards to form test log data; The monitoring terminal module sends query requests to the shared service module in real time based on the user's business query needs; The shared service module pushes the query request to the receiving and storage module through the message push module based on the query request; The receiving and storing module uploads the corresponding test log data to the shared service module, and the shared service module caches the test log data for query by the monitoring terminal module; The monitoring terminal module queries and displays the test log data cached by the shared service module in real time through the WEB API; the monitoring terminal module continuously sends query requests to the shared service module, and if the query request is not sent within a timeout period, the receiving and storage module will stop uploading the corresponding test log data to the shared service module; Any query request will be pushed to the receiving and storing module through the message pushing module, and the receiving and storing module determines whether to upload the test log to the sharing service module according to the pre-established correspondence relationship. If yes, the monitored log information of the user of the current request is generated and uploaded to the sharing service module; if not, no processing is performed; The receiving and storage module determines whether to upload the test log based on the established corresponding relationship: the test data is grouped according to its ownership, and the receiving and storage module determines whether the test data of the query request belongs to a group of objects under test DUT managed by itself. If so, the test data of the query request is pushed; if not, it is not processed.

2. A data storage and monitoring method according to claim 1, characterized in that: The receiving and storing module starts multiple instances according to the pre-established corresponding relationship to respectively receive the test data from different test boards and store the test data in partitions to the hard disk. The test data contents of the different test boards are similar.

3. A data storage and monitoring method according to claim 2, characterized in that: The pre-established corresponding relationship is to group the test boards according to the data volume of the test data. The receiving and storage module manages different test boards according to the grouping of the test boards and starts multiple instances.

4. A data storage and monitoring method according to claim 3, characterized in that: The test log text content is the relevant test data of the operation of different test boards, including one or more combinations of test process, time, date, flow, status and inspection result information.

5. A data storage and monitoring method according to claim 1, characterized in that: The specific process of the query request is: the monitoring terminal module calls the application programming interface of the shared service module to query the test log, and the shared service module is responsible for data transfer and does not store data.

6. A data storage and monitoring method according to claim 1, characterized in that: The monitored test log information is added and displayed in sequence on the log display interface of the monitoring terminal. The monitoring terminal module is responsible for real-time monitoring and does not store data.

7. A data storage and monitoring method according to claim 1, characterized in that: When the monitoring terminal module is closed, the continuous monitoring process ends.

8. A data storage and monitoring device, characterized in that: include: A receiving and storing module, which receives and partitions the test data from different test boards and transmits the corresponding test data to the shared service module based on the query request pushed by the message pushing module; A shared service module, wherein the shared service module pushes the query request sent by the monitoring terminal module to the receiving and storage module in real time through the message push module; the shared service module receives and caches the corresponding test data transmitted by the receiving and storage module for query by the monitoring terminal module; A monitoring terminal module, which sends query requests to the shared service module in real time based on the user's business query needs, and monitors and displays the test data cached by the shared service module in real time on the page for the user to view; the monitoring terminal module continuously sends query requests to the shared service module, and if the query request is not sent within a timeout, the receiving and storage module will stop uploading the corresponding test log data to the shared service module; Any query request will be pushed to the receiving and storing module through the message pushing module, and the receiving and storing module determines whether to upload the test log to the sharing service module according to the pre-established correspondence relationship. If yes, the monitored log information of the user of the current request is generated and uploaded to the sharing service module; if not, no processing is performed; The receiving and storage module determines whether to upload the test log according to the established corresponding relationship in the following manner: the test data is grouped according to its ownership, and the receiving and storage module determines whether the test data of the query request belongs to a group of DUTs managed by itself. If so, the test data of the query request is pushed; if not, no processing is performed; A message push module pushes the query request of the sharing service module to the receiving and storing module in real time.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the steps of the data storage and monitoring method according to any one of claims 1 to 7 are implemented.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the data storage and monitoring method according to any one of claims 1 to 7 are implemented.

Images