Parameter verification method and device, equipment, medium and program product

Abstract

The invention discloses a parameter verification method and device, equipment, a medium and a program product, and belongs to the technical field of big data. According to the method, in response to a parameter verification request, configuration information, target version information and target application environment information of a parameter item are obtained, and the configuration information comprises a parameter identifier and parameter content; in the preset corresponding relation, first target verification rule information corresponding to the target version information and the target application environment information is obtained, and the first target verification rule information comprises preset parameter identifiers of the preset parameter items and content constraint conditions corresponding to the preset parameter identifiers; respectively matching each parameter identifier with each preset parameter identifier to obtain a first verification sub-result; matching the parameter content with a content constraint condition to obtain a second syndrome result; and generating a target verification result. According to the embodiment of the invention, the validity and practicability of parameter verification can be enhanced, and the logic rationality and compatibility of parameter verification can be guaranteed.

Description

Technical Field

[0001] The present application belongs to the field of big data technology, and in particular relates to a parameter verification method, device, equipment, medium and program product. Background Art

[0002] During software development and operation and maintenance, parameter verification is a key link in ensuring system stability and security.

[0003] When verifying system parameters, the existing technology often simply verifies the format correctness and content accuracy of the parameters. The verification logic is single, ignoring the complex verification requirements of parameter configuration items in multiple scenarios, and cannot flexibly handle the changes and mutual influence of parameter configurations in multiple scenarios, thereby limiting the effectiveness and practicality of the verification, and cannot fully guarantee the logical rationality and compatibility of parameter verification.

[0004] Therefore, the existing parameter verification methods have poor effectiveness and practicality, and cannot fully guarantee the logical rationality and compatibility of parameter verification. Summary of the invention

[0005] The embodiments of the present application provide a parameter verification method, apparatus, device, medium and program product, which can enhance the effectiveness and practicality of parameter verification and ensure the logical rationality and compatibility of parameter verification.

[0006] In a first aspect, an embodiment of the present application provides a parameter verification method, including:

[0007] In response to the parameter verification request, obtaining configuration information, target version information, and target application environment information of the parameter item in the parameter verification request, wherein the configuration information includes a parameter identifier and parameter content;

[0008] In the correspondence between the preset version information, the application environment information and the verification rule information, first target verification rule information corresponding to the target version information and the target application environment information is obtained, wherein the first target verification rule information includes preset parameter identifiers of each preset parameter item and content constraints corresponding to each preset parameter identifier;

[0009] Match each parameter identifier with each preset parameter identifier to obtain a first syndrome result; match the parameter content with the content constraint condition to obtain a second syndrome result;

[0010] A target check result is generated based on the first syndrome result and the second syndrome result.

[0011] In a possible embodiment of the first aspect, the parameter identifier includes a system layer parameter identifier, a software layer parameter identifier, and an application layer parameter identifier; each parameter identifier is matched with each preset parameter identifier to obtain a first syndrome result, including:

[0012] The system layer parameter identifier, the software layer parameter identifier and the application layer parameter identifier are matched with each preset parameter identifier respectively to obtain a first syndrome result.

[0013] In a possible embodiment of the first aspect, the content constraint condition includes at least one of a data type, a data format, and a value range; matching the parameter content with the content constraint condition to obtain a second syndrome result includes:

[0014] The parameter content is matched with at least one of a data type, a data format, and a value range to obtain a second syndrome result.

[0015] In a possible embodiment of the first aspect, the parameter identifier includes a first-category parameter identifier and a second-category parameter identifier; the first target verification rule information also includes a dependency verification rule and a fault occurrence condition; before generating a target verification result based on the first syndrome result and the second syndrome result, the method further includes:

[0016] According to the dependency verification rule, the parameter content corresponding to the first type of parameter identifier is verified to obtain a third verification sub-result;

[0017] Matching the second type parameter identifier and its corresponding parameter content with the fault occurrence condition to obtain a fourth syndrome result;

[0018] Generating a target verification result based on the first syndrome result and the second syndrome result includes:

[0019] A target check result is generated based on the first syndrome result, the second syndrome result, the third syndrome result, and the fourth syndrome result.

[0020] In a possible embodiment of the first aspect, the dependency verification rule includes a mutually exclusive verification rule and a collaborative verification rule; the first type of parameter identifier includes a first sub-parameter identifier and a second sub-parameter identifier; according to the dependency verification rule, the parameter content corresponding to the first type of parameter identifier is verified to obtain a third verification sub-result, including:

[0021] According to the mutually exclusive verification rule, the parameter content corresponding to the first sub-parameter identifier is verified, and according to the collaborative verification rule, the parameter content corresponding to the second sub-parameter identifier is verified to obtain a third verification sub-result.

[0022] In a possible embodiment of the first aspect, the fault occurrence condition includes at least one of the lack of a first key parameter identifier, the presence of a second key parameter identifier, and the configuration content being a preset content; matching the second type parameter identifier and its corresponding parameter content with the fault occurrence condition to obtain a fourth syndrome result, including:

[0023] The second type parameter identifier and its corresponding parameter content are matched with at least one of the absence of the first key parameter identifier, the presence of the second key parameter identifier, and the configuration content being the preset content to obtain a fourth syndrome result.

[0024] In a possible embodiment of the first aspect, the second type parameter identifier and the corresponding parameter content are respectively matched with at least one of the absence of the first key parameter identifier, the presence of the second key parameter identifier, and the configuration content being the preset content to obtain a fourth syndrome result, including:

[0025] In the case where the first key parameter identifier is missing in the second type parameter identifier, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated; and / or

[0026] When the second key parameter identifier exists in the second type parameter identifier, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated; and / or

[0027] When the parameter content corresponding to the second-category parameter identifier is the preset content, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated.

[0028] In a possible embodiment of the first aspect, the method further includes:

[0029] Generate report information based on the first syndrome result, the second syndrome result, the third syndrome result, the fourth syndrome result and the target verification result;

[0030] Displays report information on the first page.

[0031] In a possible implementation of the first aspect, multiple application environments share a first page, and the multiple application environments are isolated from each other.

[0032] In a possible embodiment of the first aspect, before obtaining configuration information, target version information, and target application environment information of parameter items in the parameter verification request in response to the parameter verification request, the method further includes:

[0033] In response to the Nth update detection request of the verification rule sent by the client, obtaining the target version information and the target application environment information in the Nth update detection request, where N is a positive integer greater than 0;

[0034] In the preset correspondence between version information, application environment information and update identification information, obtaining target update identification information corresponding to the target version information and the target application environment information;

[0035] When the target update identification information is the first preset update identification information, obtaining the updated verification rule information in the database, and sending the first preset update identification information and the updated verification rule information to the client at a preset time, wherein the first preset update identification information indicates that there is a verification rule update; or

[0036] When the target update identification information is the second preset update identification information, sending the second preset update identification information to the client at a preset time, wherein the second preset update identification information indicates that there is no verification rule update;

[0037] An N+1th update detection request for the verification rule sent by the client is received, wherein the N+1th update detection request is generated by the client after receiving the first preset update identification information or the second preset update identification information.

[0038] In a possible embodiment of the first aspect, the present invention further includes:

[0039] In response to a verification rule acquisition request sent by the client, obtaining target version information and target application environment information in the verification rule acquisition request, wherein the verification rule acquisition request is sent by the client according to a preset period;

[0040] In the preset correspondence between version information, application environment information and verification rule information, obtaining second target verification rule information corresponding to the target version information and the target application environment information;

[0041] Send the second target verification rule information to the client.

