Environments

Environments lives in the Settings area of the dashboard, under Apps & data.

At a glance#

What it does#

Environments separate the same app's data by where it is running — production, staging, development, and whatever else you need. You can create, rename and delete them, and purge an environment's sessions.

An environment is the correct boundary for "same app, different deployment". Using separate apps for that would break every comparison between them; using one environment for everything means your development noise pollutes your production metrics.

When to use it#

At setup, and then rarely. The important part is not creating them — it is making sure each build reports into the right one, which is an SDK configuration decision.

Purge is the exception: you will come back for that. A development environment accumulates junk data from testing, and purging it is how you get a clean baseline.

Workflow#

1. 1

   Create the environments you actually ship to

   Production and one pre-production is enough for most teams. Every extra environment is another place data can end up unnoticed.

2. 2

   Point each build at its own environment in the SDK

   This is where it actually happens — see Configuration. The dashboard cannot route data; it can only tell you where it landed.

3. 3

   Purge development environments when they get noisy

   Cheap, and it makes the environment useful again for testing.

Permissions and prerequisites#

Creating and deleting environments requires an administrative role. Environment creation and session purges are recorded in the audit log.

Limits and edge cases#

• Environment is chosen by the SDK, not the dashboard. A misconfigured build reports into whichever environment its key belongs to, and everything looks like it is working.

• Metrics do not aggregate across environments. That is deliberate — mixing staging into production numbers would make both useless.

• Deleting an environment removes its data.

Troubleshooting#

Production data appearing in staging. A build is using the wrong key or the wrong environment configuration. Check the build, not the dashboard.

A dashboard page looks empty. Check the environment selector first. This is the most common cause of "the dashboard is broken" by a very wide margin.

Where the data comes from#

From the SDK

• Configuration

Served by

• Environments

Related#

• SDK configuration

• Apps

• SDK setup

• Data & privacy

• Symbolication

• Settings overview