Skip to main content

TTL and Data Retention

LangSmith Self-Hosted allows enablement of automatic TTL and Data Retention of traces. This can be useful if you're complying with data privacy regulations, or if you want to have more efficient space usage and auto cleanup of your traces. Traces will also have their data retention period automatically extended based on certain actions or run rule applications. For more details on Data Retention, take a look at the section on auto-upgrades in the data retention guide.

Requirements​

You can configure retention through helm or environment variable settings. There are a few options that are configurable:

  • Enabled: Whether data retention is enabled or disabled. If enabled, via the UI you can your default organization and project TTL tiers to apply to traces (see data retention guide for details).
  • Retention Periods: You can configure system-wide retention periods for shortlived and longlived traces. Once configured, you can manage the retention level at each project as well as set an organization-wide default for new projects.
config:
  ttl:
    enabled: true
    ttl_period_seconds:
      # -- TTL seconds - 400 day longlived and 14 day shortlived
      longlived: "34560000"
      shortlived: "1209600"

Was this page helpful?


You can leave detailed feedback on GitHub.