Logs
Review the log streams Devpilot records for your workspace, including deployment hook output, webhook delivery logs, and login history.
Devpilot does not operate a centralized server log shipper. Instead, it records the specific log streams it produces itself: deployment hook output, inbound webhook deliveries, and the login history for your account. These are the logs you can read directly from the dashboard.
Deployment hook logs
Every deployment runs a series of hooks (for example build steps, restart scripts, or custom commands). For each hook Devpilot stores:
| Field | Description |
|---|---|
| Stage | The deployment stage the hook belongs to. |
| Action type | The kind of action the hook performed. |
| Name | A human-readable label for the hook. |
| Run as | The user the command ran as on the server. |
| Status | The final status returned by the runner. |
| Exit code | The process exit code. |
| Message | A short status message. |
| Response | The short response body (if any). |
| Output | The full captured stdout/stderr. |
| Duration | How long the hook ran, in milliseconds. |
| Started at / completed at | Timestamps bracketing the hook execution. |
To view hook output, open a deployment and expand the hook entry you are interested in. Hooks flagged with show_user = false are hidden from the default view; change the filter to show all hooks to reveal them.
Deployment hook output is the closest thing Devpilot stores to a traditional application log. If you need richer log search, ship logs from inside your app to an external service (Logtail, Datadog, CloudWatch, your own ELK) via the server's standard logging stack.
Webhook delivery logs
Every webhook Devpilot dispatches or receives is recorded in the hook log stream. Open Integrations > Webhooks inside a workspace to see recent deliveries.
Each webhook log entry stores:
- The source of the webhook (for example server analytics).
- The event name (for example metrics update).
- The full URL the request was sent to.
- The request headers, content, and raw body.
- The response body returned by the receiver.
- The status (for example Processed or Failed).
- The configured delay and number of retries attempted, along with the most recent retry time.
- The time the delivery completed.
Click any webhook log entry to expand it. You can see the exact headers, payload, and response body so you can compare what Devpilot sent with what your receiver expected.
Failed deliveries are retried automatically up to the configured retry count. The latest-retry timestamp shows the most recent retry, and the status changes to Processed once a retry succeeds.
Login history
Your account keeps a record of every login attempt. Open your profile settings to see the login history.
Each entry records:
- The IP address used.
- Location (with longitude and latitude when available).
- Device type, device name, browser and version, operating system and version, and the raw user agent.
- The session and token identifiers.
- Whether it was a new device for your account.
- Whether the attempt was successful — and if not, the failure reason.
If you see a login from a location or device you do not recognise, change your password and review your 2FA settings immediately. Devpilot sends a notification when a login comes from a new device or new location.
Filtering
Hook output and webhook logs support filtering by:
- Date range — pick a start and end time.
- Status — narrow to failed deliveries or non-zero exit codes.
- Source / stage — narrow to a single webhook source or deployment stage.
- Text search — search across message, output, and response fields.
What Devpilot does not store
To avoid confusion, Devpilot does not currently provide:
- A centralized system log aggregator across servers (no
nginx/php-fpm/systemdlog collection). - A "live tail" stream of raw server logs in the UI.
- Long-term log retention tied to your subscription plan.
If you need those capabilities, forward logs from your server to a dedicated log service.
Related pages
- Activity logs — the audit trail of user and system actions.
- Deployment failure patterns — recurring deployment failures grouped by category.
- Quota alerts — notifications when your workspace approaches plan limits.