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
We need to initialize a template on startup of a Kibana instance. There can be more than 1 instance of Kibana starting close to each other and we will need to query for a check against the existence of it before adding it.
You can see the current template examples like so:
GET /_template
More than likely we should start out with an index named .siem-signals- since that would be similar to the ".ml-anomalies-" template.
See here:
https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-templates.html
We need to initialize a template on startup of a Kibana instance. There can be more than 1 instance of Kibana starting close to each other and we will need to query for a check against the existence of it before adding it.
You can see the current template examples like so:
More than likely we should start out with an index named
.siem-signals-
since that would be similar to the".ml-anomalies-"
template.For the ILM policies see here:
https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-index-lifecycle-management.html
Choose to start:
The text was updated successfully, but these errors were encountered: