Primary Grail tag rules in OpenPipeline derive primary_tags.* fields from fields already present on incoming records. Rules run globally and apply to all record types.
OpenPipeline Primary Grail tags is a configuration scope where you can define rules to derive and assign primary_tags.* to any record type. The rules are evaluated before ingest source pre-processing, making the resulting primary_tags.* fields immediately available for routing decisions and further processing, such as bucket assignment or access control policies. All rules are evaluated for every incoming record and overwrite existing primary_tags.* values by default.
Use primary Grail tag rules to promote existing record fields to primary_tags.*, or as a fallback when earlier-stage enrichment and central tag configuration don't cover your use case.
Before configuring primary Grail tag rules in OpenPipeline, review Best practices for enriching primary Grail fields and tags to confirm that other enrichment options don't cover your use case.
| Parameter | Description |
|---|---|
Rule name | Descriptive name for the rule. |
Primary tag field name | Configurable, unique key for the |
Matching condition | DQL expression identifying which records the rule applies to. Defaults to |
Source fields | Ordered list of source field names. The used value is the first field that exists on the record with a non-null value. Supported formats are string and numeric field single values.1 |
Keep source field | When enabled, source fields are retained on the record alongside the new primary tag and primary tags can be configured on nested fields. When disabled, top-level source fields matched by the rule are removed from the record. Primary Grail fields and important Semantic Dictionary fields, such as |
Enabled | Whether the rule is active. Defaults to enabled. |
To normalize or transform a value after it's set, use the DQL processor.
aws.tags.env, azure.tags.env, and gcp.labels.env, a single configuration maps all variants to primary_tags.env centrally.