Usage report errors

Causes and remedies for the error codes of usage reports: dates, periods, grouping, format and scope.

`error.usage_bad_date`

Text in the console: A date is not valid. Dates use the form YYYY-MM-DD. Correct the date and try again.
Meaning for API clients: A date is not YYYY-MM-DD.
Code: INVALID_ARGUMENT, HTTP 400

Argument	What it holds
`field`	the request field that holds the rejected date, `from` or `to`.

Cause. A date of the report is not written as YYYY-MM-DD, or is not a real date.

Remedy.

Write the dates as year, month and day with hyphens: kyvernon usage report --from 2026-11-01 --to 2026-11-30.
Dates are in UTC.

Text in the console: The period is not valid. The end must not be before the start and the period may not exceed ten years. Choose another period.
Meaning for API clients: to is before from or the range exceeds ten years.
Code: INVALID_ARGUMENT, HTTP 400

Cause. The end date is before the start date, or the period is longer than ten years.

Remedy.

Choose an end date on or after the start date, and a period of at most ten years. In the console, use From and To.
For a longer history, run several reports and combine them.

Text in the console: The grouping is not supported. Choose virtual machine or tenant.
Meaning for API clients: groupBy is not vm, tenant, resourcePool, folder or host.
Code: INVALID_ARGUMENT, HTTP 400

Cause. The grouping is not one that Kyvernon supports. The API accepts vm, tenant, resourcePool, folder and host.

Remedy.

Use one of the values: kyvernon usage report --from <date> --to <date> --group-by tenant.
In the console, choose a grouping with Group by. The console offers the groupings that it supports.

Text in the console: The breakdown is not supported. Choose total, per month or per day.
Meaning for API clients: period is not day, month or total.
Code: INVALID_ARGUMENT, HTTP 400

Cause. The breakdown is not day, month or total.

Remedy.

Use one of the three values: kyvernon usage report --from <date> --to <date> --period month.
In the console, choose a breakdown with Breakdown.

Text in the console: The export format is not supported. Download the report as CSV.
Meaning for API clients: format is not json or csv.
Code: INVALID_ARGUMENT, HTTP 400

Cause. The export format is not json or csv.

Remedy.

Ask for csv, or leave the format out to get json: kyvernon usage report --from <date> --to <date> --csv.
In the console, use Download CSV.

Text in the console: The scope is not an inventory container. Open a datacenter, folder, cluster, host, datastore or network and try again.
Meaning for API clients: scope is not an inventory container id.
Code: INVALID_ARGUMENT, HTTP 400

Cause. The scope is not the id of an inventory container. A scope restricts the report to the virtual machines inside one container.

Remedy.

Give the id of a datacenter, folder, cluster, host, datastore or network: kyvernon usage report --from <date> --to <date> --scope <id>.
Find the id with kyvernon inventory search <name>.
In the console, open the container first and use the usage view from there.