Environments

App page

Environments are named deployment contexts, for example DEV, QA and Production. Each environment is served by a runtime.

Where to find it

Select Environments in the main menu. An environment's name opens its detail view, for example Environments > Production > Metrics.

What you see

Environment list

• An environment name opens its detail view.
• The runtime column is a summary. The detail view shows which runtime serves the environment.
• When a runtime fails to set up, the environment shows a Provisioning failed badge with the reason, and the detail view shows the same reason.
• Opened from a project, each environment offers Set as Project Environment, which makes it the project's default runtime environment.

Environment detail

The detail view has a header with Edit, Refresh and Delete, the environment's resource figures, and five tabs.

Tab	What it shows
Overview	Counts of projects, variables and caches, the Environment Summary, and the runtime agents that serve the environment.
Metrics	CPU, RAM and storage use of the environment's runtime over time.
Projects	Projects linked to this environment.
Variables	Variables with values for this environment.
Caches	Caches linked to this environment.

Overview

The Environment Summary shows the environment, its runtime, its health, recent activity and when it was last checked (Last probe). For a Dedicated Cloud Agent or a Private Agent it also shows the runtime's Host and Port. A Shared Cloud Agent shows neither.

Below the summary, each runtime agent that serves the environment has its own row with its status and latest heartbeat.

Metrics

The Metrics tab charts the runtime's CPU, RAM and Storage use as a percentage over time.

• Choose a time range: 1h, 6h, 24h or 7d. The default is 24h.
• The line above the charts states the range shown and how many days of history are kept. A range longer than the kept history is unavailable.
• An environment with no runtime linked shows no metrics, and says so.

Use it to see whether a slow or failed run coincided with a busy runtime.

Environment health and heartbeats

The badge on the detail view checks two things, and a runtime must pass both to read Runtime Ready:

• The agent's status is Running.
• The agent has sent a recent heartbeat.

An agent that has never sent a heartbeat reads Runtime Unreachable. A new agent shows this until its first heartbeat arrives, which clears on its own.

In the environment list, an agent that has never reported shows NO HEARTBEAT. One whose last report is over 30 minutes old shows HEARTBEAT STALE, and one between 5 and 30 minutes shows HEARTBEAT SLOW.

Where a heartbeat time is shown and there has never been one, it reads never.

Runtime types

Type	Plans	Where it runs
Shared Cloud Agent	Free	Hosted by DataLug, shared with other accounts
Dedicated Cloud Agent	Professional, Teams, Business	Hosted by DataLug, for your account only
Private Agent	Teams, Business	On your own server. See Private Agent

One agent serves one environment, so the number of agents follows your environment count.

Environments per plan

• Free (30-day trial): 1 environment, on a Shared Cloud Agent.
• Professional: 2 environments.
• Teams: 3 environments.
• Business: 4 environments.

Common tasks

Add an environment

Select Add Environment. Your plan sets how many you can have.

Restart a Dedicated Cloud Agent

Each agent row on the Overview tab has a Restart button when both of the following are true:

• Your role is Admin or Owner. A Builder can edit an environment but cannot restart its runtime.
• The agent is a Dedicated Cloud Agent for your account. A Shared Cloud Agent serves every account on the shared plan and has no Restart button.

Restarting stops the runtime and starts it again. Data pipelines running on it stop, so the button asks for confirmation first.

The row reports one of three outcomes:

• Restart complete. The runtime is starting up. Status returns to running once the runtime reports back.
• Restart failed. Try again. The stop did not go through, so the runtime is still up.
• The runtime is stopped and did not restart. The stop succeeded and the start did not, so the runtime is down. Try again, or contact DataLug support if it stays down.

Delete an environment

Select Delete in the detail view header. Your role must be able to edit environments; a Viewer sees the button disabled.

Deleting asks you to type the environment's name first. It cannot be undone.

What is deleted:

• Variable values set for that environment. The variable itself stays, and so do its values in your other environments.

What is kept:

• Projects. A project is not owned by an environment, so its projects stay.
• Runtime agents. An agent that served the environment stays registered and can be assigned elsewhere.
• Run history and audit records. They stay readable; the deleted environment's name does not resolve on them.

After the delete, the page selects the first remaining environment.

Give a connection different settings per environment

An environment setting on a connection refines the connection's base settings: it replaces the fields it fills in and inherits the rest. A field left blank inherits the base value, at every level of the connection's settings.

To point an environment at something different, give the field a value. A connection setting cannot be made empty for one environment only. See Set up a connection for each environment.

Related

• Connections: per-environment connection settings.
• Jobs: run a data pipeline in a chosen environment.