elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.65k stars 8.23k forks source link

[SLM] Confusing relationship between selecting system indices and dis/enabling "Include global state" #110678

Open cjcenizal opened 3 years ago

cjcenizal commented 3 years ago

Problem

Users have reported confusion when they select specific indices, leave "Include global state" enabled, and then see their SLM policy capturing more indices than the ones they selected.

image

Suggested solutions

Off the top of my head, we can make this behavior clearer by adding a notification to the Index-selection section. When the user selects specific indices and also has "Include global state" selected, we can show an informational callout that lets the user know that system indices will also be captured as a result, even if they user hasn't selected them.

I think it makes more sense to show the notification here than in the "Include global state" section, because this is the section the user will be interacting with when acting on the intention to only capture specific indices. So this is the context where this warning will contradict the user's intentions most directly, creating the most meaning for the user.

We can also enhance the "Include global state" description to make the behavior of this setting clearer:

Stores the global cluster state and system indices as part of the snapshot. This will capture all system indices in addition to any specific indices that have been selected for capture.

elasticmachine commented 3 years ago

Pinging @elastic/kibana-stack-management (Team:Stack Management)

cjcenizal commented 3 years ago

Relates to https://github.com/elastic/kibana/issues/71244 somewhat.

yuliacech commented 2 years ago

When https://github.com/elastic/elasticsearch/issues/82671 is completed we need to remove "system indices" from the copy of "Data streams and indices" field. Backing up system indices should be configured via "feature states" (see https://github.com/elastic/kibana/issues/120314).

elasticmachine commented 2 months ago

Pinging @elastic/kibana-management (Team:Kibana Management)