Save searches and export data

Preserve repeatable filters and create bounded CSV, JSON, or Parquet export jobs.

Save a search when the same investigation filter will be reused inside Teml. Export data only when a bounded external copy is necessary for analysis, evidence, or an approved downstream workflow.

Save a search

From a supported signal view, save the current filters with a question-oriented name. Keep searches private when they contain an individual’s investigation context; share only filters that are useful to the organization.

The CLI exposes the complete saved-search contract:

teml saved-searches list --signal logs
teml saved-searches create --json '{"name":"Checkout errors","signal":"logs","query":{"service_name":"checkout","level":"error"},"is_shared":true}'

Saved searches preserve filters, not a frozen result set. Running one later uses current data and the current retention window.

Export a bounded log set

teml export logs --json '{
  "format":"csv",
  "service_name":"checkout",
  "level":"error",
  "start_time":"2026-07-20T10:00:00Z",
  "end_time":"2026-07-20T11:00:00Z"
}'

Choose CSV for spreadsheet analysis, JSON for structured processing, and Parquet for larger analytic workflows. Always set the narrowest useful project, time range, filters, and columns.

Monitor and download jobs

teml export jobs list
teml export jobs get <job-id>
teml export jobs download-url <job-id>
teml export jobs cancel <job-id> --yes

Downloads use fresh signed URLs. Treat an exported file as customer telemetry: store it in an approved location, restrict access, preserve only as long as needed, and delete local copies after use. Export does not extend the retention of the source data inside Teml.