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
Copy file name to clipboardExpand all lines: src/content/docs/radar/concepts/confidence-levels.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ sidebar:
9
9
The `result.meta.confidenceInfo.level` in the response provides an indication of how much confidence Cloudflare has in the data. Confidence levels can be affected either by internal issues affecting data quality or by not having a lot of data for a given location (like Antarctica) or Autonomous System (AS).
|**1**| There is not enough data in this time range and/or for this location or Autonomous System. Data also exhibits an erratic pattern, possibly due to the reasons previously mentioned. |
14
14
|**2**| There is not enough data in this timerange and/or in this location or Autonomous System. |
15
15
|**3**| Data exhibits an erratic pattern but is not affected by known data issues (like pipeline issues). |
|`PERCENTAGE_CHANGE`| Values represent a [percentage change](https://en.wikipedia.org/wiki/Relative_change_and_difference#Percentage_change) from a baseline period. |
19
-
|`MIN_MAX`| Values have been normalized using [min-max](https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_\(min-max_normalization\)). |
20
-
|`MIN0_MAX`| Values have been normalized using min-max, but setting the minimum value to `0`. Equivalent to a proportion of the maximum value in the entire response, scaled between 0 and 1. |
21
-
|`RAW_VALUES`| Values are raw and have not been changed. |
|`PERCENTAGE_CHANGE`| Values represent a [percentage change](https://en.wikipedia.org/wiki/Relative_change_and_difference#Percentage_change) from a baseline period. |
19
+
|`OVERLAPPED_PERCENTAGE`| Values represent percentages that exceed 100% due to overlap. |
20
+
|`MIN_MAX`| Values have been normalized using [min-max](https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_\(min-max_normalization\)). |
21
+
|`MIN0_MAX`| Values have been normalized using min-max, but setting the minimum value to `0`. Equivalent to a proportion of the maximum value in the entire response, scaled between 0 and 1. |
22
+
|`RAW_VALUES`| Values are raw and have not been changed. |
22
23
23
24
If you want to compare values across locations/time ranges/etc., in endpoints that normalize values using min-max, you must do so in the same request. This is done by asking for multiple series. All values will then be normalized using the same minimum and maximum value and can safely be compared against each other. Refer to [Make comparisons](/radar/get-started/making-comparisons/) for more information.
Copy file name to clipboardExpand all lines: src/content/docs/radar/get-started/making-comparisons.mdx
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ The second series has the following parameters:
27
27
28
28
`name=pt_data&dateRange=7d&location=PT`
29
29
30
-
All of these parameters are arrays and it is the position in the array that defines the series the filter belongs to. Refer to [NetFlow's endpoint](/api/resources/radar/subresources/netflows/methods/timeseries/) for more information on the available parameters.
30
+
All of these parameters are arrays, and it is the position in the array that defines the series the filter belongs to. Refer to [NetFlow's endpoint](/api/resources/radar/subresources/netflows/methods/timeseries/) for more information on the available parameters.
31
31
32
32
The response (shortened below for brevity) uses the provided `name` property to wrap the timestamps and corresponding values. If we chart this data, it becomes obvious that Cloudflare received much less traffic from Portugal than from the United States.
33
33
@@ -49,7 +49,8 @@ The response (shortened below for brevity) uses the provided `name` property to
Copy file name to clipboardExpand all lines: src/content/docs/radar/investigate/dns.mdx
+39-15Lines changed: 39 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,13 +25,25 @@ The response shows that most queries come from the United States and Brazil:
25
25
26
26
```json
27
27
{
28
-
"clientCountryAlpha2": "US",
29
-
"clientCountryName": "United States",
30
-
"value": "43.474518"
31
-
}, {
32
-
"clientCountryAlpha2": "BR",
33
-
"clientCountryName": "Brazil",
34
-
"value": "10.772799"
28
+
"success": true,
29
+
"errors": [],
30
+
"result": {
31
+
"top_0": [
32
+
{
33
+
"clientCountryAlpha2": "US",
34
+
"clientCountryName": "United States",
35
+
"value": "43.474518"
36
+
},
37
+
{
38
+
"clientCountryAlpha2": "BR",
39
+
"clientCountryName": "Brazil",
40
+
"value": "10.772799"
41
+
}
42
+
],
43
+
"meta": {
44
+
...
45
+
}
46
+
}
35
47
}
36
48
```
37
49
@@ -46,21 +58,33 @@ Returns the following response:
46
58
47
59
```json
48
60
{
49
-
"clientCountryAlpha2": "RU",
50
-
"clientCountryName": "Russian Federation",
51
-
"value": "73.710495"
52
-
}, {
53
-
"clientCountryAlpha2": "DE",
54
-
"clientCountryName": "Germany",
55
-
"value": "5.518052"
61
+
"success": true,
62
+
"errors": [],
63
+
"result": {
64
+
"top_0": [
65
+
{
66
+
"clientCountryAlpha2": "RU",
67
+
"clientCountryName": "Russian Federation",
68
+
"value": "73.710495"
69
+
},
70
+
{
71
+
"clientCountryAlpha2": "DE",
72
+
"clientCountryName": "Germany",
73
+
"value": "5.518052"
74
+
}
75
+
],
76
+
"meta": {
77
+
...
78
+
}
79
+
}
56
80
}
57
81
```
58
82
59
83
As expected, most queries come from Russia.
60
84
61
85
:::note
62
86
63
-
Note that these examples return the total number of DNS queries from a location to a hostname, *out* of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
87
+
Note that these examples return the total number of DNS queries from a location to a hostname, *out* of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
64
88
:::
65
89
66
90
You can also provide multiple hostnames. Refer to [Get DNS top locations](/api/resources/radar/subresources/dns/subresources/top/methods/locations/) for more information. This is useful when the application you want to explore uses several hostnames to serve its content (like a hostname for the main website, another hostname dedicated to its API, etc.).
0 commit comments