Skip to content

Update Edge proxy language #3537

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.

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

Merged
merged 2 commits into from
Sep 22, 2022
Merged

Conversation

Jaimal
Copy link
Contributor

@Jaimal Jaimal commented Sep 21, 2022

Updated known limitations for edge proxies, based on https://segment.atlassian.net/browse/DRES-983

  • Encouraged EU customers to switch to regionalized workspaces
  • Asked customers using edge proxies to switch to US api endpoint if preserving client IP addresses in payload is needed

Updated known limitations for edge proxies
@Jaimal Jaimal requested a review from a team as a code owner September 21, 2022 19:26
@Jaimal Jaimal requested review from pwseg and removed request for a team September 21, 2022 19:26
## Known Limitations
- Regional Segment is currently limited to the EU. Future expansion of Regional Segment beyond the EU is under evaluation by Segment Product and R&D.

- Edge proxies have been deprecated. Customers still using edge proxies may have US-based IP addresses show up in event payloads. For EU customers, it is recommended that a Regionalized EU workspace is used instead For non-EU customers, it is recommended that the US-based endpoint (`api.segment.io`) is used to preserve client IP addresses.

Choose a reason for hiding this comment

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

A period "." is missing in this sentence "...EU workspace is used instead. For non-EU customers..."

Choose a reason for hiding this comment

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

Noticed that this document doesnt talk about "Edge proxies", so that might be confusing?

Choose a reason for hiding this comment

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

Maybe we should call it "Data Ingestion Region endpoints"? Also, consider moving this particular limitation under "Regional Data Ingestion" section.

@markzegarelli markzegarelli requested review from markzegarelli and removed request for pwseg September 21, 2022 19:52
@markzegarelli markzegarelli merged commit d867403 into develop Sep 22, 2022
@markzegarelli markzegarelli deleted the update-endpoint-limitations branch September 22, 2022 16:10
@github-actions
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants