-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Telemetry opt-in setting #22144
Comments
Technically, |
Could this be generalized to config and admin config? I expect there's a few others, like xpack:defaultAdminEmail. |
We might need this long-term, but the difference between this setting and the |
Also, we could technically leave telemetry alone and allow users to opt into it "per space", even though the stats that would be reported would be for all spaces. |
I'm all for this proposal, but let's manage it from xpack_main rather than monitoring. |
The Spaces plugin will be making the Advanced UI Settings space-aware. There are a couple of UI Settings that do not make sense to be space-specific, such as
telemetry:optIn
. The decision to enable telemetry should be made for the entire Kibana instance, rather than for each individual space within the instance.Instead of supporting one-off cases for specific configuration settings like this one, we are proposing that we remove the
telemetry:optIn
setting from theconfig
document in favor of a dedicated document in the.kibana
index which tracks the telemetry opt-in preference.Given this, we propose the following:
telemetry:optIn
preference (if set) to the dedicated 'telemetry' documentSince the
monitoring
xpack-main
plugin writes the current telemetry settings, we propose making these changes within themonitoring
xpack_main
plugin, with the understanding that a dedicatedtelemetry
plugin may be created in the future.@kobelb @tsullivan @pickypg
The text was updated successfully, but these errors were encountered: