TWI815722B - System and method for pre-judging situation of server before test according to server log data - Google Patents

Abstract

A system and method is provided for pre-judging situation of a server before test according to a server log data. In the system and method, before executing a test flow, when an abnormal character string data comparison unit compares a configuration text of the server log data includes at least one abnormal-related character string, the server is defined as an abnormal server, which does not comply with a test requirement. Moreover, when a monitoring data comparison unit compares at least one monitoring data of the server log data being out of the at least one respective requirement range for test, the server is also defined as the abnormal server, and further more an abnormal-information generation module generates an abnormal information when the server is finally determined as the abnormal server before executing the test flow.

Description

Use server log data to predict before testing Judgment system and method for disconnecting server status

The present invention relates to a judgment system and a judgment method, and in particular to a judgment system and judgment method that utilizes server log data to pre-judge server status before testing.

With the sophistication of electronic products, more and more modules with sophisticated functions are built into electronic products. In order to monitor and manage electronic product production lines more efficiently, a large number of monitoring and control modules must be used in conjunction with the use of physical Networks, local area networks and the Internet are used to transmit a large amount of monitoring and control data, and to store and manage them. In this case, each production line is likely to be configured with at least one work server, and each work server is used to support the monitoring, control and management of at least one workstation of the production line.

In response to the needs of production line monitoring and management, the production line server records a large number of control and management rules. In order to ensure that the production line server can correctly and effectively manage the production line according to appropriate control and management rules, testing tool software provided by at least one control server is usually used for detection. Especially when there is a problem with the work content or service content provided by the work server on a specific workstation, the test tool software provided by the control server corresponding to the workstation is usually used to test the work server to eliminate errors.

However, using testing tool software often takes a long time to execute each test one by one; therefore, in some cases, configuration files in server log data are read and parsed to pre-test before testing. Determine the status of the server. Most of the existing server log data are judged by string comparison, that is, whether there is a string associated with the abnormal state in the configuration file of the server log data. If there is a string associated with the abnormal state, String, it is judged that the server is in an abnormal state that does not meet the test requirements. Then, the abnormal information obtained from the comparison can be used to make appropriate adjustments and modifications to the server's software, firmware, or hardware to meet the test requirements, thereby reducing low test results to the probability of failure.

However, some configuration files mostly only define configuration information such as the server's access path, link path, link address, and supporting hardware. It is impossible to fully determine whether the current status of the server meets the test requirements, resulting in a high misjudgment rate. , losing the substantial meaning of early prediction state.

In view of the common potential problem in the prior art that the misjudgment rate of whether the current status of the server meets the test requirements is relatively high, one of the necessary technical means adopted by the present invention to solve the problems of the prior art is to provide a method for using the server A judgment system (hereinafter referred to as the "Judgment System") that uses log data to pre-judge the status of the server before testing.

The judgment system includes a data acquisition module, a storage module, a comparison module and an abnormal information generation module. The data retrieval module is used to pre-retrieve a server log data stored in the server before testing the server. The server log data includes a configuration file and at least one previous time corresponding to at least one monitoring item. Monitor data.

The storage module establishes an exception string database and a test requirement database. The exception string database defines a plurality of exception-related strings, and the test requirement database defines at least one requirement data range corresponding to the monitoring project. . The comparison module is coupled to the data acquisition module and the storage module, and includes an abnormal string data comparison unit and a monitoring data comparison unit.

The abnormal string data comparison unit defines the server as an abnormal server whose status does not meet the test requirements when the compared configuration file contains at least one of the abnormal related strings. The monitoring data comparison unit, after comparing that the configuration file does not contain at least one of the abnormal related strings, continues to compare and finds that the previous monitoring data falls outside the corresponding required data range, the server will also Defined as an exception server. The exception information generation module is coupled to the comparison module to generate an exception information based on the abnormal server defined by the comparison module before the server is tested.

On the basis of the above necessary technical means, among the extended auxiliary technical means, preferably, the judgment system further includes a printing module. The printing module is communicatively connected to the abnormal information generation module to print the abnormal information. . The data retrieval module may be a server log data reader. The monitoring items include at least one of the server core temperature, hard disk remaining available capacity, and data access speed of the server.

