nodus get usage
View Markdownnodus get usage
Section titled “nodus get usage”Show metered usage, itemized or summed by project, kind, member, label, meter, day, segment, offering or rank
Synopsis
Section titled “Synopsis”usage lists UsageRecords, or with –group-by sums them into a UsageSummary. Group keys are project, kind,
meter, day, segment (Boot, Running, Restore, Teardown), offering (the capacity it ran on), rank (a gang member),
member (the person who started the work, with any of their keys) and label:
nodus get usage [--group-by KEY,...] [--since 30d] [--until TIME] [-o csv|json|yaml|wide] [flags]Examples
Section titled “Examples” nodus get usage --group-by member --since 30d nodus get usage --group-by project,label:team --since 30d nodus get usage --object job/ddp-2node --group-by rank,segment nodus get usage --group-by day,meter --since 7d -o csv > usage.csvOptions
Section titled “Options” --field-selector string Field selector, such as meter=ComputeSeconds --group-by strings Sum by these keys: project, kind, meter, day, segment, offering, rank, member, label:<key> -h, --help help for usage --no-headers Omit table headers --object string Only the usage of one object, as KIND/NAME -o, --output string Output format: wide, csv, json or yaml --since string Start of the range: a duration back from now (30d, 12h) or a time --until string End of the range (default now)Options inherited from parent commands
Section titled “Options inherited from parent commands” --context string Context from the config file to use --org string Organization (selects the context for that org) -p, --project string Project to work in -v, --verbose Log each API request (never credentials)SEE ALSO
Section titled “SEE ALSO”- nodus get - List or show resources