Skip to content

Commit bbf9d91

Browse files
stayseesongstayseesong
committed
formatted the integrations table and added to the regional segment page
1 parent 2dc4006 commit bbf9d91

File tree

3 files changed

+132
-8
lines changed

3 files changed

+132
-8
lines changed

‎src/_includes/content/regional-integrations-table.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
{% assign source = site.data.regional.regions %}
2+
3+
4+
<input class="table-search" type="text" id="filterInput" onkeyup="searchFilter()" placeholder="Search for an integration..">
5+
<div class="button-container" id="btnContainer">
6+
<a href="#" id="all" class="button button-link active">All</a>
7+
{% for category in source %}
8+
<a href="#" id="{{category.category | slugify}}" class="button button-link">{{category.category | capitalize}}</a>
9+
{% endfor %}
10+
</div>
11+
12+
13+
<table id="settingsTable">
14+
<thead>
15+
<tr>
16+
<th>Integration</th>
17+
<th style="text-align:center">US West Support</th>
18+
<th style="text-align:center">EU West Support</th>
19+
</tr>
20+
</thead>
21+
<tbody>
22+
{% for category in source %}
23+
<tr class="settingRow {{category.category | slugify }}">
24+
<td colspan="3" style="font-weight: bold; background-color:fafbff;font-size: 10px; text-transform: uppercase;" id="settingRow">
25+
{{category.category}}</td>
26+
</tr>
27+
{% for integration in category.integrations %}
28+
<tr
29+
class="settingRow {{category.category | slugify}}" id="settingRow">
30+
<td>{{integration.name}}</td>
31+
<td style="text-align:center">{% if integration.us_west %}✅{% else %}⬜️{% endif %}</td>
32+
<td style="text-align:center">{% if integration.eu_west %}✅{% else %}⬜️{% endif %}</td>
33+
</tr>
34+
{% endfor %}
35+
{% endfor %}
36+
</tbody>
37+
</table>
38+
39+
<script>
40+
41+
function searchFilter() {
42+
var input, filter, table, tr, td, i, txtValue;
43+
44+
input = document.getElementById("filterInput");
45+
filter = input.value.toUpperCase();
46+
table = document.getElementById("settingsTable");
47+
tr = document.getElementsByClassName("settingRow");
48+
for (i = 0; i < tr.length; i++) {
49+
td = tr[i].getElementsByTagName("td")[0];
50+
if (td) {
51+
txtValue = td.textContent || td.innerText;
52+
if (txtValue.toUpperCase().indexOf(filter) > -1) {
53+
tr[i].style.display = "";
54+
} else {
55+
tr[i].style.display = "none"
56+
}
57+
}
58+
}
59+
}
60+
</script>

‎src/connections/regional-segment-eu.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: Regional Segment (Europe)
3+
hidden: true
4+
---
5+
{% include content/plan-grid.md name="data-residency" %}
6+
7+
8+
9+
10+
Segment provides regional infrastructure across Europe, Middle East, Africa and Asia Pacific with [rate limits and SLA](/docs/connections/rate-limits/).
11+
12+
As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces ingest, store, process and deliver locally within the EU. You can set up workspaces in the EU where data is received via the Dublin, Ireland endpoint hosted in the EU for all sources, with the exception of [cloud object sources](/docs/connections/sources/#object-cloud-sources) and cloud event sources that aren't supported. Segment-hosted archives hosted in S3 AWS Dublin, Ireland, process, filter, validate, deduplicate, and archive data for EU workspaces.
13+
14+
> info ""
15+
> Regional Segment for Europe is currently in beta. Segment’s [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature.
16+
17+
## Create a new workspace with a different region
18+
To create a workspace with a different data processing region:
19+
1. Log in to your segment account.
20+
2. Click **New Workspace**.
21+
3. Select your **Data processing region**. This determines the location in which Segment collects, processes, and stores data that’s sent to and from your workspace. You can choose from *US West* or *EU Central*.
22+
4. Click **Create workspace**.
23+
24+
> info ""
25+
> Once you create a workspace with a specified data processing region, you can't change the region. You must create a new workspace to change the region.
26+
27+
## Regional Data Ingestion
28+
Regional Data Ingestion enables you to send data to Segment from both Device-mode and Cloud-mode sources through regionally hosted API ingest points. The regional infrastructure can fail across locations within a region, but never across regions.
29+
30+
Segment's EU instance only supports data ingestion from Dublin, Ireland through the `in.eu2.segmentapis.com/v1` endpoint.
31+
32+
### Set your Data Ingestion Region
33+
To set your Data Ingestion Region:
34+
1. Go to your source.
35+
2. Select the **Settings** tab.
36+
3. Click **Regional Settings**.
37+
4. Choose your **Data Ingestion Region**.
38+
* If you’re in the US region, you can select from: Dublin, Singapore, Oregon, and Sydney.
39+
* Segment’s EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com` endpoint.
40+
41+
### Client-side sources
42+
You can configure Segment’s client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you’ve updated the Data Ingestion Region in that source’s settings.
43+
44+
All regions are configured on a per-source basis. Configure the region for each source separately if you don't want to use the default region.
45+
46+
> info ""
47+
> Dublin is the only region for EU instances and defaults automatically.
48+
49+
All Segment client-side SDKs read this setting and update themselves automatically to send data to new endpoints when the app reloads. You don't need to change the code when you switch regions.
50+
51+
### Server-side and project sources
52+
When you send data from a server-side or project source, you can use the `host` configuration parameter to send data to the desired region, which will be Dublin — `in.eu2.segmentapis.com/v1`
53+
54+
## Regional Data Storage
55+
[Regional Data Storage](/docs/connections/data-residency/#regional-data-storage) isn't supported in EU workspaces.
56+
57+
## EU Updates
58+
### Data Lakes
59+
Regional Segment in the EU changes the way you [configure the Data Lakes AWS environment](/docs/connections/storage/data-lakes/data-lakes-manual-setup/#iam-role).
60+
61+
### Warehouse Public IP Range
62+
Use Segment's custom CIDR `3.251.148.96/29` while authorizing Segment to write in to your Redshift or Postgres port. [BigQuery](/docs/connections/storage/catalog/bigquery/#getting-started) doesn't require you to allow a custom IP address.
63+
64+
## Supported Integrations
65+
66+
{% include content/regional-integrations-table.md %}

‎src/utils/regional-table.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,24 +17,22 @@ title: Regional Segment Integrations
1717
<thead>
1818
<tr>
1919
<th>Integration</th>
20-
<th>Slug</th>
21-
<th>US West Support</th>
22-
<th>EU West</th>
20+
<th style="text-align:center">US West Support</th>
21+
<th style="text-align:center">EU West Support</th>
2322
</tr>
2423
</thead>
2524
<tbody>
2625
{% for category in source %}
2726
<tr class="settingRow {{category.category | slugify }}">
28-
<td colspan="4" style="font-weight: bold; background-color:fafbff;font-size: 10px; text-transform: uppercase;" id="settingRow">
27+
<td colspan="3" style="font-weight: bold; background-color:fafbff;font-size: 10px; text-transform: uppercase;" id="settingRow">
2928
{{category.category}}</td>
3029
</tr>
3130
{% for integration in category.integrations %}
3231
<tr
3332
class="settingRow {{category.category | slugify}}" id="settingRow">
3433
<td>{{integration.name}}</td>
35-
<td><code>{{integration.slug}}</code></td>
36-
<td>{{integration.us_west}}</td>
37-
<td>{{integration.eu_west}}</td>
34+
<td style="text-align:center">{% if integration.us_west %}✅{% else %}⬜️{% endif %}</td>
35+
<td style="text-align:center">{% if integration.eu_west %}✅{% else %}⬜️{% endif %}</td>
3836
</tr>
3937
{% endfor %}
4038
{% endfor %}
@@ -62,4 +60,4 @@ function searchFilter() {
6260
}
6361
}
6462
}
65-
</script>
63+
</script>

0 commit comments

Comments
 (0)