Get started

    Create an environment and get its key

    Add a development, staging or production Environment to a project and copy the key the SDK will send traces with.

    After this page you will have an Environment for each deployment you want to see separately, and its key in your clipboard. Signing up already created Default Project with a Default development Environment and a real key, so for a first trace you can skip straight to Install the SDK.

    Where Environments live

    Open Settings in the sidebar footer → This project → Environments, or the Environment switcher in the top bar → New environment. The tab shows one card per Environment: its name and label (development · staging · production), the key masked to its last four characters, Copy, Rotate, Delete, Install guide, the time of its last trace and its spans this month, and a limit indicator such as “2 of unlimited”. The limit comes from your organization’s plan (traceProjectLimit); when it is reached, New environment shows a lock and opens the upgrade panel instead of the form.

    Create one

    1. 1

      New environment

      Fill Name (for example production), choose the Environment label — development, staging or production — and an optional description. The label is stamped on every span the SDK sends with this key, so filters and facets can tell deployments apart.

    2. 2

      Create

      The key is shown once in full. Copy key puts it in the clipboard; nothing is stored in the browser. Afterwards the card shows only the last four characters; if you lose the key, rotate it.

    3. 3

      Install SDK

      The Install guide opens the quickstart with this Environment’s real key already in the snippet and starts listening for the first trace. Continue in Install the SDK.

    What the key identifies

    Each Environment has a fixed tenant id derived once at creation. Rotating the key changes only the key, so every historic trace, the Environment’s online rule and its alerts stay attached. The trace read API addresses an Environment by that tenant id, or by the literal me when the request carries the Environment’s key.

    Datasets, runs, evaluators, Models and the Playground are project-scoped and do not change when you switch Environment; Traces, Online rules, Alerts and Cost do. The Environment pill is visible on every environment-scoped page so development data is never mistaken for production.

    EvalKit is built by Syntropylabs. Published on PyPI and npm.