CN113688006B

CN113688006B - Log data verification method and device

Info

Publication number: CN113688006B
Application number: CN202110925639.0A
Authority: CN
Inventors: 王海; 朱珠; 吴鹏
Original assignee: Advanced New Technologies Co Ltd
Current assignee: Advanced New Technologies Co Ltd
Priority date: 2017-10-16
Filing date: 2017-10-16
Publication date: 2024-03-29
Anticipated expiration: 2037-10-16
Also published as: CN107844400A; CN107844400B; CN113688006A

Abstract

The embodiment of the application provides a method and a device for checking log data, wherein the method comprises the following steps: acquiring log data to be checked; acquiring a configuration file for representing log verification requirements, and determining a verification rule corresponding to the configuration file; and checking the log data to be checked by using the determined check rule, and generating a check result of the log data to be checked. Compared with a manual log verification mode or a verification mode with fixed verification rules in the related art, the log data verification method and device provided by the embodiment of the application can automatically match the verification rules according to the actual verification requirements of users, so that the effect that the verification rules can be freely configured is achieved, the automatic verification of the log data is realized by utilizing the verification rules, the flexibility and the variability of the log verification mode are improved, the application program of a business system is not required to be modified, and the log data can be verified by adopting the corresponding verification rules according to different verification requirements.

Description

Log data verification method and device

This patent application is application number: 201710957387.3, filing date: the invention discloses a method and a device for checking log data, which are applied separately from China patent application in the year 2017, the month 10 and the day 16.

Technical Field

The present disclosure relates to the field of log verification, and in particular, to a method and an apparatus for verifying log data.

Background

With the rapid development of internet technology, journals generated by various companies have undoubtedly become the largest data sources for the companies. The comprehensiveness and accuracy of the log directly influence the development of various works inside the company. Therefore, if the problems of log errors, log repetition, log deletion and the like occur, the problems need to be discovered as early as possible and solved, and the influence is minimized.

In the related art, log data is mainly checked in the following manner, specifically: the method is that log data are checked one by adopting a manual log checking mode, and the correctness of the log to be checked is determined manually and empirically; and the other mode is to check the log data one by adopting an automatic log check mode, and automatically check the correctness of the generated log by writing corresponding log check codes in the service program.

Therefore, the manual log verification method has the problems of low verification efficiency and high labor cost; for the automatic log verification mode, as the log verification rule is fixed, once the log verification rule needs to be modified, the whole modification and test of the service program are needed, the normal operation of the service system is affected, and the problems of low flexibility and poor usability exist.

Disclosure of Invention

The embodiment of the application aims to provide a method and a device for checking log data, which can automatically match checking rules according to actual checking demands of users, thereby achieving the effect that the checking rules can be freely configured, and then utilizing the checking rules to realize automatic checking of the log data, improving the flexibility and the variability of a log checking mode, and realizing that the corresponding checking rules are adopted to check the log data by combining different checking demands without modifying application programs of a service system.

In order to solve the technical problems, the embodiment of the application is realized as follows:

the embodiment of the application provides a log data verification method, which comprises the following steps:

acquiring log data to be checked;

acquiring a configuration file for representing log verification requirements, and determining a verification rule corresponding to the configuration file;

and checking the log data to be checked by using the determined checking rule, and generating a checking result of the log data to be checked.

acquiring log data to be checked;

acquiring a configuration file for representing log verification requirements, and selecting at least one verification plug-in corresponding to the configuration file from a verification plug-in library according to the configuration file, wherein each verification plug-in is used for realizing a verification function, and the verification functions of every two verification plug-ins are completely different;

And verifying the log data to be verified by utilizing a verification plug-in set formed by combining the at least one verification plug-in, and generating a verification result of the log data to be verified.

The embodiment of the application provides a log data verification device, which comprises:

the log data acquisition module is used for acquiring log data to be checked;

the verification rule determining module is used for obtaining a configuration file for representing log verification requirements and determining a verification rule corresponding to the configuration file;

and the log data verification module is used for verifying the log data to be verified by utilizing the determined verification rule and generating a verification result of the log data to be verified.

the log data acquisition module is used for acquiring log data to be checked;

the verification rule determining module is used for obtaining a configuration file for representing log verification requirements, and selecting at least one verification plug-in corresponding to the configuration file from a verification plug-in library according to the configuration file, wherein each verification plug-in is used for realizing a verification function, and the verification functions of every two verification plug-ins are completely different;

And the log data verification module is used for verifying the log data to be verified by utilizing the verification plug-in set formed by combining the at least one verification plug-in, and generating a verification result of the log data to be verified.

The embodiment of the application provides log data verification equipment, which comprises the following components:

a processor; and

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

acquiring log data to be checked;

a processor; and

acquiring log data to be checked;

The embodiments of the present application provide a storage medium for storing computer executable instructions that when executed implement the following:

acquiring log data to be checked;

The method and the device for checking the log data acquire the log data to be checked; acquiring a configuration file for representing log verification requirements, and determining a verification rule corresponding to the configuration file; and checking the log data to be checked by using the determined check rule, and generating a check result of the log data to be checked. Compared with a manual log verification mode or a verification mode with fixed verification rules in the related art, the log data verification method and device provided by the embodiment of the application can automatically match the verification rules according to the actual verification requirements of users, so that the effect that the verification rules can be freely configured is achieved, the automatic verification of the log data is realized by utilizing the verification rules, the flexibility and the variability of the log verification mode are improved, the application program of a business system is not required to be modified, and the log data can be verified by adopting the corresponding verification rules according to different verification requirements.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.

Fig. 1 is a first flowchart of a method for checking log data according to an embodiment of the present application;

FIG. 2 is a second flowchart of a method for checking log data according to an embodiment of the present disclosure;

FIG. 3 is a third flow chart of a method for checking log data according to an embodiment of the present disclosure;

FIG. 4 is a fourth flowchart of a method for verifying log data according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of an implementation principle of a log data verification process according to an embodiment of the present application;

FIG. 6 is a schematic diagram of another implementation principle of the log data verification process according to an embodiment of the present application;

FIG. 7 is a first flowchart of a method for verifying log data according to another embodiment of the present disclosure;

FIG. 8 is a second flowchart of a method for verifying log data according to another embodiment of the present disclosure;

FIG. 9 is a third flowchart of a method for verifying log data according to another embodiment of the present disclosure;

fig. 10 is a schematic diagram of a first module composition of a log data verification device according to an embodiment of the present application;

FIG. 11 is a schematic diagram illustrating a second module composition of a log data verification device according to an embodiment of the present disclosure;

Fig. 12 is a schematic structural diagram of a log data verification device according to an embodiment of the present application.

Detailed Description

In order to better understand the technical solutions in the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.

An embodiment of the application provides a method and a device for checking log data, which can automatically match checking rules according to actual checking demands of users, thereby achieving the effect that the checking rules can be freely configured, and then utilizing the checking rules to realize automatic checking of the log data, improving flexibility and variability of a log checking mode, and realizing that the corresponding checking rules are adopted to check the log data by combining different checking demands without modifying application programs of a business system.

Fig. 1 is a first flowchart of a log data verification method provided in an embodiment of the present application, where a log verification program implementing the verification method in fig. 1 may be disposed in the same hardware device as a service system program, or may be disposed in a different hardware device from the service system program, as shown in fig. 1, and the method at least includes the following steps:

Step S101, acquiring log data to be checked; the log data to be checked may be log data output by the service system, or may be log data output by a distributed data processing server in docking with the service system, where the log data may be from a server log, a client log, and a Web log, where the log data is data generated by an operation action of a user when the user uses a certain internet product, for example, a download log generated by a file download operation for the user, a browse log generated by a Web browse operation for the user, a transaction log generated by a network transfer transaction operation for the user, and so on.

Step S102, a configuration file for representing log verification requirements is obtained, and a verification rule corresponding to the configuration file is determined.

Step S103, checking the log data to be checked by using the determined checking rule, and generating a checking result of the log data to be checked. The verification result may include one or more of information including an identification of a log file having error information, an identification of a duplicate log file, an identification of a missing log file, a log error rate, a log correct rate, a log duplicate rate, and a log miss rate.

The execution subject of the verification method may be a server or a client, and a log verification program independent of the service system program is provided in the server or the client, and the steps S101 to S103 are executed when the log verification program is executed.

In the embodiment provided by the application, the log verification program is independent of the service system program, and the log verification program is changed according to the change of the configuration file when being specifically executed, and the log verification program and the service system program are loosely coupled, independent and not affected, so that the verification rule can be automatically matched according to the actual verification requirement of a user, the effect that the verification rule can be freely configured is achieved, the automatic verification of log data is realized by utilizing the verification rule, the flexibility and the variability of a log verification mode are improved, the application program of the service system is not required to be modified, and the corresponding verification rule can be adopted to verify the log data by combining different verification requirements.

It should be noted that, the steps S101 and S102 are executed in no strict sequence. However, in the case that the configuration file includes the identification information of the log data to be checked, at this time, step S102 is executed first, step S101 is executed again, and step S103 is executed finally, specifically, first, a configuration file for characterizing the log checking requirement is obtained, and a checking rule corresponding to the configuration file is determined; then, according to the identification information in the configuration file, acquiring log data to be checked corresponding to the identification information (namely, searching the log data matched with the identification information from a large amount of received log data as the log data to be checked); and finally, checking the log data to be checked by using the determined checking rule, and generating a checking result of the log data to be checked. In addition, aiming at the condition that the log data to be checked contains a plurality of log files, each log file is checked one by utilizing the determined check rule according to the log check sequence specified in the configuration file or the log check sequence automatically determined by the log check system, and a corresponding check result is generated. Therefore, a user can selectively check the log data, the usability of the log checking system is improved, the log checking sequence can be customized, and the flexibility of log checking is further improved.

The step S102 of obtaining the configuration file for characterizing the log verification requirement may include the following three modes:

mode one: the configuration file sent by the user terminal is received, the configuration file is generated in the mode, and for professional users who write the configuration file, the automatic definition verification requirement of the users can be better met, so that the effect of freely configuring the verification rule is achieved, the flexibility and the diversity of log verification are improved, and different verification requirements of the users are met.

Mode two: according to the verification configuration information sent by the user terminal, generating a configuration file corresponding to the verification configuration information, generating the configuration file in the mode, and automatically generating a corresponding position file only by combining the user with the log verification requirement of the user under the condition that the non-professional user who cannot write the configuration file but the special verification requirement exists.

Mode three: generating a configuration file corresponding to the log type according to the log type of the log data to be checked, generating the configuration file in the mode, and for a non-professional user which does not write the configuration file and does not have special checking requirements, automatically generating the configuration file corresponding to the log type of the log data to be checked according to the corresponding relation between the preset log type and the checking requirements (the corresponding relation can be determined by the system according to the configuration file selected by the user in the past), wherein on one hand, the user does not need to form the configuration file and upload the configuration file; on the other hand, the user does not need to input verification configuration information, and the verification work of the log data can be automatically completed, so that the practical application scene of the verification method is further expanded.

It should be noted that, in the implementation, the selection may be performed according to the specific situation and the actual requirement of the user.

The language format of the log verification requirement in the configuration file accords with the JSON data format.

In the embodiment of the application, the standard JSON protocol is adopted as the format of the configuration file, the JSON data format is a set of a plurality of key/value pairs, the specific contents of the plurality of keys/values can be freely configured according to the actual verification requirements of users, various log verification requirements can be written, and the flexibility of the configuration of the log verification requirements is ensured.

Specifically, as shown in fig. 2, step S102 obtains a configuration file for characterizing a log verification requirement, and determines a verification rule corresponding to the configuration file, which specifically includes:

step 1021, obtaining a configuration file for representing the log verification requirement, and analyzing the configuration file to obtain the corresponding log verification requirement;

step 1022, selecting at least one verification plug-in corresponding to the log verification requirement from the verification plug-in library according to the log verification requirement, wherein the verification plug-in is used for realizing at least one verification function;

correspondingly, the step S103 performs verification on the log data to be verified by using the determined verification rule, and generates a verification result of the log data to be verified, which specifically includes:

Step 1031, checking the log data to be checked by using at least one selected check plug-in;

step 1032, generating a verification result of the log data to be verified.

The plug-in has the characteristics of easy modification and strong maintainability, and the plug-ins are mutually independent and are connected with the log verification main program through interfaces, so that the plug-in can be deleted, inserted and modified at any time, the structure is flexible, the plug-in is easy to modify, and the software is convenient to upgrade and maintain.

Further, in order to better meet the log verification requirements of user diversification under the condition that the number of verification plug-ins is limited, based on the fact that each verification plug-in the verification plug-in library is used for realizing one verification function, and the verification functions of every two verification plug-ins are completely different;

The step 1031 of verifying the log data to be verified by using at least one verification plug-in unit selected, specifically includes:

and checking the log data to be checked by using a checking plug-in set formed by combining the plurality of selected checking plug-ins.

In the implementation, each verification plug-in the verification plug-in library can only have one verification function plug-in, namely the verification plug-in library comprises a plurality of verification plug-ins with single verification functions, such as a presence verification plug-in, a type verification plug-in, a value field verification plug-in, a content length verification plug-in, a logic relationship verification plug-in and the like, wherein the logic relationship verification plug-in comprises a causal relationship verification plug-in, a time sequence relationship verification plug-in or a dependency relationship verification plug-in and the like, and the verification functions of each verification plug-in are different.

In the embodiment provided by the application, the verification plug-ins are atomized by taking the minimum verification function as a unit, so that the characteristics of supporting multiple atomic verification operators are provided, the verification operators can be freely and flexibly combined according to the log verification requirements of users to obtain the required verification rules, and therefore, even if the number of the verification plug-ins contained in the verification plug-in library is limited, the unlimited number of verification plug-in sets meeting various log verification requirements can be obtained by randomly combining the limited verification plug-ins with a single verification function, and therefore, the log verification requirements of users can be better met under the condition that the number of the verification plug-ins is limited, and the maintenance cost of the verification plug-ins is greatly reduced.

Further, in order to improve the user experience, considering that with the continuous upgrade of the product, the user may generate new verification requirements at any time, based on this, as shown in fig. 3, the verification method further includes:

step S104, receiving a verification plug-in library updating request sent by a user terminal, wherein the updating request carries a verification plug-in identifier to be modified and modified content, or the updating request carries a verification plug-in identifier to be added and a program code, or the updating request carries a verification plug-in identifier to be deleted;

step S105, updating the verification plug-in library according to the update request to obtain an updated verification plug-in library.

In the implementation, the update request of the check plug-in library of the user terminal can be received by setting a preset interface, a user transmits the update request carrying the check plug-in identifier to be modified and the modification content, or the check plug-in identifier to be added and the program code, or the check plug-in identifier to be deleted through the interface, so that the check function is added, deleted or modified only by correspondingly adding, deleting or modifying the check plug-in, and the whole log check program architecture is not influenced in the update maintenance process of the check plug-in library, thereby the adjustment of the check function can be realized quickly, the check function is expanded, and the diversified log check requirements of the user are further guaranteed to be better met.

The verification plug-in library can be maintained by system developers or third party users with setting authority, and specifically, an open interface can be set for the third party users, so that the user diversified and personalized log verification requirements are further met, and the user experience is improved.

In addition, in order to achieve the purpose of controllable update management of the verification plug-ins, instead of any user being able to delete or modify any verification plug-in the verification plug-in library at will, respective update permissions may be set for the third party user, for example, the third party user only has the permission to update the verification plug-ins uploaded by the third party user, but cannot modify or delete the verification plug-ins uploaded by the system developer. In order to achieve the purpose of controllability of update management of the verification plug-in, in this embodiment of the present application, as shown in fig. 4, after receiving the verification plug-in library update request sent by the user terminal, step S104 further includes:

step S111, judging whether the user terminal is a third party user according to the identification of the user terminal; if not (indicating that the user terminal is a user terminal used by a system developer), directly executing step S105 to update the verification plug-in library according to the update request to obtain an updated verification plug-in library; if yes, executing step S112 to determine whether the user terminal has the update authority of the check plug-in corresponding to the update request according to the update request of the check plug-in library;

If yes, executing step S105 to update the verification plug-in library according to the update request to obtain an updated verification plug-in library;

if not, the update operation is not executed, and step S113 is executed to generate prompt information for indicating that the current user has no update authority.

Further, considering that the current log types are various, in the case that the log data to be checked includes log files of various log types, the embodiment of the present application may further configure respective check rules for log files of different log types, based on this, after acquiring the log data to be checked in the step S101, further includes:

according to the log types of the log files in the log data to be checked, dividing the log files into a plurality of categories, wherein each category comprises at least one log file of the log types, namely each category can only comprise one log file of the log types or more than two log files of the log types;

the generating a configuration file corresponding to the log type according to the log type of the log data to be checked specifically includes:

for each category, determining a check item corresponding to the category, and generating a configuration file corresponding to the category according to the check item;

The step S103 of verifying the log data to be verified by using the determined verification rule specifically includes:

and respectively checking at least one log file in each category by utilizing the determined check rule corresponding to the category one by one until checking all log files in the category is completed.

For example, the corresponding relationship between the preset log type, the preset log category and the preset check term in the embodiment of the present application may be specifically shown in table 1 below.

TABLE 1

Log type	Log category	Check item
			Transaction log, deposit log, borrow log	High sensitivity log	C
Log-in log, account modification log and password modification log	Mid sensitivity log	B
			Click log, browse log and evaluation log	Low sensitivity log	A

The method comprises the steps of dividing a log file into categories belonging to low-sensitivity logs in the case that the log type of log data to be checked is any one of click logs, browse logs and evaluation logs, wherein the corresponding check item A comprises: presence verification and value range verification;

aiming at the condition that the log type of log data to be checked is any one of log-in log, account number modification log and password modification log, dividing the log file into categories belonging to medium sensitivity log, wherein the corresponding check item B comprises: presence verification, value range verification and content length verification;

Aiming at the condition that the log type of log data to be checked is any one of transaction log, deposit log and borrow log, dividing the log file into categories belonging to high-sensitivity log, wherein the corresponding check item C comprises: presence verification, value range verification, content length verification and logical relationship verification.

In the embodiment of the application, firstly, based on the log type of each log file, classifying the plurality of log files, and classifying the log files using the same check item into one class; generating configuration files corresponding to each class, and determining corresponding verification rules according to the respective configuration files; and finally, checking according to the categories, namely after checking all log files in one category is completed, checking the log files in the next category, so that frequent replacement of checking rules is not needed, and the checking efficiency of log data is improved.

Further, considering that there may be a case where the number of log files included in some categories is relatively small, for this case, in order to further improve log verification efficiency, a separate verification rule may not be used for the log files in the category, but a more strict verification rule may be selected for verifying the log files in the category, so as to achieve the purpose of optimizing the merging process, so that the verification plug-ins do not need to be replaced frequently, and based on this, each category corresponds to a verification level, which may be specifically shown in the following table 2;

After the plurality of log files are divided into a plurality of categories according to the log types of the log files in the log data to be checked, the method further comprises:

judging whether the number of the log files in each category is smaller than a preset number threshold, for example, judging whether the number of the log files divided into three categories of low-sensitivity log, medium-sensitivity log and high-sensitivity log is smaller than the preset number threshold;

if so, merging at least one log file in the category with the log file with the check level higher than the category into one category, for example, the number of the log files divided into the category belonging to the low-sensitivity log is smaller than a preset number threshold, and at this time, merging the log file in the category belonging to the low-sensitivity log and the log file in the category belonging to the medium-sensitivity log into one category, that is, checking the log file in the category belonging to the low-sensitivity log by adopting a check rule corresponding to the category belonging to the medium-sensitivity log.

TABLE 2

Log type	Log category	Check level
			Transaction log, deposit log, borrow log	High sensitivity log	Third grade
Log-in log, account modification log and password modification log	Mid sensitivity log	Second level
			Click log, browse log and evaluation log	Low sensitivity log	First level of

The check items corresponding to each log category are the same as those in table 1, and are not described here again.

Further, since the log verification program for verifying the log data may be set in the same hardware device as the service system program, or may be set in a different hardware device from the service system program, considering that the log verification program and the service system program are set in the same hardware device, the problem of resource contention may be affected due to a certain load being required when the log verification program is run, so that the log verification program may be deployed in an independent hardware device when the idle load of the hardware device deployed with the service system program is relatively small, and the problem of data leakage, poor data transmission smoothness and data loss may exist when the transmission of the log data to be verified between the two hardware devices is required, based on this, before the step S101 obtains the log data to be verified, the method further includes:

Executing at least one of the following operations on log data transmitted by a service system or a distributed data processing system, and taking the log data after executing the at least one of the following operations as log data to be checked:

decrypting the received encrypted log data; or,

decompressing the received compressed log data; or,

and carrying out integrity verification on the log data after decryption processing and/or decompression processing.

Specifically, in the process that the service system (client) or the distributed data processing system transmits the log data to be checked to the log checking system (server), the following implementation manner is needed to solve the problems of data leakage, poor data transmission fluency and data loss, which is specifically:

(1) In order to prevent the log from being illegally intercepted and the log data from being leaked, the transmission safety of the log data is improved, firstly, the log data to be checked is encrypted in a service system (client side) or a distributed data processing system, the log data to be checked after being encrypted is transmitted to a log checking system (server side), and correspondingly, after the log checking system (server side) receives the log data after being encrypted, the encrypted log data needs to be decrypted, wherein an asymmetric encryption algorithm can be adopted to carry out encryption processing on the log data.

(2) In order to save the mobile flow required by the data transmission of the client and improve the success rate of the data transmission in the network, firstly, the business system (client) or the distributed data processing system compresses the log data to be checked, the compressed log data to be checked is transmitted to the log checking system (server), and correspondingly, the log checking system (server) needs to decompress the compressed log data after receiving the compressed log data, wherein the log data can be decompressed by adopting a GZIP algorithm.

(3) In order to ensure that log data is not re-lost and not lost in the network transmission process, the integrity and consistency of log data transmission are improved, a log verification system (a server side) receives a data transmission completion instruction sent by a service system (a client side) or a distributed data processing system, after received log data are decrypted and/or decompressed, whether transmitted log files indicated by the data transmission completion instruction are consistent or not is determined according to a received random character string token and a log number sequence_id of each log file, if the log files are missing, a log file retransmission request is sent to the service system (the client side) or the distributed data processing system, and if the log files are repeated, repeated log files are deleted.

Specifically, the step S103 of verifying the log data to be verified by using the determined verification rule includes: and executing at least one of the following checking operations on each log file to be checked contained in the log data to be checked by using the determined checking rule:

determining whether preset attribute data exist in the log file to be checked; or,

determining whether the log type of the log file to be checked is correct; or,

determining whether the length of attribute data in the log file to be checked meets the preset length requirement; or,

determining whether the value range of the attribute data in the log file to be checked meets the preset value range requirement; or,

it is determined whether an associated log file having a particular logical relationship with the log file to be checked exists.

Which items of verification operations are executed on the log data to be verified is determined by the log verification requirement written in the configuration file.

In the process of generating the product log file, a random character string, namely a token, is generated for a certain use operation of the Internet product by a user, and the marks of the log files related to the use operation all contain the random character string, namely the random character string is generated for the same use operation of the product for a group of log files with the same random character string; and also generates a respective log number, namely sequence_id, for each log file generated in the current use operation, so that the determining whether the associated log file having a specific logical relationship with the log file to be checked exists specifically includes:

Searching a plurality of associated log files with the same random character strings as the log files to be checked;

according to the log number of the log file to be checked, determining whether an associated log file meeting a specific logic relationship with the log file to be checked exists, wherein the logic relationship can be a causal relationship, a time sequence relationship, a dependency relationship and the like, specifically verifying whether the associated log file with which logic relationship with the log to be checked exists or not, and determining by a logic relationship verification type specified in a configuration file, namely determining by the actual log verification requirement of a user.

In this embodiment of the present application, taking the verification timing sequence relationship as an example, determining whether an associated log file satisfying a specific logical relationship with the log file to be verified exists according to the log number of the log file to be verified, specifically includes:

determining whether a prior log file of the log file to be checked exists (namely whether an associated log file generated before the log file to be checked is generated in a certain product use operation exists) according to the log number of the log file to be checked; or,

and determining whether a later log file of the log file to be checked exists (namely whether an associated log file generated after the log file to be checked is generated in a certain product use operation exists) according to the log number of the log file to be checked.

For example, when "a log" is specified in the configuration file, B log "will occur, then if the current log file to be checked is a log, it needs to be determined whether a B log having the same random string as a log is generated after a log is generated, and if not, the group of logs is considered to be not checked.

Further, in order to facilitate the third party user and the developer to obtain the respective required log data verification result and realize traceability of the verification result, after the verification result of the log data to be verified is generated, the method further includes: and performing at least one of the following operations on the verification result:

transmitting a verification result of log data to be verified to a corresponding user terminal; or,

transmitting a verification result of the log data to be verified to a corresponding research and development system; or,

the verification result of the log data to be verified is stored in the preset database, so that the method is favorable for related personnel to obtain the verification result of the verified log data at any time later, and traceability of the verification result is realized.

Fig. 5 is a schematic diagram of an implementation principle of a log data verification process provided in an embodiment of the present application, where, as shown in fig. 5, a rule engine is used as a main program of a log verification system, and a verification function carrier adopts a plug-in mode, and each verification plug-in with a specific verification function independently exists, and can be dynamically plugged in and plugged out with use. Specifically, the rule engine inputs log data and configuration files, and after receiving the log data and the configuration files, the rule engine can analyze the configuration files to obtain corresponding log verification requirements; selecting at least one check plug-in corresponding to the log check requirement from a check plug-in library; and finally, checking the log data to be checked by using at least one selected check plug-in, generating a check result of the log data to be checked, and outputting the check result of the log data to be checked by using the rule engine.

If the parsed log verification requirement contains log identification information to be verified, before verifying the log data to be verified by using the selected at least one verification plug-in, the method further comprises: and searching out the log data matched with the identification information as log data to be checked.

In addition, system developers and third party users can update and maintain the check plug-ins in the check plug-in library through a preset interface, the main program of the log check system is not required to be changed in the update process, the check plug-ins are directly added, deleted and modified through the preset interface, diversified and personalized log check requirements of the users are further met, and the user experience is improved.

Fig. 6 is a schematic diagram of another implementation principle of the log data verification process provided in the embodiment of the present application, as shown in fig. 6, the rule engine in fig. 5 may use a distributed programming architecture, may be a set of distributed programming framework based on ODPS (Open Data Processing Service, develop data processing services), may use a Python programming language to flexibly operate input log data, that is, perform automatic verification of the log data through a distributed server cluster, and in a case where the log data processing amount is relatively large, may use the system architecture, and perform automatic verification on the log data in parallel by multiple servers, so that the verification efficiency of the log data can be improved, and full-amount log quick verification is implemented.

Next, a specific example is given in the embodiment of the present application, and a verification process of the download log is taken as an example:

(1) The method comprises the steps of obtaining log data to be checked, wherein the log data to be checked is a downloading log, and specifically comprises the following steps:

{

"log_type":"download_start"

"uid":"abcdef123456",

"age":201,

"download_app":"",

"token":"abcabcabcabc",

"sequence_id":1

}

(2) The method comprises the steps of obtaining a configuration file for representing log verification requirements, wherein specific codes of the configuration file are as follows:

/>

(3) Analyzing the configuration file to obtain a corresponding log verification requirement, wherein the log verification requirement is that 3-aspect verification is executed on a log file with a log type of a downloading log: firstly, determining whether a sex (sex) attribute (namely presence verification) exists in the log file; secondly, determining whether an age (age) attribute in the log file is between 0 and 150 (namely checking a value range); third, it is determined whether the length of the user ID in the log file is 32 bits (content length check).

(4) And selecting at least one verification plug-in corresponding to the log verification requirement from the verification plug-in library according to the log verification requirement, namely selecting the existence verification plug-in, the value range verification plug-in and the content length verification plug-in from the verification plug-in library.

According to the log data verification method in the embodiment of the application, log data to be verified is obtained; acquiring a configuration file for representing log verification requirements, and determining a verification rule corresponding to the configuration file; and checking the log data to be checked by using the determined check rule, and generating a check result of the log data to be checked. Compared with a manual log verification mode or a verification mode with fixed verification rules in the related art, the log data verification method provided by the embodiment of the application can automatically match the verification rules according to actual verification requirements of users, so that the effect that the verification rules can be freely configured is achieved, the automatic verification of the log data is realized by utilizing the verification rules, the flexibility and the variability of the log verification mode are improved, the application program of a business system is not required to be modified, and the log data can be verified by adopting the corresponding verification rules according to different verification requirements.

According to the log data verification method, under the condition that the number of verification plug-ins is limited, the user diversified log verification requirements can be met better, and the maintenance cost of the verification plug-ins is reduced greatly.

Fig. 7 is a first flowchart of a method for checking log data according to another embodiment of the present application, as shown in fig. 7, where the method at least includes the following steps:

step S701, obtaining log data to be checked;

step S702, obtaining a configuration file for representing log verification requirements;

step S703, selecting at least one checking plug-in corresponding to the configuration file from a checking plug-in library according to the configuration file, wherein each checking plug-in is used for realizing a checking function, and the checking functions of every two checking plug-ins are completely different;

step S704, checking the log data to be checked by using a checking plug-in set formed by combining the at least one checking plug-in;

step S705, generating the checking result of the log data to be checked.

In the embodiment of the application, the verification plug-ins are atomized by taking the minimum verification function as a unit, so that the method has the characteristic of supporting multiple atomic verification operators, and the verification operators can be freely and flexibly combined according to the log verification requirements of users to obtain required verification rules, so that even if the number of the verification plug-ins contained in the verification plug-in library is limited, an infinite number of verification plug-in sets meeting various log verification requirements can be obtained by randomly combining the limited verification plug-ins with a single verification function, and therefore, the log verification requirements of the users can be better met under the condition that the number of the verification plug-ins is limited, and the maintenance cost of the verification plug-ins is greatly reduced.

Further, the user may further configure the respective log verification requirements for the log files of different log types, that is, the classification verification information may be written in the configuration file, or the verification configuration information including the classification verification information may be sent through the user terminal, so, as shown in fig. 8, after the step S702 obtains the configuration file for characterizing the log verification requirements, the method further includes:

step S706, dividing the plurality of log files into a plurality of categories according to the classification verification information in the configuration file and the log types of the log files in the log data to be verified, wherein each category comprises at least one log file of the log types;

correspondingly, the step S703 selects at least one verification plug-in corresponding to the configuration file from the verification plug-in library according to the configuration file, and specifically includes:

step S7031, determining a check item corresponding to each category, and selecting at least one check plug-in corresponding to the category from a check plug-in library according to the check item;

correspondingly, the step S704 of verifying the log data to be verified by using the verification plug-in set formed by combining the at least one verification plug-in specifically includes:

Step S7041, for each category, using the selected set of at least one verification plug-in corresponding to the category to combine the verification plug-ins, verifying at least one log file in the category one by one until the verification of all log files in the category is completed, and executing a verification operation on each log file in the next category.

Taking the corresponding relationship between the log type, the log category and the check item in table 1 as an example, the corresponding relationship is taken as classification check information in the configuration file, specifically:

aiming at the condition that the log type of log data to be checked is any one of a click log, a browse log and an evaluation log, dividing the log file into categories belonging to low-sensitivity logs, wherein the corresponding check item A comprises: presence verification and value range verification;

Further, consider that there may be a situation that the number of log files included in some categories is relatively small, for this situation, in order to improve log verification efficiency, a separate verification rule may not be used for the log files in the category, but a more strict verification rule is selected to verify the log files in the category, so as to achieve the purpose of optimizing the merging process, so that the verification plug-in is not required to be replaced frequently, and based on this, each category corresponds to one verification level, and the corresponding relationship in table 2 is still taken as an example; as shown in fig. 9, step S706, after dividing the plurality of log files into a plurality of categories according to the classification verification information in the configuration file and the log type of each log file in the log data to be verified, further includes:

step S707, determining whether the number of log files in each category is smaller than a preset number threshold, for example, determining whether the number of log files divided into three categories, i.e., a low sensitivity log, a medium sensitivity log, and a high sensitivity log, is smaller than a preset number threshold;

if so, step S708 is executed to merge at least one log file in the category and the log files with the verification level higher than the category into one category, for example, the number of log files classified into the category belonging to the low sensitivity log is smaller than the preset number threshold, at this time, the log files in the category belonging to the low sensitivity log and the log files in the category belonging to the medium sensitivity log may be merged into one category, that is, the log files in the category belonging to the low sensitivity log may be verified by using the verification rule corresponding to the category belonging to the medium sensitivity log.

If not, step S7031 is executed to determine, for each category, a check item corresponding to the category, and select at least one check plug-in corresponding to the category from the check plug-in library according to the check item.

It should be noted that, another embodiment of the present application and an embodiment of the present application are based on the same inventive concept, so that the specific implementation of this embodiment may refer to the implementation of the foregoing method, and the repetition is not repeated.

The embodiment of the present application further provides a log data verification device based on the same technical concept, as shown in fig. 10, which corresponds to the log data verification method described in fig. 2 to 6, and includes: a log data acquisition module 1001, a check rule determination module 1002, and a log data check module 1003.

In a specific embodiment, the log data obtaining module 1001 is configured to obtain log data to be checked;

the verification rule determining module 1002 is configured to obtain a configuration file for characterizing log verification requirements, and determine a verification rule corresponding to the configuration file;

the log data verification module 1003 is configured to verify the log data to be verified by using the determined verification rule, and generate a verification result of the log data to be verified.

Optionally, for the profile generation process, the above-mentioned verification rule determining module 1002 is specifically configured to:

receiving a configuration file sent by a user terminal; or,

generating a configuration file corresponding to the verification configuration information according to the verification configuration information sent by the user terminal; or,

and generating a configuration file corresponding to the log type according to the log type of the log data to be checked.

Optionally, the language format of the log verification requirement in the configuration file conforms to the JSON data format.

Optionally, for the verification rule determining process, the verification rule determining module 1002 is specifically configured to:

analyzing the configuration file to obtain corresponding log verification requirements;

according to the log verification requirement, at least one verification plug-in corresponding to the log verification requirement is selected from a verification plug-in library, and the verification plug-in is used for realizing at least one verification function;

correspondingly, the log data checking module 1003 is specifically configured to:

and checking the log data to be checked by using the selected at least one checking plug-in.

Optionally, each verification plug-in the verification plug-in library is used for realizing a verification function, and the verification functions of every two verification plug-ins are completely different;

The log data checking module 1003 is specifically configured to:

and verifying the log data to be verified by using a verification plug-in set formed by combining the plurality of selected verification plug-ins.

Optionally, as shown in fig. 11, the verification device further includes:

an update request receiving module 1004, configured to receive an update request of a verification plug-in library sent by a user terminal, where the update request carries a verification plug-in identifier to be modified and a modification content, or the update request carries a verification plug-in identifier to be added and a program code, or the update request carries a verification plug-in identifier to be deleted;

and a plug-in library updating module 1005, configured to update the verification plug-in library according to the update request, to obtain an updated verification plug-in library.

Optionally, the log data to be checked includes log files of various log types;

the verification device further comprises: the log data classification module 1006 is configured to divide a plurality of log files into a plurality of categories according to log types of log files in the log data to be verified after obtaining the log data to be verified, where each category includes at least one log file of a log type;

Correspondingly, for the configuration file generation process, the above-mentioned verification rule determining module 1002 is specifically configured to: for each category, determining a check item corresponding to the category, and generating a configuration file corresponding to the category according to the check item;

correspondingly, the log data checking module 1003 is specifically configured to: and respectively checking the at least one log file in each category by utilizing the determined check rule corresponding to the category one by one until checking all log files in the category is completed.

Optionally, each of the categories corresponds to a level of verification; the verification device further comprises: a category re-dividing module 1007, configured to determine whether the number of log files in each category is less than a preset number threshold after dividing a plurality of log files into a plurality of categories according to log types of each log file in the log data to be checked; if yes, merging at least one log file in the category with the log file with the check level higher than the corresponding check level of the category into one category.

Optionally, the verification device further includes: the data preprocessing module 1008 is configured to perform at least one of the following operations on log data transmitted by the service system or the distributed data processing system before obtaining log data to be verified, and take the log data after performing the at least one of the following operations as the log data to be verified:

Decrypting the received encrypted log data; or,

decompressing the received compressed log data; or,

Optionally, the log data checking module 1003 is specifically configured to: and executing at least one of the following checking operations on each log file to be checked contained in the log data to be checked by using the determined checking rule:

determining whether the log type of the log file to be checked is correct; or,

Optionally, the verification device further includes: a verification result processing module 1009, configured to perform at least one of the following operations on the verification result:

transmitting the verification result to a corresponding user terminal; or,

Transmitting the verification result to a corresponding research and development system; or,

and storing the verification result into a preset database.

The log data verification device in the embodiment of the application obtains log data to be verified; acquiring a configuration file for representing log verification requirements, and determining a verification rule corresponding to the configuration file; and checking the log data to be checked by using the determined check rule, and generating a check result of the log data to be checked. Compared with a manual log verification mode or a verification mode with fixed verification rules in the related art, the log data verification device provided by the embodiment of the application can automatically match the verification rules according to actual verification demands of users, so that the effect that the verification rules can be freely configured is achieved, the automatic verification of the log data is realized by utilizing the verification rules, the flexibility and the variability of the log verification mode are improved, the application program of a business system is not required to be modified, and the log data can be verified by adopting the corresponding verification rules according to different verification demands.

In another specific embodiment, the log data obtaining module 1001 is configured to obtain log data to be verified;

The verification rule determining module 1002 is configured to obtain a configuration file for characterizing a log verification requirement, and select at least one verification plug-in corresponding to the configuration file from a verification plug-in library according to the configuration file, where each verification plug-in is configured to implement a verification function, and the verification functions of every two verification plug-ins are completely different;

the log data verification module 1003 is configured to verify the log data to be verified by using a verification plug-in set formed by combining the at least one verification plug-in, and generate a verification result of the log data to be verified.

It should be noted that, since the principle of the solution of the problems of these devices is similar to that of the verification method described in fig. 7 to 9, the implementation of the device may refer to the implementation of the method, and the repetition is omitted.

Further, corresponding to the methods shown in fig. 1 to 6, based on the same technical concept, the embodiment of the present application further provides a log data verification device, which is used for executing the method for verifying log data as shown in fig. 12.

The log data verification device may be configured or configured to vary significantly, and may include one or more processors 1201 and memory 1202, where the memory 1202 may store one or more storage applications or data. Wherein the memory 1202 may be transient storage or persistent storage. The application programs stored in memory 1202 may include one or more modules (not shown in the figures), each of which may include a series of computer-executable instructions for use in a log data verification device. Still further, the processor 1201 may be configured to communicate with the memory 1202 to execute a series of computer executable instructions in the memory 1202 on the log data verification device. The log data verification device may also include one or more power supplies 1203, one or more wired or wireless network interfaces 1204, one or more input/output interfaces 1205, one or more keyboards 1206, and the like.

In a particular embodiment, the log data verification device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the log data verification device, and the execution of the one or more programs by the one or more processors comprises computer-executable instructions for:

