Actions
Story #15865
open
[arvados-dispatch-cloud] Cumulative instance time and cost metrics
Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
(Total: 0.00 h)
Story points:
-
Release:
Release relationship:
Auto
Description
From Dispatching containers to cloud VMs
In principle, these metrics can be estimated based on the existing instances_total and instances_price metrics. However:
- (counter) cumulative instance time and cost, partitioned by allocation state and node type
- prometheus doesn't offer an integral function
- updating a cumulative metric after every worker/pool update (i.e., in updateMetrics()) would provide decent accuracy even when prometheus sampling is infrequent/unreliable.
Related issues
Updated by Tom Clegg almost 4 years ago
- Related to Story #13908: [Epic] Replace SLURM for cloud job scheduling/dispatching added
Updated by Tom Clegg almost 4 years ago
example
instance_usage_cost{category="inuse",instance_type="z1.xxl"} 1.234
instance_usage_seconds{category="inuse",instance_type="z1.xxl"} 3600
Updated by Tom Clegg about 3 years ago
- Related to Feature #16636: [arvados-dispatch-cloud] Add instance metrics added
Updated by Tom Clegg over 2 years ago
- Target version changed from Arvados Future Sprints to 2021-04-28 bughunt sprint
- Assigned To set to Tom Clegg
Updated by Peter Amstutz over 2 years ago
- Target version deleted (
2021-04-28 bughunt sprint) - Assigned To deleted (
Tom Clegg)
Actions