New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 663565 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

grafana devserver_unhealthy graph is broken

Project Member Reported by pprabhu@chromium.org, Nov 9 2016

Issue description

It's hard enough to know what's happening with the devservers.

I'm proposing to not fix this graph. I'll try to move it to viceroy instead.

Assigning to myself as secondary deputy for at least triage.

+akeshet/phobbs: What goes into moving a stat to viceroy? Should I take a stab or does someone have cycles to do this before the end of next week?
 
Find wherever in the code we are emitting that to statsd, and emit something equivalent to monarch as well.

What's the name of your metric? I couldn't find "devserver_unhealthy" in the autotest tree.

Comment 2 by autumn@chromium.org, Nov 15 2016

Labels: -current-issue
Status: WontFix (was: Assigned)
graphana is dead.
Long live viceroy.

Sign in to add a comment