Index: tools/metrics/histograms/histograms.xml |
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
index 701e8de29afd11d50ea865bd94babdb51580a509..79f3015bc814dcb6eefd6ae38c47ad1c56a3d389 100644 |
--- a/tools/metrics/histograms/histograms.xml |
+++ b/tools/metrics/histograms/histograms.xml |
@@ -5404,6 +5404,16 @@ Therefore, the affected-histogram name has to have at least one dot in it. |
</summary> |
</histogram> |
+<histogram name="DomainReliability.UploadCollectorRetryDelay" units="ms"> |
+ <owner>ttuttle@chromium.org</owner> |
+ <summary> |
+ After an upload to a collector finishes (successfully or not), the delay |
+ before the scheduler can send another upload to that collector. (If the |
+ upload was successful, this will probably be 0; if not, it will be based on |
davidben
2015/02/10 19:10:36
Strike the word "probably"? Or are there cases whe
|
+ the BackoffEntry and any Retry-After header received.) |
+ </summary> |
+</histogram> |
+ |
<histogram name="DomainReliability.UploadDuration" units="ms"> |
<owner>ttuttle@chromium.org</owner> |
<summary> |