[0042] In a possible embodiment of the first aspect, before obtaining, in response to the parameter verification request, configuration information, target version information, and target application environment information of the parameter item in the parameter verification request, the method further includes:

[0043] In response to a first input on the first page, obtaining custom configuration information of a parameter item in the first input;

[0044] Sending the custom configuration information to the first client and obtaining information about the running result, wherein the information about the running result is obtained after the first client performs configuration based on the custom configuration information;

[0045] When the running result reaches the preset running result, the custom configuration information is sent to the second client.

[0046] Based on the same inventive concept, in a second aspect, an embodiment of the present application further provides a parameter verification device, including:

[0047] An acquisition module, used to respond to the parameter verification request and acquire configuration information, target version information and target application environment information of the parameter item in the parameter verification request, wherein the configuration information includes a parameter identifier and parameter content;

[0048] The acquisition module is further used to acquire first target verification rule information corresponding to the target version information and the target application environment information in the correspondence relationship between the preset version information, the application environment information and the verification rule information, wherein the first target verification rule information includes the preset parameter identifier of each preset parameter item and the content constraint condition corresponding to each preset parameter identifier;

[0049] A verification module, used to match each parameter identifier with each preset parameter identifier to obtain a first syndrome result; and match the parameter content with the content constraint condition to obtain a second syndrome result;

[0050] A generating module is used to generate a target verification result based on the first syndrome result and the second syndrome result.

[0051] Based on the same inventive concept, in the third aspect, an embodiment of the present application also provides a parameter verification device, which includes a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, it implements the first aspect, or the parameter verification method in any embodiment of the first aspect.

[0052] Based on the same inventive concept, in the fourth aspect, an embodiment of the present application further provides a computer storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the first aspect or the parameter verification method in any embodiment of the first aspect is implemented.

[0053] Based on the same inventive concept, in the fifth aspect, an embodiment of the present application also provides a computer program product. When the instructions in the computer program product are executed by the processor of the device, the device can execute the parameter verification method in the first aspect or any embodiment of the first aspect.

[0054] The parameter verification method, device, equipment, medium and program product of the embodiment of the present application, by responding to the parameter verification request, not only obtains the configuration information, target version information and target application environment information of the parameter item, but also utilizes the correspondence between the preset version information, application environment information and verification rule information, accurately locates the first target verification rule information that matches the target version and target application environment, and ensures that the verification rule is closely matched with the current application environment and system version of the client. In the subsequent verification process, basic parameter identification and parameter content matching verification are also performed respectively. By verifying whether each parameter identification is correct and whether the parameter content matches the content constraint conditions, it is possible to comprehensively capture potential problems in the configuration information of the parameter item, such as incorrect parameter items (incorrect parameter identification), parameter content not meeting the requirements, etc., and the accuracy and compliance verification of the parameter configuration can be achieved. Finally, based on the verification sub-results of multiple dimensions (first verification sub-result, second verification sub-result), a comprehensive target verification result is generated. Therefore, the embodiment of the present application effectively improves the effectiveness and practicality of parameter verification through its comprehensive and detailed verification process, can ensure the logical rationality and compatibility of parameter verification, and provides a solid guarantee for the stable operation and performance optimization of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Other features, objects and advantages of the present application will become more apparent by reading the following detailed description of non-limiting embodiments with reference to the accompanying drawings, in which the same or similar reference numerals represent the same or similar features and the accompanying drawings are not drawn to scale.

[0056] Figure 1 It is a flow chart of a parameter verification method provided in an embodiment of the present application;

[0057] Figure 2 This is another flow chart of the parameter verification method provided in the embodiment of the present application;

[0058] Figure 3 This is another flow chart of the parameter verification method provided in the embodiment of the present application;

[0059] Figure 4 It is another flow chart of the parameter verification method provided in the embodiment of the present application;

[0060] Figure 5 This is another flow chart of the parameter verification method provided in the embodiment of the present application;

[0061] Figure 6 This is another flow chart of the parameter verification method provided in the embodiment of the present application;

[0062] Figure 7It is another flow chart of the parameter verification method provided in the embodiment of the present application;

[0063] Figure 8 This is another flow chart of the parameter verification method provided in the embodiment of the present application;

[0064] Fig. 9 It is a structural schematic diagram of a parameter verification device provided in an embodiment of the present application;

[0065] Fig.10 It is a structural schematic diagram of a parameter verification device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only configured to explain the present application and are not configured to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0067] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0068] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0069] It is obvious to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit or scope of the present application. Therefore, the present application is intended to cover modifications and changes of the present application that fall within the scope of the corresponding claims (technical solutions for protection) and their equivalents. It should be noted that the implementation methods provided in the embodiments of the present application can be combined with each other without contradiction.

[0070] It should be noted that the acquisition, storage, use and processing of data in the embodiments of the present application are in compliance with the relevant provisions of national laws and regulations.

[0071] It should also be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0072] Before describing the technical solutions provided by the embodiments of the present application, in order to facilitate the understanding of the embodiments of the present application, the present application first specifically describes the problems existing in the related art:

[0073] During software development and operation and maintenance, parameter verification is a key link in ensuring system stability and security.

[0074] With the increasing complexity of software systems and the acceleration of version iterations, the differences in parameters between different versions and the specific requirements of parameters in different application environments make it difficult for traditional single, static parameter verification methods to meet actual needs. Traditional verification methods often only focus on the format correctness and content accuracy of parameters, ignoring the dependencies between parameters, environmental adaptability, and potential failure risks, which may lead to problems such as parameter configuration errors, system performance degradation, and even service interruptions in actual applications. Specifically:

[0075] Inadequate handling of version differences. Different versions of software systems often have different requirements for parameters, including parameter additions and subtractions, type changes, value range adjustments, etc. Traditional verification methods often cannot automatically identify version differences, resulting in a mismatch between the verification rules and the current version.

[0076] Poor adaptability to application environments. The parameter configuration requirements of the same software in different application environments (such as development environment, test environment, and production environment) may be completely different. Traditional verification methods lack consideration of environmental information and cannot provide customized verification rules for different environments.

[0077] Parameter dependency verification is missing. There are complex dependencies between many system parameters. A change in one parameter may require corresponding adjustments to other parameters. Traditional verification methods often only focus on the verification of a single parameter, ignoring the dependencies between parameters, which can easily lead to configuration errors.

[0078] Insufficient early warning of failure risks. Specific configurations of certain parameters may cause system failures or performance issues. Traditional verification methods lack the ability to identify and warn of these potential risks, and cannot avoid risks in advance.

[0079] Therefore, the existing parameter verification method has a single verification logic and ignores the complex verification requirements of parameter configuration items in multiple scenarios. As a result, it cannot flexibly handle the changes and mutual influence of parameter configurations in multiple scenarios, which limits the effectiveness and practicality of the verification and cannot fully guarantee the logical rationality and compatibility of parameter verification.

[0080] Based on this, the embodiments of the present application provide a parameter verification method, device, equipment, medium and program product, which can automatically identify and adapt to the verification logic of different versions and different application environments, and by verifying the correctness of parameter identification and parameter content, verifying the dependencies between parameters, identifying and warning of potential failure risks, it can enhance the effectiveness and practicality of parameter verification, and can comprehensively ensure the logical rationality and compatibility of parameter verification.

[0081] The parameter verification method provided in the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0082] Figure 1 is a flow chart of a parameter verification method provided in an embodiment of the present application, such as Figure 1 As shown, the method may include steps S110 to S140.

[0083] S110, in response to the parameter verification request, obtaining configuration information, target version information, and target application environment information of the parameter item in the parameter verification request, wherein the configuration information includes a parameter identifier and parameter content.

