Skip to main content
Modules that emit logs have a Logs tab on their page in the dashboard. Logs are queried live from CloudWatch in your AWS account — Ravion never ingests or stores your log data. From the Logs tab you can sort, filter, and select custom time ranges.

​
Log sources

Each entry in the Logs tab is a log source: a CloudWatch log group the module writes to, declared in the module’s definition. A module can have several sources — for example, rvn-aurora shows one per enabled CloudWatch log export type (postgresql for PostgreSQL, or audit, error, general, and slowquery for MySQL). Where standard-library modules send their logs: Log retention is controlled by the module where applicable — for example, rvn-lambda has a log retention days input.

​
Shipping logs elsewhere

The Logs tab doesn’t replace a dedicated log platform — it has no full-text indexing or long-term analytics. ECS modules support FireLens log routing to send app logs to destinations such as Datadog, Splunk, Firehose, OpenSearch, or S3 through a Fluent Bit sidecar. Keep the CloudWatch output enabled alongside external destinations so the Logs tab and Ravion runtime logs continue to work.

​
Querying logs from the CLI

The ravion logs cloudwatch command queries any CloudWatch log group through Ravion’s credential resolution — the same mechanism the dashboard uses — so scripts and agents don’t need their own AWS credentials:
--tail switches to live tail mode after fetching historical logs.
Build and pipeline logs are separate. A build is a pipeline step, not a module log source — use ravion logs pipeline-step <step-execution-id> to stream those.

​
For module authors

Declare log sources in the ui.logs array of your module definition. Each entry has a stable id, a display name, and a CloudWatch source — AWS account, region, log group, and an optional log stream prefix and filter pattern. Every field is templateable, so sources typically reference stack outputs like the created log group name. See UILog in the definition schema.