The meta and $state entries are used to serialize and deserialize the state of the search bar filters shown in the Custom query section of the rule configuration.
Let's explore how the JSON in the previous post maps to the screenshot of the rule configuration:
the value of the key entry in the meta section of the JSON:
"key": "user_agent.original"
corresponds with the search bar filter's Fielduser_agent.original in the screenshot you provided ( focus on the EDIT FILTER popover):
the value for the type entry in the meta section of the JSON:
"type": "exists",
is combined with the negate entry (also in the meta section of the JSON):
"negate": true,
to become Operatordoes not exist in the screenshot:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.