Manage buckets for RUM

  • Latest Dynatrace
  • How-to guide
  • 2-min read
  • Published Apr 24, 2026

When managing buckets for storing Real User Monitoring (RUM) data, it's important to know how to:

  • Create custom buckets and assign relevant RUM data to them.
  • Define the segmentation strategy, retention period, and ownership.

How RUM data and buckets work together

  • Bucket assignment is not retroactive for existing data. The rules apply only to data ingested after the rules come into effect.

  • Custom buckets for RUM are configured the same way as for other Grail data. You can create and manage them via:

When executing RUM, Dynatrace writes data into the following tables:

With custom buckets that are set to store RUM data:

  • Each session or event is assigned to exactly one bucket at the time of ingestion.
  • The bucket determines:
    • Retention period.
    • Storage tier (depending on your product configuration).
    • Query availability and performance.
  • Standard RUM tools (explorers, dashboards, notebooks) can query across:

    Depending on the UI design, this is either transparent or exposed via bucket filters and scopes.

Create a custom bucket and assign relevant RUM data to it

Create a custom bucket

  1. Go to Settings Settings > Storage management > Bucket storage management > New Bucket.
  2. Enter a bucket name, and then choose user.sessions or user.events as the Bucket table type. To be able to set Retention period (in days), join the preview program.
  3. Select Create.
  4. Select Refresh to update the bucket list.

Assign relevant RUM data to bucket

  1. Go to Settings Settings > Process and contextualize > OpenPipeline.
  2. Select User sessions or User events.
  3. Go to Pipelines and choose an existing pipeline, or create a new one by selecting Pipeline.
  4. In the Storage tab, select Processor > Bucket assignment and define the new processor.
    1. Enter the processor Name and the Matching condition (for example, frontend.name == "my-monitored-app").
    2. In the Storage list, choose the bucket you created.
  5. Select Save.

Define segmentation strategy

You can segment RUM data by:

  • Default enrichments:
    • Application—use frontend.name as a matching condition.
    • Sensitivity (containing PII vs. not containing PII)—for data that contain PII, you can, for example, utilize user interaction characteristics as matching conditions.
  • Custom properties that you can use as matching conditions.
    • Environment—add a custom property like "production" or "non-production" to all events.
    • Region—add a property based on specific country codes.
    • Team—add a custom team property.

Define retention period per segment

Preview

The default bucket retention period is 35 days. You can extend the retention period after you join the preview program. To request access, go to Preview program.

The retention period for each segment should be defined based the business criticality.

  • Critical external apps—12-24 months.
  • Internal or non-critical apps—30-90 days.
  • Applications or features that are in a temporary or exploratory phase (experiments, beta features, feature flags)—may be 30 days or less.

Define access and ownership

Define the following:

  • Who manages the bucket configuration.
  • Which team should have access to which buckets.
  • Which buckets must be covered by compliance reviews.

For details, see Data partitioning strategy ownership, Control permissions and access to Grail data, and Bucket permissions.

Related topics

Related tags
Digital Experience