Skip to main content
Utilities is the control plane for each site and each backend service. Open it from the app rail after selecting the asset in the circle selector. There are three tabs: Environment, Repository, and Archive.

​
Environment

Environment controls what Tracelit is allowed to do with traffic from each deployment stage.

​
Frontend sites

Sites use one site token for both environments. Pass environment: "development" or environment: "production" in the SDK init(...) (or script tag). Other values are rejected.

​
Backend services

You can bind a per-environment ingest key (or use the workspace ingest key with OTEL_SERVICE_NAME + deployment.environment). Supported deployment.environment values: local, development, production.

​
Gates

Save after changing gates. They apply to new work immediately.

​
Repository

Link the GitHub repository Tracelit should use for resolutions.
1

Connect GitHub

Settings → Integrations → install the Tracelit GitHub App if you have not already.
2

Link repository

In Utilities → Repository, pick a repo the app can access.
3

Map branches

Set Development and Production branches. Resolutions for those environments read code from the mapped branch.
Unlinking the repository stops new code-backed resolutions until you link again. Historical PRs are unchanged. See also: GitHub · GitLab · Bitbucket.

​
Archive

Archive pauses monitoring for the whole commercial unit:

​
What happens when you archive

  • Ingest for that site or service name is rejected (no new data).
  • The asset disappears from the circle selector and frees one plan slot.
  • Historical sessions, logs, traces, and incidents remain.

​
Billing note

Plan limits count distinct sites and distinct service names. Environments under one service name share a single slot and archive together. You will see a confirmation modal before archive. You can unarchive later (subject to plan capacity).