Business event bucket assignment via OpenPipeline
- Latest Dynatrace
- How-to guide
- 2-min read
- Published May 13, 2026
Business events can be stored in buckets that can have different retention periods. You create rules with matcher-specific DQL queries to assign matching business events to a bucket. The default retention period for a built-in business events bucket (default_bizevents) is 35 days. You can also create custom buckets with a specific retention period.
For custom buckets, the possible retention period ranges from 1 day to 10 years, with an additional week.
Business events can be stored in different buckets that determine the retention time and access permissions. You can create rules with matcher-specific DQL queries to assign matching business events to a bucket. By default, every incoming business event is stored in the default bucket with a 35-day retention period. Longer and shorter periods can also be set.
Retention period in OpenPipeline
First, create a bucket. To do so:
- Go to
Settings > Storage Management > Bucket storage management. - Add a new bucket (:PlusIcon: New bucket) or select from the pre-existing ones.
- Name your bucket.
- Optional Choose a display name. If no display name is selected, your bucket will inherit the bucket name.
- Choose the bucket table type: bizevents.
- Choose the retention period in days.
- Select Create.
Business events bucket assignment is done with OpenPipeline:
- Go to Process and contextualize > OpenPipeline > Business events.
- Select the pipeline that is processing the business event.
- Go to the Storage tab.
- From the processor list, select Bucket Assignment to add a new bucket to the pipeline.
- Name the bucket assignment configuration.
- Add a matching condition by using matcher-specific DQL query.
- Select the storage that matches the bucket created previously.
If you wish to add your business events to different buckets, create different processor rules to capture according to the use case.
Matcher examples
- If you needed to add only one event type (for example,
com.easytrade.buy-assets), the matcher would be:
matchesValue(event.type, "com.easytrade.buy-assets")
- For two event types within the same event provider, the matcher would be:
matchesValue(event.type, "com.easytrade.buy-assets") or matchesValue(event.type, "com. easytrade.sell-assets")
- In this use case, however, you need to take all event types under the EasyTrade event provider, so it is sufficient just to use:
matchesValue(event.provider, "www.easytrade.com")