---
title: "Component Environments"
description: "Create and configure execution environments for component instances"
source_url: https://ai-ops.com/docs/components/environments
---

# Component Environments

Navigate to **Components > Environments** to manage component execution environments. An environment is an isolated execution context — it defines a scan rate and contains the component instances and wiring that make up your processing logic.

---

## Environment List

The environment list page shows all environments with:

| Column | Description |
|--------|-------------|
| **Status** | Enabled (teal) or Disabled (gray) |
| **Name** | Environment name |
| **Description** | Optional description |
| **Scan Rate** | How often components execute (e.g., every 1 second) |
| **Instances** | Number of component instances in this environment |
| **Created / Updated** | Timestamps |

Click a row to open the environment detail page.

---

## Creating an Environment

1. Click **Add Environment** at the top of the list page
2. Fill in the form:

| Field | Description | Required |
|-------|-------------|----------|
| **Name** | A descriptive name for the environment | Yes |
| **Description** | What this environment does | No |
| **Scan Rate** | Execution interval in seconds (minimum 0.1s) | Yes |
| **Enabled** | Whether the engine should execute this environment | Yes |

3. Click **Create Environment**

You are taken to the environment detail page where you can start adding components on the canvas.

### Choosing a Scan Rate

The scan rate controls how frequently all components in the environment execute. Choose based on your use case:

| Scan Rate | Use Case |
|-----------|----------|
| 0.1–0.5s | Real-time control loops requiring fast response |
| 1s | General-purpose data processing and monitoring |
| 5–30s | Periodic calculations and aggregations |
| 60s+ | Slow-moving processes and batch logic |

> [!TIP] Performance
> A faster scan rate means more frequent execution. If your components take longer to execute than the scan rate allows, the engine will log a warning and skip to the next scheduled cycle. Monitor the **Execution** tab to verify your components complete within the scan window.

---

## Environment Detail

The environment detail page has a header showing the environment name, scan rate, instance count, and an **Enable/Disable** toggle. Below the header are seven tabs:

### Overview

Summary of the environment including its status, scan rate, component count, and key metrics at a glance.

### Canvas

The visual editor where you add component instances, configure them, and wire inputs and outputs. See [Component Canvas](https://ai-ops.com/docs/components/canvas.md) for the full guide.

### Execution

Real-time and historical performance metrics for this environment:

- **Scan Rate** — configured interval
- **Avg Scan Time** — how long each execution cycle takes on average
- **Latest Scan** — when the last cycle completed
- **Component Count** — number of instances in this environment

A chart shows execution time over time. Toggle between **Live** (updates in real time) and **Last Day** (historical view) using the selector above the chart.

Use this tab to verify that your components are executing within the scan rate window and to identify performance bottlenecks.

### Configuration

Edit the environment's general settings:

- **Name** — rename the environment
- **Description** — update the description
- **Scan Rate** — change the execution interval

Click **Save** after making changes.

### Parameters

View and edit runtime parameters for component instances in this environment. Parameters are configuration values defined by the component author that can be adjusted without modifying the component code. Changes take effect on the next scan cycle.

### Cross References

Shows how component instances in this environment connect to external entities (tags, devices, and other environments). Use this tab to understand the environment's dependencies and trace data flow across the system.

### Logs

View real-time logs for individual component instances. The left panel lists all instances in the environment — select one to stream its log output in the right panel.

Logs are color-coded by severity:

| Color | Level |
|-------|-------|
| Red | Error |
| Orange | Warning |
| Default | Info and Debug |

The log terminal auto-scrolls to follow new output. Scroll up to pause, scroll back to the bottom to resume. Click **Clear** to reset the terminal.

---

## Enabling and Disabling

Use the toggle in the environment header to enable or disable the environment:

- **Enabled** — the component engine executes all instances in this environment at the configured scan rate
- **Disabled** — execution stops. Component state is preserved and will resume when re-enabled.

Disabling an environment does not delete any instances or wiring — it simply pauses execution.

---

## Deleting an Environment

Open the environment detail page, click the menu icon, and select **Delete**. This permanently removes the environment and all of its instances, connectors, and wires.

---

## What's Next

- [Component Canvas](https://ai-ops.com/docs/components/canvas.md) — add instances, wire them together, and monitor live values
- [Component Libraries](https://ai-ops.com/docs/components/libraries.md) — upload the component types available on the canvas