Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EU endpoint changes requested from team #6266

Closed
wants to merge 2 commits into from
Closed

EU endpoint changes requested from team #6266

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
87628ce
Update regional-segment.md
cmastr Mar 21, 2024
ae686ad
drafting updates and consolidating bullets
cmastr Apr 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions src/guides/regional-segment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Regional Data Ingestion enables you to send data to Segment from both Device-mod
{% include content/eu-cloud-event-sources.html %}

### Client-side sources
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. Segment's EU instance only supports data ingestion from Dublin, Ireland with the `events.eu1.segmentapis.com/` endpoint. If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `events.eu1.segmentapis.com/v1`.
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. Segment's EU instance only supports data ingestion from Dublin, Ireland with the `in.eu2.segmentapis.com` endpoint. If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `in.eu2.segmentapis.com`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vbatanov & @vinodkone : I'm getting more confused now. 😬

Can you please confirm that we do still run the edge proxies in EU that forward all traffic to US?

Copy link

@vbatanov vbatanov Mar 21, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@erikdw: Yes, we still running edge proxy in EU that forward traffic to US.

Regarding this PR changes

We could have two scenarios :

  1. Client have EU workspace they must use the regional endpoint, which is events.eu1.segmentapis.com
  2. Client have US workspace and but desires to use the EU endpoint, they must use the edge proxy endpoint, which is in.eu2.segmentapis.com

The documentation need to be updated to include both cases

Copy link
Contributor Author

@cmastr cmastr Mar 21, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ohhh I seeee. will need to make some changes to my changes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you know if we still have the APAC edge proxies? I remember we set those up before, but not sure if they ever got used for reals.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we still have them and base on this metrics somebody still use them: https://segment.datadoghq.com/s/A9ih7c/df9-jqx-zpn

And would be better to mention them in this documentation as well:

  1. Client have US workspace and but desires to use the ap-southeast-1 (Singapore) endpoint, they must use the edge proxy endpoint, which is in.ap1.segmentapis.com
  2. Client have US workspace and but desires to use the ap-southeast-2 (Sydney) endpoint, they must use the edge proxy endpoint, which is in.au1.segmentapis.com

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

take a look at changes please and let me know what else might need done.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, does this apply to server side end points or just client side?


> info ""
> For workspaces that use the EU West Data Processing region, the Dublin Ingestion region is preselected for all sources.
Expand All @@ -42,7 +42,7 @@ To set your Data Ingestion Region:
3. Click **Regional Settings**.
4. Choose your **Data Ingestion Region**.
- If you're in the *US West* data processing region, you can select from: Dublin, Singapore, Oregon, and Sydney.
- If you're in the *EU West* data processing region, Segment's EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com/` endpoint.
- If you're in the *EU West* data processing region, Segment's EU instance only supports data ingestion from Dublin with the `in.eu2.segmentapis.com` endpoint.

All regions are configured on a **per-source** basis. You'll need to configure the region for each source separately if you don't want to use the default region.

Expand All @@ -51,15 +51,15 @@ All Segment client-side SDKs read this setting and update themselves automatical
### Server-side and project sources
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:
1. Oregon (Default) — `https://events.segmentapis.com/v1`
2. Dublin — `https://events.eu1.segmentapis.com/`
2. Dublin — `https://in.eu2.segmentapis.com`
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think those examples only for us or eu data processing region not for proxy


> success ""
> If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `events.eu1.segmentapis.com/v1`.
> If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `in.eu2.segmentapis.com`.

Here is an example of how to set the host:

```json
Analytics.Initialize("<YOUR WRITEKEY HERE>", new Config().SetHost("https://events.eu1.segmentapis.com (https://events.eu1.segmentapis.com/)"));
Analytics.Initialize("<YOUR WRITEKEY HERE>", new Config().SetHost("https://events.eu1.segmentapis.com (https://in.eu2.segmentapis.com)"));
```

## Create a new workspace with a different region
Expand Down