The filter allows you to configure filtering rules such as field sizes to filter data. Only data that meets the specified rules will be retained.
true
, false
, and null
).You can perform key value matching by comparing a specified prefix with the prefix in data.
For example, for data {"password":"topicname"}
, you can specify top
as the prefix of the password
value so that {"password":"topicname"}
can be normally matched.
You can perform key value matching by comparing a specified suffix with the suffix in data.
For example, for data {"password":"topicname"}
, you can specify name
as the suffix of the password
value so that {"password":"topicname"}
can be normally matched.
You can specify a field to be included in data as a match condition.
For example, for data {"password":"topicname"}
, you can specify na
to be included in the password
value so that {"password":"topicname"}
can be normally matched.
You can specify a field to be excluded from data as a match condition.
For example, for data {"password":"topicname"}
, you can specify topicname
to be excluded from the password
value so that {"password":"topicname"}
cannot be normally matched.
You can specify the value or value range of a certain field as a match condition.
For example, for data { "numeric": 10}
, you can specify the value of numeric
to be less than 15 (<15
) as a match condition so that { "numeric": 10}
can be normally matched.
The following are examples of value match rules:
- Greater than 10: Enter `>10`
- Greater than or equal to 10: Enter `>=10`
- Greater than or equal to 10, and less than or equal to 20: Enter `>=10&<=20`
- Greater than or equal to 10, or less than or equal to 5: Enter `>=10|<=5`
You can specify an IP in CIDR notation as a match condition. For example, you can enter 1.2.3.4/24
to match IPs whose leading 24 bits start with "1.2.3.".
Was this page helpful?