Observability

Alien gives you two separate views of a deployment:

deployment state   release, rollout, health, last check-in, resources
logs               application, system, AI Gateway, Encryption Gateway

Start with deployment state. Move to logs when you know which deployment or request path needs inspection.

Check deployment state

# All deployments in the linked project
alien status

# One deployment
alien status acme/production

# Stable output for an agent or script
alien status acme/production --json

For a safe resource summary without resource configuration or secrets:

alien deployments resources acme/production --json

For machine-based deployments:

alien deployments machines acme/production --json

Search application logs

alien logs --deployment acme/production --since 1h
alien logs --deployment acme/production --follow
alien logs --deployment acme/production --level error --json

alien logs hides Alien system records by default. Add --system when you are debugging the platform components themselves.

Application log bodies remain application log bodies. Alien can detect common structured severity fields without replacing the body with a nested message or msg field. See Structured log severity.

Search gateway diagnostics

Gateway diagnostics are routing and outcome metadata. They do not contain AI prompts, AI responses, encryption plaintext, or ciphertext.

alien logs --source ai-gateway \
  --status provider-error \
  --since 24h

alien logs --source encryption-gateway \
  --operation decrypt \
  --status failed

Send telemetry elsewhere

Self-hosted managers can forward telemetry through their configured OpenTelemetry pipeline. The exact logs, metrics, and traces available depend on the workload and exporter configuration; do not assume that a managed cloud service exposes a portable metric unless its resource page documents it.

See Self-hosting configuration for exporter settings.