Story #15865

[arvados-dispatch-cloud] Cumulative instance time and cost metrics

Added by Tom Clegg over 1 year ago. Updated about 21 hours ago.

Assigned To:
Start date:
Due date:
% Done:


Estimated time:
Story points:


From Dispatching containers to cloud VMs

  • (counter) cumulative instance time and cost, partitioned by allocation state and node type
In principle, these metrics can be estimated based on the existing instances_total and instances_price metrics. However:
  • 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

Related to Arvados - Story #13908: [Epic] Replace SLURM for cloud job scheduling/dispatchingResolved

Related to Arvados - Feature #16636: [arvados-dispatch-cloud] Add instance metricsResolved08/03/2020


#1 Updated by Tom Clegg over 1 year ago

  • Related to Story #13908: [Epic] Replace SLURM for cloud job scheduling/dispatching added

#2 Updated by Tom Clegg over 1 year ago


instance_usage_cost{category="inuse",instance_type="z1.xxl"} 1.234
instance_usage_seconds{category="inuse",instance_type="z1.xxl"} 3600

#3 Updated by Tom Clegg 9 months ago

  • Related to Feature #16636: [arvados-dispatch-cloud] Add instance metrics added

#4 Updated by Tom Clegg about 21 hours ago

  • Target version changed from Arvados Future Sprints to 2021-04-28 bughunt sprint
  • Assigned To set to Tom Clegg

Also available in: Atom PDF