Skip to content
Docs

Environments

On this page
  1. When to use environments
  2. Create an environment
  3. Link a sensor to an environment
  4. What an environment contains
  5. Related

An environment separates the sensors that watch different copies of your system — Production, Staging, Development. Each sensor belongs to one environment, and each environment holds its own variables and secrets: the same sensor definition can check api.corvane.example in Production and api.staging.corvane.example in Staging, with the right credentials each time.

Environments are managed in Configuration → Environments, by Managers and Admins. Creating environments requires a paid plan.

Environments page: Production (default), Staging and Development on the left; on the right, the variables of Production (API_HOST, PG_PRIMARY, WEB_HOST) and its secrets with their type and version, values hidden.
Pick an environment on the left to see and manage its variables and secrets.

When to use environments#

  • You monitor the same application in several copies: keep Production alerts apart from Staging noise, and see each copy's state separately.
  • You want sensors that differ only by a host or a credential: write them once with ${API_HOST} and a secret, and create one per environment.
  • You want to restrict who sees connection strings: secrets live in environments, which only Managers and Admins can open.

If you only monitor production, the default environment is enough.

Create an environment#

  1. Click New environment.
  2. Enter a Name (Staging) and an optional Description (Pre-production, refreshed from production every week).
  3. Save.

Your organization starts with a default environment named Default. New sensors are placed in the default environment unless you choose another one. Use Set as default on another environment to change it — for example to make Production the default.

An environment can be deleted only when no sensor uses it and it holds no variable and no secret. The default environment cannot be deleted.

Choose Environment in the General section of the wizard. The sensor then resolves its ${VARIABLES} and offers the secrets of that environment only. Lists show each sensor's environment as a badge, and incidents and service pages show it too.

What an environment contains#

Select an environment on the left to see its two cards:

  • Variables — plain values, such as hosts, ports or base URLs, reused in sensor fields as ${NAME}. See Variables.
  • Secrets — encrypted connection strings for databases, Redis and RabbitMQ, never displayed after they are saved. See Secrets.
  • Secret security — how secrets are encrypted and delivered to agents.
  • Services — the other axis of organization.