Another necessary technical means used by the present invention to solve the problems of the prior art is to provide a judgment method (hereinafter referred to as the "judgment method") that uses server log data to pre-judge the server status before testing. In this judgment method, first, an exception string database and a test requirement database are pre-established in a storage module. A plurality of exception-related strings are defined in the exception string database, and a plurality of exception-related strings are defined in the test requirement database. At least one required data range corresponding to the monitoring item is specified.

Then, before a server is tested, a data retrieval module is used to pre-retrieve a server log data stored in the server. The server log data includes a configuration file and at least one previous monitoring corresponding to the monitoring item. data. When the abnormal string data comparison unit of a comparison module is used to compare the configuration file with at least one of the abnormal related strings, the server is defined as an abnormal server whose status does not meet the test requirements. device. In addition, if the comparison shows that the configuration file does not contain at least one of the abnormal related strings, continue to use one of the monitoring data comparison units of the comparison module to compare and find that the previous monitoring data falls within the corresponding requirements. When the data is outside the range, the server is also defined as an abnormal server. Finally, an exception information generation module is used to generate an exception information based on the abnormal server defined by the comparison module before the server is tested.

On the basis of the above necessary technical means, among the extended auxiliary technical means, the best one is to use a printing module to print out the abnormal information.

As mentioned above, in the judgment technology (including judgment system and judgment method) for using server log data to judge server status provided by the present invention, the two types of abnormality-related string comparison and monitoring data comparison are combined. Comparison technology, therefore, before conducting a comprehensive test, you can accurately judge whether the current status of the server meets the test requirements, and use it as a reference for adjustments and modifications before the test, so as to effectively improve the subsequent comprehensive test. probability, thereby reducing the probability of re-conducting comprehensive testing and improving overall efficiency.

Since the judgment technology (including judgment system and judgment method) provided by the present invention for using server log data to pre-judge server status before testing can be widely used to judge whether the status of various servers is normal or abnormal, it will not be discussed here. Again, only one of the preferred embodiments will be listed for detailed description. In addition, the drawings in each embodiment are in a very simplified form, and the components are not presented in absolutely precise proportions. They are only used to conveniently and clearly assist in explaining the purpose and effect of the embodiments of the present invention.

Please refer to the first figure, which is a schematic functional block diagram of a judgment system that uses server log data to pre-judge server status before testing provided by a preferred embodiment of the present invention. As shown in the first figure, a judgment system (hereinafter referred to as the "judgment system") 100 that uses server log data to pre-judge server status before testing includes a data retrieval module 1, a storage module 2, and a Comparison module 3, an exception information generation module 4 and a printing module 5.

The data retrieval module 1 is used to retrieve a server log data 201 stored in a server 200; therefore, the data retrieval module 1 can be a server log data used to read the server log data 201 reader. The server log data 201 includes a configuration file 201a and at least one previous monitoring data 201b corresponding to at least one monitoring item. The monitoring items include at least one of server core temperature, hard disk remaining available capacity, and data access speed of the server 200 .

The storage module 2 pre-establishes an exception string database 21 and a test request database 22. A plurality of exception-related strings 211 are defined in the exception string database 21, and at least one requirement data range 221 corresponding to the monitoring item is defined in the test requirement database 22.

The comparison module 3 is coupled to the data acquisition module 1 and the storage module 2, and includes an abnormal string data comparison unit 31 and a monitoring data comparison unit 32. When the abnormal string data comparison unit 31 compares the configuration file 201a with at least one of the abnormal related strings 211, it defines the server 200 as an abnormal server whose status does not meet the test requirements. When the monitoring data comparison unit 32 compares and finds that the previous monitoring data 201b falls outside the corresponding required data range 221, the server 200 is also defined as an abnormal server. The exception information generation module 4 is coupled to the comparison module 3 to generate an exception information based on the abnormal server defined by the comparison module 3 before the server 200 is tested.

The printing module 5 is communicatively connected to the exception information generation module 4 to print the exception information. In addition, the abnormal information can also be transmitted to a terminal device (such as an industrial computer, a personal computer or a mobile communication device) operated by a manager, so that the manager can be informed of the abnormal information in real time.

