Skip to main content
Modules with the metrics capability display charts on their page in the dashboard, so you can check a service’s health without leaving Ravion or building CloudWatch dashboards by hand. Metrics are queried live from CloudWatch in your AWS account — Ravion never ingests or stores your metric data. Responses are cached for a short time to minimize your CloudWatch API costs.

What each module shows

The module’s definition determines which charts appear, so every instance of a module gets a relevant dashboard with zero setup. Some examples from the standard library: Each module’s catalog page documents its charts precisely, usually in an Observability section. Charts are for at-a-glance health. For alerting, several modules — such as rvn-rds and rvn-elasticache — can also create CloudWatch alarms through their inputs; see the module’s catalog page.

Querying metrics from the CLI

The ravion metrics cloudwatch command queries any CloudWatch metric through Ravion’s credential resolution — the same mechanism the dashboard charts use — so scripts and agents don’t need their own AWS credentials:
It isn’t limited to the metrics a module’s dashboard shows — any namespace, metric, and dimension set in the account works.

For module authors

Declare charts in the ui.metrics array of your module definition. Each entry has a stable id, a display name, a chart type (line or bar), and a CloudWatch source — namespace, metric name, statistic, dimensions, region, and AWS account. Every field is templateable, so sources typically reference stack outputs like the ECS service name or target group. The aggregation period is chosen by the requester, not the definition. See UIMetric in the definition schema.