overlane observe retention

The retention period for logs, spans, metrics and run events on the team’s plan, and the records no purge ever touches: the task ledger, evidence, the audit log, billing and decision records.

Usage

overlane observe retention

Examples

overlane observe retention
overlane observe retention --json

Behavior

Effect: read (changes nothing).
Needs credentials: yes. Uses the network: yes.
Supports --dry-run: no. Accepts --force: no.
Machine-readable description: overlane schema observe retention.

Result

With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.

{
  "type": "object",
  "properties": {
    "tenantId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 128,
      "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
      "description": "tenant identifier"
    },
    "plan": {
      "type": "string",
      "enum": [
        "free",
        "pro",
        "team",
        "business",
        "enterprise"
      ]
    },
    "retentionDays": {
      "anyOf": [
        {
          "type": "integer",
          "exclusiveMinimum": 0,
          "maximum": 9007199254740991
        },
        {
          "type": "null"
        }
      ]
    },
    "covers": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "run_events",
          "logs",
          "spans",
          "metrics",
          "runs",
          "resolved_incidents",
          "eval_results"
        ]
      }
    },
    "keeps": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "ledger",
          "evidence",
          "audit",
          "billing",
          "decisions"
        ]
      }
    }
  },
  "required": [
    "tenantId",
    "plan",
    "retentionDays",
    "covers",
    "keeps"
  ],
  "additionalProperties": false
}

See exit codes for the status the process returns.