Observe and recover

Deployment health

deliberate status
deliberate components list --env production
deliberate deployments list --env production

The Environment canvas shows the same deployed topology. Select a Component or Blueprint node for its health and operational controls.

Logs and metrics

deliberate logs --env production --component app
deliberate metrics --env production --component app

Use exec only when observation is insufficient:

deliberate exec --env production --component app -- sh

Images and vulnerabilities

The platform scans images pushed to the deliberate. registry and refreshes the results as its vulnerability database changes. Inspect the status and severity summary for an image, then open the package-level findings when needed:

deliberate images list --project hello-java
deliberate images vulns hello-java:1.0.0

The detailed report names the affected package, installed version, severity, and available fixed version. A newly pushed image may report that scanning is still in progress.

Alerts

Alert policy belongs in desired state so it follows the resource and Environment. The console edits the same operational policy for a deployed Blueprint. Use deliberate alerts events to inspect history and deliberate alerts silence for a bounded operational silence.

Backups and recovery

Managed database tier controls its protection posture. Durable volumes declare their backup policy. Creating a backup, restoring data, and rolling back a deployment are explicit runtime actions because they describe an event rather than desired state.

deliberate databases backup postgres --env production
deliberate deployments rollback --env production <revision>