[0084] The parameter verification request is a request sent by the client to the server to request the server to verify the client's system parameters. The parameter verification request may include configuration information of parameter items, target version information, and target application environment information.

[0085] The configuration information of a parameter item may include a parameter identifier and parameter content of the parameter item.

[0086] The parameter ID is used to uniquely identify a parameter item.

[0087] The parameter content is the specific configuration data of the parameter item.

[0088] The target version information is the client's system version information.

[0089] The target application environment information is information about the application environment where the client is located, such as the development environment, test environment, production environment, etc.

[0090] Specifically, when the server receives a parameter verification request sent by the client, the server will parse the parameter verification request to obtain the configuration details of the parameter items that need to be verified, including the parameter identifier and parameter content of each parameter item, as well as the target version of the client system and the target application environment information of the client.

[0091] S120, in the correspondence between the preset version information, application environment information and verification rule information, obtain the first target verification rule information corresponding to the target version information and the target application environment information, wherein the first target verification rule information includes the preset parameter identifier of each preset parameter item and the content constraint condition corresponding to each preset parameter identifier.

[0092] The first target verification rule information is a verification rule set associated with the target version information and target application environment information of the client, which is specially customized for the current environment and version of the client and is used to verify whether the parameter item meets these specific conditions.

[0093] The first target verification rule information may include preset parameter identifiers of various preset parameter items and content constraint conditions corresponding to various preset parameter identifiers.

[0094] Specifically, in the correspondence between the preset version information, application environment information and verification rule information, the server can retrieve the matching first target verification rule information for specific target version information and target application environment information. The first target verification rule information defines in detail the preset parameter identifiers of each preset parameter item and the content constraints that each parameter item should meet.

[0095] S130, matching each parameter identifier with each preset parameter identifier to obtain a first syndrome result; matching the parameter content with the content constraint condition to obtain a second syndrome result.

[0096] The first check sub-result is a check result obtained by comparing the client's parameter identifier with the preset parameter identifier. If all of them match successfully, it means that the client's parameter identifier is correct, and the check passes; if there is a mismatch, the check fails.

[0097] The second verification sub-result is a verification result obtained by matching the parameter content of each parameter item of the client with the content constraint condition. If the parameter content meets the corresponding content constraint condition, the verification passes; otherwise, the verification fails.

[0098] Specifically, during the parameter verification process, the parameter identifiers of each parameter item of the client are first matched with the preset parameter identifiers one by one to determine the validity of the parameter item and obtain the first verification sub-result. Then, the actual content of each parameter item is compared with the preset content constraint conditions to verify whether it meets the specified format, range and other requirements, and obtain the second verification sub-result.

[0099] S140: Generate a target verification result based on the first syndrome result and the second syndrome result.

[0100] Specifically, the server will generate a comprehensive target verification result based on the first check sub-result (parameter identifier matching status) and the second check sub-result (whether the parameter content meets the content constraint condition).

[0101] The parameter verification method provided in the embodiment of the present application, by responding to the parameter verification request, not only obtains the configuration information, target version information and target application environment information of the parameter item, but also utilizes the correspondence between the preset version information, application environment information and verification rule information, accurately locates the first target verification rule information that matches the target version and target application environment, and ensures that the verification rule is closely matched with the current application environment and system version of the client. In the subsequent verification process, basic parameter identification and parameter content matching verification are also performed respectively. By verifying whether each parameter identification is correct and whether the parameter content matches the content constraint conditions, the potential problems in the configuration information of the parameter item can be fully captured, such as incorrect parameter items (incorrect parameter identification), parameter content not meeting the requirements, etc., and the accuracy and compliance verification of parameter configuration can be achieved. Finally, based on the check sub-results of multiple dimensions (first check sub-result, second check sub-result), a comprehensive target verification result is generated. Therefore, the embodiment of the present application effectively improves the effectiveness and practicality of parameter verification through its comprehensive and detailed verification process, can ensure the logical rationality and compatibility of parameter verification, and provides a solid guarantee for the stable operation and performance optimization of the system.

[0102] Figure 2 This is another flow chart of the parameter verification method provided in the embodiment of the present application.

[0103] In some embodiments, Figure 2 As shown, the parameter identifier includes a system layer parameter identifier, a software layer parameter identifier and an application layer parameter identifier; in step S130, each parameter identifier is matched with each preset parameter identifier respectively to obtain a first syndrome result, which may include step S131.

[0104] S131, matching the system layer parameter identifier, the software layer parameter identifier and the application layer parameter identifier with each preset parameter identifier respectively to obtain a first syndrome result.

[0105] Specifically, the parameter identifier may include three levels: system layer parameter identifier, software layer parameter identifier, and application layer parameter identifier. The parameters at each level have their specific uses and importance. The parameter identifiers at these three levels are matched with the preset parameter identifiers respectively to obtain the first verification sub-result. The embodiment of the present application can formulate corresponding verification rules according to the characteristics of different levels, and can more accurately identify whether the parameters at different levels meet the requirements, thereby improving the pertinence and accuracy of the verification.

[0106] In one example, the parameter verification request includes data on system layer parameter items (operating system version, kernel version, number of CPU cores, memory size, disk type and size, etc.), software layer parameter items (software information such as nginx version and tomcat version), and application layer parameter items (app version information). The embodiment of the present application can accurately identify whether the parameter items of the system layer, software layer, and application layer meet the requirements, and can improve the pertinence and accuracy of the verification.

[0107] In some embodiments, you can continue to see Figure 2 , the content constraint condition includes at least one of a data type, a data format and a value range; in step S130, matching the parameter content with the content constraint condition to obtain a second syndrome result may include step S132.

[0108] S132, matching the parameter content with at least one of a data type, a data format, and a value range to obtain a second syndrome result.

[0109] The content constraints refer to a series of rules or restrictions set on the parameter content to ensure the validity, accuracy and security of the parameters. These conditions may include but are not limited to data type, data format and value range.

[0110] Specifically, it is determined whether the parameter content satisfies content constraints such as data type, data format, and value range to ensure the validity of the parameter content, and the second syndrome result is obtained accordingly. The embodiment of the present application ensures the validity and accuracy of the parameter content by refining the content constraints (including data type, data format, and value range, etc.) and performing strict matching verification on the parameter content.

[0111] Figure 3 This is another flow chart of the parameter verification method provided in the embodiment of the present application.

[0112] In some embodiments, Figure 3As shown, the parameter identifier includes a first type parameter identifier and a second type parameter identifier; the first target verification rule information also includes dependency verification rules and fault occurrence conditions; before generating the target verification result based on the first verification sub-result and the second verification sub-result in step S140, the method also includes steps S150 and S160.

[0113] S150, verify the parameter content corresponding to the first type of parameter identifier according to the dependency verification rule to obtain a third verification sub-result.

[0114] Among them, parameter identifiers with a certain dependency relationship can be called first-category parameter identifiers, and parameter identifiers that may cause failures can be called second-category parameter identifiers.

[0115] The third check sub-result is the result obtained by checking the parameter content corresponding to the first-category parameter identifier according to the dependency check rule. It reflects whether the key first-category parameter item meets the dependency requirements.

[0116] Specifically, the key parameter items of the first category may be content-checked according to the dependency check rule to ensure that the logical relationship between them is correct, thereby obtaining the third check sub-result.

[0117] S160: Match the second type parameter identifier and its corresponding parameter content with the fault occurrence condition to obtain a fourth syndrome result.

[0118] The fourth syndrome result is a verification result obtained by matching the second type parameter identifier and its corresponding parameter content with the fault occurrence condition, and indicates whether the second type parameter item may cause a system fault or an abnormal situation.

