---
title: Observe
url: "/docs/monitoring/"
canonical_url: https://docs.blossom88.com/docs/monitoring/
markdown_url: https://docs.blossom88.com/docs/monitoring.md
summary: Inspect application logs, metrics, Containers, health, and Activity
categories:
- observability
- monitoring
- troubleshooting
---

# Observe

Observe explains what an App is doing now and recently. Start from the
Environment or Service you care about, then keep the same resource and time
context while moving between views.

## Logs

Logs are the fastest way to understand a new Release, a restart, or failed
health check. Filter by Environment, Service, Container, stream, and time.

```sh
blossom logs --environment environment-100 --follow
```

Live logs show a recent tail, not a complete archive. During high output,
older lines may be skipped to keep the view responsive and show newer output.

## Metrics

Metrics show application CPU, memory, request, and runtime pressure. Use them
to decide whether to tune an App, change a Service allocation, or adjust its
scaling policy.

## Containers And Health

Containers show the exact runtime instances behind a Service. Health explains
whether the desired replica count is available, starting, replacing, or
blocked.

## Shell

`blossom shell` opens a supported shell in an application Container for
interactive diagnosis or a single command.

## Activity

Activity is the durable history of user and Blossom operations: Deploys,
scaling decisions, recovery, settings changes, and failures. Use it when the
question is “what changed?” rather than “what is the process emitting now?”

```sh
blossom activity:list
blossom activity:show --id activity-100
blossom activity:logs --id activity-100 --follow
```

If the Product reports a provider issue that requires your action, Blossom
includes the relevant cloud provider connection, permission, quota, or billing
evidence.