acquiring log data to be checked;

Optionally, the computer executable instructions, when executed, obtain a profile for characterizing log verification requirements, comprising:

receiving a configuration file sent by a user terminal; or,

Optionally, the computer executable instructions, when executed, conform to JSON data format in a language format of log verification requirements in the configuration file.

Optionally, the determining the verification rule corresponding to the configuration file includes:

and verifying the log data to be verified by using the determined verification rule, including:

Optionally, when the computer executable instructions are executed, each verification plug-in the verification plug-in library is used for realizing a verification function, and the verification functions of every two verification plug-ins are completely different;

the verifying the log data to be verified by using the selected at least one verification plug-in comprises the following steps:

Optionally, the computer-executable instructions, when executed, further comprise computer-executable instructions for:

receiving a verification plug-in library updating request sent by a user terminal, wherein the updating request carries a verification plug-in identifier to be modified and modified content, or the updating request carries a verification plug-in identifier to be added and a program code, or the updating request carries a verification plug-in identifier to be deleted;

and updating the verification plug-in library according to the update request to obtain an updated verification plug-in library.

Optionally, the computer executable instructions, when executed, the log data to be verified comprises log files of a plurality of log types;

after the log data to be checked is obtained, the method further comprises: dividing a plurality of log files into a plurality of categories according to the log types of the log files in the log data to be checked, wherein each category comprises at least one log file of the log types;

the generating a configuration file corresponding to the log type according to the log type of the log data to be checked comprises: for each category, determining a check item corresponding to the category, and generating a configuration file corresponding to the category according to the check item;

And verifying the log data to be verified by using the determined verification rule, including: and respectively checking the at least one log file in each category by utilizing the determined check rule corresponding to the category one by one until checking all log files in the category is completed.

Optionally, the computer executable instructions, when executed, each of said categories corresponds to a level of verification;

after dividing the plurality of log files into a plurality of categories according to the log types of the log files in the log data to be checked, the method further comprises:

judging whether the number of the log files in each category is smaller than a preset number threshold value or not;

if yes, merging at least one log file in the category with the log file with the check level higher than the corresponding check level of the category into one category.

Optionally, the computer executable instructions, when executed, further comprise, before the obtaining log data to be verified:

Decrypting the received encrypted log data; or,

decompressing the received compressed log data; or,

Optionally, when executed, the verifying the log data to be verified using the determined verification rule includes: and executing at least one of the following checking operations on each log file to be checked contained in the log data to be checked by using the determined checking rule:

determining whether the log type of the log file to be checked is correct; or,

Optionally, the computer-executable instructions, when executed, further comprise computer-executable instructions for: and performing at least one of the following operations on the verification result:

Transmitting the verification result to a corresponding user terminal; or,

and storing the verification result into a preset database.

The log data verification device in the embodiment of the application obtains log data to be verified; acquiring a configuration file for representing log verification requirements, and determining a verification rule corresponding to the configuration file; and checking the log data to be checked by using the determined check rule, and generating a check result of the log data to be checked. Compared with a manual log verification mode or a verification mode with fixed verification rules in the related art, the log data verification device provided by the embodiment of the application can automatically match the verification rules according to actual verification demands of users, so that the effect that the verification rules can be freely configured is achieved, automatic verification of log data is achieved by utilizing the verification rules, flexibility and variability of the log verification mode are improved, application programs of a business system are not required to be modified, and the fact that the corresponding verification rules are adopted to verify the log data according to different verification demands can be achieved.

In another particular embodiment, a log data verification device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the log data verification device, and the execution of the one or more programs by one or more processors comprises computer-executable instructions for:

Acquiring log data to be checked;

According to the log data verification device, the verification plug-ins are atomized by taking the minimum verification function as a unit, the characteristics of supporting multiple atomic verification operators are provided, the verification operators can be freely and flexibly combined according to the log verification requirements of users to obtain required verification rules, so that even if the number of the verification plug-ins contained in the verification plug-in library is limited, the unlimited number of verification plug-in sets meeting various log verification requirements can be obtained by randomly combining the limited verification plug-ins with a single verification function, the diversified log verification requirements of the users can be better met under the condition that the number of the verification plug-ins is limited, and the maintenance cost of the verification plug-ins is greatly reduced.

It should be noted that, since the principle of the problem solved by these devices is similar to that of the verification method described in fig. 7 to 9, the implementation of the device may refer to the implementation of the method, and the repetition is omitted.

Further, corresponding to the methods shown in fig. 1 to 6, based on the same technical concept, the embodiments of the present application further provide a storage medium for storing computer executable instructions, where in a specific embodiment, the storage medium may be a U disc, an optical disc, a hard disk, etc., and the computer executable instructions stored in the storage medium can implement the following flow when executed by a processor:

acquiring log data to be checked;

Optionally, the storage medium stores computer executable instructions that, when executed by the processor, obtain a profile for characterizing log verification requirements, comprising:

receiving a configuration file sent by a user terminal; or,

Optionally, the storage medium stores computer executable instructions that, when executed by the processor, conform to JSON data format in a language format of log verification requirements in the configuration file.

Optionally, the computer executable instructions stored on the storage medium, when executed by the processor, determine a verification rule corresponding to the configuration file, including:

Optionally, the computer executable instructions stored in the storage medium, when executed by the processor, are used for implementing a verification function by each verification plug-in the verification plug-in library, wherein the verification functions of the two verification plug-ins are completely different;

Optionally, the computer executable instructions stored by the storage medium, when executed by the processor, further implement the following:

Optionally, the storage medium stores computer executable instructions that, when executed by the processor, comprise log files of a plurality of log types;

Optionally, the storage medium stores computer executable instructions that, when executed by the processor, each of the categories corresponds to a level of verification;

Optionally, the computer executable instructions stored on the storage medium, when executed by the processor, further comprise, before the obtaining log data to be checked:

decrypting the received encrypted log data; or,

decompressing the received compressed log data; or,

Optionally, the computer executable instructions stored on the storage medium, when executed by the processor, perform the verification on the log data to be verified using the determined verification rule, including: and executing at least one of the following checking operations on each log file to be checked contained in the log data to be checked by using the determined checking rule:

determining whether the log type of the log file to be checked is correct; or,

Optionally, the computer executable instructions stored by the storage medium, when executed by the processor, further implement the following: and performing at least one of the following operations on the verification result:

transmitting the verification result to a corresponding user terminal; or,

and storing the verification result into a preset database.

