You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Replaced the description of two synth metrics with text from an engineer that was verified as accurate. I rewrote the description to ensure it was consistent with the text we have for other metric descriptions.
Copy file name to clipboardExpand all lines: synthetics/api-test/api-test-metrics.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,9 +108,9 @@ Each occurrence of a test from a particular device and location at a specific ti
108
108
109
109
* - Uptime
110
110
- ``synthetics.run.uptime.percent``
111
-
- The percentage of non-failed test runs. Uptime is calculated by taking the average score of all runs in the selected time frame, where a successful run receives a score of 100 and a failure receives a score of 0.
111
+
- The uptime of a test run: the value will be 0 if the test run failed and 100 if it succeeded.
112
112
113
113
* - Downtime
114
114
- ``synthetics.run.downtime.percent``
115
-
- The percentage of failed runs within the selected time frame. Downtime is calculated by taking the average score of all runs in the selected time frame, where a failed run receives a score of 100 and a successful run receives a score of 0.
115
+
- The downtime of a test run: The value will be 100 if the test run failed and 0 if it succeeded.
0 commit comments