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
Data Stream: after putting more thoughts on it, I realized that there is no value added in defining a Data Stream resource as a data stream will be created when data is indexed anyway (the Kibana UI itself does not allows creating the Data Stream in advance). The resource would only enable a kill-switch to delete all data in case the resource is delete, which I believe is not really useful. We should leave the data_stream setting in the index template as is which enables it to be able to create new data streams.
lifecycle_policy setting in Index Template - Indeed would be handy to have that defined as a shortcut for the actual setting, but then why not do the same for the other settings (such as the default ingest pipeline?). I agree which should put more thought on how to improve the resources definition under the UX perspective but I think we should properly revisit this topic in a future version. For now, let's just try to stick with what's there already without introducing new concepts/models. See [DISCUSS]: Revisit index template definition for better UX #6
The
elasticstack_data_*
defines the following:Index Template
https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-template.html
Component Template
https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-template.html#multiple-component-templates
Index Lifecycle Policy
https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-put-lifecycle.html
Snapshot Repository
https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html
The text was updated successfully, but these errors were encountered: