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: pages/cockpit/faq.mdx
+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
@@ -42,11 +42,11 @@ Cockpit stores Scaleway data in the same region as the Scaleway resource that pr
42
42
43
43
### Custom data
44
44
45
-
In order for Cockpit to store you custom data, you must first [create a custom data source](/cockpit/how-to/create-external-data-sources/) in a region of your choice. The data you send will then be stored in that custom data source’s region and will not be replicated across other regions.
45
+
In order for Cockpit to store your custom data, you must first [create a custom data source](/cockpit/how-to/create-external-data-sources/) in a region of your choice. The data you send will then be stored in that custom data source’s region and not replicated across other regions.
46
46
47
47
Even though data is region-bound, your Cockpit Grafana instance can query and visualize data across all regions where you have data sources.
48
48
49
-
If you are using Scaleway’s preconfigured dashboards in Grafana, make sure you have selected the region of the resource you want to monitor using the drop-down at the top of the dashboard. This filters the dashboards to only show data from the matching regional data-source.
49
+
If you are using Scaleway’s preconfigured dashboards in Grafana, make sure you have selected the region of the resource you want to monitor using the drop-down at the top of the dashboard. This filters the dashboards to only show data from the matching regional datasource.
50
50
51
51
## How am I billed for using Cockpit with my Scaleway data?
0 commit comments