Skip to main content
The Metrics page charts what a work item costs, how long it takes, how often a review passes it, and how many items ship. To open it, choose Metrics under the factory in the navigation. You need the View metrics permission. The owner, admin, write and read roles hold it.

The Overview dashboard

The page shows one dashboard, named Overview. It is the same for every factory, and you cannot change it. It has four widgets, and each is a line chart:

Read a widget

  • Choose 24 hours, 7 days, 30 days or 90 days to set how far back the widgets look. The page starts on 7 days and does not save your choice.
  • A widget has one point for each day with at least one item to count. A day with none has no point.
  • The large number above a chart is the average of its points. It is not a total.
  • Hover a point to read its value and how many items it covers, such as mean of 3 items shipped that day.
  • Days follow the time zone of your browser.
An empty widget says why. Every work item shipped in this range has an unpriced session means that items shipped, and none has a known cost.

How cost is counted

OuterLayer prices each session from its token counts and the price of each model the session used. A session’s cost has one of three states:

An item’s cost

An item’s cost is the sum of its confirmed sessions and their subagents. A session counts when its link to the item is confirmed. On the item page, each session’s row in the Activity section shows its cost, how it is linked and whether the link is confirmed. An item’s cost is unknown when one of its confirmed sessions has no price. It is also unknown while a confirmed session’s transcript has not arrived. OuterLayer does not fill the gap with $0.00. A subagent with no price adds nothing. The Agent cost row of the item’s sidebar shows the cost: A row on the Work page shows the same total, or ≥ and the priced part. See What a row shows. For an item built on a managed runner, the row also shows the number of managed builds and their time. A member who can read billing also sees what their overage costs. Session cost and managed build overage are separate amounts. See Managed build-hours.

How the widgets count items

All four widgets read the items on the Work page. They share these rules:
  • An item counts on the day it first shipped. The Work page shows a shipped item as Done.
  • An item that ships again after its issue reopens counts only on its first day.
  • Cost per work item, Time to complete and Throughput count the same items. Cost per work item then leaves out items with an unknown cost, so it can cover fewer items than Throughput.
Quality counts reviewed items only:
  • An item is reviewed when a person approved it or requested changes on it. An item that nobody reviewed is left out.
  • A reviewed item is good when no person ever requested changes. A later approval does not erase a request for changes.
  • A follow-up sent with Send to agent is not a review, so it does not count.
  • The item counts on the day it shipped, or on the day its issue closed with no merged pull request.
See Submit a review.

Next steps

  • Review and merge: read an item’s cost beside its review.
  • Use the MCP server: read model costs, trends and pull request outcomes from an agent. The tools use UTC dates.