[0119] Specifically, for the second type of parameter identifiers and their contents, they are checked to see whether they meet specific fault occurrence conditions to prevent potential system problems and obtain a fourth syndrome result.

[0120] Step S140 generates a target verification result based on the first syndrome result and the second syndrome result, and may include step S141.

[0121] S141, generating a target verification result based on the first syndrome result, the second syndrome result, the third syndrome result and the fourth syndrome result.

[0122] Specifically, based on the first syndrome result, the second syndrome result, the third syndrome result, and the fourth syndrome result, a target verification result may be generated. For example, when the first syndrome result, the second syndrome result, the third syndrome result, and the fourth syndrome result are all verified to pass, the generated target verification result is verified to pass.

[0123] The parameter verification method provided in the embodiment of the present application, by responding to the parameter verification request, not only obtains the configuration information, target version information and target application environment information of the parameter item, but also utilizes the correspondence between the preset version information, application environment information and verification rule information, accurately locates the first target verification rule information that matches the target version and target application environment, and ensures that the verification rule is closely matched with the current application environment and system version of the client. In the subsequent verification process, basic parameter identification and parameter content matching verification are also performed respectively, and the level of dependency verification and fault risk warning is also deepened. By respectively verifying whether each parameter identification is correct, whether the parameter content matches the content constraint conditions, the dependency relationship of the first type of parameter identification corresponding to the content, and the matching of the second type of parameter identification and its content with the fault occurrence conditions, it is possible to comprehensively capture the potential problems in the configuration information of the parameter item, such as incorrect parameter item (incorrect parameter identification), parameter content not meeting the requirements, dependency conflicts and possible faults, etc., which can not only realize the accuracy and compliance verification of parameter configuration, but also realize logical irrationality and compatibility verification. Finally, based on the syndrome results of multiple dimensions (the first syndrome result, the second syndrome result, the third syndrome result and the fourth syndrome result), a comprehensive target verification result is generated. Therefore, the embodiment of the present application effectively improves the effectiveness and practicality of parameter verification through its comprehensive and detailed verification process, and can fully guarantee the logical rationality and compatibility of parameter verification, providing a solid guarantee for the stable operation and performance optimization of the system.

[0124] Figure 4 This is another flow chart of the parameter verification method provided in the embodiment of the present application.

[0125] In some embodiments, Figure 4 As shown, the dependency verification rules include mutually exclusive verification rules and / or collaborative verification rules; the first type of parameter identifier includes a first sub-parameter identifier and a second sub-parameter identifier; in step S150, the parameter content corresponding to the first type of parameter identifier is verified according to the dependency verification rules to obtain a third verification sub-result, which may include step S151.

[0126] S151, verify the parameter content corresponding to the first sub-parameter identifier according to the mutually exclusive verification rule, and verify the parameter content corresponding to the second sub-parameter identifier according to the collaborative verification rule to obtain a third verification sub-result.

[0127] Among them, dependency verification rules are rules used to ensure the correctness of the association relationship between parameter items. In a complex system, there may be interdependent relationships between parameters, and dependency verification rules can help verify whether these dependencies are correct.

[0128] Mutually exclusive check rules are used to ensure that multiple parameter items do not meet certain mutually exclusive conditions at the same time, thereby avoiding conflicts or errors. For example, if the load balancing algorithm in Nginx is ip hash, polling cannot be selected, that is, two algorithms cannot be selected at the same time.

[0129] The coordination verification rule can be simply understood as the main switch must be turned on for the light switch operation to make sense. For example, in the configuration coordination scenario: the Linux operating system kernel is configured to disable the IPv6 module, but the network card configuration file is configured to enable the IPv6 configuration, so the network card configuration is equivalent to an invalid configuration.

[0130] Specifically, the server verifies the parameter content corresponding to the first sub-parameter identifier according to the mutually exclusive verification rule to ensure that there is no mutually exclusive conflict; at the same time, the server verifies the parameter content corresponding to the second sub-parameter identifier according to the collaborative verification rule to ensure that they can be coordinated and consistent to avoid invalid configuration. The two verification processes of the mutually exclusive verification rule and the collaborative verification rule together constitute the dependency verification of the parameter content under the first type of parameter identifier, and derive the third verification sub-result based on this. By implementing the mutually exclusive verification rule and the collaborative verification rule, the embodiment of the present application can ensure that the dependency relationship between parameter items in complex configurations is correct, avoid mutual exclusion conflicts and invalid configurations, and thus improve the accuracy and stability of the system configuration.

[0131] In some embodiments, you can continue to see Figure 4 The fault occurrence conditions include the absence of a first key parameter identifier, the presence of a second key parameter identifier, and the configuration content being at least one of the preset contents; step S160 matches the second type parameter identifier and its corresponding parameter content with the fault occurrence conditions to obtain a fourth check sub-result, which may include step S161.

[0132] S161, matching the second type parameter identifier and its corresponding parameter content with at least one of the absence of the first key parameter identifier, the presence of the second key parameter identifier, and the configuration content being the preset content, to obtain a fourth syndrome result.

[0133] Among them, the fault occurrence condition defines a specific situation in the system configuration parameters that may cause a fault or error. For example, the fault occurrence condition is at least one of the lack of a first key parameter identifier, the presence of a second key parameter identifier, and the configuration content being a preset content. The fault occurrence condition is used to identify configuration problems that may cause system instability, functional failure, or erroneous behavior.

[0134] Specifically, the second type of parameter identifier and its corresponding parameter content are compared with a series of preset fault conditions, such as the lack of a first key parameter identifier, the presence of a second key parameter identifier, and the configuration content is compared with the preset content. By checking whether the fault conditions are met one by one, it is possible to determine whether there is a parameter configuration that matches the fault conditions, and generate a fourth check sub-result accordingly. The embodiment of the present application can accurately identify any configuration errors that may cause system instability or malfunction by exhaustively comparing the second type of parameter identifier and its corresponding parameter content with a series of preset fault conditions (including checking whether key parameters are missing, whether there are parameters that should not appear, and whether the parameter content matches the preset value). This comparison process ensures the accuracy and compliance of the configuration, and provides a solid guarantee for the stable operation of the system by verifying and generating the fourth check sub-result one by one.

[0135] In some embodiments, step S161 matches the second type parameter identifier and its corresponding parameter content with at least one of the absence of the first key parameter identifier, the existence of the second key parameter identifier, and the configuration content being the preset content to obtain a fourth check sub-result, which may include steps S1611 to S1613.

[0136] S1611, when the first key parameter identifier is missing in the second type parameter identifier, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated.

[0137] Specifically, when the set of the second type of parameter identifiers does not contain the first key parameter identifier, this means that a parameter that is critical to normal operation is missing in the system configuration. In this case, the missing parameter constitutes a fault condition. Therefore, the verification process will output a clear fourth check result, i.e., "verification failed", and generate an alarm prompt message, which is intended to promptly notify the system administrator or relevant maintenance personnel to pay attention to this configuration missing problem so that appropriate remedial measures can be taken to ensure that the system can restore integrity and stability.

[0138] S1612, and / or, when the second key parameter identifier exists in the second type parameter identifier, the fourth syndrome result is obtained as verification failure and an alarm prompt information is generated.

[0139] Specifically, when the set of the second type of parameter identifiers includes the second key parameter identifier, this usually indicates that there is an unexpected or disallowed parameter in the system configuration, which may interfere with the normal operation of the system. Therefore, if the second key parameter identifier is found, the verification process will output a clear fourth check sub-result, i.e., "verification failed", and generate an alarm prompt message to remind the system administrator or relevant maintenance personnel to pay attention to this configuration problem so that they can take appropriate measures to remove or modify the parameter, thereby ensuring the stability and security of the system.

[0140] S1613, and / or, when the parameter content corresponding to the second type parameter identifier is the preset content, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated.

[0141] Specifically, if the parameter content corresponding to the second type of parameter identifier happens to match the preset content, it indicates that there is an unexpected or potential risk item in the configuration. When the parameter content matches these preset contents, the system verification process will output a clear fourth verification sub-result, that is, "verification failed", and generate an alarm prompt message to notify the system administrator or maintenance personnel that there may be problems with the parameter content and further inspection or adjustment is required to ensure the normal operation and security of the system.

[0142] The embodiment of the present application can identify various configuration problems that may exist in the second type of parameter identification and its parameter content, including the absence of key parameters, the presence of unexpected parameters, and the matching of parameter content with preset values. This detailed verification mechanism not only improves the accuracy and compliance of system configuration, but also ensures that system administrators or maintenance personnel can respond quickly and take corresponding remedial measures by generating alarm prompt information in a timely manner, thereby effectively maintaining the stability, security and integrity of the system.

[0143] Figure 5 This is another flow chart of the parameter verification method provided in the embodiment of the present application.

[0144] In some embodiments, Figure 5 As shown, the method may further include steps S171 and S172.

[0145] S171, generating report information based on the first syndrome result, the second syndrome result, the third syndrome result, the fourth syndrome result and the target verification result.

[0146] Specifically, a detailed report can be generated by combining multiple check sub-results (including the first, second, third and fourth check sub-results) and the final target check result. This report information fully reflects all aspects of the configuration check, including which check items have passed the verification, which check items have failed and triggered alarms or error prompts. Through this report, system administrators or maintenance personnel can clearly understand the overall status of the configuration, quickly locate the problem, and formulate corresponding repair or optimization strategies accordingly.

[0147] S172, displaying report information on the first page.

[0148] Specifically, the generated report information can be directly displayed on the first page for users to view. Users can immediately view an overview and detailed analysis of the verification results without additional navigation or search, thereby improving the user experience.

[0149] The embodiment of the present application provides detailed report information including multiple verification sub-results and target verification results, and displays them directly on the first page, so that system administrators or maintenance personnel can quickly obtain comprehensive feedback on configuration verification. This instant and intuitive report display method not only improves the efficiency of problem diagnosis, but also simplifies the operation process and improves the user experience.

[0150] In some embodiments, multiple application environments share a first page, and the multiple application environments are isolated from each other.

[0151] Specifically, multiple application environments are isolated from each other. In other words, each application environment has its own independent database to store its unique verification rule information. This design allows the server to process parameter verification requests from different clients in parallel without interfering with each other. This parallel processing and isolation mechanism not only improves the verification speed of parameter verification, but also ensures the security and accuracy of data, allowing the system to serve diverse application needs more efficiently.

[0152] The embodiment of the present application designs multiple application environments to share a first page but each has an independent database to store verification rules, thereby achieving effective isolation and parallel processing capabilities between application environments, improving the speed and efficiency of parameter verification, and ensuring the security and accuracy of data, providing more stable and reliable service support for diverse application needs.

[0153] Figure 6 This is another flow chart of the parameter verification method provided in the embodiment of the present application.

[0154] In some embodiments, Figure 6As shown, before responding to the parameter verification request in step S110 and obtaining the configuration information, target version information and target application environment information of the parameter items in the parameter verification request, the method further includes steps S181 to S185.

[0155] S181, in response to the Nth update detection request of the verification rule sent by the client, obtaining the target version information and the target application environment information in the Nth update detection request, where N is a positive integer greater than 0.

[0156] Wherein, N represents a serial number of an update detection request, which is used to distinguish different update detection requests.

[0157] Specifically, when the client initiates an update detection request for the verification rule, the system obtains the target version information and the target application environment information of the client in the update detection request.

[0158] S182, obtaining target update identification information corresponding to the target version information and the target application environment information in the preset correspondence relationship between the version information, the application environment information and the update identification information.

[0159] Specifically, the target update identification information matching the target version information and the target application environment information may be searched in the correspondence relationship among the preset version information, the application environment information and the update identification information to obtain the target update identification information.

[0160] S183, when the target update identification information is the first preset update identification information, obtain the updated verification rule information in the database, and send the first preset update identification information and the updated verification rule information to the client at a preset time, wherein the first preset update identification information indicates that there is a verification rule update.

[0161] Specifically, when it is detected that the target update identification information is the first preset update identification information, it means that the verification rules for the target version and the target application environment have been updated. At this time, the server will automatically retrieve and obtain the updated verification rule information in the local database. Then, at the preset time, the server will send the first preset update identification information and the updated verification rule information to the client, so as to promptly notify the client that an update to the verification rule is available and provide it with the latest verification rule information to ensure the real-time update parameter configuration of the client system parameters.

[0162] S184, or, in the case where the target update identification information is the second preset update identification information, sending the second preset update identification information to the client at a preset time, wherein the second preset update identification information indicates that there is no verification rule update.

[0163] Specifically, when the target update identification information detected by the server is the second preset update identification information, it indicates that there is no available update for the verification rule for the target version and the target application environment. In this case, the server will send the second preset update identification information to the client at a preset time.

[0164] S185, receiving the N+1th update detection request for the verification rule sent by the client, wherein the N+1th update detection request is generated by the client after receiving the first preset update identification information or the second preset update identification information.

[0165] Specifically, after the server sends the first preset update identification information (indicating the existence of an update) or the second preset update identification information (indicating the absence of an update) of the verification rule update to the client, the client will again initiate a new update detection request, i.e., the N+1th update detection request.

[0166] The embodiment of the present application detects and notifies the client of the update status of the verification rules (the existence of an update or the absence of an update) through a long connection, and automatically triggers a new round of update detection requests after the client receives the first preset update identification information or the second preset update identification information, thereby effectively improving the updating efficiency and real-time performance of the verification rules, ensuring that the client always uses the latest verification rules, and enhancing the accuracy of the system parameter configuration.

[0167] In one example, after receiving the http request for pulling configuration sent by the client (the Nth update detection request for the verification rules), the server will briefly hold the request for a period of time. If the server has the configuration update data of the client, for example, the target update identification information is the first preset update identification information, the new configuration item (the updated verification rule information) will be returned to the client, and the client configurator will synchronously refresh the parameter configuration to the disk for persistent storage. If the server does not have the data of the client, it will return 304 (the second preset update identification information). Regardless of whether the current request status code of the client is 200 (the first preset update identification information) or 304 (the second preset update identification information), the client has completed the process of accepting the configuration push from the server, and the client will immediately initiate the http request again (the N+1th update detection request) to proceed with the next process of obtaining the new configuration in real time. The embodiment of the present application detects and notifies the client of the update status of the verification rules (the existence of an update or the absence of an update) through a long connection, and automatically triggers a new round of update detection requests after the client receives the first preset update identification information or the second preset update identification information, thereby effectively improving the updating efficiency and real-time performance of the verification rules, ensuring that the client always uses the latest verification rules, and enhancing the accuracy of the system parameter configuration.

[0168] Figure 7This is another flow chart of the parameter verification method provided in the embodiment of the present application.

[0169] In some embodiments, Figure 7 As shown, the method also includes steps S191 to S193.

[0170] S191, in response to a verification rule acquisition request sent by a client, acquiring target version information and target application environment information in the verification rule acquisition request, wherein the verification rule acquisition request is sent by the client according to a preset period.

[0171] Specifically, upon receiving a verification rule acquisition request sent periodically (according to a preset period) by the client, the server will first extract the target version information and target application environment information specified in the verification rule acquisition request, so as to subsequently provide corresponding verification rules based on this information.

[0172] S192, obtaining second target verification rule information corresponding to the target version information and the target application environment information in the preset correspondence relationship between the version information, the application environment information and the verification rule information.

[0173] Specifically, the preset correspondence between version information, application environment information and verification rule information associates different version information, application environment information and corresponding verification rule information, so the server can obtain the latest second target verification rule information.

[0174] S193, sending second target verification rule information to the client.

[0175] In the embodiment of the present application, the server can respond to the verification rule acquisition request sent by the client, obtain the current latest second target verification rule information and send it to the client, ensuring that the update of the verification rules will not be delayed or omitted due to temporary problems on the server, thereby improving the accuracy and reliability of system parameter verification.

[0176] Figure 6 This is another flow chart of the parameter verification method provided in the embodiment of the present application.

[0177] In some embodiments, Figure 6 As shown, before responding to the parameter verification request in step S110 and obtaining configuration information, target version information and target application environment information of the parameter items in the parameter verification request, the method may further include steps S210 to S230.

[0178] S210: In response to a first input on a first page, obtain custom configuration information of a parameter item in the first input.

[0179] Specifically, the server will respond to the first input made by the user on the first page and obtain the custom configuration information set by the user for the parameter items on the page to meet the user's specific needs or preferences.

[0180] S220, sending the custom configuration information to the first client, and obtaining information on the running result, wherein the running result information is obtained by running the first client after performing configuration based on the custom configuration information.

[0181] Specifically, the server sends custom configuration information to some clients, and then collects operation result information generated by the operation of some clients after the clients are configured according to the custom configuration information.

[0182] S230: When the operation result reaches a preset operation result, send the custom configuration information to the second client.

[0183] Specifically, after some clients configure and start running according to the received custom configuration information, if their running results meet the preset expected results, the server will further send the custom configuration information to other clients so that all clients that need custom configuration can make corresponding configuration adjustments.

[0184] The embodiment of the present application tests the actual effect of the custom configuration information on a part of the clients first to ensure that some of the clients can achieve the expected operating results before promoting it to other clients, thereby effectively reducing the risk of configuration errors, improving the stability of the system and user experience, and also speeding up the deployment efficiency of the new configuration.

[0185] In one example, the user presets a custom configuration on the first page, selects some clients to which the configuration needs to be applied, writes the configuration distribution task into the storage module, and sends it to some clients after approval by authorized personnel. These clients synchronize the configuration and run. If some clients that apply the configuration achieve the expected results, you can choose to publish the configuration in full. The embodiment of the present application tests the actual effect of the custom configuration information on some clients first, ensures that some of its clients can achieve the expected operating results, and then promotes it to other clients, which effectively reduces the risk of configuration errors, improves the stability of the system and user experience, and also speeds up the deployment efficiency of new configurations.

[0186] In another example, a parameter verification system includes a client and a server.

[0187] The client includes a parameter configuration agent module, which is mainly responsible for communicating with the server. For example, sending a parameter verification request to the server. For another example, receiving a configuration update instruction issued by the server.

[0188] The server includes registration module, storage module, management module, monitoring module and evaluation module.

[0189] The registration module is used to provide routing services for client service calls.

[0190] The storage module is used to store various types of data, such as preset version information, the correspondence between application environment information and verification rule information, and specific verification rule information.

[0191] The management module includes user management (adding and deleting users), permission management (ordinary users and administrators, configuring permission control for addition, deletion, modification and query, and authorization for users or user groups), configuration reception (receiving parameter verification requests sent by the client), configuration grayscale release (configuration modification objects can be selectively partially distributed and rolled back, for example, the modified configuration is first distributed to some clients, and then fully distributed after the expected effect is met), and configuration real-time release (establishing a long connection, automatically triggering a new round of update detection requests after the client receives the first preset update identification information or the second preset update identification information).

[0192] The monitoring module is mainly responsible for issuing alarm notifications for incorrect or non-compliant configuration items reported by the client, for example, an alarm indication message may be issued.

[0193] The evaluation module is mainly responsible for verifying the client's system parameter configuration and generating verification results and report information.

[0194] Users can manage multiple isolated environments on the same page. For example, the production environment corresponds to one server, and the test environment corresponds to another server. The server corresponding to the production environment includes a first registration module, a first storage module, a first management module, a first monitoring module, and a first evaluation module. The server corresponding to the test environment includes a second registration module, a second storage module, a second management module, a second monitoring module, and a second evaluation module. Among them, the first storage module is used to store the verification rule information corresponding to the production environment, and the second storage module is used to store the verification rule information corresponding to the test environment.

[0195] The parameter verification system of the embodiment of the present application realizes comprehensive management and accurate verification of the client system parameter configuration by integrating the client parameter configuration agent with the registration, storage, management, monitoring and evaluation modules of the server. The system can provide a flexible configuration release (including grayscale release and real-time release) mechanism, and can monitor and warn of non-compliant configurations in real time, thereby ensuring the accuracy, compliance and efficiency of the system parameter configuration. It also supports multi-environment isolation management, realizes effective isolation and parallel processing capabilities between application environments, and improves the overall stability and performance of the system.

[0196] Based on the same inventive concept, the embodiment of the present application also provides a parameter verification device, such as Fig. 9 As shown, the device 900 may include an acquisition module 910 , a matching module 920 , and a generation module 930 .

[0197] The acquisition module 910 is used to obtain configuration information, target version information and target application environment information of the parameter item in the parameter verification request in response to the parameter verification request, wherein the configuration information includes a parameter identifier and a parameter content;

[0198] The acquisition module 910 is further used to acquire first target verification rule information corresponding to the target version information and the target application environment information in the correspondence relationship between the preset version information, the application environment information and the verification rule information, wherein the first target verification rule information includes the preset parameter identifier of each preset parameter item and the content constraint condition corresponding to each preset parameter identifier;

[0199] Verification module 920, used to match each parameter identifier with each preset parameter identifier to obtain a first syndrome result; match the parameter content with the content constraint condition to obtain a second syndrome result;

[0200] The generating module 930 is configured to generate a target verification result based on the first syndrome result and the second syndrome result.

[0201] The parameter verification device provided in the embodiment of the present application, by responding to the parameter verification request, not only obtains the configuration information, target version information and target application environment information of the parameter item, but also utilizes the correspondence between the preset version information, application environment information and verification rule information, accurately locates the first target verification rule information that matches the target version and target application environment, and ensures that the verification rule is closely matched with the current application environment and system version of the client. In the subsequent verification process, basic parameter identification and parameter content matching verification are also performed respectively. By verifying whether each parameter identification is correct and whether the parameter content matches the content constraint conditions, the potential problems in the configuration information of the parameter item can be fully captured, such as incorrect parameter items (incorrect parameter identification) and parameter content not meeting the requirements, and the accuracy and compliance verification of parameter configuration can be achieved. Finally, based on the verification sub-results of multiple dimensions (first verification sub-result, second verification sub-result), a comprehensive target verification result is generated. Therefore, the embodiment of the present application effectively improves the effectiveness and practicality of parameter verification through its comprehensive and detailed verification process, can ensure the logical rationality and compatibility of parameter verification, and provides a solid guarantee for the stable operation and performance optimization of the system.

[0202] In some embodiments, the parameter identifier includes a system layer parameter identifier, a software layer parameter identifier, and an application layer parameter identifier; the verification module is used to match each parameter identifier with each preset parameter identifier to obtain a first syndrome result, which can be specifically used to:

[0203] The system layer parameter identifier, the software layer parameter identifier and the application layer parameter identifier are matched with each preset parameter identifier respectively to obtain a first syndrome result.

[0204] In some embodiments, the content constraint condition includes at least one of a data type, a data format, and a value range; the verification module is used to match the parameter content with the content constraint condition to obtain a second syndrome result, which can be specifically used to:

[0205] The parameter content is matched with at least one of a data type, a data format, and a value range to obtain a second syndrome result.

[0206] In some embodiments, the parameter identifier includes a first type parameter identifier and a second type parameter identifier; the first target verification rule information also includes a dependency verification rule and a fault occurrence condition; before the generation module is used to generate a target verification result based on the first syndrome result and the second syndrome result, the device also includes a matching module:

[0207] The verification module is further used to verify the parameter content corresponding to the first type of parameter identifier according to the dependency verification rule to obtain a third verification sub-result;

[0208] A matching module, used for matching the second type parameter identifier and its corresponding parameter content with the fault occurrence condition to obtain a fourth syndrome result;

[0209] The generation module is used to generate a target verification result based on the first syndrome result and the second syndrome result, and can be specifically used to:

[0210] A target check result is generated based on the first syndrome result, the second syndrome result, the third syndrome result, and the fourth syndrome result.

[0211] In some embodiments, the dependency verification rule includes a mutually exclusive verification rule and a collaborative verification rule; the first type of parameter identifier includes a first sub-parameter identifier and a second sub-parameter identifier; the verification module is used to verify the parameter content corresponding to the first type of parameter identifier according to the dependency verification rule to obtain a third verification sub-result, which can be specifically used for:

[0212] According to the mutually exclusive verification rule, the parameter content corresponding to the first sub-parameter identifier is verified, and according to the collaborative verification rule, the parameter content corresponding to the second sub-parameter identifier is verified to obtain a third verification sub-result.

[0213] In some embodiments, the fault occurrence condition includes at least one of the lack of a first key parameter identifier, the presence of a second key parameter identifier, and the configuration content being a preset content; the verification module is used to match the second type parameter identifier and its corresponding parameter content with the fault occurrence condition to obtain a fourth verification sub-result, which can be specifically used to:

[0214] The second type parameter identifier and its corresponding parameter content are matched with at least one of the absence of the first key parameter identifier, the presence of the second key parameter identifier, and the configuration content being the preset content to obtain a fourth syndrome result.

[0215] In some embodiments, the verification module is used to match the second type parameter identifier and its corresponding parameter content with at least one of the absence of the first key parameter identifier, the presence of the second key parameter identifier, and the configuration content being the preset content, to obtain a fourth verification sub-result, which can be specifically used to:

[0216] In the case where the first key parameter identifier is missing in the second type parameter identifier, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated; and / or

[0217] When the second key parameter identifier exists in the second type parameter identifier, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated; and / or

[0218] When the parameter content corresponding to the second-category parameter identifier is the preset content, the fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated.

[0219] In some embodiments, the apparatus further comprises:

[0220] Generate report information based on the first syndrome result, the second syndrome result, the third syndrome result, the fourth syndrome result and the target verification result;

[0221] Displays report information on the first page.

[0222] In some embodiments, multiple application environments share a first page, and the multiple application environments are isolated from each other.

[0223] In some embodiments, before the acquisition module is used to respond to the parameter verification request and obtain the configuration information, target version information and target application environment information of the parameter item in the parameter verification request, the device further includes a sending module and a receiving module:

[0224] The acquisition module is further used to respond to the Nth update detection request of the verification rule sent by the client, and obtain the target version information and the target application environment information in the Nth update detection request, wherein N is a positive integer greater than 0;

[0225] The acquisition module is further used to acquire target update identification information corresponding to the target version information and the target application environment information in the correspondence relationship between the preset version information, the application environment information and the update identification information;

[0226] a sending module, configured to obtain updated verification rule information from a database when the target update identification information is the first preset update identification information, and send the first preset update identification information and the updated verification rule information to the client at a preset time, wherein the first preset update identification information indicates that there is a verification rule update; or

[0227] The sending module is further used to send the second preset update identification information to the client at a preset time when the target update identification information is the second preset update identification information, wherein the second preset update identification information indicates that there is no verification rule update;

[0228] The receiving module is used to receive the N+1th update detection request of the verification rule sent by the client, wherein the N+1th update detection request is generated by the client after receiving the first preset update identification information or the second preset update identification information.

[0229] In some embodiments, it also includes:

[0230] The acquisition module is further used to respond to the verification rule acquisition request sent by the client, and acquire the target version information and the target application environment information in the verification rule acquisition request, wherein the verification rule acquisition request is sent by the client according to a preset period;

[0231] The acquisition module is further used to acquire second target verification rule information corresponding to the target version information and the target application environment information in the correspondence relationship between the preset version information, the application environment information and the verification rule information;

[0232] The sending module is also used to send the second target verification rule information to the client.

[0233] In some embodiments, before obtaining configuration information, target version information, and target application environment information of parameter items in the parameter verification request in response to the parameter verification request, the apparatus further includes:

[0234] The acquisition module is further used to acquire, in response to the first input on the first page, the custom configuration information of the parameter item in the first input;

[0235] The acquisition module is further used to send the custom configuration information to the first client and obtain the information of the operation result, wherein the information of the operation result is obtained after the first client performs the configuration based on the custom configuration information;

[0236] The sending module is also used to send the custom configuration information to the second client when the running result reaches the preset running result.

[0237] Each module in the parameter verification device provided in the embodiment of the present application can realize Figures 1 to 8 The functions of each step of the provided parameter verification method and the ability to achieve the corresponding technical effects are described briefly and will not be repeated here.

[0238] Fig.10 A schematic diagram of the hardware structure of a parameter verification device provided in an embodiment of the present application is shown.

[0239] The parameter verification device may include a processor 1001 and a memory 1002 storing computer program instructions.

[0240] Specifically, the processor 1001 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0241] Memory 1002 may include a large capacity memory for data or instructions. By way of example and not limitation, memory 1002 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, memory 1002 may include a removable or non-removable (or fixed) medium. In appropriate cases, memory 1002 may be inside or outside a calibration device for a parameter. In a particular embodiment, memory 1002 is a non-volatile solid-state memory.

[0242] The memory may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of the present disclosure.

[0243] The processor 1001 implements any parameter verification method in the above embodiments by reading and executing computer program instructions stored in the memory 1002 .

[0244] In one example, the parameter verification device may further include a communication interface 1003 and a bus 1004. Fig.10 As shown, the processor 1001, the memory 1002, and the communication interface 1003 are connected via a bus 1004 and communicate with each other.

[0245] The communication interface 1003 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0246] Bus 1004 includes hardware, software or both, and couples the components of the parameter verification device to each other. For example, but not limitation, the bus may include Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), Hyper Transport (HT) interconnection, Industry Standard Architecture (ISA) bus, InfiniBand interconnection, Linear Predictive Coding (LPC) bus, memory bus, MicroChannel Architecture (MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (Peripheral Component Interconnect-X, PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association Local (VESA Local Bus, VLB) bus or other suitable bus or two or more of these combinations. Where appropriate, bus 1004 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.

[0247] The device can execute the parameter verification method in the embodiment of the present application based on each unit / component in the parameter verification device, thereby realizing the combination Figures 1 to 6 Describes the verification method of the parameters.

[0248] In addition, in combination with the parameter verification method in the above embodiment, the embodiment of the present application can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any parameter verification method in the above embodiment is implemented.

[0249] The present application also provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes each process of an embodiment of a method for verifying any of the above parameters.

[0250] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0251] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), appropriate firmware, plug-in, function card, etc. When implemented in software, the elements of the present application are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or communication link by a data signal carried in a carrier. "Machine-readable medium" may include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (Read-Only Memory, ROM), flash memory, erasable read-only memory (Erasable Read Only Memory, EROM), floppy disks, compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical discs, hard disks, optical fiber media, radio frequency (Radio Frequency, RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0252] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0253] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0254] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A parameter verification method, characterized in that: include: In response to the parameter verification request, obtaining configuration information, target version information, and target application environment information of the parameter item in the parameter verification request, wherein the configuration information includes a parameter identifier and parameter content; In the correspondence between the preset version information, the application environment information and the verification rule information, obtaining the first target verification rule information corresponding to the target version information and the target application environment information, wherein the first target verification rule information includes the preset parameter identifier of each preset parameter item and the content constraint condition corresponding to each preset parameter identifier; Matching each of the parameter identifiers with each of the preset parameter identifiers to obtain a first syndrome result; matching the parameter content with the content constraint condition to obtain a second syndrome result; A target verification result is generated based on the first syndrome result and the second syndrome result.

2. The method according to claim 1, characterized in that The parameter identifiers include a system layer parameter identifier, a software layer parameter identifier, and an application layer parameter identifier; and the matching of each of the parameter identifiers with each of the preset parameter identifiers to obtain a first syndrome result includes: The system layer parameter identifier, the software layer parameter identifier and the application layer parameter identifier are matched with each of the preset parameter identifiers to obtain a first syndrome result.

3. The method according to claim 1, characterized in that The content constraint condition includes at least one of a data type, a data format, and a value range; and matching the parameter content with the content constraint condition to obtain a second syndrome result includes: The parameter content is matched with at least one of the data type, the data format and the value range to obtain a second syndrome result.

4. The method according to claim 1, characterized in that The parameter identifier includes a first type parameter identifier and a second type parameter identifier; the first target verification rule information also includes a dependency verification rule and a fault occurrence condition; Before generating a target verification result based on the first syndrome result and the second syndrome result, the method further includes: Verify the parameter content corresponding to the first type of parameter identifier according to the dependency verification rule to obtain a third verification sub-result; Matching the second type parameter identifier and the corresponding parameter content with the fault occurrence condition to obtain a fourth syndrome result; The generating a target verification result based on the first syndrome result and the second syndrome result includes: A target check result is generated based on the first syndrome result, the second syndrome result, the third syndrome result, and the fourth syndrome result.

5. The method according to claim 4, characterized in that The dependency verification rule includes a mutually exclusive verification rule and a collaborative verification rule; the first type of parameter identifier includes a first sub-parameter identifier and a second sub-parameter identifier; the parameter content corresponding to the first type of parameter identifier is verified according to the dependency verification rule to obtain a third verification sub-result, including: According to the mutually exclusive verification rule, the parameter content corresponding to the first sub-parameter identifier is verified, and according to the collaborative verification rule, the parameter content corresponding to the second sub-parameter identifier is verified to obtain a third verification sub-result.

6. The method according to claim 4, characterized in that The fault occurrence condition includes at least one of the lack of a first key parameter identifier, the presence of a second key parameter identifier, and the configuration content being a preset content; the matching of the second type parameter identifier and the corresponding parameter content with the fault occurrence condition to obtain a fourth syndrome result includes: The second type parameter identifier and the corresponding parameter content are matched respectively with at least one of the lack of the first key parameter identifier, the existence of the second key parameter identifier, and the configuration content being the preset content to obtain a fourth syndrome result.

7. The method according to claim 6, characterized in that The second type parameter identifier and the corresponding parameter content are matched respectively with at least one of the lack of the first key parameter identifier, the existence of the second key parameter identifier, and the configuration content being the preset content to obtain a fourth syndrome result, including: In the case where the first key parameter identifier is missing from the second type parameter identifier, a fourth syndrome result is obtained as a verification failure and an alarm prompt message is generated; and / or When the second key parameter identifier exists in the second type parameter identifier, a fourth syndrome result is obtained as a verification failure and an alarm prompt information is generated; and / or When the parameter content corresponding to the second-type parameter identifier is the preset content, the fourth check sub-result is a check failure and an alarm prompt information is generated.

8. The method according to claim 4, characterized in that Also includes: generating report information based on the first syndrome result, the second syndrome result, the third syndrome result, the fourth syndrome result, and the target verification result; The report information is displayed on a first page.

9. The method according to claim 8, characterized in that Multiple application environments share one first page, and the multiple application environments are isolated from each other.

10. The method according to any one of claims 1 to 9, characterized in that: Before obtaining, in response to the parameter verification request, configuration information, target version information, and target application environment information of the parameter item in the parameter verification request, the method further includes: In response to an Nth update detection request for the verification rule sent by the client, obtaining target version information and target application environment information in the Nth update detection request, wherein N is a positive integer greater than 0; In the preset correspondence between version information, application environment information and update identification information, obtaining target update identification information corresponding to the target version information and the target application environment information; In the case where the target update identification information is the first preset update identification information, obtaining the updated verification rule information in the database, and sending the first preset update identification information and the updated verification rule information to the client at a preset time, wherein the first preset update identification information indicates that there is a verification rule update; or In a case where the target update identification information is the second preset update identification information, sending the second preset update identification information to the client at a preset time, wherein the second preset update identification information indicates that there is no verification rule update; Receive the N+1th update detection request for the verification rule sent by the client, wherein the N+1th update detection request is generated by the client after receiving the first preset update identification information or the second preset update identification information.

11. The method according to claim 10, characterized in that Also includes: In response to a verification rule acquisition request sent by a client, obtaining target version information and target application environment information in the verification rule acquisition request, wherein the verification rule acquisition request is sent by the client according to a preset period; In the preset correspondence between version information, application environment information and verification rule information, obtaining second target verification rule information corresponding to the target version information and the target application environment information; The second target verification rule information is sent to the client.

12. The method according to claim 1, characterized in that Before obtaining, in response to the parameter verification request, configuration information, target version information, and target application environment information of the parameter items in the parameter verification request, the method further includes: In response to a first input on the first page, obtaining custom configuration information of a parameter item in the first input; Sending the custom configuration information to the first client, and obtaining information about the running result, wherein the information about the running result is obtained by running the first client after performing configuration based on the custom configuration information; When the running result reaches the preset running result, the custom configuration information is sent to the second client.

13. A parameter verification device, characterized in that: include: An acquisition module, configured to acquire, in response to a parameter verification request, configuration information, target version information, and target application environment information of a parameter item in the parameter verification request, wherein the configuration information includes a parameter identifier and parameter content; The acquisition module is further used to acquire first target verification rule information corresponding to the target version information and the target application environment information in the correspondence relationship between the preset version information, the application environment information and the verification rule information, wherein the first target verification rule information includes a preset parameter identifier of each preset parameter item and a content constraint condition corresponding to each preset parameter identifier; A verification module, used to match each of the parameter identifiers with each of the preset parameter identifiers to obtain a first syndrome result; and match the parameter content with the content constraint condition to obtain a second syndrome result; A generating module is used to generate a target verification result based on the first syndrome result and the second syndrome result.

14. A parameter verification device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the parameter verification method according to any one of claims 1 to 12 is implemented.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the parameter verification method according to any one of claims 1 to 12 is implemented.

16. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of a device, the device is enabled to perform the parameter verification method according to any one of claims 1 to 12.

Images