Skip to main content

Logging

DoubleDino writes logs to standard output and standard error streams.

It does not require a separate logging system.

Your existing infrastructure can collect, store, search, and alert on logs using your preferred tools.

Examples:

  • Docker logs
  • Kubernetes logging
  • systemd journal
  • Cloud provider logging
  • Existing observability platforms

Log format​

DoubleDino supports two output formats.

JSON​

Recommended for production environments.

export DD_LOG_FORMAT=json

Example:

{
  "level": "audit",
  "message": "query completed",
  "duration": 42
}

JSON logs are easier to process with automated systems.

Text​

Human-readable output.

export DD_LOG_FORMAT=text

Useful for:

  • Local testing.
  • Manual troubleshooting.
  • Development environments.

Log level​

The log level controls the amount of operational information produced.

Configure using:

export DD_LOG_LEVEL=audit

Available levels:

info
audit
DPI

info​

Basic operational information.

Useful for:

  • Startup.
  • Shutdown.
  • Connection status.
  • Errors.

Example:

DoubleDino started
Connected to postgres source
HTTP server listening on port 8080

audit​

Recommended for production.

Includes security and operational events.

Useful for:

  • Query activity.
  • Transformation events.
  • Clone progress.
  • Important workflow events.

DPI​

Deep Packet Inspection logging.

Provides detailed request-level information.

Use carefully.

DPI logging can generate significantly more output and should only be enabled when detailed troubleshooting is required.

Collecting logs​

DoubleDino does not manage log storage.

Your deployment environment controls:

  • Where logs are stored.
  • How long logs are retained.
  • Who can access logs.
  • How alerts are created.

Example:

Docker:

docker logs doubledino

systemd:

journalctl -u doubledino

Kubernetes:

kubectl logs doubledino

Security considerations​

Logs may contain operational information about queries, requests, or system activity.

Follow your organisation's logging policies.

Recommended practices:

  • Restrict log access.
  • Use appropriate retention periods.
  • Avoid enabling verbose logging permanently.
  • Review access to audit logs.

Next steps​

Continue with:

  • Troubleshooting for common deployment issues.
  • Developer Guide for using the Proxy API.