Control Costs with Retention Quotas

Esta página aún no está disponible en español. Estamos trabajando en su traducción.
Si tienes alguna pregunta o comentario sobre nuestro actual proyecto de traducción, no dudes en ponerte en contacto con nosotros.
Join the Preview

Retention Quotas are in Preview.

Request Access

Overview

Retention quotas let you cap the number of sessions retained per day across your retention filters.

This gives you tighter cost control and prevents unexpected billing spikes caused by traffic surges or misconfigured filters.

How quotas work

You define a daily quota as a maximum number of retained sessions. After the quota is reached, you can choose one of two behaviors:

  • Stop retention: Datadog retains no additional sessions for the rest of the day and drops all incoming sessions until the quota resets.
  • Slow down retention: Retention continues but at a slower rate. Datadog retains only 10% of sessions that would normally be retained.

Setup

To set up a retention quota for an application:

  1. In Datadog, navigate to Digital Experience > Real User Monitoring > Manage Applications.
  2. Select your application.
  3. Go to Product Settings > Retention Filters.
  4. Set a daily quota threshold, a reset time, and a behavior when the quota is reached.
The retention quota configuration panel showing the daily quota threshold, reset time, and behavior options.
Quotas do not apply to sessions retained by Permanent Retention Filters.

Configuration is done at the application level, which means you can apply different retention strategies per application. Any configuration change (quota limit, retention behavior, reset time) is instantly applied.

Monitor quota usage

The retention filters page shows a breakdown of retained user sessions, including sessions blocked once the quota is reached. For dashboards and alerts, use the metric rum.measure.usage.quota_blocked_sessions.

A daily breakdown chart showing user sessions retained by custom filters, sessions retained by permanent filters, and sessions blocked once the quota was reached.

Further reading