493759 - Set up talos dashboard

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Chris AtLee [:catlee]]

Johnath's dashboard needs to be given a new home.  I've ported his code over to use the same data that my regression analysis is using.

This needs to be set up on a new VM, and then have results pushed somewhere publicly accessible.

Comment 1

[Aki Sasaki (not active)]

I suspect if Alice/Catlee were actively doing this, they'd have grabbed the bug.
Plus, waiting on VM.
-> future.

Comment 2

[Johnathan Nightingale [:johnath]]

This probably shouldn't be future, since it's blocking the new graph server deployment, as I understand it.  catlee would know more, though.

Comment 3

[Chris AtLee [:catlee]]

This is set up now at http://graphs-new.mozilla.org/dashboard

Comment 4

[Johnathan Nightingale [:johnath]]

As I've said before - this is great to see, thanks Chris.

My one concern is that the mobile data is absent from these graphs, I think because it isn't sent to the new graph server the way the other trees are? I can't really shut down my dashboard or redirect to this one if it removes reporting that the mobile team depends on - should we file a follow-up bug for that work, or is it something that will start to "just work" once graphs-new becomes graphs?

That one concern aside though - woot woot!

Comment 5

[Chris AtLee [:catlee]]

(In reply to comment #4)
> As I've said before - this is great to see, thanks Chris.
> 
> My one concern is that the mobile data is absent from these graphs, I think
> because it isn't sent to the new graph server the way the other trees are? I
> can't really shut down my dashboard or redirect to this one if it removes
> reporting that the mobile team depends on - should we file a follow-up bug for
> that work, or is it something that will start to "just work" once graphs-new
> becomes graphs?

There is already a bug for this: #487335.

Comment 6

[Johnathan Nightingale [:johnath]]

(In reply to comment #5)
> There is already a bug for this: bug 487335.

Well that's just wonderful, then!

Comment 7

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

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.