-
Notifications
You must be signed in to change notification settings - Fork 82
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
disableInternalUsageMetrics has been removed in relay v8 #264
Comments
Hi @husseinsakr , Previously the data collected by the Relay Proxy and sent to LaunchDarkly was only used for internal diagnostic purposes. Because this data wasn’t critical, LaunchDarkly provided a In the near future, this data will have increased importance on the LaunchDarkly platform. As a result, LaunchDarkly removed the option for customers to disable this data’s publication. |
Thank you @cwaldren-ld
How will this effect the launchdarkly relay proxy in offline mode in the future? Specifically your mentioning of "this data will have increased importance on the LaunchDarkly platform". For our fedramp solution, we use the relay proxy in offline mode which today enables |
Offline mode will continue to be supported. In offline mode, the internal usage metrics will not be sent to LaunchDarkly. At this time, the change only affects the default behavior of Relay (not offline), which is to connect to LaunchDarkly for flag data. To be clear, offline mode and |
Thank you @cwaldren-ld ! |
Is your feature request related to a problem? Please describe.
In version 8 of
ld-relay
,disableInternalUsageMetrics
was deprecated. We currently use the launchdarkly relay proxy with it enabled to avoid unnecessary network data sent to launchdarkly. Is it possible to add it back?Describe the solution you'd like
Re-adding
disableInternalUsageMetrics
optionDescribe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: