lightsout report
Show where a plan's hours and money went: every level of the run down to each harness process, with its time, tokens and cost.
lightsout report
When to reach for it
Reach for it after planning a ticket, when you want to know which step burned the hours, how many harness processes it took and what it cost. It reads what the plan commands recorded, so it spends nothing and can be run as often as you like. Name a ticket folder rather than one plan to see what the whole ticket cost.
How to run it
lightsout report| flag | meaning | left out |
|---|---|---|
| --plan <name> | The plan to report on — a plan address, a legacy plan folder name, or a ticket folder, which reports every plan under it beneath one totalled ticket row. | required |
| --json | Print the same totalled tree as data instead of the table, so a chart and this table read one calculation. | The table is printed. |
| --cwd <path> | Repository whose plan folders are read. | The process working directory. |