NoDevserverInSubnet for subnet 172.22.38.0/23 alerts |
|||||
Issue descriptionThis staging alert could be improved. First, it contains this entry: name: NoDevserverInSubnet current value: 0.002824451345755694 Which doesn't make much sense to me. Second, it would be very helpful to know which devservers it thinks exist in the range, and how many devservers it thinks SHOULD exist.
,
Dec 14 2017
Ah.... chromeos3 is not one of our main labs. Maybe we should blacklist it in this (and other devserver related) alerts?
,
Dec 28 2017
I think those are the machines that are always unreachable whenever I run commands across our whole prod fleet. Should we be tracking them in our server database if they are unreachable for us?
,
Dec 28 2017
,
Dec 28 2017
I show the following devservers as online: chromeos3-infra-devserver 172.22.39.161 chromeos3-infra-devserver1 172.22.39.162 chromeos3-infra-devserver2 172.22.39.163 chromeos3-infra-devserver3 172.22.39.164 I think these should be added to the tracking list. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dgarr...@chromium.org
, Dec 14 2017