1075023 - Cost metrics data

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Chris AtLee [:catlee]]

We need to present our ongoing cost on the KPI dashboard.

Let's focus on AWS cost initially, and report this both as gross cost, as cost per push, and cost per CPU-hour ran on AWS.

Comment 1

[Chris Cooper [:coop] (he/him)]

IIRC kmoir did some work on cost-per-push earlier in the year.

Comment 2

[Chris Cooper [:coop] (he/him)]

(In reply to Chris Cooper [:coop] from comment #1)
> IIRC kmoir did some work on cost-per-push earlier in the year.

If nothing else, kmoir also gathers the monthly push stats. Even getting that automated as part of the dashboard would be a win.

Comment 3

[Kim Moir [:kmoir] ET]

I look at the number of pushes per month when I write the monthly blogpost.  On our internal docs, I take the AWS bill and divide by #pushes to get a cost per push. This is not accurate because it doesn't include the costs for our on premise infrastructure.  I agree that having this automatically generated would be a win because now it takes me about 1hr to do.  But it has not been a priority to automate.  fyi, here's the current process

https://wiki.mozilla.org/User:Armenzg/Data

Comment 4

[Chris Cooper [:coop] (he/him)]

(In reply to Kim Moir [:kmoir] from comment #3)
> I look at the number of pushes per month when I write the monthly blogpost. 
> On our internal docs, I take the AWS bill and divide by #pushes to get a
> cost per push. This is not accurate because it doesn't include the costs for
> our on premise infrastructure.  I agree that having this automatically
> generated would be a win because now it takes me about 1hr to do.  But it
> has not been a priority to automate.  fyi, here's the current process
> 
> https://wiki.mozilla.org/User:Armenzg/Data

We're not looking at anything more sophisticated for the first pass. A static cost that can be filled in with data taken directly from Amazon in the future will suffice.