Commit Graph

17 Commits

Author SHA1 Message Date
12de429ead lint (#276) 2023-03-22 15:01:05 -04:00
b172ca1100 limit journal logic for limits.Agent (#273, #276) 2023-03-22 14:10:07 -04:00
b103195f88 working out the hitches in the limit journals (#273) 2023-03-22 13:09:21 -04:00
d0dd04a141 share limits check owned by limits.Agent now (#277) 2023-03-21 16:34:45 -04:00
79e9f484dc centralized environment limits check (#277) 2023-03-21 16:18:17 -04:00
2ec228c496 basic limits infrastructure for detecting warning and enforcement conditions (#271) 2023-03-21 14:06:23 -04:00
73ef98d7a6 queue-based internal design for limits.Agent (#271) 2023-03-21 13:05:22 -04:00
7360598df5 naming (#271) 2023-03-21 12:38:31 -04:00
40ae2da2c9 better account and environment total efficiency and accuracy; 'bytesRead'/'bytesWritten' -> 'rx'/'tx' (#271) 2023-03-20 15:37:21 -04:00
8bf6875c3f probably not an optimal approach for this flux query, but seems to be working (#271) 2023-03-20 15:05:45 -04:00
96d2f15055 working (but not correct) values for account and environment rx/tx (#271) 2023-03-17 14:04:01 -04:00
df56e49fab flux query influx for duration totals (#271) 2023-03-17 13:51:12 -04:00
9418195150 more limits.Agent elaboration (#271) 2023-03-17 13:13:33 -04:00
192a49fe19 wire in the new 'limits.Agent' infrastructure; extend the 'metrics.Agent' to support additional 'metrics.UsageSink' instances (#271) 2023-03-16 15:05:39 -04:00
858872f861 lint 2023-03-14 14:45:44 -04:00
bc1b42d946 incorporate a separate 'warning' and 'limit' threshold (#235) 2023-03-10 14:32:00 -05:00
83ab21f00c roughed in limits model that incorporates bandwidth limit specs (#235) 2023-03-10 14:25:29 -05:00