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
* Release connection on error
* Remove dates from user group information
* Ensure uniquely keyed entries when double-counting group costs
* Remove date range from user group query in tests
Copy file name to clipboardExpand all lines: docs/topics/cost-calculations.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,10 @@ The proportional usage described above does not take into account the underutili
44
44
45
45
Group-level costs are calculated by aggregating the user-level costs for all users within a group. Each entry in the [`/costs-per-user`](#id-costs-per-user) endpoint includes a `usergroup` key that indicates the group which the user belongs.
46
46
47
+
:::{note}
48
+
Only user group memberships from the most recent dates are considered. Historical user group memberships incur a heavy performance penalty.
49
+
:::
50
+
47
51
There are a few extra endpoints provided by the cost monitoring application to help track user group costs.
Process the response from the Prometheus server to extract user group information.
267
+
Process the response from the Prometheus server to extract user group information. Note that only the most recent date of user group membership is used.
0 commit comments