The computer executable instructions stored by the storage medium in the embodiment of the application, when executed by the processor, acquire log data to be checked; acquiring a configuration file for representing log verification requirements, and determining a verification rule corresponding to the configuration file; and checking the log data to be checked by using the determined check rule, and generating a check result of the log data to be checked. Compared with a manual log verification mode or a verification mode with fixed verification rules in the related art, the automatic log verification method can automatically match the verification rules according to actual verification requirements of users, so that the effect that the verification rules can be freely configured is achieved, automatic verification of log data is achieved by utilizing the verification rules, flexibility and variability of the log verification mode are improved, application programs of a business system are not required to be modified, and verification of the log data by adopting corresponding verification rules in combination with different verification requirements can be achieved.

In another specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, or the like, where the computer executable instructions stored in the storage medium when executed by the processor implement the following procedures:

When the computer executable instructions stored in the storage medium are executed by the processor, the verification plug-ins are atomized by taking the minimum verification function as a unit, the computer executable instructions have the characteristic of supporting multiple atomic verification operators, the verification operators can be freely and flexibly combined according to the log verification requirement of a user to obtain the required verification rule, and therefore, even if the number of the verification plug-ins contained in the verification plug-in library is limited, the infinite number of the verification plug-in sets meeting various log verification requirements can be obtained by randomly combining the limited verification plug-ins with a single verification function, so that the user diversified log verification requirement can be better met under the condition that the number of the verification plug-ins is limited, and the maintenance cost of the verification plug-ins is greatly reduced.

It should be noted that, since the principle of the problem solved by these storage media is similar to that of the verification method described in fig. 7 to 9, the implementation of the storage media can be referred to the implementation of the method, and the repetition is omitted.

In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. The method is applied to electronic equipment, the electronic equipment is provided with a log verification program independent of an application program corresponding to a service system, the service system generates log data, and the electronic equipment runs the log verification program and comprises the following steps:

acquiring log data to be checked;

dividing a plurality of log files into a plurality of categories according to the log types of the log files in the log data to be checked, and acquiring a check rule corresponding to each category;

Checking at least one log file in each category by using a checking rule corresponding to the category, and generating a checking result of the log data to be checked;

the verifying, by using a verification rule corresponding to the category, for at least one log file in each category, includes:

verifying at least one log file in the category by using the selected at least one verification plug-in; the selected at least one check plug-in is a check plug-in selected from a check plug-in library according to the category of the log file contained in the log data to be checked, and the check plug-in is used for realizing at least one check function.

2. The method of claim 1, the obtaining the verification rule corresponding to each category, comprising:

determining a check item corresponding to the category, and generating a configuration file corresponding to the category and used for representing log check requirements according to the check item;

and determining a verification rule corresponding to each category based on the configuration file.

3. The method of claim 2, wherein the language format of the log verification requirement in the configuration file conforms to JSON data format.

4. A method according to claim 3, said determining, based on said profile, a verification rule corresponding to said each category, comprising:

and selecting at least one check plug-in corresponding to the log check requirement from a check plug-in library according to the log check requirement.

5. The method according to claim 4, wherein each verification plug-in the verification plug-in library is used for realizing a verification function, the verification functions of every two verification plug-ins are completely different, and each category comprises at least one log file of a log type;

the verifying at least one log file in the category by using the selected at least one verification plug-in includes:

and verifying at least one log file in the category by using a verification plug-in set formed by combining the selected plurality of verification plug-ins.

6. The method of claim 4, further comprising:

7. The method of claim 1, each of the categories corresponding to a level of verification;

8. The method of claim 1, further comprising, prior to the obtaining log data to be checked:

decrypting the received encrypted log data; or,

decompressing the received compressed log data; or,

9. The method of claim 1, wherein the verifying, with the verification rule corresponding to the category, for at least one log file in each of the categories, respectively, includes: and respectively checking at least one log file in each category by using a checking rule corresponding to the category to execute at least one of the following checking operations:

determining whether the log type of the log file to be checked is correct; or,

10. The method of claim 1, further comprising: and performing at least one of the following operations on the verification result:

transmitting the verification result to a corresponding user terminal; or,

and storing the verification result into a preset database.

11. The method of claim 1, the verification result comprising at least: log correctness.

12. The method is applied to electronic equipment, the electronic equipment is provided with a log verification program independent of an application program corresponding to a service system, the service system generates log data, and the electronic equipment runs the log verification program and comprises the following steps:

acquiring log data to be checked;

selecting at least one check plug-in corresponding to each category from a check plug-in library by using a check rule corresponding to the category, wherein each check plug-in is used for realizing a check function, and the check functions of every two check plug-ins are completely different;

and verifying at least one log file in the category by using a verification plug-in set formed by combining the at least one verification plug-in, and generating a verification result of the log data to be verified, wherein the verification result at least comprises: log correctness.

13. A log data verification device, the device is provided with a log verification program independent of an application program corresponding to a service system, the service system generates log data, and the log verification program is used for triggering each module in the device to operate, and the device comprises:

the log data acquisition module is used for acquiring log data to be checked;

the verification rule determining module is used for dividing a plurality of log files into a plurality of categories according to the log types of the log files in the log data to be verified, and obtaining the verification rule corresponding to each category;

the log data verification module is used for verifying at least one log file in each category by utilizing a verification rule corresponding to the category, and generating a verification result of the log data to be verified;

the log data verification module is used for:

14. A log data verification device, the device is provided with a log verification program independent of an application program corresponding to a service system, the service system generates log data, and the log verification program is used for triggering each module in the device to operate, and the device comprises:

the log data acquisition module is used for acquiring log data to be checked;

the plug-in selection module is used for selecting at least one check plug-in corresponding to each category from a check plug-in library by utilizing a check rule corresponding to the category, wherein each check plug-in is used for realizing a check function, and the check functions of every two check plug-ins are completely different;

the log data verification module is used for verifying at least one log file in the category by utilizing a verification plug-in set formed by combining the at least one verification plug-in, and generating a verification result of the log data to be verified, wherein the verification result at least comprises: log correctness.

15. A log data verification apparatus provided with a log verification program independent of a corresponding application program of a business system in which log data is generated, the log verification program being arranged as computer executable instructions to trigger the apparatus to operate, comprising:

a processor; and

acquiring log data to be checked;

16. A log data verification apparatus provided with a log verification program independent of a corresponding application program of a business system in which log data is generated, the log verification program being arranged as computer executable instructions to trigger the apparatus to operate, comprising:

a processor; and

acquiring log data to be checked;

17. A storage medium storing computer executable instructions, the executable instructions including a log verification program independent of a corresponding application program of a business system in which log data is generated, the executable instructions when executed implementing the following procedures:

acquiring log data to be checked;

18. A storage medium storing computer executable instructions, the executable instructions including a log verification program independent of a corresponding application program of a business system in which log data is generated, the executable instructions when executed implementing the following procedures:

acquiring log data to be checked;