l4 commitments coverage

l4 commitments coverage answers how exposed you are to on-demand rates: eligible usage sitting on a commitment, over all eligible usage.

l4 commitments coverage [flags]

Every percentage is weighted by the dollars behind it, so a small reservation cannot move the figure as far as a large one.

Coverage is not utilization

The two look similar and answer opposite questions.

	Divides	Answers
Coverage	eligible usage on a commitment, by all eligible usage	how exposed am I to on-demand rates
Utilization	commitment hours used, by commitment hours purchased	am I getting value from what I bought

They have different denominators and are never averaged together. The valuable reading is the mismatch: full utilization alongside low coverage means the commitment is undersized, not that it is performing well, because every eligible dollar above it pays the on-demand rate.

Flags

Flag	Description
`--instrument <i>`	Restrict to `ri` or `sp`. Both when omitted
`--provider <id>`	`aws` or `gcp` (resolved if omitted)

Global flags apply. See CLI overview.

Output

Covered 80.8%   Covered spend $41200.00/mo   Uncovered spend $24800.00/mo

By service
  RI   Amazon Redshift                      95.0%   2026-09-18
  RI   Amazon Relational Database Service   66.6%   2026-09-18
  SP   compute                              54.9%   not measured

The covered and uncovered dollars sit beside the percentage so it names its own denominator. A reservation's row is a service; a plan's row is a plan type, which has no billed service name of its own and so reads as its key.

Measured on is the date the figure was last measured, not today. A commitment sweep runs daily.

What it will not tell you

A sweep that has not run says so, rather than reporting nothing covered:

Coverage is not measured for AWS yet.

Those are opposite answers, and a 0.0% would merge them. The same discipline applies inside the table: see not measured is not zero.

Google Cloud reports a coverage percentage but no covered spend. The only dollar figure stored beside its rate is the commitment fee, and reporting that as covered spend would claim more covered spend than there was bill to cover. The cell reads not measured.

Why this replaced an older number

An earlier coverage read averaged percentages across the commitments in a service, so a hundred dollar reservation moved the figure as far as a fifty thousand dollar one. It also selected one row per commitment held, which meant usage that no commitment covers had no row and could not appear, and that is the larger half of coverage. This command reads a spend-weighted figure with the uncovered side measured.

l4 commitments summary shows the same number, from the same source, so the two cannot disagree about one estate.

Examples

l4 commitments coverage
l4 commitments coverage --instrument sp
l4 commitments coverage --provider gcp
l4 commitments coverage --jq '.data.totals.coverage_pct'

--json prints the untouched payload, which carries two blocks the table leaves out: covered spend per consuming account, and the uncovered on-demand base per service.

l4 commitments: the rest of the group
l4 commitments plan: what buying would cover the uncovered base
l4 commitments utilization: the other half of the pair