For example, if in one of the situations, the content in the configuration file 201a of the server log data 201 of the server 200 includes the string "$path/$file_err"; the exception defined in the exception string database 21 The associated string 211 includes "$path/$file_err". At this time, the abnormal string data comparison unit 31 will compare and find that the configuration file 201a of the server log data 201 contains the exception-related string 211 "$path/$file_err", indicating that there is a file path error in the configuration file 201a. , does not meet the test requirements; therefore, the server 200 is defined as an abnormal server whose status does not meet the test requirements.

For example, if in another situation, even if the configuration file 201a of the server log data 201 does not have the exception-related string 211 at all, if the last monitoring data 201b shows that the remaining available capacity of the hard disk is 10Gb, the test request database 22 At least one required data range 221 corresponding to the remaining available capacity of the hard disk is defined to be greater than 20 Gb. At this time, the monitoring data comparison unit 32 will compare and find that the previous monitoring data 201b falls outside the corresponding required data range 221, and the same is true Server 200 will be defined as an abnormal server whose status does not meet the test requirements.

As mentioned above, if the comparison module 3 compares the content in the configuration file 201a with the abnormal related string 211 of "$path/$file_err", and compares the hard disk residue in the previous monitoring data 201b, it is available. If the capacity falls outside the remaining available capacity of the hard disk defined by the corresponding required data range 221, the exception information generation module 4 will generate an exception message based on the exception server defined by the comparison module 3 (including the above exception reasons).

If the above two abnormal situations are combined, after the administrator reads the above abnormal information, he can reset the file path in the configuration file 201a and clear the data in the hard disk of the server 200 so that the remaining hard disk of the server 200 can be used. After the capacity exceeds 20 Gb, update the configuration file 201a and the previous monitoring data 201b in the server log data 201, and then use the comparison module to compare again to determine whether the server 200 has returned to a normal state that meets the test requirements, and After confirming that it has returned to a normal state that meets the test requirements, execute the complete test script for a comprehensive test.

Based on the above content, the preferred embodiment of the present invention can also be presented by using a judgment method that uses server log data to pre-judge the server status before testing. Please refer to the first and second figures. The second figure is a simplified flow chart showing a method for pre-determining server status before testing by using server log data according to a preferred embodiment of the present invention.

As shown in the first and second figures, in a judgment method that uses server log data to pre-judge the server status before testing, first, a storage module 2 can pre-create an abnormal string database 21 and A test requirement database 22. A plurality of exception-related strings 211 are defined in the exception string database 21, and at least one requirement data range 221 corresponding to the monitoring item is defined in the test requirement database 22 (step S110).

Next, before the server 200 is tested, a data retrieval module 1 is used to pre-retrieve a server log data 201 stored in the server 200. The server log data 201 includes a configuration file 201a and a configuration file corresponding to the monitoring item. At least one previous monitoring data 201b (step S120). The abnormal string data comparison unit 31 of the comparison module 3 is used to compare whether the configuration file 201a contains at least one of the abnormal related strings 211 (step S130). If the comparison result in step S130 is yes, the server 200 is defined as an abnormal server whose status does not meet the test requirements (step S140 ). If the comparison result in step S130 is negative, continue to use the monitoring data comparison unit 32 of one of the comparison modules 3 to compare whether the previous monitoring data falls outside the corresponding required data range (step S150)?

If the comparison result in step S150 is yes, the server 200 is defined as an abnormal server whose status does not meet the test requirements (step S140 ). If the comparison result in step S150 is negative, the server 200 is defined as a normal server whose status meets the test requirements (step S160 ).

After step S140, an exception information generation module 4 can be used to generate an exception information based on the abnormal server defined by the comparison module 3 before the server is tested (step S170), and a printing module can be used 5. Print out the exception information (step S180).

Based on the above, in the judgment technology (including judgment system and judgment method) for judging server status by using server log data provided by the present invention, the two types of abnormality-related string comparison and monitoring data comparison are combined. Comparison technology, therefore, before conducting a comprehensive test, you can accurately judge whether the current status of the server meets the test requirements, and use it as a reference for adjustments and modifications before the test, so as to effectively improve the subsequent comprehensive test. probability, thereby reducing the probability of re-conducting comprehensive testing and improving overall efficiency.

