Create an environment and get its key

An Environment is one deployment of your project, such as development, staging or production. Each has its own key and its own traces. Signing up creates a project called Default Project with a development Environment called Default, so for a first trace you can go straight to Install the SDK.

Where Environments live

Open Settings in the sidebar footer, then This project → Environments. The Environment switcher in the top bar also has New environment and Manage environments.

The tab lists every Environment in a table. A row shows:

• its name and kind (development, staging or production)
• its key, masked except for the first eight and last four characters, with Copy key, which copies the full key at any time
• when it last received a trace, or "none in 30 d" if nothing arrived in the last 30 days
• its tenant id and when it was created
• Install guide, and a menu with Rotate key and Delete

Above the table, the Environments tile counts them against the plan limit (traceProjectLimit), for example "2 of unlimited". At the limit, Create environment opens a panel with Request upgrade instead of the form, and New environment in the switcher shows a lock.

Until you upgrade, that panel suggests keeping the development Environment and setting environment='production' in the SDK to label production traffic.

Create one

1. 1

   Open the form

   Click Create environment on the Environments tab, or New environment in the switcher.

2. 2

   Name it and pick its kind

   Fill in Name, for example production, choose the Kind and add an optional Description. The kind is stamped on every span the SDK sends with this key, so filters and facets can tell deployments apart.

3. 3

   Create it and copy the key

   Click Create. The Environment created dialog shows the full key to paste into your SDK config. You can copy it again later from the Environments tab.

4. 4

   Install the SDK

   Click Install guide in the same dialog. The quickstart opens with this key already in the snippet and waits for the first trace. Continue in Install the SDK.

What the key identifies

Each Environment has a fixed tenant id, derived once when it is created. Rotating the key changes only the key, so past traces, the Environment's online rule and its alerts stay attached. The trace read API addresses an Environment by its tenant id, or by the literal me when the request carries the Environment's key.

Datasets, runs, Models and the Playground belong to the project, and evaluators to the Organization, so none of them change when you switch Environment. Traces, Online rules, Alerts and Cost do. The top bar shows the selected Environment's kind next to the project name on every page, so development data is not mistaken for production.