Logging

DoubleDino writes logs to standard output and standard error. It does not manage log storage or require a separate logging system.

Your deployment environment can collect and manage the logs using its existing tooling.

Log format

Set the output format with DD_LOG_FORMAT.

Default: json

Values: json, text

export DD_LOG_FORMAT=json

JSON is recommended for production because it is easier to collect and process automatically.

Use text for human-readable output during local development or troubleshooting.

Set the logging level with DD_LOG_LEVEL.

Values: info, audit, DPI

export DD_LOG_LEVEL=audit

Basic operational events such as startup, shutdown, connections, and errors.

Operational and security-related events, including query activity, transformations, and important workflow events.

Detailed request-level inspection.

DPI can produce significantly more log output and should normally be enabled only when detailed troubleshooting is required.

DoubleDino writes directly to stdout and stderr. Your infrastructure determines how logs are collected, stored, retained, and accessed.

For example:

# Docker
docker logs doubledino

# systemd
journalctl -u doubledino

# Kubernetes
kubectl logs doubledino

Logs can contain information about requests, queries, and system activity.

Restrict access to logs and apply the same retention and access policies you use for other operational data.

Avoid leaving DPI logging enabled when it is not required.