A multi-service scenario-based filtering expression intelligent configuration method

Abstract

The application discloses a kind of filtering expression intelligent configuration methods based on multi-service scene, it is related to electronic digital data processing technical field.The application includes the following steps: step 1: rule design, filtering condition is abstracted as multiple condition combinations, the relationship between conditions in group is "and" (and) relationship, group and group are "or" (or) relationship, each condition includes field (field), operator (oper) and target value (values).The application, by abstract design, supports multiple matching modes, meets the filtering needs in different scenarios, with high flexibility;By minimizing configuration complexity, improve user configuration efficiency, so that configuration is simple, and has simpler and more intuitive condition expression configuration mode;By easily extending new matching mode and application scenario, maintain the long-term competitiveness of the system, with strong expansibility;Through multiple matching modes, the accuracy and efficiency of condition screening are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of electronic digital data processing, and in particular to a filtering expression intelligent configuration method based on multiple service scenarios. BACKGROUND

[0002] In the monitoring and management of software systems, it is often necessary to filter and process alarms, faults or events according to specific conditions. The existing condition expression implementation method is often complex and not flexible enough, and it is difficult to meet the changing business needs.

[0003] The prior art has the following defects:

[0004] The existing condition expression implementation method is not intuitive and is complex to configure.

[0005] Lack of flexibility, difficult to adapt to changing business scenarios;

[0006] It is difficult to achieve fine-grained control and diversified matching rules.

[0007] Therefore, a filtering expression intelligent configuration method based on multiple service scenarios is proposed. SUMMARY

[0008] The purpose of the present application is to solve the problems raised in the background art. The present application provides a filtering expression intelligent configuration method based on multiple service scenarios.

[0009] In order to achieve the above purpose, the present application specifically adopts the following technical solutions:

[0010] A filtering expression intelligent configuration method based on multiple service scenarios, comprising the following steps:

[0011] Step 1: rule design, filtering conditions are abstracted as multiple sets of condition combinations, the conditions within the set are in an "and" relationship, and the sets are in an "or" relationship, each condition contains a field, an operator and a target value;

[0012] Step 2: target value matching, providing flexible matching methods to meet the needs of multiple scenarios;

[0013] Step 3: describe the filtering condition expression, match alarms of specific severity or have specific check labels by combining condition expressions;

[0014] Step 4: realize intuitive description of filtering condition expression, simplify the expression of filtering conditions through simple and intuitive operator (oper) and rich target value (values) description method.

[0015] Further, the application scenarios of the method filtering condition include: dispatch strategy, silence rule, suppression rule, alarm aggregation, routing rule, and label enhancement.

[0016] Further, the operator (oper) includes the following types:

[0017] Type one: match any, matching when any target value meets the condition;

[0018] Type two: match none, matching when all target values do not meet the condition.

[0019] Further, the target value matching of step 2 includes regular matching, wildcard matching, IP segment matching, numerical value size matching, and exact matching.

[0020] Further, the step 4 implements the intuitive description of the filtering condition expression, including the following steps:

[0021] Step 41: The operator (oper) is simple, supporting "match any" and "none match" logic;

[0022] Step 42: The target value (values) supports multiple, cooperating with the operator (oper), to realize the inclusion (in) and interval (between) scenarios;

[0023] Step 43: The target value (values) is flexible and extensible, using an expression to describe the filtering condition, supporting regular, wildcard, IP segment, and numerical value size matching methods;

[0024] Step 44: Conditions only have an and relationship, and condition groups only have an or relationship, to realize simple and easy-to-remember logical combinations, and the overall combination supports most condition filtering scenarios, to improve the flexibility and efficiency of configuration.

[0025] Further, the method does not depend on a specific programming language or platform, to have universality and portability.

[0026] The beneficial effects of the present application are as follows:

[0027] Through abstract design, multiple matching methods are supported to meet the filtering needs in different scenarios, to have high flexibility;

