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.

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

Lazy + changeable site/region selection #1090

Open
hirschbp opened this issue Oct 17, 2022 · 2 comments
Open

Lazy + changeable site/region selection #1090

hirschbp opened this issue Oct 17, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@hirschbp
Copy link

Is your feature request related to a problem? Please describe.
We have the case that the region/site is not known on app launch but selected by the user later. A user might even log out and into a different account which could mean a switch of regions during app runtime. Currently the library does only support setting the site during initialization and does not support changing it afterwards.

Describe the solution you'd like

  • The library should offer a lazy setting of the site during initialization while already caching logs (e.g. similar to TrackingConsent.PENDING).
  • The site should be changeable during runtime (switch to different site or back to pending).

Describe alternatives you've considered

  • The library does not offer a public reset function (Datadog.stop() is internal only)
  • The only working but very ugly solution we came up with at the moment is to force the user to re-launch the app in order to switch the site.
@hirschbp hirschbp added the enhancement New feature or request label Oct 17, 2022
@0xnm
Copy link
Member

0xnm commented Oct 18, 2022

Hello @hirschbp! Thanks for the feature suggestion.

To better understand the priority of this feature, can you please tell us what is the reasoning behind changing the Datadog region when switching user accounts: is it some multi-branding application or this need is related to some legal regulations (like data storage in US vs EU region), or maybe something else (like different backends for different accounts)?

@hirschbp
Copy link
Author

It is related to legal regulations, exactly as you mentioned: data storage in US vs EU region.

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

No branches or pull requests

2 participants