Remove investigation of UMA chirp alerts from network triage documentation.

Bug: 840992
Change-Id: I0f11538f3c91371e7a0e18085ae79ade6a8d2a2d
Reviewed-on: https://chromium-review.googlesource.com/1053362
Commit-Queue: Eric Roman <eroman@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557588}

net/docs/bug-triage-suggested-workflow.md

@@ -29,24 +29,6 @@
 
 * If non-network causes also seem possible, attach those components as well.
 
-## Investigate UMA notifications
-
-For each alert that fires, determine if it's a real alert and file a bug if so.
-
-* Don't file if the alert is coincident with a major volume change.  The volume
-  at a particular date can be determined by hovering the mouse over the
-  appropriate location on the alert line.
-
-* Don't file if the alert is on a graph with very low volume (< ~200 data
-  points); it's probably noise, and we probably don't care even if it isn't.
-
-* Don't file if the graph is really noisy (but eyeball it to decide if there is
-  an underlying important shift under the noise).
-
-* Don't file if the alert is in the "Known Ignorable" list:
-    * SimpleCache on Windows
-    * DiskCache on Android.
-
 ## Investigating component=Internals>Network bugs
 
 * Note that you may want to investigate Needs-Feedback bugs first, as

net/docs/bug-triage.md

@@ -8,7 +8,6 @@ label seems suitable.
 
 ### Required, in rough order of priority:
 * Identify new network bugs on the tracker.
-* Investigate UMA notifications.
 * Investigate recent Internals>Network issues with no subcomponent.
 * Follow up on Needs-Feedback issues for all network components.
 * Identify and file bugs for significant new crashers.
@@ -33,8 +32,8 @@ uniform, predictable two day commitment for all triagers.
 * Identify new network bugs on the bug tracker, looking at [this issue tracker
   query](https://bugs.chromium.org/p/chromium/issues/list?q=status%3Aunconfirmed&sort=-id&num=1000).
 
-  * All Unconfirmed issues filed during your triage rotation should be scanned,
-    and, for suspected network bugs, a network component assigned and a
+  * All Unconfirmed issues filed during your triage rotation should be scanned
+    for suspected network bugs, a network component assigned and a
     chrome://net-export/ log requested.  Suggested text: "Please collect and
     attach a chrome://net-export log. Instructions can be found here:
     https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details".
@@ -45,24 +44,6 @@ uniform, predictable two day commitment for all triagers.
     3:00 pm EST of the last day of the previous triager's rotation until the
     same time on the last day of their rotation.
 
-* Investigate UMA notifications.
-
-    * UMA notifications ("chirps") are alerts based on UMA histograms that are
-      sent to   chrome-network-debugging@google.com.  Triagers should subscribe
-      to this list.  When an alert fires, the triager should determine if the
-      alert looks to be real and file a bug with the appropriate label if so.
-      Note that if no label more specific than Internals>Network is
-      appropriate, the responsibility remains with the triager to continue
-      investigating the bug, as above.
-
-    * The triager is responsible for looking at any notification previous
-      triagers did not, so when an issue is investigated, the person who did
-      so should respond to chrome-network-debugging@google.com with a short
-      email, describing their conclusions.  Future triagers can then use the
-      fact an alert was responded to as an indicator of which of them need
-      to be followed up on.  Alerts fired before the beginning of the
-      previous triager's rotation may be ignored.
-
 * Investigate [Unconfirmed / Untriaged Internals>Network issues that don't belong to a more specific network component](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DInternals%3ENetwork+status%3AUnconfirmed,Untriaged+-label:Needs-Feedback&sort=-modified),
   prioritizing the most recent issues, ones with the most responsive reporters,
   and major crashers.  This will generally take up the majority of your time as