Issue metadata
Sign in to add a comment
|
Expose ganeti monitoring to the ChromeOS infrastructure team |
||||||||||||||||||||
Issue descriptionDuring a recent outage (see postmortem link in Design-Doc box), an issue occurred that would have been obvious to diagnose as a ganeti issue if we had visibility into the ganeti dashboards. Add a link to the ganeti dashboards to vi/chromeos. Include a brief explanation somewhere useful (on the dashboard?) for how to make use the dashboard. Specifically, it would have been useful to find the broken machine, look it up in http://portal/, find the "Primary Node" associated with it (by looking it up and clicking on it), and then looking it up in ganeti's dashboards. Here's a link to their dashboards: https://viceroy.corp.google.com/managed_storage/Storage%20Virtual%20Machines/ganeti%20msc301/ganeti_msc301_svm03?duration=3d&utc_end=1526943043&volume=ganeti_msc301_svm03_vol27&utm_source=shortn&utm_medium=inorganic&utm_campaign=shortn
,
May 30 2018
,
Jun 11 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by akes...@chromium.org
, May 29 2018Owner: cra...@chromium.org