Lifecycle table
Create one rule per row. Each rule matches the prefix and expires objects after the stated period. Do not set a period shorter than the one shown, and do not leave a row without a rule.
Prefixes are matched from the start of the key, so each one is the first segment of the object key. Existing prefixes are unchanged: if you already hold rules for the three older ones, they keep working.
Which destinations accept oversized writes
- S3 and compatible stores accept oversized writes.
- Azure Blob needs you to confirm the rules exist. Today the trace spool refuses oversized writes until you do, and the other kinds will follow. LangWatch holds a data-plane key and cannot read a management-plane lifecycle policy back, so the confirmation is your statement, not a check.
- The local filesystem always refuses oversized writes. A filesystem cannot expire objects.
Confirming the rules on Azure
SetOBJECT_RETENTION_CONFIRMED=true once every row above has a rule on the container. With Helm, set app.dataplane.objectRetentionConfirmed: true.
AZURE_BLOB_SPOOL_RETENTION_CONFIRMED (Helm app.dataplane.providers.azureBlob.spoolRetentionConfirmed) was the earlier setting, which covered only the trace spool. It still confirms when OBJECT_RETENTION_CONFIRMED is unset, so an installation that set it keeps working. A value of false on OBJECT_RETENTION_CONFIRMED takes precedence over it. Move to the new name when convenient; the old one will be retired in a later release.
See Environment Variables for the Azure Blob settings.