Ceph » mgr » Dashboard

Lenz Grimmer wrote:

display a sample report of the data that is sent to telemetry.ceph.com.

I'm wondering if we want to display the whole report in the dashboard or rather want to show a download button (or even both).

I'm also wondering where we want to display the sample report and if Cluster -> Manager modules -> telemetry might be a good place for it. Or if it's too less prominent.
A second idea would be to have a separate dashboard widget for the telemetry plugin to guide the user through the configuration and also to show a download button for the sample report.

I like option 2 with the widget.

Alternatively another idea would be to display a dialog after the first dialog which allows the user to enable the telemetry options and shows an example (which must not be the one from the current system). This solution can be easily implemented via Angular route guard :-) I know, another one, but this is a great solution to implement such behavior. The only challange is to store a flag that can be used to remember that the dialog has been displayed already.

Volker Theile wrote:

I like option 2 with the widget.

Alternatively another idea would be to display a dialog after the first dialog which allows the user to enable the telemetry options and shows an example (which must not be the one from the current system). This solution can be easily implemented via Angular route guard :-) I know, another one, but this is a great solution to implement such behavior.

I'm not really sure what you mean by 'after the first dialog'. Or do you mean 'after the first login'? - In that case the dialog would only be shown once per user, right? - But what if the admin wants to see the sample report at a later point?

The only challange is to store a flag that can be used to remember that the dialog has been displayed already.

And that's not the only challenge as it's a system wide setting. Imagine the following: The admin logs in for the first time -> Does not enable the Telemetry plugin -> Creates another admin user. The second admin logs in and might enable the Telemetry plugin although the first admin decided against it?

I don't think this should be a per user setting. Maybe we can add a general dashboard setting "ask_for_telemetry_enablement" (or something similar) which is true until an admin passed the configuration dialog (either enabled the plugin or not). I'm wondering if it would be possible to reset the setting (to true) after each major update.

Oh right, seems to be more complex than it looks.

I just learned via #44320 that it's possible to configure a HTTP Proxy for sending these outgoing HTTPS requests. I think it would make sense to allow the user to change this setting in this workflow as well (maybe as an "advanced option")?