Environments

Environments let you separate bug reports by deployment stage — for example Development, Staging, and Production. API tokens are scoped to a specific environment, so reports are automatically tagged.

Creating an environment

Navigate to your project and open the Environments tab. Click Add Environment.

A URL-safe slug is generated automatically from the name.

Using environments

Token scoping

When you create an API token, you select both a project and an environment. All data ingested with that token is automatically tagged with the environment.

Filtering

The dashboard lets you filter reports and events by environment. The color tag appears next to report entries for quick visual identification.

Dashboard metrics

The project dashboard shows activity by environment — how many reports each environment is generating. This helps you identify whether bugs are concentrated in a specific deployment stage.

Editing an environment

Environments cannot be edited after creation from the dashboard — the Environments tab only supports creating and deleting them. To change a name or color, delete the environment and create a new one (existing reports keep their original environment tag).

Deleting an environment

Delete an environment from the Environments tab. Existing reports and events that reference this environment will retain their environment tag for historical purposes, but new data cannot be ingested against a deleted environment.

Best practices

• Create at least three environments — Development, Staging, Production — to mirror your deployment pipeline.
• Use distinct colors — makes it easy to spot production bugs in the report list.
• Scope tokens tightly — give each build configuration its own token pointed at the right environment.