Through the above detailed description of the preferred embodiments, it is hoped that the characteristics and spirit of the present invention can be more clearly described, but the scope of the present invention is not limited by the above disclosed preferred embodiments. On the contrary, the intention is to cover various modifications and equivalent arrangements within the scope of the patent for which the present invention is intended.

100:Judgment system 200:server 201:Server log data 201a:Configuration file 201b: Last monitoring data 1: Data acquisition module 2:Storage module 21:Exception string database 211:Exception associated string 22:Testing requirements database 221: Request data range 3: Comparison module 31: Abnormal string data comparison unit 32: Monitoring data comparison unit 4: Exception information generation module 5: Printing module S110~S180: steps

The first figure is a functional block diagram showing a judgment system for pre-judging server status before testing by using server log data according to a preferred embodiment of the present invention; and The second figure is a simplified flow chart showing a method for pre-determining server status before testing by using server log data according to a preferred embodiment of the present invention.

100:Judgment system

200:server

201:Server log data

201a:Configuration file

201b: Last monitoring data

1: Data acquisition module

2:Storage module

21:Exception string database

211:Exception related string

22:Testing requirements database

221: Request data range

3: Comparison module

31: Abnormal string data comparison unit

32: Monitoring data comparison unit

4: Exception information generation module

5: Printing module

Claims (6)

A judgment system that uses server log data to pre-judge server status before testing, including: A data retrieval module is used to pre-retrieve a server log data stored in a server before testing the server. The server log data includes a configuration file and information corresponding to at least one monitoring item. At least one previous monitoring data; A storage module establishes an exception string database and a test requirement database. The exception string database defines a plurality of exception-related strings, and the test requirement database defines a string corresponding to the at least one monitoring At least one of the items requires a data range; A comparison module is coupled between the data retrieval module and the storage module, including: An abnormal string data comparison unit defines the server as an abnormal server whose status does not meet the test requirements when the configuration file is compared with at least one of the abnormal related strings; and A monitoring data comparison unit, after comparing that the configuration file does not contain at least one of the abnormal related strings, continues to compare the at least one previous monitoring data to the corresponding at least one required data. When out of range, the server is also defined as the abnormal server; and An exception information generating module is coupled to the comparison module to generate an exception information based on the abnormal server defined by the comparison module before the server is tested. The judgment system that uses server log data to pre-judge server status before testing as described in request 1 further includes a printing module that is communicatively connected to the exception information generation module to print The exception information. The judgment system for pre-judging server status before testing by using server log data as described in claim 1, wherein the data acquisition module is a server log data reader. The judgment system that uses server log data to pre-judge server status before testing as described in request 1, wherein the at least one monitoring item includes the server core temperature, hard disk remaining available capacity and data access of the server At least one of the speeds. A method of using server log data to pre-judge server status before testing, including the following steps: (a) Pre-create an exception string database and a test requirement database in a storage module. A plurality of exception-related strings are defined in the exception string database, and the test requirement database defines a corresponding At least one required data range of at least one monitoring item; (b) Before testing a server, use a data retrieval module to pre-retrieve a server log data stored in the server. The server log data includes a configuration file and corresponding to the at least one monitoring item. At least one previous monitoring data; (c) Using an abnormal string data comparison unit of a comparison module to compare the configuration file with at least one of the abnormal related strings, the server is defined as having a status that does not meet the requirements. One of the test requirements is an abnormal server; (d) If the comparison shows that the configuration file does not contain at least one of the abnormal related strings, continue to use one of the monitoring data comparison units of the comparison module to compare at least one of the previous monitoring data. When the data falls outside the corresponding at least one required data range, the server is also defined as the abnormal server; and (e) Use an exception information generation module to generate an exception information based on the abnormal server defined by the comparison module before the server is tested. The method of using server log data to pre-judge the server status before testing as described in request 5 further includes a step (f), and the step (f) uses a printing module to print the exception information.

Images