Environments

Overview

An environment is a logical boundary that groups configuration for a given context — such as Production, Staging, or Development. Within an environment, you manage variables (plain-text values) and secrets (encrypted credentials) that your sensors can reference at execution time.

Environments ensure complete isolation: a sensor linked to Production will never receive a Staging connection string, and vice versa.

You can manage environments from Settings → Environments in the Onagre dashboard.

Getting started

Create an environment

1. Navigate to Settings → Environments.
2. Click Add environment.
3. Enter a name (e.g. Production) and an optional description.
4. Save.

You can create as many environments as your workflow requires.

Default environment

One environment can be marked as the default. When creating a new sensor, the default environment is pre-selected. You can change the default at any time from the environment list.

Link a sensor to an environment

Each sensor is associated with a single environment. Select the target environment when creating or editing a sensor. The sensor will only have access to the variables and secrets of that environment.

What's inside an environment

Each environment contains two types of configuration:

Variables

Non-sensitive, plain-text key-value pairs that can be injected into sensor fields using the ${KEY} syntax.

https://${API_HOST}:${API_PORT}/health

Learn more about Variables →

Secrets

Encrypted credentials — typically connection strings for databases, key-value stores, or message brokers. Secret values are write-only and never displayed after creation.

Learn more about Secrets →

Security

All secrets are encrypted at rest using AES-GCM 256-bit with a two-tier key architecture. Communications with agents are encrypted end-to-end via TLS.

Learn more about Security →

Summary