Skip to main content

Overview

View and stream logs from any service — application, container, database, or job — running on Qovery.

Commands

Stream Logs

Stream real-time logs:
qovery log
Stream logs for a specific service (regardless of its type):
qovery log --service "httpbin"
Stream logs for a specific application:
qovery log --application "my-api"
Stream logs in raw JSON format:
qovery log --service "httpbin" --raw

Options

FlagShortDescription
--organizationOrganization Name
--projectProject Name
--environmentEnvironment Name
--service-sService name — tries application, container, database, and job APIs until a match is found
--service-idService UUID — directly stream logs by ID, skips name lookup (use with IDs from console URLs)
--application-aApplication Name
--container-nContainer Name
--database-dDatabase Name
--job-jJob Name
--raw-rDisplay logs in raw format (json)
--helpShow help

Examples

Stream Logs by Service Name

# Stream logs — works for any service type
qovery log --service "httpbin"

# Stream logs for a specific application
qovery log --application "my-api"

# Stream logs for a specific database
qovery log --database "postgres-main"

# Stream logs for a specific job
qovery log --job "backup-job"

Use Service ID from Console URL

When you have a Qovery console URL, you can use the service ID directly:
# Extract the ID from a URL like:
# .../service/2c69dfd4-1c5a-44c3-ac65-8c6399cfbf31/service-logs
qovery log --service-id "2c69dfd4-1c5a-44c3-ac65-8c6399cfbf31"

Raw Log Output

# Display logs as raw JSON
qovery log --service "my-api" --raw

Specify Context Explicitly

# Provide full context to skip interactive prompts
qovery log \
  --organization "My Org" \
  --project "Backend" \
  --environment "production" \
  --service "my-api"

Tips

Use --service-id with the UUID from your Qovery console URL to stream logs without needing to know the service name. The ID is visible in the URL when you navigate to a service in the console.
Use --service when you don’t know (or don’t want to specify) the type of your service. Qovery will try each API (application, container, database, job) until it finds a match. Use a specific flag (--application, --database, etc.) if you want to target a precise service type.
Use --raw / -r to get logs in JSON format, which is useful for piping output to tools like jq for further processing.