Key concepts
Workspace
Section titled “Workspace”A workspace is the top-level organisational unit in TraceStax — typically your company or team. Billing, plan limits, and team members are managed at the workspace level.
Project
Section titled “Project”A project maps to a single application or service. Each project has a unique API key used by the SDK to authenticate events. You might have separate projects for orders-service, notifications-service, and ml-pipeline.
A single telemetry record emitted by the SDK when a job starts, succeeds, or fails. Events are immutable once ingested. See the event schema reference.
A job is a discrete unit of background work identified by its name (e.g. send_welcome_email, ProcessOrderJob). TraceStax tracks statistics per job name within a project.
The named queue or topic that delivers work to your workers. TraceStax tracks queue depth and throughput independently for each queue.
Worker
Section titled “Worker”An individual process that consumes and executes jobs. Workers are identified by a stable worker.key — either set explicitly in the SDK config or derived from the hostname and PID.
Baseline
Section titled “Baseline”The statistical model TraceStax builds for each (job, queue) pair over a configurable lookback window. Used by the anomaly detection system to identify deviations without manual threshold configuration.
A notification fired when TraceStax detects an anomaly. Alerts route to your configured on-call integration and auto-resolve when the underlying behaviour returns to baseline.
API key
Section titled “API key”A secret credential that authenticates event ingest for a project. Treat it like a password — rotate it from the project settings page if it is ever exposed. API keys have the prefix ts_live_.