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
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.
The text was updated successfully, but these errors were encountered:
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)?
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
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: