Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sluice.sh/llms.txt

Use this file to discover all available pages before exploring further.

​
What Sluice collects

Sluice collects task metadata and operational telemetry — not the contents of your tasks. Specifically:
  • Task metadata — task name, state transitions, timestamps, duration, retry count, worker hostname, queue name, traceback on failure.
  • Worker info — hostname, software version, active/online/offline state, heartbeat timestamps, prefetch count.
  • Queue metrics — queue depth (message count), consumer count, sampled at regular intervals.

​
What Sluice does NOT collect

  • Task arguments and return values are not sent to Sluice by default. The SDK strips args, kwargs, and result from events before forwarding. This is a deliberate design choice — these fields often contain PII, credentials, or large payloads that have no business leaving your infrastructure.
  • No source code, environment variables, or filesystem data.
  • No HTTP requests, database queries, or general APM telemetry.

​
Where data is stored

All data is stored in a cloud-hosted PostgreSQL database managed by Sluice. Connections to the database are encrypted in transit (TLS) and at rest (AES-256).

​
Data retention

PlanRetention
Free tier24 hours
Paid plansTBD — longer retention windows will be available at launch
After the retention window, data is permanently deleted in automated cleanup jobs.

​
Deleting your data

Deleting a connection in the dashboard deletes all associated data — jobs, workers, queue snapshots, and event history. This action is immediate and irreversible. Go to Connections in the dashboard, select the connection, and click Delete Connection.

​
Data Processing Agreement

A DPA is available on request for paid plans. Contact [email protected].