Environments and keys

An Environment is a key plus a kind: development, staging or production. The kind labels every trace and scopes online rules, alerts and cost. Use one Environment for each deployment.

The Environments tab

The tab lists the active Environments of the project with their kind, their key masked to the first 8 and last 4 characters, and when the last trace arrived ("none in 30 d" after 30 quiet days). A read that fails shows "unknown", never zero. Each row has Install guide and a menu with Rotate key and Delete.

The Environments tile counts them against the plan's limit, such as "2 of unlimited" or "1 of 1". Spans per Environment this month are on General and on Plan, usage and locks.

Create and edit

Create environment asks for a name, a kind and an optional description. It then shows the full key with Install guide, which opens the quickstart with this key filled in; see Install the SDK. The key stays copyable from the table.

At the plan's limit, the dialog shows Environment limit reached with Request upgrade, and no form. Editing is API only: PATCH /trace-projects/:id changes the name, description, kind and active state, never the tenant id or the key. Any member can create an Environment. Owners, Admins and the Member who created it can edit, rotate and delete it.

Rotate a key

Rotate key issues a new tk_live_… key and changes nothing else. The tenant id is derived once, at creation, and never recomputed, so stored traces, the online rule and alerts stay attached.

The old key stops being accepted within about 10 minutes, because the trace service caches key lookups for that long. There is no overlap window: deployments still sending with the old key get 401. Deploy the new key first, then rotate.

After you type the Environment's name to confirm, New key issued shows the new key, and its Install guide waits for a trace sent with it. Which key sent a given trace is not recorded, and there is no organization-level audit trail of who rotated.

Delete

Delete is a soft delete with no restore. You type the name and click Delete environment, and the Environment leaves the switcher and every list. Its key stops being accepted within the same 10 minutes, and its online rule and alerts stop. Stored traces stay until retention expires but are no longer listed.

Datasets and runs belong to the project and are never affected. Nothing blocks the delete: GET /trace-projects/:id/dependents lists the online rule, auto-add rules and simulation runs that reference the Environment, and they lose their target.