Logging

Stackpad provides a unified logging pipeline that collects, stores, and searches logs from all your services. Logs are available in real time from the dashboard.

How logging works

Stackpad’s logging pipeline consists of:

1. Collection — Vector runs on every compute node and collects stdout/stderr from all containers
2. Enrichment — logs are tagged with organization, project, service, and deployment metadata
3. Storage — logs are stored in ClickHouse, a high-performance analytics database
4. Query — the dashboard queries ClickHouse for filtered, searchable log views

All components run on European infrastructure — your logs never leave the EU.

Viewing logs

From the dashboard

1. Open your project
2. Click on a service
3. Select the Logs tab

You’ll see a real-time log stream with:

• Timestamp — when the log line was emitted
• Log level — info, warn, error, etc. (if structured)
• Message — the log content

Filtering

Filter logs by:

• Service — view logs from a specific service
• Log level — show only errors, warnings, etc.
• Time range — narrow down to a specific time window
• Full-text search — search for specific text across all log messages

Real-time streaming

The log viewer uses Server-Sent Events (SSE) to stream new log lines as they happen. This is useful for:

• Watching deployment progress
• Debugging errors in real time
• Monitoring application behavior

Build logs

Deployment build logs are stored separately from runtime logs. To view build logs:

1. Go to the Deployments tab
2. Click on a specific deployment
3. Build logs show the full output of the build process

Build logs are useful for debugging:

• Failed builds
• Slow builds
• Missing dependencies

Log retention

Plan	Retention
Starter	7 days
Pro	30 days
Business	90 days

Logs older than the retention period are automatically deleted.

What’s next?

• Git push deploy — understand the deployment pipeline
• Rollbacks — debug failed deployments