[0028] By minimizing configuration complexity, user configuration efficiency is improved, making configuration simple, and having a simpler and more intuitive condition expression configuration method;

[0029] By easily extending new matching methods and application scenarios, the long-term competitiveness of the system is maintained, to have strong expansibility;

[0030] The accuracy and efficiency of condition screening are improved through various matching modes. BRIEF DESCRIPTION OF DRAWINGS

[0031] Figure 1 is a schematic diagram of a plurality of condition combinations of the present application. DETAILED DESCRIPTION

[0032] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings can be arranged and designed in various different configurations.

[0033] Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative labor are within the scope of protection of the present application.

[0034] It should be noted that: similar reference numerals and letters represent similar items in the following drawings, therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. In addition, the terms "first", "second", etc. are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.

[0035] In the description of the embodiments of the present application, it should be noted that the positions or location relationships indicated by the terms "inner", "outer", "upper", etc. are based on the positions or location relationships shown in the drawings, or the positions or location relationships of the product of the present application when it is usually placed, which are only for the convenience of describing the present application and simplifying the description, and cannot be understood as indicating or implying that the indicated device or element must have a particular position, be constructed and operated in a particular position, therefore, cannot be understood as limiting the present application.

[0036] As Figure 1 shown, a multi-service scenario-based filtering expression intelligent configuration method includes the following steps:

[0037] Step 1: rule design, filtering conditions are abstracted as a plurality of condition combinations, the conditions in the group are in an "and" relationship, the groups are in an "or" relationship, and each condition includes a field, an operator and a target value.

[0038] Step 2: target value matching, flexible matching modes are provided to meet the needs of various scenarios;

[0039] Step 3: rule matching, the rule is matched with the target value, and the rule is matched with the target value.

[0039] Step 3: Describe the filtering condition expression, match the alarm of specific severity or with specific check label by combining condition expressions;

[0040] Step 4: Realize the intuitive description of filtering condition expression, simplify the expression of filtering condition by concise and intuitive operator (oper) and rich value description method.

[0041] The application scenarios of the method filtering condition include:

[0042] Dispatching strategy: support setting dispatching object based on different filtering conditions;

[0043] Silencing rule: match specific fault by filtering condition to realize fault silencing;

[0044] Suppression rule: match new triggered fault with active fault to realize fault suppression;

[0045] Alarm aggregation: control alarm aggregation dimension in fine granularity, match specific alarm by filtering condition;

[0046] Routing rule: global routing matching rule, route alarm to specific collaboration space based on filtering condition;

[0047] Label enhancement: generate label for alarm according to filtering condition.

[0048] The operator (oper) includes the following types:

[0049] Type one: match_any: match when any target value meets the condition;

[0050] Type two: match_none: match when all target values do not meet the condition.

[0051] The target value matching of step 2 includes:

[0052] Regular matching: when the value string is prefixed and suffixed with / , it is identified as a regular expression, which needs to meet the regular;

[0053] Wildcard matching: when the value contains * or? and has no / prefix and suffix, it is identified as a wildcard expression, which supports fuzzy matching;

[0054] IP segment matching: when the value is prefixed with cidr:, it is identified as an IP segment, which needs to meet the IP segment range;

[0055] Numeric size matching: When value is prefixed with num:[gt|ge|lt|le]:, it is recognized as a numerical size matching, supporting numerical judgments of greater than (gt), greater than or equal to (ge), less than (lt), and less than or equal to (le);

[0056] Exact match: When the value does not meet the above format, it is considered an exact match. Matches are made when the strings are completely equal.

[0057] The step 4 implements an intuitive description of the filter condition expression and includes the following steps:

[0058] Step 41: The operator (oper) is extremely simple and supports "match any" and "match none" logic;

[0059] Step 42: Multiple target values ​​are supported, and the operator (oper) is used to implement the inclusion (in) and interval (between) scenarios;

[0060] Step 43: Target values ​​are flexible and scalable. Filter conditions can be described using expressions, supporting regular expressions, wildcards, IP segments, and numerical values.

[0061] Step 44: Conditions have only an "and" relationship with each other, and condition groups have only an "or" relationship with each other, to achieve simple and easy-to-remember logical combinations. The overall combination supports most conditional filtering scenarios to improve configuration flexibility and efficiency.

[0062] The method is not dependent on a specific programming language or platform and is therefore universal and portable.

[0063] Example expression:

[0064] Bash

[0065] # " == " means match_any | " != " means match_none

[0066] (severity == Critical|Warning and labels.check == Binlog sync delay)

[0067] or (labels.check == / cpu / | / io / | / disk / and labels.value == num:gt:90)

[0068] The example shows how to combine conditional expressions to match alerts of a specific severity or alerts with a specific inspection tag and a value greater than 90.

[0069] In summary: through the abstract design, support multiple matching methods, meet the filtering requirements in different scenarios, have high flexibility; through minimizing configuration complexity, improve user configuration efficiency, make the configuration simple, and have a more simple and intuitive condition expression configuration method; through easy to extend new matching methods and application scenarios, maintain the long-term competitiveness of the system, have strong expansibility; through multiple matching methods, improve the accuracy and efficiency of condition screening.

[0070] The basic principles, main features and advantages of the present application are shown and described above. Those skilled in the art should understand that the present application is not limited to the above embodiments, and the above embodiments and descriptions in the specification are only the principles of the present application. Without departing from the spirit and scope of the present application, various changes and improvements can be made to the present application, and these changes and improvements all fall within the scope of the claimed present application. The scope of protection required by the present application is defined by the appended claims and their equivalents.

Claims

1. A method for intelligently configuring filter expressions based on multiple business scenarios, characterized in that: The following steps are involved: Step 1: Rule design. The filtering conditions are abstracted into multiple groups of conditions. The conditions within a group are in an "and" relationship, and the conditions between groups are in an "or" relationship. Each condition contains a field, an operator, and a target value. Step 2: Target value matching, providing flexible matching methods to meet the needs of various scenarios; Step 3: Describe the filter condition expression and combine the condition expressions to match alarms of a specific severity or with specific inspection tags. Step 4: Implement intuitive descriptions of filter condition expressions. This simplifies the expression of filter conditions through concise and intuitive operators (operators) and rich target value (values) descriptions. The operators (oper) include the following types: Type 1: match_any: any target value that meets the conditions is matched; Type 2: match_none: matches when all target values ​​do not meet the conditions; The step 4 implements an intuitive description of the filter condition expression and includes the following steps: Step 41: The operator (oper) is extremely simple and supports "match any" and "match none" logic; Step 42: Multiple target values ​​are supported, and the operator (oper) is used to implement the inclusion (in) and interval (between) scenarios; Step 43: Target values ​​are flexible and scalable. Filter conditions can be described using expressions, supporting regular expressions, wildcards, IP segments, and numerical values. Step 44: Conditions have only an "and" relationship with each other, and condition groups have only an "or" relationship with each other, to achieve simple and easy-to-remember logical combinations. The overall combination supports most conditional filtering scenarios to improve configuration flexibility and efficiency.

2. A method for intelligently configuring filtering expressions based on multiple business scenarios according to claim 1, characterized in that: Application scenarios of this method's filtering conditions include: dispatch strategy, silent rules, suppression rules, alarm aggregation, routing rules, and label enhancement.

3. The method for intelligently configuring filtering expressions based on multiple business scenarios according to claim 1, characterized in that: The target value matching in step 2 includes regular matching, wildcard matching, IP segment matching, numerical value matching and exact matching.

4. A method for intelligently configuring filtering expressions based on multiple business scenarios according to any one of claims 1 to 3, characterized in that: The method is not dependent on a specific programming language or platform and is therefore universal and portable.

Images