Monitor Environment Status

Monitor environment (collection) status and deployment information in Bluebricks. Each environment listed by bricks collection ls represents a collection in the platform.

Prerequisites

• Bluebricks CLI installed

• Authenticated with Bluebricks (bricks login)

• Existing environments (collections)

Environment Status Information

Status Display

The bricks collection ls command shows comprehensive environment information:

GUID                                NAME           CLOUD PROVIDER   CLOUD ACCOUNT   SLUG              STATUS
----------------------------------- -------------- ---------------- --------------- ----------------- -------------------------
env-uuid-123                        production    AWS              aws-prod        production        DEFAULT, web-app (running)
env-uuid-456                        development   AWS              aws-dev         development       api-service (completed)
env-uuid-789                        staging       GCP              gcp-staging     staging           INACTIVE

Status Fields

GUID

• Environment unique identifier

• Used for API operations

• Required for some commands

NAME

• Environment display name

• Set during creation

• Human-readable identifier

CLOUD PROVIDER

• Connected cloud provider (AWS, GCP, Azure)

• Shows - if no cloud account connected

• Indicates where deployments run

CLOUD ACCOUNT

• Connected cloud account name

• Shows - if no cloud account connected

• Links to specific cloud credentials

SLUG

• Environment slug for commands

• Used in deployment commands

• Short identifier for CLI operations

STATUS

• Environment status indicators

• Latest deployment information

• Special flags (DEFAULT, INACTIVE)

Status Indicators

Environment Flags

• DEFAULT: Environment is set as default

• INACTIVE: Environment is disabled

• No flags: Environment is active and ready

Deployment Information

• Latest deployment name: Most recent deployment

• Deployment stage: Current stage (running, completed, failed)

• No deployment: No deployments in environment

Monitoring Commands

Basic Status Check

# Check all active environments
bricks collection ls

# Check all environments (including inactive)
bricks collection ls --all

Environment Details

# List environments with full details
bricks collection ls --all

Status Examples

Active Environment

GUID                                NAME           CLOUD PROVIDER   CLOUD ACCOUNT   SLUG              STATUS
----------------------------------- -------------- ---------------- --------------- ----------------- -------------------------
env-uuid-123                        production    AWS              aws-prod        production        DEFAULT, web-app (running)

Inactive Environment

GUID                                NAME           CLOUD PROVIDER   CLOUD ACCOUNT   SLUG              STATUS
----------------------------------- -------------- ---------------- --------------- ----------------- -------------------------
env-uuid-789                        staging       GCP              gcp-staging     staging           INACTIVE

Environment with No Deployments

GUID                                NAME           CLOUD PROVIDER   CLOUD ACCOUNT   SLUG              STATUS
----------------------------------- -------------- ---------------- --------------- ----------------- -------------------------
env-uuid-456                        development   AWS              aws-dev         development       -

Status Monitoring

Regular Monitoring

# Check environment status regularly
bricks collection ls

# Monitor all environments
bricks collection ls --all

Deployment Tracking

# Check deployment status
bricks collection ls

# Monitor deployment progress
bricks collection ls

Environment Health

# Check environment connectivity
bricks collection ls

# Verify cloud account status
bricks collection ls

Best Practices

Regular Checks

• Check collection status regularly

• Monitor deployment progress

• Verify cloud account connectivity

Status Interpretation

• Understand status indicators

• Monitor deployment stages

• Check for inactive collections

Troubleshooting

• Use status information for debugging

• Check collection connectivity

• Verify cloud account status

See also

• Collections -- collection concepts, policies, and best practices

• Environment Management -- enable, disable, and delete environments

• Deployment Status Monitoring -- track individual deployment progress