Deployment events

Deployment activity explains how application versions move from source to production traffic. Most deployment lifecycle detail lives in Deployments, not inside Observability charts.

Use Observability to measure what happened after a deployment became Ready.

What to inspect in Deployments

From the project Deployments view (and CLI inspect), you can typically see:

• Deployment created and status transitions
• Build logs and failure reasons
• Environment (preview or production)
• Source commit and branch
• Promotion and Instant Rollback actions
• Which deployment is Current for production domains

See Deployments, Promote, and Rollback.

Correlate with Observability

After a release:

1. Note the deployment ID and Ready timestamp.
2. Open Observability for a window that starts at that time.
3. Watch error rate, compute, cold starts, and bandwidth.
4. Filter Logs by deployment ID when investigating a regression.
5. Open request Traces for slow or failing examples.

Observability does not currently draw automatic deployment markers on charts. Use the deployment timestamp and filters instead.

Configuration changes

Firewall rules, Attack Mode, and deployment protection can change traffic shape without a new deployment. When investigating a sudden block or challenge spike:

• Check Project settings security controls
• Review Security events
• Confirm the change time against the Observability window

Environment variable changes apply to new deployments via snapshots. See Secrets and Environments.

Related guides

• Request analytics
• Deployments overview
• CLI deployments