You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users viewing a usage report should recognize where that usage happened. This means differentiating between usage for different workspace classes (which are metered at different rates), as well as separating usage of workspaces like prebuilds, from regular workspaces.
The text was updated successfully, but these errors were encountered:
In #11043, we've added configuration to price different classes differently. The remaining work is to expose the WorkspaceType in the results. To do this, we'll need to join WorkspaceInstances with Workspaces.
We'll need to something like the following query to get the:
SELECT wsi.id, wsi.creationTime, wsi.startedTime, wsi.stoppedTime, wsi.usageAttributionId, ws.projectId, ws.type
FROM d_b_workspace_instance AS wsi
LEFT JOIN d_b_workspace AS ws
ON wsi.workspaceId = ws.id
LIMIT 100;
Users viewing a usage report should recognize where that usage happened. This means differentiating between usage for different workspace classes (which are metered at different rates), as well as separating usage of workspaces like prebuilds, from regular workspaces.
The text was updated successfully, but these errors were encountered: